1
Feature Requests / Restart Modbus TCP connection
« on: November 13, 2017, 02:07:37 AM »
The Modbus TCP plugin works fine, if all devices are already up and running when Mach3 is started.
If a Modbus TCP device is powered on fter the start of Mach3, no connection is established. This leads to irregular function, in worst case to a crash (i.e. VFD does not start spindle...)
I suggest to (at least one or all)
- reconnect to all activated Modbus devices when reset condition is released
- automated reconnect to all activated Modbus devices if they fall off
- automated reconnect to all activated Modbus devices in time periods
- offer a function to initiate a Modbus reconnect by script
- offer a function to test for established Modbus connections
Thanks
Uli
If a Modbus TCP device is powered on fter the start of Mach3, no connection is established. This leads to irregular function, in worst case to a crash (i.e. VFD does not start spindle...)
I suggest to (at least one or all)
- reconnect to all activated Modbus devices when reset condition is released
- automated reconnect to all activated Modbus devices if they fall off
- automated reconnect to all activated Modbus devices in time periods
- offer a function to initiate a Modbus reconnect by script
- offer a function to test for established Modbus connections
Thanks
Uli