Hello,
reading association view is terminated by error message:
Failed to receive reply from the device in given time.
As i remember from distant past this function never was reliable. The meter type is Landis&Gyr E550, client id = 80 (Level 4). When I analyze logs i see that reading is terminated on this packet (please see last three packets):
[08:53:04:332] Written data (COM20)
7e a0 36 03 a1 b6 25 ab 08 01 ff 03 00 00 03 01 ~ 6.ˇ¶%«..˙.....
01 01 08 02 ff 03 00 00 03 01 01 01 08 03 ff 03 ....˙.........˙.
00 00 03 01 01 05 08 01 ff 03 00 00 03 01 01 05 ........˙.......
08 02 ff 03 00 72 58 7e ..˙..rX~
[08:53:04:410] Read data (COM20)
7e a8 4f a1 03 9a 6d 9f e6 e7 00 c4 03 c1 0a 00 ~¨Oˇ.šmźćç.Ä.Á..
02 02 0f 00 16 ff 00 02 02 0f 00 16 ff 00 02 02 .....˙......˙...
0f 00 16 ff 00 02 02 0f 00 16 ff 00 02 02 0f 00 ...˙......˙.....
16 ff 00 02 02 0f ff 16 1e 00 02 02 0f ff 16 1e .˙....˙......˙..
00 02 02 0f ff 16 1e 00 02 02 0f ff 16 20 36 52 ....˙......˙. 6R
7e ~
[08:53:04:623] Written data (COM20)
7e a0 19 03 a1 7c d9 ff e6 e6 00 c0 01 c1 00 07 ~ ..ˇ|Ů˙ćć.Ŕ.Á..
01 00 63 62 00 ff 03 00 f3 2c 7e ..cb.˙..ó,~
[08:53:09:644] Written data (COM20)
7e a0 19 03 a1 7c d9 ff e6 e6 00 c0 01 c1 00 07 ~ ..ˇ|Ů˙ćć.Ŕ.Á..
01 00 63 62 00 ff 03 00 f3 2c 7e ..cb.˙..ó,~
[08:53:14:707] Written data (COM20)
7e a0 19 03 a1 7c d9 ff e6 e6 00 c0 01 c1 00 07 ~ ..ˇ|Ů˙ćć.Ŕ.Á..
01 00 63 62 00 ff 03 00 f3 2c 7e ..cb.˙..ó,~
After parsing:
│ └──DLMS_PDU[192] {** getRequest **}
│ └──GetRequest[1] {** Get-request-normal **}
│ └──GetRequestNormal Sequence
│ ├──InvokeIdPriority
│ │ ├──InvokeID (0..3): 1
│ │ ├──ServiceClass (6): confirmed
│ │ └──Priority (7): high
│ ├──CosemAttributeDescriptor Sequence {** Cosem-Attribute-Descriptor **}
│ │ ├──CosemClassID = 7 (0x0007) {** Cosem-Class-Id **}
│ │ ├──CosemObjectInstanceID[6] = 1.0.99.98.0.255 {** Cosem-Object-Instance-Id **}
│ │ └──CosemObjectAttributeID = 3 {** Cosem-Object-Attribute-Id **}
│ └──Optional Flag = False {** Access-Selection **}
I have no problem reading load profile from my application as can be seen here:
[09:08:31:561] Written data (COM20)
7e a0 19 03 a1 54 93 52 e6 e6 00 c0 01 c1 00 07 ~ ..ˇT“Rćć.Ŕ.Á..
01 00 63 62 00 ff 03 00 f3 2c 7e ..cb.˙..ó,~
[09:08:31:670] Read data (COM20)
7e a8 5a a1 03 74 eb 3c e6 e7 00 c4 01 c1 00 01 ~¨Zˇ.të<ćç.Ä.Á..
05 02 04 12 00 08 09 06 00 00 01 00 00 ff 0f 02 .............˙..
12 00 00 02 04 12 00 03 09 06 00 00 60 f0 0c ff ............`đ.˙
0f 02 12 00 00 02 04 12 00 03 09 06 00 00 60 f0 ..............`đ
0c ff 0f 0c 12 00 00 02 04 12 00 03 09 06 00 00 .˙..............
60 f0 0c ff 0f 13 12 00 00 6d c2 7e `đ.˙.....mÂ~
[09:08:31:889] Written data (COM20)
7e a0 07 03 a1 71 df 49 7e ~ ..ˇqßI~
[09:08:32:108] Read data (COM20)
7e a0 1b a1 03 76 d5 4f 02 04 12 00 03 09 06 00 ~ .ˇ.vŐO........
00 61 61 00 ff 0f 02 12 00 00 68 d2 7e .aa.˙.....hŇ~
After parsing:
--- Packet 5 ---
DLMS_PDU[192] {** getRequest **}
└──GetRequest[1] {** Get-request-normal **}
└──GetRequestNormal Sequence
├──InvokeIdPriority
│ ├──InvokeID (0..3): 1
│ ├──ServiceClass (6): confirmed
│ └──Priority (7): high
├──CosemAttributeDescriptor Sequence {** Cosem-Attribute-Descriptor **}
│ ├──CosemClassID = 7 (0x0007) {** Cosem-Class-Id **}
│ ├──CosemObjectInstanceID[6] = 1.0.99.98.0.255 {** Cosem-Object-Instance-Id **}
│ └──CosemObjectAttributeID = 3 {** Cosem-Object-Attribute-Id **}
└──Optional Flag = False {** Access-Selection **}
--- Packet 6 ---
DLMS_PDU[196] {** GetResponse **}
└──GetResponse[1] {** Get-response-normal **}
└──GetResponseNormal Sequence
├──InvokeIdPriority
│ ├──InvokeID (0..3): 1
│ ├──ServiceClass (6): confirmed
│ └──Priority (7): high
└──GetDataResult Result[0] {** data **}
└──Data[1] {** Array **}
└──SequenceOf 5 Element(s)
├──0: Data[2] {** Structure **}
│ └──SequenceOf 4 Element(s)
│ ├──0: [18] Unsigned16 = 8 (0x0008)
│ ├──1: [9] OctetString[6] = 00 00 01 00 00 FF
│ ├──2: [15] Integer8 = 2 (0x02)
│ └──3: [18] Unsigned16 = 0 (0x0000)
├──1: Data[2] {** Structure **}
│ └──SequenceOf 4 Element(s)
│ ├──0: [18] Unsigned16 = 3 (0x0003)
│ ├──1: [9] OctetString[6] = 00 00 60 F0 0C FF
│ ├──2: [15] Integer8 = 2 (0x02)
│ └──3: [18] Unsigned16 = 0 (0x0000)
├──2: Data[2] {** Structure **}
│ └──SequenceOf 4 Element(s)
│ ├──0: [18] Unsigned16 = 3 (0x0003)
│ ├──1: [9] OctetString[6] = 00 00 60 F0 0C FF
│ ├──2: [15] Integer8 = 12 (0x0C)
│ └──3: [18] Unsigned16 = 0 (0x0000)
├──3: Data[2] {** Structure **}
│ └──SequenceOf 4 Element(s)
│ ├──0: [18] Unsigned16 = 3 (0x0003)
│ ├──1: [9] OctetString[6] = 00 00 60 F0 0C FF
│ ├──2: [15] Integer8 = 19 (0x13)
│ └──3: [18] Unsigned16 = 0 (0x0000)
└──4: Data[2] {** Structure **}
└──SequenceOf 4 Element(s)
├──0: [18] Unsigned16 = 3 (0x0003)
├──1: [9] OctetString[6] = 00 00 61 61 00 FF
├──2: [15] Integer8 = 2 (0x02)
└──3: [18] Unsigned16 = 0 (0x0000)
Timeout is set to 5 seconds.
Attaching compare of HDLC…
Attaching compare of HDLC packets. Left: DLMS Director, Right - our application. Packets are same with the exception of send and receive packets numbers a CRC which is normal.
Hi, There is some strange…
Hi,
There is some strange data before Get request. There are several reasons why the meter is not replying. Can you add GXDLMSDirector hex log so I can check what is really happening?
You can get it when you select "View", "Log" and "View Log".
BR,
Mikko
Hi, Thank you for the log…
Hi,
Thank you for the log. There is something in with scalers and units reading that causes this. I need to check this from the bytes and it'll take some time.
Select "Supported Services" and then un-select "Multiple references".
I believe that you can now read your meter without problems.
BR,
Mikko
Unchecking multiple…
Unchecking multiple references helped. Thank you.
Hi, The new version is…
Hi,
The new version is released during the next week where this is fixed.
BR,
Mikko