Data services feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for CONNECT data services. For links to our other feedback portals, please see RESOURCES below.

ADD A NEW IDEA

Clear

Ideas

Showing 10

Allow AVEVA Adapter for Modbus TCP to collect data on INT64 and UINT64 registers

Certain equipment is providing energy data under INT64 or UNIT64 register types. However, the Adapter currently only supports FLOAT64, which is not compatible. We want to be able to configure the Adapter for Modbus TCP to collect data on INT64 and...
Guest about 1 month ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 Future consideration

Ability to create nested parent/child events using AVEVA Advanced Analytics

Support the ability to trigger events from data including parent/child relationships. Support mapping to Event Types that represent the S88 batch standard.
Todd Brown over 1 year ago in Events 0 Needs review

Support retrieving value at start and end of an event for an Asset property of non-numeric data type

As a developer, I'd like to be able to query the value of an asset property at the start or end of an event even when the property is not numeric (Enum, string,etc). Currently, the summaries section of the GraphQL query does not return values for ...
Jessica Rammo over 1 year ago in Events 0 Needs review

Support retrieving stream values at start and end of an event even when the data in the time range exceeds data retrieval limits

As a developer using querying the events database via GraphQL, I'd like the ability to retrieve "property," "start," and "end" summary statistics even when the stream data over my event duration exceeds 250K data events. Currently, I receive the e...
Jessica Rammo over 1 year ago in Events 0 Needs review

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...
Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

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 about 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

support multiple assets with one AssetSupportedType reference

Simplify configuration, one API call instead of multiple for a set of assets.
Glenn Moffett about 1 year ago in Events 0 Needs review

Allow multiple references to holding register for bit extraction

Given a 16bit integer holding register, in certain instances we only care for specific bits rather the integer value. Using the bitmap allows the selection of those specific bits but you can only reference the register once. i.e. In data selection...
Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 8 Future consideration

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 over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

Accept HEX numbers for Register offsets in data selection

Most modbus equipment providers provide information using registers in Hex format i.e. 0x0000 ~ 0xFFFF. It would be nice if the offset could accept this to avoid error in conversions HEX to DEC. Would make things alot more seamless/easier.
Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 Future consideration