Integrate BACnet Schedules into Scheduler

A BACnet device can be configured to incorporate its own schedule as a set of schedule-object and calendar-object properties. If you install the BACNET driver, Citect SCADA can read and write to these object properties at runtime. This allows you to integrate BACnet schedules into Scheduler.

This functionality is enabled via the following process:

• A BACnet I/O device is configured in Citect SCADA and connected via the BACNET driver.
• Variable tags and equipment definitions that represent the device's schedule and calendar objects are configured on the Citect SCADA I/O server. You can achieve this using the Import Variable Tags tool.
• The Citect SCADA reports server subscribes to the tags on the I/O server and generates schedule entries in Scheduler.
• Any changes to the schedule entries are written back to the BACnet device via the I/O server.

Note:
• The present value for a BACnet schedule is evaluated in the BACnet device, not by the Citect SCADA system. This means Citect SCADA entry actions are not supported for equipment states that are associated with a BACnet schedule.
• If a BACnet schedule object has exception schedules configured, they are presented in Scheduler using Special Days.
• If the date range specified for an exception schedule or calendar object is excessively long, it can affect system performance. For this reason, only the first six months of a date range will display in Scheduler.
• If the date range specified for an exception schedule or calendar object has a start date that is beyond three years in the future, it will not display in Scheduler.
• Wildcards (for example, "*") are not supported by the Scheduler.
• Exception schedule or calendar objects that use a WeekNDay (WD) configuration will not display in Scheduler.

To integrate BACnet schedules into Scheduler:

1. Install the latest version of the BACNET driver.

The latest version of the BACNET driver is available from the Citect SCADA Driver Web.

2. Add the BACnet device to your project as an I/O device (see Using the Device Communications Wizard).
3. Create the variable tags and equipment required to support the BACnet calendar and schedule object types.

You can automatically generate the required tags and equipment using the Import Variable Tags tool (see Importing Variable Tags from an External Database). If you use this approach, you need to observe the following:

• The source Database Type specified on the Import Variable Tag dialog needs to be set to "BACnet".
• The BACnet Device Configuration dialog is used to configure the tag import. This dialog is accessible via the Browse button next to the External Database field. Information on how to use this dialog is accessible via the Help button.
• Select the Import BACnet Schedule Instances as Equipment option to create the equipment required to support the schedule entries in Scheduler.
4. Specify a data type for each BACnet schedule object so that they match the data type configured for the corresponding schedule entry on the BACnet device.

This can be done via Equipment Editor by modifying each Schedule Instance in the Equipment View. The parameter "DataType" can be set to the following values: "Int", "Dig", "Dbl", "Enum", "UInt", "Real". For more information, see Specify a Data Type for a BACnet Schedule.

Note:
• Scheduler integration will not operate correctly if a data type configuration is not correctly matched with the device.
• If you do not specify a data type for each BACnet schedule object, a "Bad IO device variable" error notification will be generated when you attempt to compile your project.

5. Run an equipment update to generate the required tags (see Update Equipment).

Alternatively, you can manually create instances of the required equipment using the BACnet equipment type templates provided in Citect SCADA's Include project.

The BACNET schedule entries will appear in Scheduler when you run your project (see View and Edit BACnet Schedules at Runtime).

Published June 2018