Read Push messages

Hi Mikko,

thanks for your hint.
I wonder if your example proposal is the better approach, when my target plattform is Arduino ESP32.
After I set the client address to 0x33FF
I see the debug message "data complete", but the next check for data.moreData returns 4( DLMS_DATA_REQUEST_TYPES_GBT) instead of 0.
if (data.moreData == DLMS_DATA_REQUEST_TYPES_NONE)

I've tried the following setup with now success
client Address 16 does not comes back with data complete, the hint for the strane 0x33FF comes from the Gurux Director

Notify.init(true, 0x33FF, 1, DLMS_AUTHENTICATION_NONE, NULL, DLMS_INTERFACE_TYPE_HDLC);
{
const unsigned char ln[6] = {1, 0, 1, 7, 0, 255};
INIT_OBJECT(pushSetup, DLMS_OBJECT_TYPE_PUSH_SETUP, ln);
}
arr_push(&pushSetup.pushObjectList, key_init(&pushSetup, co_init(2, 0)));
arr_push(&pushSetup.pushObjectList, key_init(&clock1, co_init(2, 0)));

here an example of the HDLC frame
7E A0 84 CE FF 03 13 12 8B E6 E7 00 E0 40 00 01 00 00 70 0F 00 01 BC 51 0C 07 E7 04 17 07 10 15 05 FF 80 00 00 02 0D 01 0D 02 04 12 00 28 09 06 00 08 19 09 00 FF 0F 02 12 00 00 02 04 12 00 28 09 06 00 08 19 09 00 FF 0F 01 12 00 00 02 04 12 00 01 09 06 00 00 60 01 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 00 01 07 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 00 02 07 00 FF 0F 02 12 00 00 A9 E9 7E 7E A0 7D CE FF 03 13 D0 45 E0 40 00 02 00 00 6C 02 04 12 00 03 09 06 01 00 03 07 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 00 04 07 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 01 01 08 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 01 02 08 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 01 05 08 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 01 06 08 00 FF 0F 02 12 00 00 19 3D 7E 7E A0 79 CE FF 03 13 C0 68 E0 C0 00 03 00 00 68 02 04 12 00 03 09 06 01 01 07 08 00 FF 0F 02 12 00 00 02 04 12 00 03 09 06 01 01 08 08 00 FF 0F 02 12 00 00 09 06 00 08 19 09 00 FF 09 08 36 31 37 37 33 37 33 32 06 00 00 00 4F 06 00 00 00 00 06 00 00 00 00 06 00 00 00 0A 06 00 00 12 9B 06 00 00 00 00 06 00 00 00 00 06 00 00 00 00 06 00 00 00 00 06 00 00 05 76 A3 E9 7E

Do you have any additional hint for the Arduino example?

Hi Mikko,
my fault, the copy paste lost the leading 0. I have replaced it with a new one. My current assumption is, that the DLMS message consist of 3 HDLC PDUs.

I was able to dig a bit deeper in the Arduino PushListener.
My little knowledge about the DLMS tells me, my messages are GBT messages, consisting of several HDLC frames. The example assumes that there is exactly one HDLC frame. It evens deletes the following HDLC frame as soon the first one is detected as complete.
Line 139 in the pushListener.ino
if (data.complete)
{
bb_empty(&frameData);
In general this might work if there is enough time between the frames and there is no hardware buffer in the serial. prefered would be a ringbuffer for the frameData.

Nevertheless I guess the main question is about the reassembling of the GBT frame.
May be I can find the answer in the python implementation.