Hi,
I am running sample client with smartmeter via HDLC. In case of LLS authentication, I am getting the below error,
Jul 14, 2022 2:38:00 PM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 42 Expected: 52
The meter sends an invalid HDLC frame sequence number. You need to ask if there is a firmware update available for the meter. There is not much that you can do about this.
It seems like the issue is still on the meter. I checked the data that the meter is returning and I believe that you try to read the association view. Inform the meter vendor of this and ask if there is a firmware update for this problem.
You can also try to add COSEM objects manually if you know the logical name and object type. You can do it by selecting "Edit" and "Add Object". I believe that you can read current values without problems because the data is so small that it can fit in one packet.
Hi,
Hi,
The meter sends an invalid HDLC frame sequence number. You need to ask if there is a firmware update available for the meter. There is not much that you can do about this.
BR,
Mikko
Hi Mikko,
Hi Mikko,
Thanks for the reply. I updated the firmware, but I am still getting the same error as below:
Connect using serial port connection gurux.serial.GXSerial@e73f9ac
Authentication: Low
ClientAddress: 0x20
ServerAddress: 0x1
Standard: DLMS
----------------------------
Proposed conformance:
[GET, GENERAL_PROTECTION, BLOCK_TRANSFER_WITH_GET_OR_READ, DELTA_VALUE_ENCODING, SET, BLOCK_TRANSFER_WITH_SET_OR_WRITE, ACCESS, SELECTIVE_ACCESS, BLOCK_TRANSFER_WITH_ACTION, MULTIPLE_REFERENCES, ACTION]
Negotiated conformance:
[GET, BLOCK_TRANSFER_WITH_GET_OR_READ, SELECTIVE_ACCESS]
MaxReceivePDUSize: 832
Jul 23, 2022 4:45:15 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 42 Expected: 52
Jul 23, 2022 4:45:15 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 42 Expected: 52
Jul 23, 2022 4:45:16 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 42 Expected: 52
Jul 23, 2022 4:45:16 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 44 Expected: 52
Jul 23, 2022 4:45:16 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 42 Expected: 52
Jul 23, 2022 4:45:16 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 44 Expected: 52
Jul 23, 2022 4:45:17 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 42 Expected: 52
Jul 23, 2022 4:45:17 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 44 Expected: 52
Jul 23, 2022 4:45:17 AM gurux.dlms.GXDLMSSettings checkFrame
INFO: Invalid HDLC Frame: 56 Expected: 52
Data send failed. Try to resend 1/3
Data send failed. Try to resend 2/3
RX: 04:48:17.181 7E A9 1E 41 03 42 E0 0E E6 E7 00 C4 02 C1 00 00 00 00 01 00 82 02 E6 01 76 02 04 12 00 01 11 00 09 06 00 00 2A 00 00 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 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 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 01 02 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 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 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 01 00 00 02 00 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 5E 5B 09 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 5E 5B 0B FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 F0 67 7E 7E A9 1E 41 03 44 D6 6B 04 12 00 01 11 00 09 06 00 00 5E 5B 0C FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 01 04 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 01 00 00 08 00 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 01 00 00 08 04 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 01 00 00 08 05 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 5E 5B 00 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 00 01 00 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 02 00 FF 02 02 01 02 A8 FA 7E 7E A0 D4 41 03 56 56 EE 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 0B 00 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 0B 01 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 0B 02 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 0B 03 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 02 04 12 00 01 11 00 09 06 00 00 60 0B 04 FF 02 02 01 02 02 03 0F 01 16 01 01 00 02 03 0F 02 16 01 01 00 01 00 90 F8 7E
DisconnectRequest
Access Error : Unknown error.
Process finished with exit code 1
Please advise.
Regards
Pooja
Hi,
Hi,
It seems like the issue is still on the meter. I checked the data that the meter is returning and I believe that you try to read the association view. Inform the meter vendor of this and ask if there is a firmware update for this problem.
You can also try to add COSEM objects manually if you know the logical name and object type. You can do it by selecting "Edit" and "Add Object". I believe that you can read current values without problems because the data is so small that it can fit in one packet.
BR,
Mikko