OPC to Triconex
Has anyone done a redundant OPC interface between an 800xA system and an Invensys Triconex system? This would be for an 800xA SV5.1/FP4 system. Triconex would supply a redundant pair of OPC servers from their system. This is a one-way data stream from Triconex to 800xA.
I would like to have the Triconex OPC servers in the 800xA domain for both time synchronization and RNRP.
One thought is to install OPC client software on the Triconex OPC servers but I'm not sure how to handle the redundancy issue.
Answers
If the 3rd party can provide two independent OPC servers providing the *exact* same name space, you can use the OPC DA Connector redundancy just as if the PLC had been an AC 800M or any other of our controllers.
One has to remember that System 800xA failover is driven by the result of the GetStatus() call issued from the OPC DA connector to the OPC server every 5th second. Non-good results in connector aborting and restart (=clients will be forced to failover).
If one item gets "bad" in server A, System 800xA will not "fix this" by failing over clients to this item to the B server. System 800xA expects the OPC server to be "100%" good or not good at all.
Add new comment