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.
-
Support interfaces on Windows IoT operating system
Allow interfaces and connectors to run on the Windows IoT operating system (formerly Windows Embedded)
24 votesOSIsoft Interfaces and Connectors which support Windows 10 can be run on Windows 10 Professional, Windows 10 Enterprise and Windows 10 IoT Enterprise. However, Windows 10 IoT Core is not supported.
If Windows 10 IoT Enterprise doesn’t meet the needs of your implementation, we encourage you to create a feedback idea for the protocol and implementation that you need to support.
-
PI BACnet interface doesn't say which PI point caused the device to return Error 31
For the PI BACnet interface, the following error can be returned from the device for a particular request and then written into the message logs:
" >> BACnet error packet received. Error Code: 31; Error Desc: Unknown Object; InvokeID: 0"
However, this log message does not include which request caused the error. This error message should include which PI point resulted in this error so that the customer can easily find the relevant point and either correct the configuration or investigate why the device cannot find the object.
17 votesVersion 1.4.4.9 of the PI Interface for Building Automation and Control Network (BACnet) added a new debug setting that logs additional information for rejected ReadPropertyMultiple requests.
In order to enable these extra log messages, the user must manually set /bacnetdbg=0×2000 in the interface’s .bat file. Note that the next time the interface’s .bat file is modified by ICU, this parameter will be gone and the user will have to add it again if they wish to continue to receive this specific additional logging.
-
4 votes
-
Store Tagdata in Batch Eventframe
Our customer want to have the ability to build Batch Reports centrally in AF so that several Applications can access the same data.
We are already transmitting batch data as Event Frames from our DCS batch package like Simatic Batch and others to AF. We also included other reported values from DCS batchpackage like Educts. But some information like actual product amount or other is not available in DCS batch but as classical PI Tag.
We would like to have the possibility to add these information to the procedure of the Batch Event Frames. Either by an extension of the…3 votesThis is already possible today, and requires template configuration on the AF side.
-
Bring in UOM from EMDVBCS source files.
EMBVBCS currently does not bring in UOM from source files to the interface.
3 votes -
Clarification on InstrumentTag attribute
If you use IntrumentTag for the query, it has to be a file containing the query, not the query itself.
You can specify the actual query in Exdesc.1 vote -
Create a new function signaling the Beginning of the Stream
Create a new function signaling the Beginning of the Stream. For example, BOS() returns 1 if this is the first line of a stream; otherwise it returns 0.
0 votes
- Don't see your idea?