Skip to content

BACnet Schedules

3.9.9

NF discovers BACnet schedule objects during device scanning and manages them through the centralized schedule service. This page covers BACnet-specific behavior; see the schedule overview for general schedule concepts and the sync documentation for detailed sync operations.

Discovery

When you scan a BACnet device's object list, any schedule objects (object type schedule) are automatically imported into the schedule service. The import reads the weekly schedule, exception schedule, default value, effective period, and out-of-service flag via ReadPropertyMultiple.

Imported schedules appear on the Schedules page with a BACnet source badge. Rescanning the same device updates existing schedules rather than creating duplicates.

Schedule Editor

Sync Modes

Imported schedules default to read-only sync. You can change this to bidirectional to allow editing rules in NF and writing them back to the controller. See BACnet Schedule Sync for details.

Local BACnet Schedule Objects

Local schedules created in NF can be exposed as BACnet schedule objects on the gateway, making them readable by external BACnet clients. Enable Expose as BACnet in the schedule editor. See Exposing Local Schedules.

Data Conversion

NF converts between BACnet and internal representations automatically:

  • Dates: BACnet uses year-1900 encoding on the wire; NF stores full calendar years.
  • Times: BACnet hundredths of a second are converted to milliseconds.
  • Values: All BACnet application data types (real, unsigned, boolean, enumerated, character string, etc.) are supported.
  • Special events: BACnet calendar entries (single date and date range) map to NF special events with priority.