Add the function to able to act as (“scanner”).
At this moment the connect can only act as an adapter, that means that It can't collect data from other device that also are connector is an adapter.
As an advanced user, I would like to be able to specify a user-defined data type for the array sent to the PI Connector for EtherNet/IP. For example, if I have a 32-bit array composed of one INT and two SINTs, I would like to be able to configure the connector to parse this array correctly. Currently the data type specification of the array is limited to one data type (DINT, INT, FLOAT, or SINT).9 votes
Currently, the connector will create 124 or 248 tags per data source, regardless of how many meaningful data points are actually in the data set.
This greatly limits the use of the connector to any customer that is not an EA.5 votes
For the PI Connector for EtherNet IP you can have up to 100 data sources. Typing in all of them is tedious. It would be nice if we could copy/paste information from Excel OR have a structured import/export file to the data source list.4 votes
String data, such as serial numbers, are supported by the EtherNet/IP protocol and are often collected to help understand what was being made by a piece of equipment at any given time.4 votes
The EtherNet/IP protocol does not specify timestamps when data is transmitted, the connector currently assigns the timestamps base on when the data is being processed.
This leads to the following issue, if the network/computer/etc gets busy, we will have several values be processed at the same time. Thus, many values with the same timestamps.
A possible work around is that the connector specifies time frequency, for example values come 10ms apart.
If the connector read this frequency, the connector could possibly assign better timestamps for values that are processed at the same time.3 votes
Need EtherNet/IP connector to be able to read and write.
Currently EtherNet/IP connector is read only.2 votes
Related enhancement request: https://feedback.osisoft.com/forums/555139/suggestions/37362121.
There are use cases where the need for exception go beyond simply reducing network traffic achieved by the current wire-level compression. The Ethernet IP connector has the potential to send very high frequency data which often exists in the real-world as noise. Other PI System components that operate off of snapshot data such as the PItoPI interface and various visualization products can be negatively impacted by this lack of a data filter.1 vote
- Don't see your idea?