Hi Mikko,
You mentioned in this chain that you had tested with 256 and 512 maxPduSize. Can you confirm that it works with 64-bytes or 128- bytes PDU size as well!
I get endless transaction without any data due to out of memory case.
GXDLMSDirector 9.0.2505.0602
Log created 13:00:38
13:00:38 Send AARQ request.
00 01 00 01 00 01 00 40 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 01 AC 12 80 10 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 31 BE 10 04 0E 01 00 00 00 06 5F 1F 04 00 00 1E 5D 00 80
13:00:41
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 1C 19 00 80 00 07
13:00:41 Parsing AARE reply succeeded.
13:00:49 --- Collecting objects. ---
13:00:49 Collecting objects
00 01 00 01 00 01 00 0D C0 01 C1 00 0F 00 00 28 00 00 FF 02 00
13:00:52
00 01 00 01 00 01 00 92 C4 02 C1 00 00 00 00 01 00 76 01 4D 02 04 12 00 0F 11 02 09 06 00 00 28 00 00 FF 02 02 01 0B 02 03 0F 01 16 01 00 02 03 0F 02 16 01 00 02 03 0F 03 16 01 00 02 03 0F 04 16 01 00 02 03 0F 05 16 01 00 02 03 0F 06 16 01 00 02 03 0F 07 16 01 00 02 03 0F 08 16 01 00 02 03 0F 09 16 01 00 02 03 0F 0A 16 01 00 02 03 0F 0B 16 01 00 01 06 02 02 0F 01 16 00 02 02 0F 02 16 00 02 02 0F 03 16 00 02 02 0F 04 16 00 02 02 0F 05 16 00 02 02 0F 06 16 00
13:00:52 Get Next Data block.
13:00:52 Collecting objects
00 01 00 01 00 01 00 07 C0 02 C1 00 00 00 01
13:00:53
00 01 00 01 00 01 00 15 C4 02 C1 00 00 00 00 02 00 00 00 C4 02 C1 00 00 00 00 02 00 00
13:00:53 Get Next Data block.
13:00:53 Collecting objects
00 01 00 01 00 01 00 07 C0 02 C1 00 00 00 02
13:00:55
00 01 00 01 00 01 00 15 C4 02 C1 00 00 00 00 03 00 00 00 C4 02 C1 00 00 00 00 03 00 00
13:00:55 Get Next Data block.
13:00:55 Collecting objects
00 01 00 01 00 01 00 07 C0 02 C1 00 00 00 03
13:00:56
00 01 00 01 00 01 00 15 C4 02 C1 00 00 00 00 04 00 00 00 C4 02 C1 00 00 00 00 04 00 00
13:00:56 Get Next Data block.
13:00:56 Collecting objects
00 01 00 01 00 01 00 07 C0 02 C1 00 00 00 04
13:00:59
00 01 00 01 00 01 00 15 C4 02 C1 00 00 00 00 05 00 00 00 C4 02 C1 00 00 00 00 05 00 00
13:00:59 Get Next Data block.
13:00:59 Collecting objects
00 01 00 01 00 01 00 07 C0 02 C1 00 00 00 05
13:01:00
00 01 00 01 00 01 00 15 C4 02 C1 00 00 00 00 06 00 00 00 C4 02 C1 00 00 00 00 06 00 00
13:01:00 Get Next Data block.
13:01:00 Collecting objects
00 01 00 01 00 01 00 07 C0 02 C1 00 00 00 06
13:01:01
00 01 00 01 00 01 00 15 C4 02 C1 00 00 00 00 07 00 00 00 C4 02 C1 00 00 00 00 07 00 00
13:01:01 Get Next Data block.
-----------------------------this keeps going on forever!----------------------
Correction in title: While…
Correction in title:
While reading object list with the GxDlmsDirector, the server (base on
Gurux DLMS for ANSI C) is not able to provide object list with maxPduSize 64 or 128 (or anything below 156-bytes PDU size).
Hi, If you are not using…
Hi,
If you are not using malloc, the content of the object attribute must fit into PDU. To optimise the memory usage, the content of the attribute is saved directly to the PDU.
The minimum PDU size depends on the read attribute. Using PDU sizes smaller than 256 is not recommended because it will increase the number of frames between the client and meter.
BR,
Mikko