|
I really like the Modbus protocol which is very simple and popular. I would like to know in which case you find Modbus appropriate or not. Thanks in advance |
|
We use Modbus/TCP in our non-proprietary control system for the following reasons:
The downsides of Modbus/TCP (in my opinion) are:
|
|
I used Modbus about 10 years ago in a DOS program written in Pascal to talk to a Modicon PLC. That was the serial version. The advantage was that the spec was available for free. Now Modbus/TCP is popular and since it's also open, there are lots of 3rd party libraries you can use to connect directly to PLCs without the need for an OPC server. Great for interfacing with a custom data collection system. |
|
Modbus is a very versitile and very cheap communication protocol, especially when trying to tie multiple devices or controllers together in some form of network. There are many limitations when connecting using a RS-232 connection; however, the Modbus/TCP option removes many of those limitations. I have seen a few different advantages to using the Modbus/TCP protocol in either a Modbus PLC Controller / Modbus Meters / Modbus Management Systems. You can create a very large Node network on a small budget compared to ethernet or some other protocol. Another useful tool is the designation of the Addresses used in Modbus. If every device is programmed the same, or even if there are slight changes, all you need to know if the register values. When programming an HMI / OPC all you would need to know is the NODE / IP Address and a some type of spreadsheet with the register addresses. You can then program remotely without any problem. While I don't prefer Modbus over other protocols, I can understand why it is still in use. |



See http://controlsoverload.com/questions/19/what-is-your-favourite-on-machine-distributed-i-o-network. Modbus isn't on the list yet!