Reputation: 4583
I am making two SCADA systems exchanging data. I aim to use modbus over tcp since both systems support this protocol. Trouble is, of course, that both systems can only act as modbus master.
With all the fieldbus open source out there, I was surprised that there was no "bridge" utility that would make two masters speak to eachother. I am not particularily well versed in the technologies, but from the outside it appears that it would be trivial to implement a process that would open up two ports and act as a slave to two separate masters.
Both masters would perceive the intermediary as a slave, but the input registers from the POV of Master1 be the output registers from the POV of Master2 and vice versa.
Is there anything, conceptually or protocol wise, that would suggest that this is problematic?
Upvotes: 1
Views: 1138
Reputation: 1
Liking to OPC Server together , just use the KEPware LinkMaster
, the perfect solution to solve this issue.
Upvotes: 0
Reputation: 3730
If both SCADA systems can access the same PLC, then use SCADA1 to write data to some datablock in that PLC, and use SCADA2 to read the same data. The other option is to implement simple MODBUS TCP server in some higher language and put it on some PC where both SCADA systems will have access to it. Alternatively you can run some MODBUS TCP server simulator instead of implementing it on your own.
SCADA systems are not very friendly supporting options that are not build in, so building MODBUS TCP server inside SCADA is in a task range from very difficult to impossible - depending on SCADA system you are using. Most SCADA systems can act as both OPC clients (accessing data from various OPC data sources) and as OPC servers (providing reading/writing option for all their tags to OPC clients). If your SCADA system is like that, then you can use OPC to achieve what you want.
Upvotes: 4