PI Interfaces

Welcome to the PI Interfaces feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Interfaces. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Add a configuration option to UniInt so that the user can adjust the minimum wait time for checking for new events from the Update Manager

    This affects the delay in Event\Trigger tags. KCS: Delay in Event Points.

    The largest and most variable delay seems to come from the time the event is written to the PI Server and the time the interface (UniInt) picks, which is between 0ms-1,000ms from my testing. This seems to be due to a built-in, hard-coded, delay in how often UniInt checks for events from the PI Server update manager. The serviceeventsx function that is part of the main UniInt loop only checks for new events once a second; this means that sometimes there is no delay if the…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add a configuration option to the OPC DA Interface so that the user can adjust the maximum advise tag exception delay for Event/Trigger tags

    This affect to delay in Event\Trigger points. KCS: Delay in Event Points.

    When using Event Points, we purposefully do have a delay (if excMax is > 2 s then 2 s else 0.9*excMax) for advise tags (Trigger Point) before they're sent to the PI Server if the event value has not changed since the last scan.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support for VT_UI2 Data type

    As a PI System User, I would like to archive values for the VT_UI2 data type using the PI System.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  4. Automatically recreate advise groups when they are discarded by RSLinx OPC Server

    The Rockwell RSLinx OPC Server may discard advise groups when there are too many bad quality tags or incorrect ItemIDs added to the group. The PI Interface for OPC DA should automatically recreate advise groups after it has determined that the group has been discarded from the OPC server.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  5. Use /opcstopstat when both interfaces in failover pair are shut down

    We would like to have some sort of digital state such as "Intf Shut" written to all OPC tags when both interfaces in a failover pair are shut down.

    Currently, the /opcstopstat and /stopstat parameters (which write a specified state to all tags when the interface is shut down) are ignored if the interface is in failover. We'd like for some sort of status to be written to tags when no data is being collected by either interface.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  6. Clamp Value at Limit

    Ability to clamp or ignore values outside a threshold.
    Example would be to clamp the low value to 'zero' attribute and/or a high value at 'span' - many xmtrs read erratically when at limit (e.g., an empty flow transmitter often reads negative)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support for the VT_UI4 data type

    As a PI System User I would like to archive and analyse VT_UI4 data using the PI System.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  8. Preferring a primary interface failover member

    hen the primary Interface becomes available and healthy again, it becomes "back up". I need the primary Interface to become the "primary" whenever it is healthy.

    https://pisquare.osisoft.com/thread/42591-revert-back-to-primary-data-collector

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  9. Automatic restart of the OPC interface whenever OPC server is restarted

    whenever the OPC server undergoes any restarts or configuration changes, the OPC interface will delete all old connections, groups, etc. and it will establish a new connection to the OPC server, loading all ItemID's etc (as if it is an automatic restart of the interface).

    The reason for this enhancement request:
    if OPC server is restarted or undergone configuration changes, all the handles and subscriptions for advise tags are not valid anymore. The interface would get the advise values in an inconsistent manor (values betwen the OPC server and the interface would show a mismatch)

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  10. PI OPCtoCSV Tool: Subbranch filter depth

    The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. It is possible to filter the items by subbranch however it recurses all sub-subbranches.
    We have an OPC server with around 20k items that we read into PI, however, using the OPCtoCSV tool it takes 12 hours to extract about 2k of these PI tags and 200k other OPC items that we are not interested (mostly just metadata). If we could specify a subbranch and also specify how many levels below this branch to recurse or how many levels above a leaf,…

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  11. PI OPCtoCSV Tool: Filter by OPC ItemID

    The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. It is possible to filter the items by subbranch like the PI APS Connector for OPC DA interface, but unlike the APS Connector, it is not possible to filter by OPC ItemID using the PI OPCtoCSV tool.
    We have an OPC server with around 20k items that we read into PI, however, using the OPCtoCSV tool it takes 12 hours to extract about 2k of these PI tags and 200k other OPC items that we are not interested (mostly just metadata). Filtering…

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  12. OPC DA interface to read data for advise and polled tags at startup

    If digital tags are part of advise groups and the flag to write "Intf Shut" is enabled in the OPC DA interface, then digital tags can read "Intf Shut" for hours/days/weeks, if the value does not change after an interface restart (for example, 2 pumps on the same duty, and they are only swapped every 2-3weeks). The unused pump reads "intf Shut" until it is started.

    It would be better for the OPC interface to get new values for ALL tags after a restart, regardless of whether the value has stayed the same before and after the restart, and timestamp…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support dynamic OPC addresses

    My OPC server's items have the OPC server node name included in the itemID, for example: serverA.AB_1234.PV. I have redundant OPC servers and redundant interfaces (in failover) and would like the tags to refer to the correct OPC address including when the OPC servers fail over. Currently the workaround is to create two sets of tags, each pointing to one OPC server's itemIDs in their instrument tags and then merge the data with AF or a PE.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  14. Monitor data throughput for PI OPC DA interface

    Just knowing if the interface service is running is not enough. Knowledge of data throughput, events/sec, of PI OPC DA interface is needed to know if the OPC DA server is up and running and there are no connection issues.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  15. Parameter for restarting the interface if no connection to the OPC server can be established after a defined period of time

    We use the Phoenix Contact Firewall with the OPC Inspector. When the OPC server restarts or breaks the connection for a few seconds, the firewall blocks all ports except port 135. After initial connection through this port, new firewall rules are dynamically established for DCOM connections. If connection break to OPC Server we have to restart interface manually.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  16. OPC interface retries sending InstrumentTag/ItemID to OPC Server

    The idea is to have PI Interface for OPC DA/HDA to be able to send again Instrument Tag/Item ID after a configurable time when OPC Server is not able to resolve it (AddItem failed). This would be a workaround for an OPC server issue and would help customers avoid the need to restart interface or modify affected tags in order to have tag incorporated into interface's list.

    22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  17. Modifying the functionality of Trend Advise feature for PI OPC interface

    As a PI OPC Interface user I would like to get step-like trends whenever that the Trend Advise parameter is enabled (even with having large exception and compression deviations that filter some of the events) so that I don't need to enable the step attribute for each PI tag.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  18. Allow OPC DA  Output Tags to capture OOO events

    Currently there is no way to send corrected values to the OPC DA Server since they are triggered by snapshot. It would be useful if there was a way to alter the values that get sent in case there are substituted/replaced values.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  19. change the default behavior of the OPC DA interface to use /DC

    per the OPC DA 2.x spec, the OPC server will call us back for all points that have a changes; even those points where we are polling.

    We have a switch to disable the callbacks for points that are not set to advise: /DC

    Can we make that the default?!

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  20. AutoPointSync for OPC DA should work on 64bit servers.

    AutoPointSync for OPC DA does not install or run correctly on 64bit servers. As most new servers are 64bit this would seem to be an essential capability.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED