Johnson Controls Metasys Intelligent Fire Network Technical Manual page 48

Table of Contents

Advertisement

48
IFC Networking—Metasys Intelligent Fire Network
Only Fire-Net NCMs and Fire OWSs can have node addresses in those
ranges. None of the other standard (non-Fire OWS) Operator
Workstations, IFC panels, standard NCMs, or INAs can use these node
addresses. However, nodes that are exclusive to either the N1 LAN or the
FN can use the same node addresses. For example, an IFC panel on the FN
only can use the same node number as an NCM that is connected to the
N1 LAN only, because each device is connected exclusively to the FN or
the N1 respectively and therefore not in direct communication with both
FN and N1, as is the case with the Fire OWS and the Fire-Net NCM.
If you already have network nodes that are within the designated ranges for
the Fire-Net NCM and Fire OWS, you may need to change their node
addresses. Refer to the appropriate technical bulletin for how to change
that node's address. For example, to change the node number of an
NCM300 that falls within the 70-79 range, see Defining the Hardware
Connected to the NCM in the Engineering section of the Network Control
Module 300 Series Technical Bulletin (LIT-6360251) located in the
Metasys Network Technical Manual (FAN 636).
Note: Power on each INA must be cycled whenever the node address of
any online FN node is changed. This will flush the existing
network configuration in the INA and rebuild it with the new
configuration.
If a non-Fire-Net NCM has an address that is within the 70-79 range, you
may observe the following:
• The NCM will log errors when any Fire OWS starts up.
• An offline condition will be reported on the FN for that NCM during
the Fire OWS startup initial condition reporting.
• If the NCM is offline on the N1, the NCM will be listed as offline in
the Fire Network summary.
• If the NCM is online on the N1, the NCM will not appear in the
Fire Network summary.
• If the NCM is a 200, 300, or 350, and has N2 connected fire panels, it
may register Error Log 87 for illegal message type.
• If the NCM is a 101 with N2 connected fire panels, it may register
Error Log 171, and object log does not exist.
• If the NCM is not connected to either the N2 Fire System or the FN, it
may register additional errors.

Hide quick links:

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Metasys Intelligent Fire Network and is the answer not in the manual?

Table of Contents