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 DLMS/COSEM
Overview
dc3-driver-dlms is the DLMS/COSEM protocol driver of the IoT DC3 platform. It is intended to read COSEM object
attributes from energy meters and similar devices over TCP or serial transports, using the Gurux DLMS library to build
and decode DLMS frames.
⚠️ Work in progress. This driver is a skeleton — its class documentation explicitly states "Protocol-level I/O is not yet fully implemented" and the method bodies carry TODO markers. The Gurux client generates DLMS frames, but the transport send/receive is not implemented:
read()returns anullvalue,write()returnstrueunconditionally,health()only checks whether a client object is cached (no real connectivity probe), andgetConnector()does not establish a TCP/serial connection or HDLC handshake. Treat it as a starting template, not a production-ready driver.
Module Information
- Group ID: io.github.pnoker
- Artifact ID: dc3-driver-dlms
- Driver Name: DLMS/COSEM Driver
Driver Attributes (Device-level)
| Attribute | Description |
|---|---|
| Transport Type | Transport type (TCP, SERIAL) |
| Host | Remote device address (TCP mode) |
| Port | Remote device port (TCP mode) |
| Serial Port | Serial port path (SERIAL mode) |
| Baud Rate | Baud rate (SERIAL mode) |
| Client Address | DLMS client address (public client = 16) |
| Server Address | DLMS server address |
| Authentication | Authentication method (NONE, LOW, HIGH) |
| Password | Authentication password |
Point Attributes
| Attribute | Description |
|---|---|
| Object Type | DLMS object type (REGISTER, CLOCK, DATA, etc.) |
| Logical Name | Object logical name / OBIS code (e.g. 1.0.1.8.0.255) |
| Attribute ID | Attribute ID (2 = Present Value) |
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
A reachable DLMS/COSEM device (or simulator) over TCP (default port 4059) or serial, plus the matching client/ server addresses and authentication settings.
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-dlms -am package
java -jar dc3-driver/dc3-driver-dlms/target/dc3-driver-dlms.jar
Testing
Run the module tests from the repository root:
mvn -s .mvn/settings.xml -pl dc3-driver/dc3-driver-dlms -am test
Related Modules
dc3-common-driver— Driver SDK for registration, scheduling, and RabbitMQ integration