Best practice approach? Use OPC Client objects compared to PCS

Question

Hi Aveva Team and community, 
 Is there a general recommendation if it's better to use opc clients objects in the app server or directly use the PCS framework (scope) to access items? In general I am interested in performance or debugging possibilities or stability. 
 What are the differences between SuiteLink v2/v3 and iData v2/v3? 
 Thanks Peter

rickard.norin · Accepted Answer

Hi, 
 PCS is our new approach to access data through the Communication Drivers and it is still evolving. Current limitations to be aware of is that IData currently is limited to approx. 50,000 data changes per second and we do not (yet) provide a built-in redundancy mechanism for it. 
 By comparison, using the OPC client to access the driver supports a higher throughput, and using the SuteLink client is even faster than that. The DI objects include the Redundant DI Object to provide redundancy and automatic failover between DI objects. 
 We are continuing to expand on PCS capabilities, to have the Communicaiton Drivers more tightly integrated to each product, for a simplified architecture, and to eliminate some of the extra configuration work currently required for DI objects. We're also expanding on communication patterns, such as the recently introduced IMethods interface which faciliates OPC UA Methods client and will soon also facilitate method calls to RTUs through AVEVA Telemetry Server.

Best practice approach? Use OPC Client objects compared to PCS

Top Replies