PI OPC UA Connector Array support
Add reading capability for OPC UA Arrays. Currently items with “ValueRank“ = 1 are ignored.
This is an important feature to use. Its lack is causing vendor rework.
i was really surprised discovering that the product doesn't support failover neither arrays. IMHO aren't optional features but an essential characteristic of the product. I hope you'll implement in next release.
andrea zuccon commented
We have dropped the OPC-DA and PI interface to use OPC-UA and the "new" PI OPCUA Connector, but the results are not good because the PI connector doesn't handle array and failover.
It is very important to develop these features as soon as possible
It’s very frustrating all the development effort is being focused on newer technologies that have less functionality that their legacy counterparts. I.E. PI OPC DA Interface supports arrays and failover. This forced me to take a highly secure and optimized protocol that is natively available in my equipment, OPC UA, and downgrade it to OPC DA. This costs us extra money and management of the Zero value added Kepware middleware. And now connectors are already being pushed aside in favor of adapters.
Most of our assets that connect with OPC UA uses the array data type for things like error messages and is therefore vital that we get this functionality.
We need to read machine data that can only be accessed as Array. Please Support ARRAY in PI OPC UA connector
Array support is critical to our OPC UA connector usage.
We are currently using PI to access Seimens 840D machines. Most relevant data Load, Power, etc. is stored in array's. Please make this a priority. Thanks!
Christopher Biernacki commented
I have 2 specific use cases in mind:
I have a setup that has many (potentially hundreds) replicas of an identical PLC (i.e. all of the tags associated with them are identical copies). The best way to configure the OPC UA server in this case is by using an array of the PLC tags and replicating it across the many PLCs. Without access to the arrays, it is a very cumbersome process to set up.
Because of the nature of my business we will be provisioning new PLCs (and therefore expanding the OPC UA server) on a moderately frequent basis. Therefore, this cumbersome effort is not simply a 1 and done process. Having the ability to utilize arrays in this case would simplify our efforts.
Additionally, these identical copies have their naming and id's stored in a separate NamespaceArray (which is by name an array). If we could access this array as well that would allow us to better identify the tags created (which use the NameSpaceIndex followed by a string that is not unique i.e 33.Data_Out where the number 33 is the only thing that changes between assets).