The client side framecounter is set to the server side framecounter (extracted from the PDU) + 1 instead of just being incremented. The RX and TX maintained by the device are different.
You are right on this. Problem is that there are several meter models that we can't read if we accept this change. Some meters are sending same frameCounter value that client sends. Some are sending client frameCounter + 1 and some meters have own counter. Some meters don't increase value at all. They are using static value.
I'll check if we can add two counters for server-side and client-side works as it works now, but it take some time because we don't want to break anything and tests take time.
client side frame counter not automatically handled correctly
Hi,
You are right on this. Problem is that there are several meter models that we can't read if we accept this change. Some meters are sending same frameCounter value that client sends. Some are sending client frameCounter + 1 and some meters have own counter. Some meters don't increase value at all. They are using static value.
I'll check if we can add two counters for server-side and client-side works as it works now, but it take some time because we don't want to break anything and tests take time.
BR,
Mikko