Fault records by panel

Most likely to occur in the event of a broken network connection, i.e. short or open circuit cable or broken optical fibre. May also indicate an NGM PCB hardware fault. There would normally be two fault messages, one at…

The source states this fault has the same cause and remedy as 'ID2net: Channel 1 Link Fault' — see that entry.

The ID2net Network Gateway Module (NGM) has not been detected, although it has been configured as present on the network. Action: Make sure the NGM PCB is fitted in every panel where the 'Mon' column is ticked.…

Displayed only if the NGM PCB stopped working after a period of working correctly. If this is not quickly followed by the Network startup fault message, the NGM PCB has successfully re-started. Action (shared with…

Displayed if either: a. the NGM PCB fails to start initially, or b. the NGM PCB fails to start after the occurrence of a runtime fault, such as a panel/NGM PCB communication loss. Action (shared with Network runtime…

If a control panel previously configured to be in the fire network is not detected, a fault message indicating the offline status (with the Firenet ID) is reported. From the ZP2 Series Installation Manual, "Firenet…

The panel has detected a newly installed network card not yet stored in its configuration.

There is a break in the network between Panel X and Panel Y, where X and Y are the panel numbers.

A network fault has occurred causing the panel to ignore data from network CH1. Not available on some panel options.

There is a fault in the network card's isolated power supply; replace the card.

A network fault has occurred causing the panel to ignore data from network CH2. Not available on some panel options.

The configuration data received by the network card is corrupt.

Two master panels have been detected on the network — either two panels were assigned as master in their configuration data (correct via the PC commissioning software), or a double break in the network wiring left two…

The network has initialised with two panels sharing the same number; correct this using the PC commissioning software. Neither panel is allowed to transmit an event, so each will eventually also display a Slave CTS…

The network is not operational because there are too many faults.

The communications link between the local network card and the core network card is faulty. Not available on some panel options.

One or more panels in the master panel's network configuration data is missing.

One or more panels has its network CH1 and CH2 wiring reversed.

There is a short circuit fault in the network between CH1+ and CH1-. Not available on some panel options.

There is a short circuit fault in the network between CH1+ and the screen. Not available on some panel options.

There is a short circuit fault in the network between CH1- and the screen. Not available on some panel options.

The panel has an event to transmit but the network master panel is not permitting it to transmit. This fault will be reported by duplicate panels.

The network has initialised with too many panels. The network supports a maximum of 64 panels.

The network has initialised with a panel that is not in the master panel's network configuration data.

There is a memory corruption in the network card; replace the card.

The network card is not communicating with the network; check that switch 1 is off.

The "Network Fault" LED on the 6500 panel's indicator strip, covering the panel-to-panel network connection used when multiple 6500 panels are networked together. This is one of the labelled LED indicators on the 6500…

The network has unexpectedly lost the master panel, so another panel has automatically been assigned as master until the problem is fixed.

Per the manual, a steady yellow Network Fault indicator means a system network error has occurred. Action listed: call the service engineer.

Two nodes have the same node id. Action: Change the id number of one of the duplicate nodes (use the diagnostic tool).