The following table presents the supported BACnet schedule parameter values for reading:
BACnet ScheduIe Parameter | FIN Supported VaIue |
BACnet Time | ‘hour’ and ‘min’ granularity only |
BACnet Calendar reference | Not supported |
BACnet WeekNDay ‘month’ | 1 12 |
BACnet WeekNDay ‘week of month’ | 1 5 |
BACnet WeekNDay ‘day of week’ | 1 7 any |
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.
Before and after any event modified in BACnet schedule side:
A Week event created in the FIN schedule event section will merge into the Weekly section once read is synced. For example, a “week” event scheduled under the Event section from 8 am to 5 pm on Monday will appear in the weekly section after read syncs and subsequently disappear from the Event section of the FIN schedule.
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.
When a FIN schedule is linked to multiple BACnet schedule points, the latest synced BACnet point's data will override others. For instance, if changes are made to both SCH1 and SCH2 in a BACnet device, the schedule from the most recently updated point will be prioritized during synchronization. It is recommended to modify only one BACnet schedule point to ensure consistent updates across all points during the FIN schedule synchronization process.