When I try read from meter any data (for example object Clock with obis-code 0.0.1.0.0.255) I get PUSH-message from meter. But this message put into "Trace TextBox" and application get me Error Message "LLC bytes are missing from the message" and data not receving.
Before update i don't have any problem with DataNotification.
Sorry, but last HDLC frame is 7E A0 1F 61 02 21 74 5E 96 E6 E7 00 C4 01 C1 00 09 0C 07 E5 0A 0D 03 08 21 1C FF 80 00 01 CA 46 7E and it's not Notification. It is Data Frame and he send after Notify. For Notify don't need acknowledge, then FINAL BIT will not be TRUE. In last frame (with data) FINAL BIT is TRUE, and after this frame work with device may be contimued. It's wrotten in GreenBook paragraph 8.4.4.1
And about FINAL BIT for UI frame with Notify wotten in GreenBook paragraph 8.4.5.4.7
I believe that I have a design that can handle this when HDLC windows size is bigger than 1 and in your case. This will be included for next week release.
This is improved and the new version from GXDLMSDirector is released on Monday.
You can try this if you update Gurux.DLMS.Net component to Version 9.0.2201.2801.
LLC bytes are missing from your push message and it will cause that parsing will fail. You need to fix that.
7E A0 23 61 02 21 03 87 32 //LLC bytes are missing.
0F 00 00 00 01 0C 07 E5 0A 0D 03 08 21 05 00 80 00 FF 02 01 06 00 00 20 12 96 C2 7E
Hi,
Hi,
Can you add a hex trace so I can check what might be the reason for this?
BR,
Mikko
I get in trace only this
I get in trace only this
13:46:50 Read object type Clock index: 2
TX: 7E A0 1A 02 21 61 54 18 87 E6 E6 00 C0 01 C1 00 08 00 00 01 00 00 FF 02 00 60 1A 7E
13:46:50
RX: 7E A0 23 61 02 21 03 87 32 0F 00 00 00 01 0C 07 E5 0A 0D 03 08 12 29 00 80 00 FF 02 01 06 00 00 20 12 3B 07 7E
This log from External
This log from External "Listener" on COM-port
7E A0 08 02 21 61 93 63 97 7E
7E A0 1F 61 02 21 73 E1 E2 81 80 12 05 01 80 06
01 80 07 04 00 00 00 01 08 04 00 00 00 01 53 3B
7E
7E A0 4D 02 21 61 10 86 C6 E6 E6 00 60 3E A1 09
06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60
85 74 05 08 02 02 AC 12 80 10 47 3E 66 0D 42 47
04 45 29 0C 1C 44 70 40 14 24 BE 10 04 0E 01 00
00 00 06 5F 1F 04 00 00 1E 9F FF FF A9 A0 7E
7E A0 59 61 02 21 30 C4 68 E6 E7 00 61 4A A1 09
06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05
A1 03 02 01 0E 88 02 07 80 89 07 60 85 74 05 08
02 02 AA 12 80 10 61 62 63 64 65 66 67 68 69 6A
6B 6C 6D 6E 6F 70 BE 10 04 0E 08 00 06 5F 1F 04
00 00 18 1D 04 00 00 07 63 D8 7E
7E A0 2C 02 21 61 32 61 6E E6 E6 00 C3 01 C1 00
0F 00 00 28 00 00 FF 01 01 09 10 5E 14 F4 6E 66
62 29 10 BF E9 A9 EC 27 72 85 26 6C CC 7E
7E A0 25 61 02 21 52 13 4A E6 E7 00 C7 01 C1 00
01 00 09 10 BB 6B 21 90 D9 F6 87 54 91 97 6F 0B
18 68 68 7E BA 64 7E
7E A0 1A 02 21 61 54 18 87 E6 E6 00 C0 01 C1 00
08 00 00 01 00 00 FF 02 00 60 1A 7E
7E A0 23 61 02 21 03 87 32 0F 00 00 00 01 0C 07
E5 0A 0D 03 08 21 05 00 80 00 FF 02 01 06 00 00
20 12 96 C2 7E 7E A0 1F 61 02 21 74 5E 96 E6 E7
00 C4 01 C1 00 09 0C 07 E5 0A 0D 03 08 21 1C FF
80 00 01 CA 46 7E
Hi,
Hi,
Your date notification Frame type is 0x3 and it should be 0x13 because it's the last HDLC frame.
7E A0 23 61 02 21
03 //This should be 0x13
87 32 0F 00 00 00 01 0C 07 E5 0A 0D 03 08 21 05 00 80 00 FF 02 01 06 00 00 20 12 96 C2 7E
This frame type check is improved because there are meters that are using HDLC Window size other than one.
http://www.gurux.fi/Gurux.DLMS.Objects.GXDLMSHdlcSetup
BR,
Mikko
Sorry, but last HDLC frame is
Sorry, but last HDLC frame is 7E A0 1F 61 02 21 74 5E 96 E6 E7 00 C4 01 C1 00 09 0C 07 E5 0A 0D 03 08 21 1C FF 80 00 01 CA 46 7E and it's not Notification. It is Data Frame and he send after Notify. For Notify don't need acknowledge, then FINAL BIT will not be TRUE. In last frame (with data) FINAL BIT is TRUE, and after this frame work with device may be contimued. It's wrotten in GreenBook paragraph 8.4.4.1
And about FINAL BIT for UI frame with Notify wotten in GreenBook paragraph 8.4.5.4.7
Am I wrong here?
Hi,
Hi,
I believe that I have a design that can handle this when HDLC windows size is bigger than 1 and in your case. This will be included for next week release.
BR,
Mikko
Hi,
Hi,
This is improved and the new version from GXDLMSDirector is released on Monday.
You can try this if you update Gurux.DLMS.Net component to Version 9.0.2201.2801.
LLC bytes are missing from your push message and it will cause that parsing will fail. You need to fix that.
7E A0 23 61 02 21 03 87 32 //LLC bytes are missing.
0F 00 00 00 01 0C 07 E5 0A 0D 03 08 21 05 00 80 00 FF 02 01 06 00 00 20 12 96 C2 7E
BR,
Mikko