DLMS / COSEM Online Tools
Local-First Dissector Online engineering tools for DLMS/COSEM, including protocol analysis, OBIS decoding, security inspection and IEC 62056 troubleshooting utilities.DLMS / COSEM Protocol Analyzer
Assembles 12-byte IV from System Title (8B) + Frame Counter (4B) to verify 96-bit GMAC Auth Tag and decrypt via WebCrypto.
Parsed protocol fields, OBIS attributes, and values will appear here.
DLMS / COSEM Protocol Standards & Specifications
Complete architectural breakdown of supported IEC 62056 standards and client-side cryptographic capabilities.
Client-Side AES-GCM Decryption
100% offline WebCrypto AES-GCM-128 (Security Suite 1) decryption. Computes 12-byte IV from 8-byte System Title and 4-byte Frame Counter (Invocation Counter). Authenticates 96-bit GMAC Auth Tag without server exfiltration.
HDLC & TCP-Wrapper Framing
Parses IEC 62056-46 HDLC Type 3 framing (SNRM, UA, DISC, DM, I-Frame, RR, FRMR) with dual CRC-16 (HCS/FCS) calculations and IEC 62056-47 TCP/UDP port 4059 wrapper headers.
COSEM APDU & OBIS Trees
Hierarchical AST parser for xDLMS APDUs (AARQ, AARE, GET, SET, ACTION, Data-Notification) mapping 6-group OBIS codes (IEC 62056-61) and interface class attributes (IEC 62056-62).
Frequently Asked Questions (FAQ)
Common engineering questions regarding DLMS/COSEM framing, APDU parsing, and AES-GCM decryption.
How does the client-side AES-GCM decryption work without uploading keys?
Sharur uses standard browser WebCrypto APIs to perform AES-GCM-128 (Security Suite 1) decryption directly in local browser memory. The 12-byte Initialization Vector (IV) is assembled from the 8-byte System Title and 4-byte Frame Counter (Invocation Counter). Your keys, system title, and meter packets never leave your machine.
Which IEC 62056 standards are supported by this analyzer?
Sharur supports IEC 62056-21 (Optical Mode E), IEC 62056-46 (HDLC Data Link Layer with CRC-16 HCS/FCS), IEC 62056-47 (TCP/UDP 4059 Transport Wrapper), IEC 62056-53 (COSEM APDUs: AARQ, AARE, GET, SET, ACTION, Data-Notification), IEC 62056-61 (OBIS Object Identification System), and IEC 62056-62 (COSEM Interface Classes).
What is the difference between Logical Name (LN) and Short Name (SN) referencing?
Logical Name (LN) referencing uses 6-byte OBIS codes (e.g. 1.0.1.8.0.255) to address meter objects directly, specified in Application Context 2.16.756.5.8.1.1 or 2.16.756.5.8.1.2. Short Name (SN) referencing maps object attributes to 2-byte 16-bit integer offsets, defined in Application Context 2.16.756.5.8.1.3.
How do I ask for help or share captured traces safely with the community?
After dissecting a frame, click 'Ask in Community (with Redaction)'. The workbench automatically generates a sanitized Markdown summary that replaces sensitive meter identifiers and keys with placeholders, ensuring your production telemetry remains private.
Post Question to Community
The snippet below has been sanitized. Key fields and addresses are preserved in structured markdown ready to ask for help on Sharur.