In general, the library does not handle frames of this type correctly. For example, when receiving a frame with NS and NR == 0, the client or server must respond with the same frame and not increment the frame number.
ANSI C will pass the tests because it's usually used with microcontrollers and that is the language that our clients are using.
ANSI C++ is used usually in client-side applications. I need to think should ANSI C++ also pass the DLMS tests.
Since our controller supports embedded linux, it was decided to use the C++ library. Here we are faced with the above problem, one of them.
Take a closer look at my PR on Github
In your code, when receiving an RR frame with N(R), the frame increment occurs, but it should not. RR should be returned with N(R) equal to the current receiver frame. If previous frame we send wasn't I frame.
Hi, Can you tell me a little…
Hi,
Can you tell me a little bit more? Are you talking from GXDLMSDirector T_HDLC_FRAME_P2 test?
BR,
Mikko
In general, the library does…
In general, the library does not handle frames of this type correctly. For example, when receiving a frame with NS and NR == 0, the client or server must respond with the same frame and not increment the frame number.
Hi, ANSI C will pass the…
Hi,
ANSI C will pass the tests because it's usually used with microcontrollers and that is the language that our clients are using.
ANSI C++ is used usually in client-side applications. I need to think should ANSI C++ also pass the DLMS tests.
BR,
Mikko
Since our controller…
Since our controller supports embedded linux, it was decided to use the C++ library. Here we are faced with the above problem, one of them.
Take a closer look at my PR on Github
In your code, when receiving…
In your code, when receiving an RR frame with N(R), the frame increment occurs, but it should not. RR should be returned with N(R) equal to the current receiver frame. If previous frame we send wasn't I frame.