How do architectural differences between Modbus RTU and DLMS/COSEM shape protocol selection in IoT gateways?
-
️ Technical Redaction & Safe Harbor Warning:
Industrial IoT deployment topologies have been sanitized.When designing multi-protocol energy management gateways, engineers interface both industrial sensors (PLC, variable frequency drives using Modbus RTU/TCP) and revenue meters (DLMS/COSEM IEC 62056-53 Clause 6.2) reading
1.0.1.8.0.255.
What are the fundamental architectural tradeoffs between Modbus and DLMS in latency, payload overhead, and data integrity? -
Here is the engineering trade-off comparison matrix per Blue Book Chapter 4:
Metric Modbus RTU / TCP DLMS / COSEM (IEC 62056) Primary Domain Real-time millisecond industrial control Legal metrology, billing, asset lifecycle Polling Latency 10~50 ms deterministic cycle 100~500 ms (session & encryption overhead) Data Modeling Flat 16-bit registers (Coils, Holding) Object-oriented (62 COSEM interface classes) Header Overhead 8 bytes request, 5 bytes response 30~80 bytes (HDLC/Wrapper + xDLMS APDU) Security & Audit None natively (plain text) AES-GCM-128/256, GMAC, non-volatile $IC$ Self-Description None (requires external manual) Native (OBIS code, unit enum, scaler) PLCs stick with Modbus because industrial closed-loop control demands deterministic millisecond polling cycles that cannot tolerate cryptographic handshake latency.
-
However, in legal metrology and revenue billing, Modbus is completely unsuitable due to security vulnerabilities:
Any rogue device on an unencrypted RS-485 bus can broadcast function code0x06to modify register values or reset billing registers.
In contrast, DLMS COSEM Class 70 (Disconnect Control0.0.96.3.10.255) and Class 22 (Single Action Schedule0.0.15.0.0.255) require authenticated HLS 5 association with digital signatures and Invocation Counter anti-replay protection per Green Book Section 8.4. -
In our edge gateways, we adopt a decoupled architecture:
Modbus RTU runs on south-bound industrial loops, and the gateway maps Modbus holding registers into virtual DLMS COSEM objects for north-bound grid dispatch.
Parsing DLMS request bytes:C0 01 C1 00 03 01 00 01 08 00 FF 02 00ensures secure, standardized metrology reporting upstream per IEC 62056-53 Clause 6.2.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login