Configure XNET Network

  1. Each XNET requires a dedicated driver that runs on a server or FEP station. The association between network and driver is fixed and cannot be modified after the database import. If you wish to change driver or if a network is not required after creation, you can delete the XNET node, thus removing all child nodes previously imported.
  2. System Manager is in Engineering mode.
  3. You configured an XNET driver that suits the type of network you are installing (via XNET card).
  1. In System Browser, select Management View.
  2. Select Project > Field Networks.
  3. In the Object Configurator tab, click New , and select New XNET Network.
  4. In the New Object dialog box, enter a name and description.
  5. Click OK.
  6. The newly created network is automatically selected in System Browser.
  7. In the XNET tab, select the Network Settings expander.
  8. From the Monitored by Driver drop-down list, select the XNET driver you configured previously.
    NOTE: An XNET driver can only be associated to one XNET network.
  9. From the Alarm detection level drop-down list, select the geographic grouping level of the Detection node in which alarms will be assigned. Select Not displayed to exclude the Detection node and generate alarms at the original device level.
  10. From the Block command scope drop-down list, select Panel if you want block command settings to be set and executed at the individual panel level or select Network to have block command settings at the network level. In the latter case the user must be the owner of the entire network.
  11. In the Hierarchies Settings expander, set the System Browser views where you want the XNET panel configurations to be imported. For each hierarchy structure in the list:
    • Management view: Select the check box if you want the structure to populate Management View.
    • Additional import view: Select an additional view where you want the structure to also be imported. Leave blank or select None if you do not want to populate any additional view.
  12. In the Block Commands Behavior expander, select the check boxes to enable broadcasting of the following commands across the fire network:
    • Block acknowledge
    • Block reset
    • Block silence/unsilence
  13. Macros for broadcasting the commands that you enable here will be automatically created under Applications > Logics > Macros > Block Command Macros.
    NOTE:     During event handling, the block commands apply to all categories events of the entire fire network. In System Manager, the block commands only apply to the selected area.
  14. In the Ownership Settings expander, select one of the Control Capability modes, which define the control command capability of the stations over the fire network.
    • Full System Control
      This setting is possible for systems that do not require any UL/ULC approval. All stations are permanently enabled to control the events of the network.
    • Panel Control via Request/Grant/Deny (UL-864 compliant)
      Only one station at the time is enabled to control the events of a panel, and the assignment is dynamically determined by a manual request.
    • Panel Control when Linked Panel has Control (UL-864 10th Edition and ULC-S527 compliant)
      Each panel may have an associated station to which the panel extends the capability to control the events of the fire network. After importing the fire network, in the panel configuration, select the associated station.
      NOTE: If you change the ownership mode after importing the fire network, a new import is required, and a warning message prompts you to do that.
  15. Click Save .