Our AMR has to be able to reconfigure the display configuration of an specific meter. To do that, it is necessary to perform a write attribute operation, changing an attr that is of type 'array'. Each position of this array represents one of the screens to be displayed by the meter, so the more screens are needed, the longer the array needs to be.
In the case, we are using Gurux DLMC for C to perform the DLMS operations.
Well, we have been successful to perform this write when the array is short - only a few positions - but if the array is too long then operation fails. When this happens, the meter's display is not properly configured and at the end of the dlms transactions it informs an error of 'LongSetOrWriteAborted'.
The operation works well when we use the manufacturer configuration utility tool and, by checking the DLMS messages, we can see that their structure is considerably different.
I'll provide a few DLMS transactions below, ommiting the part of connecting to the meter and such.
1) 'Short' write (where there aren't many fields to cause the error). It suceeds:
TX >>> 7EA84603CD3299A5E6E600C101C100010080150001FF020001060911010100000902FF020030303120202020200911010100000901FF02003030322020202020091103010059A97E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA84903CD345672010800FF020030303320202020200911030100010801FF020030303420202020200911030100010803FF020030303620202020200911030100010802FF020030A0D97E
RX >>> 7EA007CD037111CF7E
TX >>> 7EA01003CD36112730382020202020ED6F7E
RX >>> 7EA010CD0392048EE6E700C501C10050897E
2) 'Long' write (too many fields, operation fails):
TX >>> 7EA84603CD3299A5E6E600C102C100010080150001FF020000000000018198010A0911010100000902FF020030303120202020200911010100000901FF0200303032202020CF297E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA84903CD34567220200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010803FF02003030362020202020091103010078287E
RX >>> 7EA007CD037111CF7E
TX >>> 7EA03B03CD365768010802FF020030303820202020200911030100010804FF020030303920202020200911030100050800FF02003032342020202FF17E
RX >>> 7EA013CD0392C9ABE6E700C502C1000000010F037E
TX >>> 7EA84603CD58C569E6E600C103C100010080150001FF02000100000002282020091101000060321AFF020030383820202020200911030100020800FF02003130332020202062F97E
RX >>> 7EA007CD03B11D097E
TX >>> 7EA00A03CD5A749120CEE77E
RX >>> 7EA014CD03D4DADBE6E700C503C111000000010C207E
3) 'Long' write performed by manufacturer utility. It succeeds:
S: 7E A0 B8 03 CD 32 D0 26 E6 E6 00 C1 02 40 00 01 00 80 15 00 01 FF 02 00 00 00 00 00 01 81 98 01 11 09 11 01 01 00 00 09 02 FF 02 00 20 20 20 20 20 20 30 31 09 11 01 01 00 00 09 01 FF 02 00 20 20 20 20 20 20 30 32 09 11 03 01 00 01 08 00 FF 02 00 20 20 20 20 20 20 30 33 09 11 01 00 00 60 32 1A FF 02 00 38 38 00 00 00 00 00 00 09 11 03 01 00 02 08 00 FF 02 00 31 30 33 00 00 00 00 00 09 11 01 00 00 61 62 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 01 01 00 00 01 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 00 04 1D 00 FF 02 00 00 00 00 00 00 00 21 CB 7E
R: 7E A0 13 CD 03 52 C5 6D E6 E7 00 C5 02 40 00 00 00 01 1E 82 7E
S: 7E A0 B8 03 CD 54 E0 20 E6 E6 00 C1 03 40 00 00 00 00 02 81 A2 00 00 09 11 03 01 00 03 1D 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 00 04 08 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 00 03 08 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 20 24 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 34 24 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 48 24 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 20 20 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 34 20 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 48 20 80 7A E8 7E
R: 7E A0 13 CD 03 74 F1 29 E6 E7 00 C5 02 40 00 00 00 02 85 B0 7E
S: 7E A0 20 03 CD 76 E7 29 E6 E6 00 C1 03 40 FF 00 00 00 03 0B FF 02 00 00 00 00 00 00 00 00 00 8F AE 7E
R: 7E A0 14 CD 03 96 CC BA E6 E7 00 C5 03 40 00 00 00 00 03 93 BD 7E
--------------------------------------------------------------
By putting the above examples on the GuruxDLMSTranslator for messages, it can be seen that the manufacturer's message performs a SetRequestFirstDataBlock and it explicitily states the object's LN, class and attribute, whereas the messages from the Gurux generated messages do not.
We don't know how to proceed to solve this issue.
By the data provided above, would you be able to provide us assistance or it would be needed more details?
Thank you in advance.
Hi, When the client…
Hi,
When the client establishes the connection it proposes the maximum HDLC frame size. In default, it is 128 bytes.
The other application uses a bigger HDLC frame size. You need to use the same HDLC frame size that the other application is using.
BR,
Mikko
Hi Kurumi, Thank you for the…
Hi Kurumi,
Thank you for the quick reply, but I'm affraid this didn't solve this issue.
The transactions below are made by the manufacturer's tool when connecting to the meter:
Building Link Layer Connection ...
[16:44:06 202] S: 7E A0 20 03 CD 93 44 99 81 80 14 05 02 04 00 06 02 04 00 07 04 00 00 00 01 08 04 00 00 00 07 44 86 7E
[16:44:06 607] R: 7E A0 20 CD 03 73 71 34 81 80 14 05 02 00 AF 06 02 00 AF 07 04 00 00 00 01 08 04 00 00 00 01 D2 0B 7E
Building Link Layer Connection Successful
Building Application Layer Connection ...
[16:44:06 699] S: 7E A0 46 03 CD 10 A9 FD E6 E6 00 60 38 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 0C 80 0A 32 36 38 36 36 35 38 36 30 30 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 7E 1F 00 00 1C 33 7E
[16:44:06 983] R: 7E A0 37 CD 03 30 6E D0 E6 E7 00 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 38 1F 00 AC 00 07 6A F5 7E
Building Application Layer Connection: Successful
Using the translator tool, we can check that the connection is stabilished with:
<MaxInfoTX Value="175" />
<MaxInfoRX Value="175" />
<WindowSizeTX Value="1" />
<WindowSizeRX Value="1" />
<NegotiatedMaxPduSize Value="172" />
I tried to do the same with our AMR, setting the same values on the Gurux Settings.
The result was the transactions below, where we can check that the properties are new applied, but the result is the same - LongSetOrWriteAborted.
DLMS>Connect
TX >>> 7EA01E03CD93F47B8180120501AF0601AF0704000000010804000000015E127E
RX >>> 7EA020CD03737134818014050200AF060200AF070400000001080400000001D20B7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400001E1DFFFFA7CA7E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181D00AC000782667E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 14
TX >>> 7EA8B503CD327FF7E6E600C102C100010080150001FF020000000000018198010E0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010803FF020030303620202020200911030100010802FF020030303820202020200911030100010804FF020030303920202020200911030100050800FF0200303234786E7E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA00C03CD3496502020207DCE7E
RX >>> 7EA013CD0372C74CE6E700C502C1000000010F037E
TX >>> 7EA09303CD56B44CE6E600C103C100010080150001FF02000100000002742020091101000060321AFF020030383820202020200911030100020800FF020031303320202020200911030100020801FF020031303420202020200911030100020803FF020031303620202020200911030100020802FF020031303820202020200911030100020804FF020031303920202020209BF37E
RX >>> 7EA014CD0394DE99E6E700C503C111000000010C207E
Hi, You should set the frame…
Hi,
You should set the frame size to 1024 and now it's 175.
BR,
Mikko
Continuing Andre's work: I…
Continuing Andre's work:
I tried setting the frame size to 1024, but same problem is still happening. While we're still having this problem we did have some developments.
Going back to the default frame size (128) this is the first "set display" message being send (after the link and application layers):
7E A8 86 03 CD 32 40 9E
E6 E6 00 C1 02 C1 00
01 00 80 15 00 01 FF 02
00 00 00 00 00 01 81 98
01 0F
09 11
01 01 00 00 09 02 FF 02 00 30 30 31 20 20 20 20 20
09 11
01 01 00 00 09 01 FF 02 00 30 30 32 20 20 20 20 20
09 11
03 01 00 01 08 00 FF 02 00 30 30 33 20 20 20 20 20
09 11
03 01 00 01 08 01 FF 02 00 30 30 34 20 20 20 20 20
09 11
03 01 00 01 08 02 FF 02 00 30 30 38 20 20 20 20 20
09 11
03 01 00
CA DF 7E
Translating the PDU with gurux translator we have:
<GatewayRequest>
<NetworkId Value="230" />
<PhysicalDeviceAddress Value="" />
<SetRequest>
<SetRequestFirstDataBlock>
<!--Priority: HIGH ServiceClass: CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="C1" />
</SetRequestFirstDataBlock>
</SetRequest>
</GatewayRequest>
The byte refering to the data size is wrong, on the fourth line the last byte (0x98) should be 0x66, by manually changing only this byte the gurux translator was able to corretly interpret the PDU:
<GatewayRequest>
<NetworkId Value="230" />
<PhysicalDeviceAddress Value="" />
<SetRequest>
<SetRequestFirstDataBlock>
<!--Priority: HIGH ServiceClass: CONFIRMED invokeID: 1-->
<InvokeIdAndPriority Value="C1" />
<AttributeDescriptor>
<!--DATA-->
<ClassId Value="0001" />
<!--0.128.21.0.1.255-->
<InstanceId Value="0080150001FF" />
<AttributeId Value="02" />
</AttributeDescriptor>
<DataBlock>
<LastBlock Value="00" />
<BlockNumber Value="00000001" />
<RawData Value="010F0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF020030303820202020200911030100" />
</DataBlock>
</SetRequestFirstDataBlock>
</SetRequest>
</GatewayRequest>
A 0x98 size data would fit on a 175 window frame (just to clarify I translated the link and app layer messages and confirmed that the agreed frame was 128), regardless of frame size this value is always the same (tried several frame values). Is this value supposed to be fixed? Shouldn't it change according to the raw data size?
OBS: Just to clarifiy I understand that setting a 175 frame should make the size values match and the operation work, but the AMR is always sending 3 less bytes than the agreed max value. While I haven't looked into why it always sends 3 less bytes I don't believe this is the problem, we shouldn't need to set the frame size to max for this to work right?
Hello all, We are still…
Hello all,
We are still experiencing the issue - we are unable to successfully do the writing operation stated on this post.
Does the information provided by Renato Pepe help to understand what is going on? How can we proceed/
Hi, Please, I need the…
Hi,
Please, I need the complete log. Now I don't know what frame or PDU size you have used. There are multiple parameters and the connection fails if one is different than the meter expects.
BR,
Mikko
Hello. I'm pasting here a…
Hello.
I'm pasting here a few different attempts, changing frames and PDU sizes.
In all of them the operation is aborted by the meter.
Also in all of them you'll notice that the gurux translator can't properly translate the first "write attribute" operation PDU. In the anexed figure I'm showing how the translation is vs how it's supposed to be by manually changing the size byte.
========================================================================================
Dlms Gurux Set Display:
* Regular operations:
- Does not request specific values and accept meter rules
DLMS>Connect
TX >>> 7EA00703CD9336417E
RX >>> 7EA020CD037371348180140502008006020080070400000001080400000001CE6A7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400001E1DFFFFA7CA7E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181D00AC000782667E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 11
TX >>> 7EA88603CD32409EE6E600C102C100010080150001FF020000000000018198010B0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF02003030382020202020091101000002467E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA03B03CD34454B60321AFF0200303838202020202009110301800C2080FF0200000000000000000009110301800C2480FF0200000000000000C47B7E
RX >>> 7EA013CD0372C74CE6E700C502C1000000010F037E
TX >>> 7EA05A03CD560E8EE6E600C103C100010080150001FF020001000000023B00000911030100020803FF020031303620202020200911030100020802FF020031303820202020200911030100020800FF020031303320202020202E9F7E
RX >>> 7EA014CD0394DE99E6E700C503C111000000010C207E
DLMS>Disconnect
TX >>> 7EA00703CD533A877E
RX >>> 7EA007CD037303EC7E
============================================================================================
*Operation changing sizes:
-Max TX and RX = 175
-PDU = 172
DLMS>Connect
TX >>> 7EA01E03CD93F47B8180120501AF0601AF0704000000010804000000015E127E
RX >>> 7EA020CD03737134818014050200AF060200AF070400000001080400000001D20B7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400001E1D00AC79557E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181D00AC000782667E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 13
TX >>> 7EA8B503CD327FF7E6E600C102C100010080150001FF020000000000018198010D0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF02003030382020202020091101000060321AFF0200303838202020202009110301800C2080FF0200000000000000000009110301800C2480FF0200000000AF6E7E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA00C03CD34965000000077CF7E
RX >>> 7EA013CD0372C74CE6E700C502C1000000010F037E
TX >>> 7EA08003CD56D8AAE6E600C103C100010080150001FF020001000000026100000911030100020803FF020031303620202020200911030100020802FF020031303820202020200911030100020800FF020031303320202020200911030100050800FF020030323420202020200911030100070802FF02003132342020202020D24C7E
RX >>> 7EA014CD0394DE99E6E700C503C111000000010C207E
DLMS>Disconnect
TX >>> 7EA00703CD533A877E
RX >>> 7EA007CD037303EC7E
============================================================================================
- Max TX and RX = PDU = 172
DLMS>Connect
TX >>> 7EA01E03CD93F47B8180120501AC0601AC07040000000108040000000188867E
RX >>> 7EA020CD03737134818014050200AC060200AC07040000000108040000000134357E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400001E1D00AC79557E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181D00AC000782667E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 13
TX >>> 7EA8B203CD325EA0E6E600C102C100010080150001FF020000000000018198010D0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF02003030382020202020091101000060321AFF0200303838202020202009110301800C2080FF0200000000000000000009110301800C2480FF020016A67E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA00F03CD345B7500000000000073837E
RX >>> 7EA013CD0372C74CE6E700C502C1000000010F037E
TX >>> 7EA08003CD56D8AAE6E600C103C100010080150001FF020001000000026100000911030100020803FF020031303620202020200911030100020802FF020031303820202020200911030100020800FF020031303320202020200911030100050800FF020030323420202020200911030100070802FF02003132342020202020D24C7E
RX >>> 7EA014CD0394DE99E6E700C503C111000000010C207E
DLMS>Disconnect
TX >>> 7EA00703CD533A877E
RX >>> 7EA007CD037303EC7E
============================================================================================
- Max TX and RX greater than 175
- PDU = 172
DLMS>Connect
TX >>> 7EA01E03CD93F47B8180120501B20601B2070400000001080400000001C1217E
RX >>> 7EA020CD03737134818014050200AF060200AF070400000001080400000001D20B7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400001E1D00AC79557E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181D00AC000782667E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 13
TX >>> 7EA8B503CD327FF7E6E600C102C100010080150001FF020000000000018198010D0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF02003030382020202020091101000060321AFF0200303838202020202009110301800C2080FF0200000000000000000009110301800C2480FF0200000000AF6E7E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA00C03CD34965000000077CF7E
RX >>> 7EA013CD0372C74CE6E700C502C1000000010F037E
TX >>> 7EA08003CD56D8AAE6E600C103C100010080150001FF020001000000026100000911030100020803FF020031303620202020200911030100020802FF020031303820202020200911030100020800FF020031303320202020200911030100050800FF020030323420202020200911030100070802FF02003132342020202020D24C7E
RX >>> 7EA014CD0394DE99E6E700C503C111000000010C207E
DLMS>Disconnect
TX >>> 7EA00703CD533A877E
RX >>> 7EA007CD037303EC7E
============================================================================================
- Max TX and RX greater than 175
- PDU != 172
TX >>> 7EA01E03CD93F47B8180120501B20601B2070400000001080400000001C1217E
RX >>> 7EA020CD03737134818014050200AF060200AF070400000001080400000001D20B7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400001E1D007D7D927E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181D00AC000782667E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 13
TX >>> 7EA8B503CD327FF7E6E600C102C100010080150001FF020000000000018198010D0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF02003030382020202020091101000060321AFF0200303838202020202009110301800C2080FF0200000000000000000009110301800C2480FF0200000000AF6E7E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA00C03CD34965000000077CF7E
RX >>> 7EA013CD0372C74CE6E700C502C1000000010F037E
TX >>> 7EA08003CD56D8AAE6E600C103C100010080150001FF020001000000026100000911030100020803FF020031303620202020200911030100020802FF020031303820202020200911030100020800FF020031303320202020200911030100050800FF020030323420202020200911030100070802FF02003132342020202020D24C7E
RX >>> 7EA014CD0394DE99E6E700C503C111000000010C207E
DLMS>Disconnect
TX >>> 7EA00703CD533A877E
RX >>> 7EA007CD037303EC7E
Hi, The manufacturer…
Hi,
The manufacturer application doesn't use block transfer.
The meter says that is supports BlockTransferWithGetOrRead, but it seems that is not true.
Remove BlockTransferWithGetOrRead from the proposed conformance.
BR,
Mikko
Hello again. Thanks for the…
Hello again.
Thanks for the reply. We found a solution to the problem, fixing the size problem and properly sending a complete block transfer frame, but another issue appeared.
First of all I think the meter does support block transfer, at the end of this comment I pasted a few operations and the first one is using the meter's proprietary software, and if I'm not wrong the write is successfully done through blocks.
I tried changing the block related conformaces like you suggested, but still resulting in errors. The pasted operations 2 and 3 are the results of this attempt.
The solution we found: Updating the setting "maxPduSize" to match the value of "maxServerPDUSize" after the connection and before the write fixed the size problem. Pasted oiperation 4 contains the logs of this attempt, the meter now recognizes the operation, and gurux translator can properly decode the first write frame.
The new issue: The first frame is working perfectly, but on the second frame the "BlockNumber" parameter seems to be wrong, it should be 2, but's it's always 0x01008015 (this can be seen through gurux translator). Comparing the meter's software frame with the one being sent by our AMR it's possible to see the difference (better seen on the anexed image). While the software only sends the "display LN info" on the first frame, our AMR seems to be sending it on every frame. We can't figure out why, is there any setting or configuration related to this? I've tried changing the proposed conformances and looking into gurux defines and configs, but so far no success.
Operation 1: Meter's proprietary software operation
==========================================================================
Building Link Layer Connection ...
[16:44:06 202] S: 7E A0 20 03 CD 93 44 99 81 80 14 05 02 04 00 06 02 04 00 07 04 00 00 00 01 08 04 00 00 00 07 44 86 7E
[16:44:06 607] R: 7E A0 20 CD 03 73 71 34 81 80 14 05 02 00 AF 06 02 00 AF 07 04 00 00 00 01 08 04 00 00 00 01 D2 0B 7E
Building Link Layer Connection Successful
Building Application Layer Connection ...
[16:44:06 699] S: 7E A0 46 03 CD 10 A9 FD E6 E6 00 60 38 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 0C 80 0A 32 36 38 36 36 35 38 36 30 30 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 7E 1F 00 00 1C 33 7E
[16:44:06 983] R: 7E A0 37 CD 03 30 6E D0 E6 E7 00 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 38 1F 00 AC 00 07 6A F5 7E
Building Application Layer Connection: Successful
Setting Normal display mode ...
[16:44:07 103] S: 7E A0 B8 03 CD 32 D0 26 E6 E6 00 C1 02 40 00 01 00 80 15 00 01 FF 02 00 00 00 00 00 01 81 98 01 11 09 11 01 01 00 00 09 02 FF 02 00 20 20 20 20 20 20 30 31 09 11 01 01 00 00 09 01 FF 02 00 20 20 20 20 20 20 30 32 09 11 03 01 00 01 08 00 FF 02 00 20 20 20 20 20 20 30 33 09 11 01 00 00 60 32 1A FF 02 00 38 38 00 00 00 00 00 00 09 11 03 01 00 02 08 00 FF 02 00 31 30 33 00 00 00 00 00 09 11 01 00 00 61 62 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 01 01 00 00 01 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 00 04 1D 00 FF 02 00 00 00 00 00 00 00 21 CB 7E
[16:44:07 776] R: 7E A0 13 CD 03 52 C5 6D E6 E7 00 C5 02 40 00 00 00 01 1E 82 7E
[16:44:07 804] S: 7E A0 B8 03 CD 54 E0 20 E6 E6 00 C1 03 40 00 00 00 00 02 81 A2 00 00 09 11 03 01 00 03 1D 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 00 04 08 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 00 03 08 00 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 20 24 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 34 24 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 48 24 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 20 20 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 34 20 80 FF 02 00 00 00 00 00 00 00 00 00 09 11 03 01 80 48 20 80 7A E8 7E
[16:44:08 292] R: 7E A0 13 CD 03 74 F1 29 E6 E7 00 C5 02 40 00 00 00 02 85 B0 7E
[16:44:08 319] S: 7E A0 20 03 CD 76 E7 29 E6 E6 00 C1 03 40 FF 00 00 00 03 0B FF 02 00 00 00 00 00 00 00 00 00 8F AE 7E
[16:44:08 810] R: 7E A0 14 CD 03 96 CC BA E6 E7 00 C5 03 40 00 00 00 00 03 93 BD 7E
Setting Normal display mode: Successful
Release Connection ...
[16:44:09 885] S: 7E A0 07 03 CD 53 3A 87 7E
[16:44:10 021] R: 7E A0 07 CD 03 73 03 EC 7E
Release Connection: Successful
==========================================================================
Operation 2: Removing GET_BLOCK flag
==========================================================================
DLMS>Connect
TX >>> 7EA01E03CD93F47B8180120501B20601B2070400000001080400000001C1217E
RX >>> 7EA020CD03737134818014050200AF060200AF070400000001080400000001D20B7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400000E1D007DDC517E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000081D00AC000732247E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 10
TX >>> 7EA8B503CD327FF7E6E600C102C100010080150001FF020000000000018198010A0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF020030303820202020200911030100010803FF020030303620202020200911030100010804FF020030303920202020200911030100020800FF02003130339FA67E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA00C03CD3496502020207DCE7E
RX >>> 7EA013CD0372C74CE6E700C502C1000000010F037E
TX >>> 7EA04703CD5620C6E6E600C103C100010080150001FF020001000000022820200911030100020801FF020031303420202020200911030100020802FF02003130382020202020C27E7E
RX >>> 7EA014CD0394DE99E6E700C503C111000000010C207E
DLMS>Disconnect
TX >>> 7EA00703CD533A877E
RX >>> 7EA007CD037303EC7E
==========================================================================
Operation 3: Removing GET_BLOCK and WRITE_BLOCK flags
==========================================================================
Connect
TX >>> 7EA01E03CD93F47B8180120501B20601B2070400000001080400000001C1217E
RX >>> 7EA020CD03737134818014050200AF060200AF070400000001080400000001D20B7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F040000061D007D04B47E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000001D00AC00076A057E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 10
TX >>> 7EA8B503CD327FF7E6E600C102C100010080150001FF020000000000018198010A0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF020030303820202020200911030100010803FF020030303620202020200911030100010804FF020030303920202020200911030100020800FF02003130339FA67E
RX >>> 7EA007CD035113EE7E
TX >>> 7EA00C03CD3496502020207DCE7E
RX >>> 7EA010CD03720A69E6E7000E0106022CD67E
DLMSGURUX>Error getting data. Code 258: Invalid parameter..
DLMS>Disconnect
==========================================================================
Operation 4: Updating seetings PDU
==========================================================================
DLMS>Connect
TX >>> 7EA01E03CD93F47B8180120501B20601B2070400000001080400000001C1217E
RX >>> 7EA020CD03737134818014050200AF060200AF070400000001080400000001D20B7E
TX >>> 7EA04603CD10A9FDE6E6006038A1090607608574050801018A0207808B0760857405080201AC0C800A32323232323232323232BE10040E01000000065F1F0400001E1D007D7D927E
RX >>> 7EA037CD03306ED0E6E7006129A109060760857405080101A203020100A305A103020100BE10040E0800065F1F040000181D00AC000782667E
DLMS>WriteObjComplexAttr 0.128.21.0.1.255 1 2 10
TX >>> 7EA08903CD329976E6E600C102C100010080150001FF020000000000016A010A0911010100000902FF020030303120202020200911010100000901FF020030303220202020200911030100010800FF020030303320202020200911030100010801FF020030303420202020200911030100010802FF020030303820202020200911030100010803FFCBA17E
RX >>> 7EA013CD0352C56DE6E700C502C1000000010F037E
TX >>> 7EA07503CD54B690E6E600C103C100010080150001FF0200010000000256020030303620202020200911030100010804FF020030303920202020200911030100020800FF020031303320202020200911030100020801FF020031303420202020200911030100020802FF0200313038202020202009C27E
RX >>> 7EA014CD0374D07EE6E700C503C111000000010C207E
DLMS>Disconnect
TX >>> 7EA00703CD533A877E
RX >>> 7EA007CD037303EC7E
==========================================================================
Hi, For some reason, your…
Hi,
For some reason, your AMR is sending an invalid block number. You need to check what might cause it. It's hard to tell what might cause this.
BR,
Mikko