It's a string as byte array if transport_service is TCP/IP. Like this:
10.10.109.178:4059
As Hex:
31 30 2E 31 30 2E 31 30 39 2E 31 37 38 3A 34 30 35 39
By the way is there any documented example in any of the specification document as for interoperability every product has to do same encoding and decoding.
That is defined on IDIS, but it's not defined on DLMS standard or India standards.
This is just what most of the meters are using, but there might be meters that are using own custom solutions here.
Hi,
Hi,
It's a string as byte array if transport_service is TCP/IP. Like this:
10.10.109.178:4059
As Hex:
31 30 2E 31 30 2E 31 30 39 2E 31 37 38 3A 34 30 35 39
BR,
Mikko
Thanks Mikko for the prompt
Thanks Mikko for the prompt response.
By the way is there any documented example in any of the specification document as for interoperability every product has to do same encoding and decoding.
Thanks in Advance
Hi,
Hi,
That is defined on IDIS, but it's not defined on DLMS standard or India standards.
This is just what most of the meters are using, but there might be meters that are using own custom solutions here.
BR,
Mikko