Read and write
BACnet schedules

One vendor's tool per schedule

Schedule and Calendar objects are standard BACnet, but most tools that can edit them belong to whichever controller vendor installed the system.

A site with controllers from two or three manufacturers means two or three engineering packages, each with its own login, its own quirks, and often a fee to unlock write access. But a Schedule object's actual data — seven days of time/value pairs, a default, and a list of exception schedules pointing at Calendar entries — is defined the same way by the BACnet standard regardless of vendor. BACManager reads and writes that data directly, generically, on any BACnet device that exposes it.

A weekly grid, not a hex dump

Open a Schedule object from the property browser and it opens straight into an editable view, not raw bytes.

Holidays, ranges and recurring dates

Calendar objects show their date entries in the same editable style: specific dates for one-off holidays, date ranges for a shutdown period, and recurring weekday patterns for things like "every last Friday of the month." Add or remove entries and write the calendar back to the device — the schedules that reference it via exception schedules apply the new dates the next time they evaluate.

Validated byte-for-byte

A wrong bit in a Schedule or Calendar encoding is the kind of bug that only shows up weeks later, as a zone running on the wrong hours with no error anywhere. BACManager's schedule and calendar codec has been checked byte-for-byte against independent reference BACnet stacks, so what you write is exactly what the standard specifies — not an approximation that happens to look right in one viewer.

Schedule editor — FAQ