mirror of
https://gitee.com/pnoker/iot-dc3.git
synced 2026-10-31 10:11:49 +08:00
pnoker
dc2164f46e
a live-stack sweep of all 36 drivers surfaced five sdk-level defects that left reads dead or the whole fleet unbootable: - drop the empty spring.main stub in the shared driver profile; the boot 4.1 binder rejects null-valued keys and every driver died at startup with a bind exception - rename the schedule enable flag to enable to match what every driver application.yml actually spells; with the old enabled key the read and custom quartz jobs were silently never scheduled - treat proto3 zero-versions as unset when reconciling registration so a driver restart re-registers instead of failing the optimistic lock with 'driver version conflict' - ignore the driver's own registration event that can be consumed before applymetadata finishes instead of logging an error - initialize jdbc/serial connection maps eagerly: the registration event handler invalidates pools and nped on a lazy-null map - ble: exclude the guava 18 pin dragged in by bluetooth-manager - kafka: use the starter (boot 4 split autoconfigurations out of the bare jar) and read the compose-provided bootstrap variable - lwm2m: pin californium to the 3.x api leshan m14 needs and configure an explicit coap endpoint - mqtt: replace the orphaned spring-integration gateway with a paho publisher so the send path exists again - boot sweep result: 36/36 drivers start, 0 errors
DC3 Driver OPC DA
Overview
dc3-driver-opc-da is the OPC DA (Data Access) protocol driver of the IoT DC3 platform. It connects to OPC DA servers
using DCOM/J-Interop to read real-time process data from OPC-compliant industrial devices and SCADA systems.
Work in progress. Protocol-level I/O is not fully implemented in
OpcDaDriverCustomServiceImpl. Treat this module as an integration skeleton, not a production-ready OPC DA driver, until its read/write TODOs are completed and verified against a real server.
Module Information
- Group ID: io.github.pnoker
- Artifact ID: dc3-driver-opc-da
- Driver Name: OPC DA Driver
Driver Attributes (Device-level)
| Attribute | Description |
|---|---|
| Host | OPC DA server hostname or IP |
| CLSID | OPC server CLSID (COM class identifier) |
| Username | Windows DCOM authentication username |
| Password | Windows DCOM authentication password |
Point Attributes
| Attribute | Description |
|---|---|
| Group | OPC DA item group name |
| Tag | OPC DA item tag name |
The module application.yml is authoritative for attribute codes, types, default values, scheduling, health, and local
buffering. Keep this README aligned when those user-facing settings change.
Prerequisites
- An OPC DA server running on a Windows host accessible via DCOM
- DCOM permissions configured to allow remote access from the driver host
- OPC DA specification: OPC DA 2.0 / 3.0
Running Locally
1. Start Infrastructure and Center Services
make up-db
make up-dev GROUP=core
2. Build and Run
mvn -s .mvn/settings.xml -pl dc3-driver/dc3-driver-opc-da -am package
java -jar dc3-driver/dc3-driver-opc-da/target/dc3-driver-opc-da.jar
Testing
Run the module tests from the repository root:
mvn -s .mvn/settings.xml -pl dc3-driver/dc3-driver-opc-da -am test
Related Modules
dc3-common-driver— Driver SDK for registration, scheduling, and RabbitMQ integration