BACnet Schedule Configuration

We created this tool to configure BACnet schedule points (Object type: SCH) for reading and/or writing after they are imported into the database from a BACnet connector and associated to a FIN schedule. A FIN schedule is needed to be able to sync between both instances.

How to use BACnet Schedule Configuration tool

1. First the user will go to DB Builder.

2. Navigate to Connectors → BACnet → BACnet connector where the schedule originates from.

3. Discover the points to find the schedule object.

4. Import the BACnet schedule into the database under an equip.

5. Then select the schedule point in DB Builder and go the gear icon at the bottom left to open the tools list. It only works with one schedule point at a time.

6. They would find and select the BACnet Schedule Configuration tool.

   

   1. The first few options of the tool are:

      1. Schedule - This dropdown will display the available schedules in FIN based on the same type that the user can choose from.

      2. Automatic Schedule Sync: Reading - The user can choose whether to enable/disable syncing schedule events from a BACnet schedule to a FIN schedule.
         The read syncing supports the following:

         1. Weekly_Schedule - This property will be synced after the BACnet schedule weekly part updates and poll frequency is met.

         2. Exception_Schedule - This property will be synced after the BACnet schedule exception part updates and poll frequency is met.

         3. Schedule_Default - This property will be synced after the BACnet schedule default value updates and poll frequency is met.

      3. Automatic Schedule Sync: Writing - The user can choose whether to enable/disable syncing schedule events from a FIN schedule to a BACnet schedule.
         The write syncing supports the following:

         1. Weekly_Schedule - This property will be written when the FIN schedule weekly part updates.

         2. Exception_Schedule - This property will be written when the FIN schedule event part updates.

         3. Schedule_Default - This property will be written when the FIN schedule default value is set.

            

   2. Then next set of options available for either reading and/or writing when enabled are:

      1. Read Path - This will display the object instance of the selected schedule point. If the user wants to read from a different schedule than the write, they can change it here.

      2. Read Frequency - This frequency, defined in minutes or hours by the user, determines how often the reading sync occurs. This process is based on polling. If the schedule doesn't need to change frequently, we recommend using a slower frequency. This is applied to the connector with the tag bacnetScheduleReadFreq, therefore applies to all schedule points associated to the same connector.

      3. Write Path - This will display the object instance of the selected schedule point. If the user wants to write to a different schedule than the read, they can change it here.
         Note: Write sync will only occur when there is change in the FIN schedule. This will sync the weekly, exception and default properties.

      4. Write Level - This is the priority level in which to write to on the schedule object instance in the device side.

This is what the schedule record would look like depending on which settings are configured.

• scheduleRef

• reading:

  • bacnetScheduleRead

• writing:

  • bacnetScheduleWrite

  • bacnetScheduleWriteLevel

Additional Read Sync details

• Following are the supported BACnet schedule parameter values for reading.

• If any event in the Exception_Schedule is modified in the BACnet schedule, the corresponding FIN schedule events will be renamed sequentially as EVENT-X when synced. This occurs because the events on the device side lack names. Users can rename these events in the FIN schedule, which will then update the BACnet schedule accordingly.

Note: Week event created in the FIN schedule event section will be flatten into Weekly section while when read is synced. For instance, if a user creates a “week” event under the Event section scheduled from 8 am to 5 pm on Monday, it will appear in the weekly section after read syncs. Subsequently, this event will be removed from the FIN schedule under the Event section.

• In cases where a FIN schedule is mapped to multiple BACnet schedule points, the values from the most recently synced BACnet schedule point will take precedence.
  
  For instance, a FIN schedule can be mapped to multiple BACnet schedule points, such as SCH1 and SCH2. If the user changes the BACnet schedule for both SCH1 and SCH2 at the BACnet device side, the most recently synced schedule point will take precedence before the schedule read sync occurs. Ideally, the user should change only one BACnet schedule point. This way, when the read sync occurs, all other BACnet schedule points will be updated during the FIN schedule write sync.