Hi Mikko,
I am using GuruX director v8.2.2111.1801. I have made a setup to to periodically pull data from 5 meters over 4G TCP wrapper. I sometimes observed that communication is failing because of additional garbage bytes appended at the beginning of the frame. I tried probing meter to see if meter is sending these garbage values but didnt find any garbage outputting from meter. Your view on understanding the problem would help solve the issue.
Also one more observation when it happens is, part of previous response bytes gets appended to subsequent responses.
WRAPPER is expecting that TCP/IP channel is reliable. There are no check-sum, etc in WRAPPER, but I know what you are talking about. Sometimes there might be extra data. I have seen strange data coming before and after the DLMS data in GRPS network.
The easy fix is to improve the antenna and communication channel reliability.
In your example case, there are only extra bytes but I have seen cases where data is corrupted and because the checksum is missing from the WRAPPER it will cause serious problems.
It's possible to find the WRAPPER frame, but I would say that the best way to handle this is to close the connection and read the meter again. You can't be 100% sure if the received data is corrupted or not.
The bad this is that this is happening more often as the frame size increases. So try to read as little data as possible.
Hi,
Hi,
WRAPPER is expecting that TCP/IP channel is reliable. There are no check-sum, etc in WRAPPER, but I know what you are talking about. Sometimes there might be extra data. I have seen strange data coming before and after the DLMS data in GRPS network.
The easy fix is to improve the antenna and communication channel reliability.
In your example case, there are only extra bytes but I have seen cases where data is corrupted and because the checksum is missing from the WRAPPER it will cause serious problems.
It's possible to find the WRAPPER frame, but I would say that the best way to handle this is to close the connection and read the meter again. You can't be 100% sure if the received data is corrupted or not.
The bad this is that this is happening more often as the frame size increases. So try to read as little data as possible.
BR,
Mikko