AVEVA™ Adapters

Showing 63

Error message should be generated for the Modbus request time out

After request time out, Modbus adapter should generate an error as time out after specified duration set by user.

Guest 11 months ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

Support System States for the Adapter for Azure Event Hubs

The data passed through the Adapter for Azure Event Hubs can be very dynamic in its configuration. It would be useful to be able to send system states to indicate bad data, and possibly the nature of that bad data. In the same way that interfaces ...

Mike Horrocks 12 months ago in AVEVA™ Adapters / AVEVA Adapter for Azure Event Hubs 2 No status

2 VOTE

host adapter(s) as a service

SaaS solution for customers with benefits thereof.

Guest 12 months ago in AVEVA™ Adapters / General 0 No status

2 VOTE

Expand Healthpoint (Device Status) Information of the PI Adapter for Modbus TCP from Component to "Device" Level

When configuring PI Modbus TCP adapter you first define a component level and under this type you define your different devices/machines/sensors. In case of a broken connection to one of the devices the healthpoints currently only deliver the stat...

Mario Amrhein about 1 year ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

3 VOTE

Adapters using Text parser be able to dynamically generate the stream name or ID based on fields of the text parsed

This could be a good feature for any adapters that uses the text parser. MQTT, SDF, Azure Event Hubs. When using JsonPath or Xpath to parse a file or payload the stream name and stream id have to be hardcoded their value cannot be based on a the v...

Randy Giguere about 1 year ago in AVEVA™ Adapters / General 0 No status

4 VOTE

API to check Adapter buffer statistics

We can check buffer statistics with PI Buffer subsystem (pibufss -cfg, qs) and also with PI Connector/Relay, to verify whether Buffer is healthy, events in queue and etc.Adapter does not has any API to check this.

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

3 VOTE

Allow restricting access to the Adapter to only allow configuration by specific users

We want to make sure that we have more control over who can update an Adapter. Is there a way to add a login or other restriction to only permit certain users to be able to modify Adapters, similar to how, with PI Connectors, only specific Windows...

Daniel Lopez about 1 year ago in AVEVA™ Adapters / General 1 No status

1 VOTE

Add the option "Ignore Bad_WaitingForInitialData Status"

In the connectors there was the option "Ignore Bad_WaitingForInitialData Status", as described here. For gen 1 there was a need to edit the config files directly, and in gen 2 the option was integrated into the UI. Instead for the adapter I recent...

sahilp about 1 year 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 over 1 year ago in AVEVA™ Adapters / General 1 No status

2 VOTE

Support for "RTU over TCP" for Modbus Adapter using MBAP header

Challenge: Today, the PI Adapter for Modbus TCP does not natively support " RTU over TCP". It does support Modbus TCP, so as long as the "bridge" properly converts Modbus RTU to Modbus TCP (including the MBAP header), it should work fine. If the b...

Hans-Otto Weinhold over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

Please enter your email address

FILTER BY CATEGORY