Advanced Modbus Driver always sends transaction identifier '0' when attempting to establish outstation comms - request update to increment value

[acj47]

The Advanced Modbus Driver always sends transaction identifier '0' when attempting to establish communication with a Modbus TCP outstation. This is problematic due to a recent device (see this post for more details) not responding to '0'.

My request is to update the Advanced Modbus Driver to increment the the transaction identifier value when attempting to establish communication. 

Please if this change can be made ASAP in the next release it would be very helpful for my customer! 

[sbeadle]

As discussed the driver behaves correctly, but you can work around this using the Simple driver.