Configure the FS92 BACnet Fire Network
Create the BACnet Network
- You configured a BACnet driver.
- In System Browser, select Project > Field Networks.
- In the Object Configurator tab, click New
, and select New BACnet Network.
- In the New Object dialog box, enter a name and description.
- Click OK.
- The newly created network is automatically selected in System Browser.
- Select the BACnet tab and open the Network Settings expander.
- In the Monitored by driver drop-down list, select the driver.
- Click Save
.
Configure the Block Commands
The Block Commands Behavior expander contains the check boxes to enable broadcasting of the acknowledge, reset, and silence/unsilence commands across the fire network.
You do not need to configure the block commands now. The block commands will be automatically configured during the SiB-X metafile import based on the Single event acknowledge required parameter setting in the FXS2002 tool. However, note that, if you import multiple SiB-X metafiles, you will need to check your configuration for consistency.
Note also that macros for broadcasting the block commands enabled here are automatically created under Applications > Logics > Macros > Block Command Macros.
NOTE: If the block command macros are subject to validation, make sure that the BACnet network is set with the same validation profile as the block command macros or higher.
Configure the T1/T2 Countdown Display
In the Fire System Options tab, in the Alarm Handling Timers expander, you can enable the alarm-handling countdown display on the user interface when a relevant event is presented.
- Select Project > Field Networks > [BACnet network].
- Select the Fire System Options tab.
- Open the Alarm Handling Timers expander.
- Select the Enable T1/T2 Timers check box to enable the countdown display during alarm handling.
- Click Save
.
NOTE: Make sure the management stations and the fire panels are set to the same local time zone. This is required for the countdown timers to work properly.
Configure the Fire Control Ownership
In the Request/Grant/Deny tab, configure the fire norms to apply:
- UL-864 9th edition, or
- UL-864 10th edition and ULC-S527.
UL-864 9th ed. requires a request/grant/deny mechanism of the control capability. UL-864 10th ed. and ULC-S527 require an association between the management station and the PMI of the fire system: the management station will take ownership of the fire network when the associated panel has the fire network ownership. This behavior is independent of the visibility configured in the DesigoFSWorks tool.
See Ownership of FS92 Fire Panels. Search also for Colocation of Control Panel and Management Station.
- Select Project > Field Networks > [BACnet network].
- Select the Request/Grant/Deny tab.
- In the Configuration expander, select either of the following:
- PMI via Request/Grant/Deny (UL-864 compliant):
Proceed to the last step to save the setting.
- PMI when Linked Panel has control (UL-864 10th ed. and ULC-S527 compliant):
This selection results in the association table being activated, proceed to the next step to configure it.
- For UL-864 10th ed. and ULC-S527 compliant systems, set the management stations associated to (located in the same room as) the PMI objects of the fire panels.
In the Configuration expander, click Add.
- A new line displays that you can configure.
- In the Panel list, select the first fire panel.
- In the RGD Object list, select the PMI objects to associate.
- In the Station list, select the associated management station.
- Repeat step 4 to 7 for all panels and all required PMI objects.
Select a line and click Remove to delete an association.
- Click Save
.
NOTE 1: Users with no fire command rights can still execute fire commands from the associated management stations. You can exclude such users from accessing the management station altogether or you must allow them to execute fire commands.
NOTE 2: After reimporting the FS20 configuration, the fire control ownership on the running management stations is restored.

In the BACnet tab, the Auto Discovery Progress and the Global Objects Folder Mapping expanders are not used.