G
I've worked with Modbus/TCP for a while, and I think it's very easy to implement in most control applications where I need a robust link for my data from one controller to another (or between PC's). I've also tried different OPC servers and client programs(Scada), and have had some bad experience with them. The main problem have been that either the server or client program have been 'shut down' or 'locked/frozen' by the OS (Windows is the worst one). I have a great need to supply my costumers with a large MTBF number.
When I ask the OPC-Client/Server sales personell about the stability of their products, they of course say it's 'the state of the art' and that the OPC is built on 'proven software technology' and Standards. When I talk to the technicians (of the same suppliers) they tell me that OPC is 'not yet' fully accomplished as 'Standard' and some of them prefer that I use Modbus/TCP for connection to peripher equipment for collection of data for instance from one of their server software.
I've tried this, and it seems to be correct in most cases.
My question is therefore (finally) this :
What is your experience as users or suppliers in the issue of Modbus/tcp versus OPC for transportation of data between different systems?
When I ask the OPC-Client/Server sales personell about the stability of their products, they of course say it's 'the state of the art' and that the OPC is built on 'proven software technology' and Standards. When I talk to the technicians (of the same suppliers) they tell me that OPC is 'not yet' fully accomplished as 'Standard' and some of them prefer that I use Modbus/TCP for connection to peripher equipment for collection of data for instance from one of their server software.
I've tried this, and it seems to be correct in most cases.
My question is therefore (finally) this :
What is your experience as users or suppliers in the issue of Modbus/tcp versus OPC for transportation of data between different systems?