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 votes
Allow a way to bulk edit EFGen configuration, preferably in a spreadsheet format.14 votes
To enable us to move from PIBAGEN to EF Gen interface, we need 'merge consecutive' to work when running in PIBAGEN mode. Currently none of this functionality is working, and the following known issues is already found.
119695 - Merge consecutive at unit procedure level does not merge all consecutive unit procedures.
124407 - Unit Procedures may be improperly merged in PIBaGenCompatibility mode.
119363 - Consecutive subbatches can get merged incorrectly
Please make an updated version of the 'PI Event Frames Generator' where this important functionality is working.5 votes
The next version of EFGen will more closely mimic PIBaGen when running in PIBaGen compatibility mode.
- Don't see your idea?