Bacnet Event Enrollment Descriptor (bacnet-BacnetEventEnrollmentDescriptor)

This dynamically created export descriptor exposes an Event Enrollment component. The Event Enrollment descriptor cannot be added manually using the Bacnet Export Manager view of the BACnet Export Table. You can only create an Event Enrollment object dynamically using a remote Create-Object request.

The Event Enrollment object is used for working with information related to the management of events in BACnet systems. For example, this object can be used to create: alarms, external alarms, and algorithmic alarms. Or it might be used to describe an event that might be an error condition ("Input out of range") or an alarm that other devices need to know about. It can directly tell one device about the event or use a Notification Class object to tell multiple devices.

A BACnet client can send a request to a BACnet controller to dynamically create this component by using either an Object Id or Object Type. Optionally, the request may simultaneously specify initial values for one or more of a specified set of component properties.

Only the following read-only properties qualify for initial value setting during object creation. Requests that include non-qualified properties from the client cause a request to fail.

  • Device Status Facets
  • Discovery History Type

  • Object Name
  • Description
  • Notify Type
  • Event Parameters
  • Object Property Reference
  • Event Enable
  • Notification Class

You use the Bacnet Export Manager view of the BACnet Export Table to add, edit, delete, and access exported components.

Figure 134.   Bacnet Event Enrollment Descriptor properties
Image

In addition to the common properties (Status and Fault Cause), this component has these properties.

Property Value Description
Event Detection Enable true (default) or false
Turns detection of an input event on (true) and off (false) for analog, binary and multi-state descriptors.
Bacnet Status Flags read-only indicator and check boxes
Configures four status flags for BACnet. These options are available to enable detection of specific status conditions.
Event Enrollment Ord Slot or Handle Defines the path to the source Event Enrollment object.
Object Id drop-down list and number (from 0 to 4194302)
Identifies each device and component by the type of entity (Object Id) combined with a unique Instance Number.

For devices (controllers, instruments, meters, etc.), Instance Number must be unique within the BACnet internetwork. For components (points, schedules, analog inputs, files, groups, multi state inputs, etc.), it must be unique within the device.

Object Name text in the format name.name.name.name (default includes the entire component path in the station using period (“/) delimiters between parent.child levels)
Identifies a BACnet object. This name should be unique within this specific device.

For components, this name includes the entire component path under the station’s Config using period (.) delimiters between parent.child levels. This enforces (externally) the BACnet requirement for unique names for all objects in a device.

For a proxy point, this is the default name in the station.

You can shorten or edit Object Name, however, each Object Name must be unique among all server descriptors under the Export Table.

Description text
Provides additional information, which could include the camera’s geographical location or other unique information.
 NOTE: After creation (adding) BACnet file descriptors, note that each descriptor also has additional properties accessible in its property sheet, along with those seen in the Add and Edit window.  
Type of Event read-only Indicates the referenced object event type, such as an error or alarm condition.
Notification Class Id text Specifies the notification class used for routing when handling and generating event notifications for this object.
Reliability read-only
Provides information when an error interrupts communication with a device.

No Fault Detected indicates that things are OK.

Unreliable Other indicates that the exported BACnet object appears in fault. This might happen, for example, if the source (exported) component is a proxy point under some other driver, and device communications are down or if the point has been disabled.

In this case, the BACnet export descriptor retains a status of ok.