Modbus TCP to OPC
Hello,
I am planning to read the data from modbus TCP to third party OPC and from OPC to 800xa scada. Could you advice that third party OPC soft better to use or you have another solution. I tested couple opc softs and for "Integration objects" root (Item ID) are separated with slash and for "Top Server" root (Item ID) are separated with l dot. Which better slash or dot and what is the difference?
Voted best answer
Giving specific recommendations for one software vendor over another is difficult. In this kind of case it is best to be clear .... Free advice on the Internet is worth exactly what you paid for it.
However, from personal experience. Kepware OPC servers seem to work much better than Matrikon products.
However, from personal experience. Kepware OPC servers seem to work much better than Matrikon products.
Answers
Hi,
You can use Matrikon or any other software to convert the modbus TCP to OPC and broadcast the same to 800xA OPC client.
https://www.matrikonopc.com/opc-drive...
Any separator like DOT or Slash can be selected based on the OPC server or client, can be used, if supported. Dot is universal and supported by most of the OPC client/servers. Other than that there is no difference or significance with respect to the separator. It is just used for the representation considering the support available by the 3rd party OPC vendor.
You can use Matrikon or any other software to convert the modbus TCP to OPC and broadcast the same to 800xA OPC client.
https://www.matrikonopc.com/opc-drive...
Any separator like DOT or Slash can be selected based on the OPC server or client, can be used, if supported. Dot is universal and supported by most of the OPC client/servers. Other than that there is no difference or significance with respect to the separator. It is just used for the representation considering the support available by the 3rd party OPC vendor.
Source: System 800xA 6.1 AC 800M OPC Server
Add new comment