Skip to main content
Fire

Notifier by Honeywell ID3000 fault records

49 fault messages this panel shows on site, each with what it means and the document it's drawn from. Product family recorded from the cited official manufacturer source.

Fault records

Aux. Output X Fault

Not yet verified

Parameterised message covering auxiliary outputs 1 and 2 (X = 1 or 2), as printed in the source ('Aux. Output 1 Fault'; 'Aux. Output 2 Fault'). Indicates a failure of the auxiliary drive circuits, not the attached cables. Action: If the fault is on either circuit, change the Base PCB (Kit PN: 020-568).

Battery Failure

Not yet verified

These faults indicate the occurrence of one or more of: a. Faulty or disconnected batteries (if discharged batteries are connected, they may remain in Battery Low Voltage for a period until the voltage is raised by the charger); b. Battery charger fuse (FP2 on PSU3A) has blown; c. Faulty PSU. Action: Replace items as required. The source adds specifically for this message: 'Battery Failure' may indicate that the impedance of the battery wiring is too high — Action: check the battery wiring connections.

Battery Low Voltage

Not yet verified

These faults indicate the occurrence of one or more of: a. Faulty or disconnected batteries (if discharged batteries are connected, they may remain in Battery Low Voltage for a period until the voltage is raised by the charger); b. Battery charger fuse (FP2 on PSU3A) has blown; c. Faulty PSU. Action: Replace items as required.

Dev#0 Present

Not yet verified

This indicates that a device has been installed without setting a valid address, i.e. left at factory default of '00'. No separate remedial action is stated beyond this cause in the source.

Earth Fault

Not yet verified

The earth fault monitor detects the presence of an earth on the positive or negative sides of the system. Should this condition occur, disconnect the field circuit wiring one cable at a time and view the LED at the top right of the Base PCB; if the LED extinguishes, the current cable is faulty. Then use a meter to locate the earth fault.

Fault 47 - CPU/Display hardware fault

Not yet verified

Communications fault between the CPU and the display. Action: Change the CPU PCB assembly (PN: 020-569) and/or the Display PCB/Membrane Keypad (PN: 020-571-XXX).

Fault 48 - Base PCB/Expansion h/w fault

Not yet verified

No separate cause description is given for this message beyond its name. Action: Change the Base PCB (PN: 020-568) or Extension Chassis with Display Module Kit (PN: 020-559-XXX).

Fault 71 - Config. needs Expansion Card

Not yet verified

This fault message can only appear when ID3000 panels are networked with earlier compatible panels; it is not applicable to the 'local' ID3000 Series panel. Where it is applicable, an Extension Chassis with Display Module Kit (PN: 020-559-XXX) is required.

Fault 72 - Config. needs RS485 Card

Not yet verified

Missing PCB — the panel is configured for network but no RS485 PCB is present. Fit Isolated RS485 Module Kit (PN: 020-479) or change configuration.

Fault 73 - Config. needs RS232 Card

Not yet verified

Missing PCB — the panel is configured for 3rd-party protocol but no RS232 PCB is present (does not apply to other modes of the port). Fit Isolated RS232 Module Kit (PN: 020-478) or change configuration.

Fault 74 - RS232\RS485\PRINTER Card displaced

Not yet verified

An attempt has been made to remove one of these items while the panel is powered up. Remove power before proceeding.

ID2net: Channel 1 Link Fault

Not yet verified

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 each panel either side of the cable fault; in some situations only one message may be displayed where communication is only operating in one direction. Action: Check that the appropriate jumper link is fitted, dependent on the connection medium (copper-conductor cable or optical fibre) — refer to the NGM PCB instruction sheet (ref. 997-449-000-X) for correct jumper link setting.

ID2net: Flash Checksum Error

Not yet verified

This message indicates an NGM PCB failure. Action: Replace the NGM PCB. Note: the source states other fault conditions may occur in exceptional circumstances, in which case contact your supplier for guidance.

ID2net: Network card missing

Not yet verified

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. Alternatively, check that the NGM PCB has been correctly installed as described in its instruction sheet (ref. 997-449-000-X).

ID2net: Network runtime fault

Not yet verified

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 Network startup fault): if these fault messages persist, replace the NGM PCB.

ID2net: Network startup fault

Not yet verified

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 fault): if these fault messages persist, replace the NGM PCB.

Incompatible or faulty sensor installed

Not yet verified

No separate cause description is given beyond the message name. Action: For IPX sensors, replace with SDX751TEM or equivalent. For other MULTI and SMART sensors, replace (sensor is faulty).

OPTIPLEX incompatible with LIB software

Not yet verified

An Optiplex sensor has been found on the loop but the LIB software does not support it. Action: Replace the Base PCB and LIB PCBs with revisions that have LIB software version 8.0 or above (as shown in lamp test).

Panel Fault 17 - Card Missing

Not yet verified

Loop PCB missing or failed to respond. Possible causes are: a. Wrong ribbon cable connected; b. Ribbon cable disconnected; c. Loop PCB failure. Action: For the last case, change the loop PCB (PN: 020-588).

Panel Fault 49 - CPU Watchdog timer fault

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

Panel Fault 5 - Power Restart

Not yet verified

These four fault messages are grouped in the source as all indicating a loop PCB failure. Action: Replace the loop PCB (PN: 020-588).

Panel Fault 65 - Clock set to after AD2099

