Learn about the Community. Join our Core Community to Get Started

Schneider Electric Exchange Community

Discuss and solve problems in energy management and automation. Join conversations and share insights on products and solutions. Co-innovate and collaborate with a global network of peers.

Register Now
Knowledge Base
cancel
Showing results for 
Search instead for 
Did you mean: 

BACnet Alarm User Actions, Attachment and Presentation

Issue

BACnet Alarm User Actions, Attachment and Presentation

Product Line

EcoStruxure Building Operation

Environment

  • Alarm handling and Presentation Server BACnet
  • User Action, Attachment and Presentation

Cause

If the BACnet Alarm User Actions appear to be working incorrectly, the "Alarm handling and presentation" setting may be incorrect

Resolution

BACnet Alarm Enrollments only


If the User Action, Attachment and Presentation from the Alarm itself are required then Alarm handling and presentation should be set to "Intrinsic" as below

If the User Action, Attachment and Presentation from the BACnet Notification are required then Alarm handling and presentation should be set to "BACnet Notification object" as below

NOTES
When a b3 is created or a 3rd party device uploaded within Building Operation, the Alarm Enrollments and Alarm Notification Objects include Alarm handling and presentation properties (Presentation, User Action(Cause note, Action Notes, Comments, and Checklist) and Attachments tabs). These properties are stored only in the Building Operation Server (AS or ES) database.

To use these properties, the "Alarm handling and Presentation" (in "Properties" tab “Basic”) should be set to "Intrinsic", as above, top example.

The settings are saved only in the Building Operation database - as part of the notification class proxy, or the event-enrollment (or point object in the case of intrinsic alarms) proxy. Cause notes, action notes, comments, and checklist are Building Operation specific data, not part of the BACnet protocol. So there is no way for it to be sent to the device (b3, 3rd party or otherwise).

Labels (1)
100% helpful (1/1)