01-25-2023, 08:06 PM
It seems that Virtuino is ignoring the Unit ID in the MBAP header of a MODBUS response?
I have 2 units in a MODBUS connection that share some of the same value addresses. However, when Virtuino is unable to read these values from one of the units (e.g. due to some network or hardware failure), it has some probability to read them from a response returned by the other unit containing the same address (but maybe even with a different function code).
If I disable or remove the faulty unit from the MODBUS connection, keeping the other one reading data properly, and then modify the server-side code to hard-code the Unit ID in the response to a different value, but Virtuino could still read the data!
This makes a MODBUS connection with multiple units very unstable. Hope this problem can be solved, thanks.
I have 2 units in a MODBUS connection that share some of the same value addresses. However, when Virtuino is unable to read these values from one of the units (e.g. due to some network or hardware failure), it has some probability to read them from a response returned by the other unit containing the same address (but maybe even with a different function code).
If I disable or remove the faulty unit from the MODBUS connection, keeping the other one reading data properly, and then modify the server-side code to hard-code the Unit ID in the response to a different value, but Virtuino could still read the data!
This makes a MODBUS connection with multiple units very unstable. Hope this problem can be solved, thanks.