Not yet verified

No separate cause description is given beyond the message name. Action: Set the clock to the correct date and time.

Power Fault, ID2net Booster n

Not yet verified

This message indicates an open circuit on the power fault input of the NGM. Action: Check for missing or broken wiring. Check that the PSU is not faulty.

Printer Fault

Not yet verified

Internal printer only. This fault may be an indication of a paper jam or malfunction, no paper, or the printer may be disconnected. Note: the printer operation is only monitored if the printer was functional at the last power-on.

PSU Fault: Crowbar Active

Not yet verified

No separate cause description is given for this message beyond its name. Action: Remove mains and battery power supplies, wait 5 minutes, then perform the power up procedure; if the condition returns, call a Service Engineer.

PSU/Charger Fault

Not yet verified

These faults indicate the occurrence of one or more of: a. Faulty or disconnected batteries (if discharged batteries are connected, they may remain in Battery Low Voltage for a period until the voltage is raised by the charger); b. Battery charger fuse (FP2 on PSU3A) has blown; c. Faulty PSU. Action: Replace items as required.

SENSOR FAULT

Not yet verified

For VIEW, MULTI (Optiplex), or SMART sensors: the analogue reading is below the Chamber fault threshold, or below the Maintenance Urgent threshold, or a Maintenance Alert has existed for longer than 100 days without any action being taken. For HEAT, ION, OPT or GAS sensors, the analogue reading is below the Chamber fault threshold. Action: Notify the service engineer.

Short Circuit

Not yet verified

A short circuit has occurred on the loop between the panel and isolator (if fitted). If isolators are fitted, the system shows NO REPLY/MISSING for the devices located between the isolation points, or LOSS OF PART LOOP if more than three devices are missing (a fault display is then available for each missing device). Action: Disconnect the affected section of the loop and use a meter to find the fault. The source notes that because isolators disconnect the affected section, a short circuit between two isolators is instead reported as a 'Suspected Break' — that related message is named but not given its own separate cause/action text in this source.

Signal Degraded

Not yet verified

Data returned from a loop device is being corrupted over a period of time. Action - Check: a. The continuity of loop screens; b. The screen is connected to earth at one point only (normally at the panel). Note: the default time is one hour; after a reset, it will be one hour before this fault is re-reported.

Sounder Cct.X OPEN-CIRCUIT

Not yet verified

Parameterised message covering sounder circuits 1-4 (X = 1, 2, 3 or 4), as printed in the source. Indicates an open circuit (disconnection condition) fault on the sounder circuit wiring. Action: For circuits 3 and 4, check that the user-defined links (JP5, JP8 and JP7, JP9 respectively) on the Base PCB are in the correct position. Action: Disconnect the wiring and use a meter to locate the faulty sounder or cable — a 4k7 resistor or diode should be connected to the end of the cables.

Sounder Cct.X RELAY FAULT

Not yet verified

Parameterised message covering sounder circuits 1-4 (X = 1, 2, 3 or 4), as printed in the source. Indicates a failure of the drive circuits (circuits 1 or 2) or drive relays (circuits 3 or 4) to the sounder circuits, not the attached cables. Action: If the fault is on any circuit, change the Base PCB (Kit PN: 020-568).

Sounder Cct.X SHORT-CCT.

Not yet verified

Parameterised message covering sounder circuits 1-4 (X = 1, 2, 3 or 4), as printed in the source. Indicates a short circuit fault on the corresponding sounder circuit wiring. Action: For circuits 3 and 4, check that the user-defined links (JP5, JP8 and JP7, JP9 respectively) on the Base PCB are in the correct position (see Section 7.7, Volt-free Contact Output Option). Action: Disconnect the sounder circuit wiring and use a multimeter to locate the fault.

System Fault 1 - Loop-CPU Fault

Not yet verified

These four fault messages are grouped in the source as all indicating a loop PCB failure. Action: Replace the loop PCB (PN: 020-588).

System Fault 29 - LIB ROM Checksum

Not yet verified

These four fault messages are grouped in the source as all indicating a loop PCB failure. Action: Replace the loop PCB (PN: 020-588).

System Fault 40 - Main CPU Watchdog Operated

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 41 - EPROM Memory Checksum

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 42 - E2PROM Memory Write Error

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 43 - FLASH Memory Checksum

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 45 - FLASH Memory Write Error

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 46 - Software error

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 64 - CPU Watchdog not enabled

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 66 - CPU Clock Monitor Failure

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

System Fault 67 - CPU Illegal Instruction

Not yet verified

This message is one of ten Processor Fault messages the source groups together under a single shared action: if any of these faults occur repeatedly and randomly, replace the CPU PCB assembly (PN: 020-569). No separate cause is stated per message beyond its name.

Terminal Link Fault

Not yet verified

This fault indicates that the peripheral unit connected to the third-party-protocol RS232 port has not responded to the enquiry code sent, or the link to the third-party equipment is not connected (this would normally indicate a fault in the external device). Action: First check the cable; if this is OK, replace the unit with an RS232 monitor or device known to work; if that checks out OK, replace the unit; if not, change the RS232 Module (PN: 020-478). Note: monitoring of this link is a configurable option.

Records marked “sourced — not yet independently verified” carry a real citation but have not yet completed formal review. Always confirm against the manufacturer's current documentation before acting on site.