M
M Griffin
I was thinking of just the message format and the TTY versus socket issues. I hadn't considered message timing, so you have a good point there. Modbus/TCP doesn't have worry about timing as those sorts of issues are up to TCP/IP to take care of. If your rack controller doesn't need "silent periods" between polls you will probably get better throughput as well.
I found a couple of web sites that discuss how they handle Modbus through USB. The first one uses Modbus/RTU:
http://www.fieldofcows.com/index.php?title=USB_Modbus_Interface
This is a board that someone made to do a CNC retrofit.
The second uses Modbus/TCP:
http://labjack.com/support/modbus
This something called LabJack, and in this case they also provide a program which re-directs the socket interface over USB.
Both of these have source code that you may want to look at.
I found a couple of web sites that discuss how they handle Modbus through USB. The first one uses Modbus/RTU:
http://www.fieldofcows.com/index.php?title=USB_Modbus_Interface
This is a board that someone made to do a CNC retrofit.
The second uses Modbus/TCP:
http://labjack.com/support/modbus
This something called LabJack, and in this case they also provide a program which re-directs the socket interface over USB.
Both of these have source code that you may want to look at.
