AVEVA™ Adapters

Showing 61

Allow the PI Point description to not be populated by the adapter

Implement a configuration flag that allows one to NOT synchronize description from OPC UA server into PI Tag. In instances where the description is empty "", the description cannot be set in PI. Similarly, the description on the OPC UA Server sid...

Gabriel Verreault over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 3 No status

7 VOTE

PI Adapter for OPC UA should preiodically retry to subscribe to each node for which subscription failed at startup

Currently the PI Adapter for OPC UA tries to subscribe to all the OPC UA nodes configured in the Data Selection configuration at startup. However, when as issue occurs during the subscription to an OPC UA node, that node will not be included in da...

Bernard Lafrance 9 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

3 VOTE

displayname/localname for identifier that excludes namespace and data type

Example: OPC UA Server 'Name': 2.0:W-HVAC-AC-1-IO!Wtot Namespace: 2 Datatype: 0 Identifier: W-HVAC-AC-1-IO!Wtot OPC UA Server 'DisplayName': W-HVAC-AC-1-IO!Wtot OPC UA Adapter {Identifier} returns: 2.0:W-HVAC-AC-1-IO!Wtot Required stream name: W-H...

Guest 5 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

3 VOTE

option to not collect quality

Quality is not supported by the OPC UA Server/always zero.

Guest 5 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

18 VOTE

Support outputs/write data from PI Adapters

No description provided

Allison Muraski over 2 years ago in AVEVA™ Adapters / General 3 No status

2 VOTE

Improve the message for performing on demand History Recovery on datacollectionmode: "CurrentWithBackfill" and "CurrentOnly"

Running edgecmd to perform HR on demand on the datasource: datacollectionmode of Non HistoryOnly. will return the following error: Operation Failed: NotFound (404)Unexpected error: Unexpected character encountered while parsing value: 0. path '", ...

Ee Sheing Lee 4 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

8 VOTE

Adapter to failover when there is egress issue

When connection to the datasource are all good for all the adapter failover members, but the primary adapter having issue connecting to the PI web API (egress) for example, adapter does not failover. Unlike PI Interface UNIINT failover, when there...

Ee Sheing Lee about 1 year ago in AVEVA™ Adapters / General 1 No status

8 VOTE

Ua Server force failover / improve failover logic

Let me preface this by saying that I know it is a workaround for a non-compliance with the OPC UA specifications. The point is that the situation described below is unfortunately all too common and the workaround is needed. It often happens that t...

sahilp over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 1 No status

8 VOTE

Prevent PI Adapter for OPC UA from modifying/override stream overrides and metadata upon restart

Problem: I have configured PI Adapter for OPC UA to collect data from an OPC UA Server. Since UoMs are not assigned properly, I created stream overrides in AVEVA Data Hub to assign the proper UoM to the particular stream. I also associated stream ...

Hans-Otto Weinhold over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 2 No status

13 VOTE

PI Adapter for MQTT should include MQTT broker

Having to deal with a MQTT broker between the data source and the PI Adapter adds a single point of failure to the data handling and weakens the data flow end-to-end. From the data source we can guarantee that the data will reach the MQTT broker, ...

Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Please enter your email address

FILTER BY CATEGORY