Best practice approach? Use OPC Client objects compared to PCS

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.

Thank you Rickard,

How many data changes the OPC client is capable of then?

Thanks
Peter

I don't have an exact metric for that. We have seen around 150,000 changes per second with SuiteLink and my impression is that OPC is somewhere between PCS and SuiteLink.

You also asked about differences between versions. The main difference for SuiteLink is that v3 implements TLS encryption. I'm not sure about IData versions but it too is encrypted these days and there may have been some improvements to the transport channel.

I don't have an exact metric for that. We have seen around 150,000 changes per second with SuiteLink and my impression is that OPC is somewhere between PCS and SuiteLink.

You also asked about differences between versions. The main difference for SuiteLink is that v3 implements TLS encryption. I'm not sure about IData versions but it too is encrypted these days and there may have been some improvements to the transport channel.