DLMS/COSEM Error Codes & Exception Responses Comprehensive Analysis

[elena_rostova]

Decoding DLMS/COSEM Data-Access-Result and Confirmed-Service-Error Codes

When a GET, SET, or ACTION fails, the meter returns a numeric error code. Here is the definitive reference:

Code	Data-Access-Result	Root Cause & Resolution
0	success	Operation completed successfully
1	hardware-fault	Memory or peripheral communication failure in meter
2	temporary-failure	Meter is busy (e.g. executing flash write or billing calculation)
3	read-write-denied	Insufficient permissions in current Association LN
4	object-undefined	Requested OBIS code does not exist in meter firmware
9	object-class-inconsistent	Class ID in request does not match device model
11	type-unmatched	Data type in SET request differs from attribute specification
12	scope-of-access-violated	Selective access range or entry exceeds valid buffer bounds
13	data-block-unavailable	Block transfer index requested is out of range

Use this lookup matrix to automate error handling in your HES drivers!

[marcus_vance]

For code 2 (temporary-failure), our HES implements an exponential backoff retry (1s, 2s, 4s). For code 3 (read-write-denied), it immediately triggers an association privilege alert.

[david_miller]

For code 11 (type-unmatched), always double check whether the attribute expects an octet-string vs visible-string. Passing ASCII text as raw visible-string when octet-string is required is a frequent source of type mismatch.