Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status Completed
Product PI Interfaces
Categories General
Created by Guest
Created on Aug 17, 2022

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.
  • ADMIN RESPONSE
    Aug 17, 2022
    Version 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=0x2000 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.
  • Attach files