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.
-
Improve DNP3 Output performance
Currently DNP3 outputs are done one event at a time. We could improve performance by either supporting multiple DNP messages per TCP packet or multiple analog output commands per DNP message.
2 votes -
RDBMS time stamp precision
Currently the ODBC connection is configured with a SQL date time parameter when retrieving the TS parameter (snapshot time stamp).
Due to the fact lots of sources system having more precision in their time stamps, it makes it hard to compair source time stamp to the pi time stamp (precision and rounding issue in SQL).
I request to add support for sql datetime2 into the ODBC connection, or an option to read the time from the snapshot in seconds since 1.1.19702 votes -
Provide support for Modbus function code 20
Provide support for Modbus function code 20
2 votes -
POINDexter app be modified such that addresses beyond 64000 can be used
POINDexter application be modified such that addresses beyond 64000 are able to be ‘tested’ / polled, rather than having to configure a tag to read those registers
2 votes -
Support string tags in PI Interface for CSI UCOS
The newest version of UCOS now supports string tags. Currently the CSIUCOS interface (1.0.0.22 as of writing) does not support these types of tags.
2 votes -
PI Interface for GE HABConnect support of SCTIME request
Currently, the PI Interface for GE HABConnect supports FLDTIME requests, which provides the timestamp of the field device. In the absence of this, the default is the timestamp of the Sampler when HAB API makes an unsolicited update to the interface.
If SCTIME was a request that was supported, the timestamp that the sampler received data from the field device could be returned instead. This would be helpful for two reasons.
1. As an alternative to FLDTIME: SCTIME would standardize the timestamps coming in when field devices are not on synced time clocks
2. As an alternative to the update…
2 votes -
Source and destination tag mapping list
Customer would like the ability to have PItoPI create a list of tags that includes the FULL name of the source tags, as well as the destination tags they are mapped to. This will greatly assist in managing tags that are being sent to a remote customer.
2 votes -
Accept weeks and years in the relative time syntax for history recovery start and end times
For whatever reason, times such as *-1w or *-1y are not accepted, but times such as *-1mo and *-1d are OK.
Please make the PI Interface for RDBMS accept the same relative times that other PI programs accept.
2 votes -
Provide localized versions of PI ICU
For instance, cyrillic characters are not rendered correctly in spite of appropriate regional settings.
2 votes -
UFL Interface - Option for PRINT statement to not write to PI SDK log
I use PRINT statements in my UFL ini files to help identify points that need to be created or edited in our PI System. The ini file has useful parameters to help me manage the size of UFL logs on the disk. Unfortunately all the PRINT messages also get written to the PI SDK log. All these messages cause the log files to grow to very large sizes (a few hundred MB daily). It also makes the logs difficult to read if we need to find another issue.
Could we have the option to have PRINT write only to the…
2 votes -
Add option to select interface behavior for bad timestamps (PI RDBMS)
When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the interface attempts to use the current timestamp instead and logs the following error:
"pitm_settime() error - 15002. Using current time."
The interface should instead include an option that controls what to do in this situation. The potential options would be to either discard the event entirely after logging an appropriate error or to use the current timestamp of when the event was retrieved (Also logging an appropriate warning).
2 votes -
add SNMPTrap interface to live library
I had a case (794719) with a customer who would like to have SNMPTrap interface available on our live library so that he can browse online instead of downloading the user manual.
Thank you!2 votes -
Cal ISO: allow instruction level data to use batch level start time
allow instruction level data to use batch level start time. Add an option to allow this. use case: the instruction level start time is the time when the DOT should be ramped up or down. The batch start time is a few minutes before that timestamp. To get the turbines adjusted in time, they need to use the batch start time. This gives the operator enough time to adjust the set point and have the new target met by the instruction start time.
2 votes -
When Citect Interface loses connection to a device, throttle errors relating to failed tag reads
OSI PI Citect Interface
The interface will log an entry to the message log for every tag that it can't source data for. This is fine for a small number of tags that have not been able to read data from Citect. However, when a Citect Unit (eg PLC) goes offline and there are thousands of tags assigned to that unit, every single tag that is scanned is logged with the same message generating thousands and at times hundreds of thousands of log entries in a short time frame, eg every second. This results in a very, very large log…
2 votes -
CSI UCOS Enhancement: Implement Bumpless Download
The new CSI UCOS API now supports a "bumpless download".
"CSI has recently added what they call a “bumpless download” feature to their UBrowser application that the interface uses to communicate with the database. What this does is allows the database to be updated without stopping the service. "
Please implement this feature.
Note: This was previously Enhancement 121741.
2 votes -
Create a new function indicating if the string can be turned into a number
Create a new function indicating if the string can be turned into a number. For example, IsNumber() function could return 1 if the string can be turned into a number 0 if not.
2 votes -
Enhancement for OPC HDA to add switch '/outputsnaptime'
OPC HDA Interface would be enhanced to use switch '/outputsnaptime'. For output tags, the interface would use the timestamp from the original event that triggered the output to timestamp the data.
Note: This was previously Enhancement 124754.
2 votes -
Increase max. service ID for PI UFL Interface
According to https://customers.osisoft.com/s/knowledgearticle?knowledgeArticleUrl=3645819457236571808-241124 , any number larger than 99 can NOT be specified for PI UFL Service ID. It would be better for us if the larger number such as 300 could be specified.
1 vote -
PI OPCClient able to sort List of all structure instances
PI OPCClient able to sort List of all structure instances. Currently: Chronologically is pretty annoying.
While listing the content of opc server structure, the folders are not listed alphabetically.
While there are many items, export is not possible - pi opc client crashes
This could enhance the user experience and be more user friendly.
Searching takes a long time.
1 vote -
PI Werum PAS-X Batch Interface - Event frame creation for Interface Basic Functions
Allow the PI Interface for Werum PAS-X Batch to create event frames for Interface Basic Function created by the Message Based Shopfloor Integration (MSI) feature package for Werum PAS-X. The Interface Basic Function describe the communication between PAS-X and the ordering system e.g. DCS, with order parameters for workflows, status and exceptions etc.
1 vote
- Don't see your idea?