ProposedMaxPduSize value

Forum Rules

Before commenting read Forum rules

Don't comment the topic if you have a new question.

You can create a new topic selecting correct category from Gurux Forum and then create a new topic selecting "New Topic" from the top left.

By Ingvar , 20 February, 2023
Forums
Gurux.DLMS

There is a problem. When polling the Meter correctly polled only on the first cycle, on the second authorization does not pass.
After studying the log it turned out that the problem is in the transmitted value ProposedMaxPduSize - the first cycle passes the value 65535, authorization passes, but the second cycle is 100 and the counter responds with an error.
As I understand this value is returned by the device itself as the NegotiatedMaxPduSize parameter, and your stack then uses this value.
It turns out that this is an error in the device?
I am attaching the log at the link.
https://drive.google.com/file/d/1KoHde_Jt0VaQCFGQxhv4cAOxiA2xJyt5/view?…

Hi,

I checked this and ANSI C++ doesn't save the initial values at the moment if the release is not called. This is changed for consistency. The new version is released tomorrow where this is changed.

BR,
Mikko