wolverine

No. This error is very much still there. All you have to do is to run Master snippet at this stackoverflow answer [link] to get this error. Ofcourse, we have to replace modbus_new_rtu with modbus_new_tcp. Also need to comment out modbus_set_slave to reproduce this error with TCP master. The exact sample runs with other Modbus slave simulators like at modbus tools

Error resolved at Modbuspal 1.6c. Thanks a lot. Kindly ignore the previous post.

Detailed error report at https://github.com/zeelos/ModbusPal/issues/4