By nhzq , 18 August, 2022 Forums Gurux.DLMS Hi, I tried to translate the message but it gave me error: Invalid DLMS framing. I checked with GuruxDLMSTranslator and it worked. Message: 00 01 00 01 00 01 00 64 C4 01 C1 00 01 01 02 05 05 00 00 0A 8D 0A 10 53 4D 58 31 30 35 39 30 32 31 30 30 30 30 31 38 06 0F 00 00 01 06 00 00 00 01 02 07 09 0C 07 E6 08 12 04 08 00 00 FF 01 E0 00 06 00 00 0C FA 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 11 00 Translated message from GuruxDLMSTranslator : <WRAPPER len="108" > <TargetAddress Value="1" /> <SourceAddress Value="1" /> <PDU> <GetResponse> <GetResponseNormal> <!--Priority: HIGH ServiceClass: CONFIRMED invokeID: 1--> <InvokeIdAndPriority Value="193" /> <Result> <Data> <Array Qty="1" > <Structure Qty="5" > <Int32 Value="2701" /> <String Value="SMX1059021000018" /> <UInt32 Value="251658241" /> <UInt32 Value="1" /> <Structure Qty="7" > <!--2022-08-18 08:00:00--> <OctetString Value="07E6081204080000FF01E000" /> <UInt32 Value="3322" /> <!--0--> <Float64 Value="0000000000000000" /> <!--0--> <Float64 Value="0000000000000000" /> <!--0--> <Float64 Value="0000000000000000" /> <!--0--> <Float64 Value="0000000000000000" /> <UInt8 Value="0" /> </Structure> </Structure> </Array> </Data> </Result> </GetResponseNormal> </GetResponse> </PDU> </WRAPPER> Can you please tell me on how to fix this? Thanks Hi, Hi, Can you read your meter with the client example and add the total hex trace here so I can check it? https://github.com/Gurux/Gurux.DLMS.Python/tree/master/Gurux.DLMS.Clien… BR, Mikko Hi, thanks for the response. Hi, thanks for the response. Here is the log: TX: 16:31:03 00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 32 32 32 32 32 32 32 32 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF RX: 16:31:03 00 01 00 01 00 01 00 2B 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 1E 1D 04 00 00 07 TX: 16:31:03 00 01 00 01 00 01 00 20 C0 01 C1 00 09 01 00 63 01 00 FF 02 00 02 02 04 06 00 00 0A 8D 06 00 00 0A 8D 12 00 01 12 00 00 RX: 16:31:03 00 01 00 01 00 01 00 64 C4 01 C1 00 01 01 02 05 05 00 00 0A 8D 0A 10 53 4D 58 31 30 35 39 30 32 31 30 30 30 30 31 38 06 0F 00 00 01 06 00 00 00 01 02 07 09 0C 07 E6 08 12 04 08 00 00 FF 01 E0 00 06 00 00 0C FA 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 11 00 TX: 16:31:03 00 01 00 01 00 01 00 09 62 03 80 01 00 03 80 01 00 RX: 16:31:03 00 01 00 01 00 01 00 17 63 11 80 01 00 BE 0F 04 0E 08 00 06 5F 1F 04 00 00 1E 1D 04 00 00 07 Hi, Hi, There is a bug on the meter. Your meter is returning the structure as below and that is not the correct format. You need to ask the meter vendor if there is new firmware available. BR, Mikko <Structure Qty="05" > <Int32 Value="00000A8D" /> <String Value="SMX1059021000018" /> <UInt32 Value="0F000001" /> <UInt32 Value="00000001" /> <Structure Qty="07" > <!-- 18.8.2022 8.00.00-08:00 --> <OctetString Value="07E6081204080000FF01E000" /> <UInt32 Value="00000CFA" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <UInt8 Value="00" /> </Structure> BR, Mikko
Hi, Hi, Can you read your meter with the client example and add the total hex trace here so I can check it? https://github.com/Gurux/Gurux.DLMS.Python/tree/master/Gurux.DLMS.Clien… BR, Mikko
Hi, thanks for the response. Hi, thanks for the response. Here is the log: TX: 16:31:03 00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 32 32 32 32 32 32 32 32 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF RX: 16:31:03 00 01 00 01 00 01 00 2B 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 1E 1D 04 00 00 07 TX: 16:31:03 00 01 00 01 00 01 00 20 C0 01 C1 00 09 01 00 63 01 00 FF 02 00 02 02 04 06 00 00 0A 8D 06 00 00 0A 8D 12 00 01 12 00 00 RX: 16:31:03 00 01 00 01 00 01 00 64 C4 01 C1 00 01 01 02 05 05 00 00 0A 8D 0A 10 53 4D 58 31 30 35 39 30 32 31 30 30 30 30 31 38 06 0F 00 00 01 06 00 00 00 01 02 07 09 0C 07 E6 08 12 04 08 00 00 FF 01 E0 00 06 00 00 0C FA 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 11 00 TX: 16:31:03 00 01 00 01 00 01 00 09 62 03 80 01 00 03 80 01 00 RX: 16:31:03 00 01 00 01 00 01 00 17 63 11 80 01 00 BE 0F 04 0E 08 00 06 5F 1F 04 00 00 1E 1D 04 00 00 07
Hi, Hi, There is a bug on the meter. Your meter is returning the structure as below and that is not the correct format. You need to ask the meter vendor if there is new firmware available. BR, Mikko <Structure Qty="05" > <Int32 Value="00000A8D" /> <String Value="SMX1059021000018" /> <UInt32 Value="0F000001" /> <UInt32 Value="00000001" /> <Structure Qty="07" > <!-- 18.8.2022 8.00.00-08:00 --> <OctetString Value="07E6081204080000FF01E000" /> <UInt32 Value="00000CFA" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <!-- 0 --> <Float64 Value="0000000000000000" /> <UInt8 Value="00" /> </Structure> BR, Mikko
Hi,
Hi,
Can you read your meter with the client example and add the total hex trace here so I can check it?
https://github.com/Gurux/Gurux.DLMS.Python/tree/master/Gurux.DLMS.Clien…
BR,
Mikko
Hi, thanks for the response.
Hi, thanks for the response. Here is the log:
TX: 16:31:03 00 01 00 01 00 01 00 38 60 36 A1 09 06 07 60 85 74 05 08 01 01 8A 02 07 80 8B 07 60 85 74 05 08 02 01 AC 0A 80 08 32 32 32 32 32 32 32 32 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D FF FF
RX: 16:31:03 00 01 00 01 00 01 00 2B 61 29 A1 09 06 07 60 85 74 05 08 01 01 A2 03 02 01 00 A3 05 A1 03 02 01 00 BE 10 04 0E 08 00 06 5F 1F 04 00 00 1E 1D 04 00 00 07
TX: 16:31:03 00 01 00 01 00 01 00 20 C0 01 C1 00 09 01 00 63 01 00 FF 02 00 02 02 04 06 00 00 0A 8D 06 00 00 0A 8D 12 00 01 12 00 00
RX: 16:31:03 00 01 00 01 00 01 00 64 C4 01 C1 00 01 01 02 05 05 00 00 0A 8D 0A 10 53 4D 58 31 30 35 39 30 32 31 30 30 30 30 31 38 06 0F 00 00 01 06 00 00 00 01 02 07 09 0C 07 E6 08 12 04 08 00 00 FF 01 E0 00 06 00 00 0C FA 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 00 11 00
TX: 16:31:03 00 01 00 01 00 01 00 09 62 03 80 01 00 03 80 01 00
RX: 16:31:03 00 01 00 01 00 01 00 17 63 11 80 01 00 BE 0F 04 0E 08 00 06 5F 1F 04 00 00 1E 1D 04 00 00 07
Hi,
Hi,
There is a bug on the meter. Your meter is returning the structure as below and that is not the correct format. You need to ask the meter vendor if there is new firmware available.
BR,
Mikko
<Structure Qty="05" >
<Int32 Value="00000A8D" />
<String Value="SMX1059021000018" />
<UInt32 Value="0F000001" />
<UInt32 Value="00000001" />
<Structure Qty="07" >
<!-- 18.8.2022 8.00.00-08:00 -->
<OctetString Value="07E6081204080000FF01E000" />
<UInt32 Value="00000CFA" />
<!-- 0 -->
<Float64 Value="0000000000000000" />
<!-- 0 -->
<Float64 Value="0000000000000000" />
<!-- 0 -->
<Float64 Value="0000000000000000" />
<!-- 0 -->
<Float64 Value="0000000000000000" />
<UInt8 Value="00" />
</Structure>
BR,
Mikko