How can we improve PI Interfaces?

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.

14 votes
Sign in Sign in with OSIsoft
Signed in as (Sign out)

We’ll send you updates on this idea

Stefen Hillman shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

0 comments

Sign in Sign in with OSIsoft
Signed in as (Sign out)
Submitting...

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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED