Difficulty reading meter Serial number

By ambimat , 3 March, 2022

Forums

Hello,

We are able to read the meter serial number of our meter and see it on the DLMS director (See screenshot attached) but when we go through the log we cannot see the serial number.

If the serial number is 3956611 what is the exact data that we should search in the log file?

Image

Hi,

Meter serial number can be octet-string, UInt32 and sometimes it's a string. Find 0.0.96.1.0.255 and check what the meter is replying to.

BR,
Mikko

Hi Mikko,

There are three instances of the matching serial number OBIS code but we cannot figure out the actual serial number from the response.

Can you please help?

Instance 1

7E A0 13 03 41 36 B0 27 E6 E6 00 C0 02 C1 00 00 00 02 CA 8C 7E

7E A8 89 41 03 92 C7 6A E6 E7 00 C4 02 C1 00 00 00 00 03 00 82 01 C7 02 04 12 00 01 11 00 09 06 00 00 5E 5B 0C FF 02 02 01 02 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 01 00 FF 02 02 01 02 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 01 01 FF 02 02 01 02 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 01 00 02 04 12 00 01 11 00 09 93 0C 7E
Duration: 223

Instance 2
Reading object 0.0.94.91.10.255, interface ProfileGeneric
7E A0 19 03 41 38 60 12 E6 E6 00 C0 01 C1 00 07 00 00 5E 5B 0A FF 03 00 58 06 7E
Get profile generic columns...
7E A0 19 03 41 38 60 12 E6 E6 00 C0 01 C1 00 07 00 00 5E 5B 0A FF 03 00 58 06 7E

7E A8 89 41 03 B2 C5 4B E6 E7 00 C4 01 C1 00 01 09 02 04 12 00 01 09 06 00 00 60 01 00 FF 0F 02 12 00 00 02 04 12 00 01 09 06 00 00 60 01 01 FF 0F 02 12 00 00 02 04 12 00 01 09 06 01 00 00 02 00 FF 0F 02 12 00 00 02 04 12 00 01 09 06 00 00 5E 5B 09 FF 0F 02 12 00 00 02 04 12 00 01 09 06 00 00 5E 5B 0B FF 0F 02 12 00 00 02 04 12 00 01 09 06 00 00 5E 5B 0C FF 0F 02 12 00 00 02 04 12 00 01 09 06 01 00 00 04 05 41 7E
Duration: 219

Instance 3

7E A0 19 03 41 98 6A B7 E6 E6 00 C0 01 C1 00 01 00 00 60 01 00 FF 02 00 89 A0 7E

7E A0 15 41 03 B8 44 C7 E6 E7 00 C4 01 C1 00 06 00 3C 5F 83 DC DD 7E

Hi,

You are reading the profile generic object. You will find the location of the serial number from the capture objects (Attribute index #3).
https://www.gurux.fi/Gurux.DLMS.Objects.GXDLMSProfileGeneric

BR,
Mikko

Hello,

We are trying to understand the log for the OBIS 0x00 0x00 0x60 0x01 0x00 0xFF and for two different meters we are getting these two logs

For a Premier 300 from Secure meters when we only try to request for the Serial number we get the following string back

CMD: 7E A0 19 03 41 32 3A BD E6 E6 00 C0 01 C1 00 01 00 00 60 01 00 FF 02 00 89 A0 7E

RESPONSE: 7E A0 1A 41 03 52 E9 3D E6 E7 00 C4 01 C1 00 09 08 53 36 32 32 34 38 37 33 C7 CA 7E

Here we know that the Serial number is 8 bytes long and that is S6224873 but when we run the command on the HPL meter (using Indian Standard) we get the following response:

CMD: 7E A0 19 03 41 58 66 71 E6 E6 00 C0 01 C1 00 01 00 00 60 01 00 FF 02 00 89 A0 7E

RESPONSE: 7E A0 15 41 03 B4 28 0D E6 E7 00 C4 01 C1 00 06 00 0B 16 AF 67 AD 7E

This means that we are getting an 'unsigned integer (06)' and the data field has 0 bytes. But then there is a random byte string '0B 16 AF 67' and the serial number of the meter is 726703

Once the connection is done and we are able to read the meter we cleared the log and only requested for the serial number and it 'magically' (I am sure it isn't magic) appeared on the DLMS Director.

Can you please help us to understand how did you translate/convert '0x0B 0x16 0xAF 0x67' to 726703?

Thanks

Ambimat