Configuring an XNET Fire Network

Scenario

You want to configure Desigo CC for connecting to fire control panels on XNET networks. For related information, see:

• XNET Network Configuration Reference
• Block Commands and System Behavior
• Ownership of XNET Fire Panels
• Running XNET Fire Network Wizard
• Monitoring-Only Fire Architecture Through MOSA
• UL/ULC Compliance: XNET Fire Panel Settings section in the Compliance Notice for UL Norms page or Compliance Notice for ULC Norms page.

Prerequisites

• The extension modules corresponding to the specific fire panels in use were installed and included in the active project. They can be one or more of the following:
  - FireFinder XLS MXL
  - Desigo Fire Safety Modular UL
  - Cerberus Pro Modular UL
• One of the following XNET communication card is installed on the Desigo CC server or FEP station.
• NCC-2F card (see NCC-2F Card for XNET)
• SNC USB card (see SNC Card for XNET)
• XND (MOSA) adapter, for monitor-only solutions
  NOTE: Monitor-only solutions can be implemented using an external XND (MOSA) adapter. Refer to document P/N S54465-C62-A1.
  Note also that, if you change the external MOSA adapter on a running installation, you need to stop and restart your Desigo CC project, and then configure the new XND (MOSA) adapter on the XNET driver.
• The XML configuration file -containing the complete internal structure of one or more fire panels- is available locally or over the network.
  Depending on the XNET configuration, you can create the XML file in one of the following ways:
• XNET with MXL panels only: use the CSGM tool to export the MXL configuration file that you will import into Desigo CC.
• XNET with FireFinder XLS panels only: use the Zeus tool to export the FireFinder XLS configuration file that you will import into Desigo CC.
• XNET with both MXL and FireFinder XLS panels: create a consistent configuration in CSGM and Zeus tools, and export two configuration files that you will import into Desigo CC.
• (For Zeus 15.1.0001 and higher) All the devices within the same panel must be configured with the same self-restoring supervision behavior. For example, if one device in a panel is configured for non self-restoring supervision, all other devices of the same panel must be configured in the same way.

Overview