Bacnet Calendar Descriptor (ServerCalendarDesc)
You use the Bacnet Export Manager view of the BACnet Export Table to add, edit, delete, and access exported components.
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.
- Device Status Facets
- Discovery History Type
- Object Name
- Description
Figure 122. Bacnet Calendar Descriptor properties
In addition to the common properties (Status and Fault Cause), this component has these properties.
| Property | Value | Description |
|---|---|---|
| Calender Ord | ||
| 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.), |
| 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 |
| Description | text | Adds information to more fully explain an object’s purpose, function or location.
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.
|