Hochiki Fire Alarm Fault Codes: A Field Reference for ESP and CHQ Systems

Hochiki panels are among the most common you'll encounter on UK commercial sites — ESP addressable systems dominate mid-tier installations, and CHQ appears regularly on larger multi-panel networks. The fault codes and event log entries can be cryptic if you're used to a different panel range.

This guide covers the fault codes and diagnostic messages that come up most often on Hochiki systems, what they mean in practice, and what to check first on site.

Hochiki System Overview

Before getting into codes, a quick orientation:

ESP (Enhanced System Protocol) — Hochiki's addressable loop protocol. Up to 127 devices per loop (some panel variants up to 250 with loop extenders). Devices include the standard SLR/SLK detector range, DCP-E manual call points, and the YBO relay output bases.

CHQ — Used on the larger Hochiki CPU panels (CHQ-M, CHQ-E). Two-wire loop protocol with up to 127 devices per loop per card. Often seen in multi-panel networked systems via Hochiki's HFnet or on single-panel installations in larger premises.

Panel variants you'll encounter: FIRElink (entry-level), FX-2000, FX-3000, CHQ-Zone, CHQ-M2 series. The fault code structure is broadly similar across the ESP range.

Reading the Event Log

On all Hochiki panels, the event log is your first stop. Access it from the control panel (engineer level access required on most panels). The log records:

• Event type (Alarm, Fault, Isolate, Test, Restore)
• Date and time
• Device address (loop and position)
• Device type
• Description/code

Always pull the full log before touching anything. The sequence of events is often more diagnostic than the current panel state.

Common Fault Codes — ESP Systems

Loop Communication Fault

Display: "COMMUNICATION FAULT — Loop X — Address YY"

What it means: The panel is losing communication with a specific device at address YY on Loop X. The device isn't responding consistently to polls.

What to check:

1. Go to the device. Check the detector base or MCP sub-base terminal connections — a loose or oxidised contact here is the most common cause.
2. Swap the detector head with a known-good unit. If the fault follows the head, replace the device. If it stays at the address, the issue is in the base or wiring.
3. Check for mechanical damage to the cable between this device and the previous address. Communication faults often indicate a partially damaged cable — the device is polling but the signal is degraded enough to intermittently fail.

Loop Short Circuit / Isolator Operation

Display: "SHORT CIRCUIT — Loop X" and "ISOLATOR OPERATED — Loop X — Address YY"

What it means: A short circuit has been detected on Loop X. The loop's built-in isolators have activated at address YY to contain the short and maintain the rest of the loop.

What to check:

1. Note which isolator(s) operated — this narrows the short to the cable section between those addresses.
2. Disconnect devices in that section one by one. When the short clears, the last device you disconnected (or its wiring) is the source.
3. Check for cable damage: mechanical impact, water ingress at a junction box, or a device with a shorted terminal board (common after water ingress into a base).

Loop Open Circuit

Display: "OPEN CIRCUIT — Loop X" or missing device addresses

What it means: A break in the loop wiring. On ESP systems, the panel will typically report the last responding address before the break — devices downstream of the break show as missing.

What to check:

1. Note the last responding address and start your search from that device's outgoing connections.
2. Check the termination at that device first — open circuit faults on Hochiki systems are frequently just a loose terminal screw.
3. If the termination is secure, use a test meter to check continuity from that device's output terminals onward.

Device Type Mismatch

Display: "TYPE FAULT — Loop X — Address YY" or "WRONG TYPE"

What it means: The device type installed at address YY doesn't match what the panel configuration expects. Either the device has been replaced with a different type, or the panel database has a discrepancy.

What to check:

1. Note the expected device type in the panel configuration (accessible through the engineer menu) versus what's physically installed at that address.
2. Common cause: a heat detector was replaced with a smoke detector (or vice versa) without updating the panel configuration, or a relay output base was installed where a standard base was configured.
3. Either replace the device to match the configuration, or update the panel configuration to match the installed device — but make sure the change is documented and appropriate for the system design.

PSU Fault

Display: "PSU FAULT" or "CHARGER FAULT" or "BATTERY FAULT"

What it means:

• PSU Fault: The power supply output is outside normal parameters
• Charger Fault: The battery isn't charging correctly
• Battery Fault: The battery voltage is below threshold under load

What to check:

1. Confirm mains supply is present at the panel. Measure input voltage.
2. Measure battery terminal voltage (typically 26.8–27.3V on a fully charged 24V system). Below 24V is typically fault threshold.
3. Check battery age. Hochiki recommends replacement every 4 years — most batteries show degradation before then in warm environments.
4. If mains is present, battery is charged, and the fault persists, suspect the charger circuit — likely a panel repair or replacement.

Zone Fault (Conventional Zones on CHQ-Zone Panels)

Display: "ZONE FAULT — Zone X"

What it means: The zone wiring is outside acceptable resistance parameters — either open circuit (resistance too high) or short circuit (resistance too low).

What to check:

1. Measure resistance at the panel terminals for that zone. Open: infinite resistance. Short: near zero.
2. Disconnect devices in the zone progressively to isolate the fault section (standard conventional zone diagnosis — see fault finding guide for details).

CHQ-Specific Codes

Network Fault

Display: "NETWORK FAULT — Panel X" (on CHQ networked systems)

What it means: The panel has lost communication with another panel on the HFnet network.

What to check:

1. Confirm the remote panel has power.
2. Check the network cable between panels — CHQ networks typically use dedicated screened cable and are sensitive to termination quality.
3. Verify the network addresses are set correctly on the affected panel (physical DIP switch or software configuration depending on panel variant).

Analogue Value Out of Range

Display: "ANALOGUE DRIFT — Loop X — Address YY" or "PRE-ALARM"

What it means: The device at address YY is reporting an analogue value outside its normal clean-air range — the detector is dirty, contaminated, or in an environment that's affecting its baseline reading.

What to check:

1. Go to the device and clean the detector chamber using the appropriate method for the detector type (consult Hochiki's cleaning guidance — most detectors use a vacuum and soft brush, not compressed air).
2. After cleaning, check the analogue value from the panel engineer menu. Normal clean-air value for Hochiki optical detectors is typically 0–30 counts (panel-dependent); a pre-alarm condition usually starts above 80–100.
3. If analogue value doesn't recover after cleaning, replace the detector.

Accessing the Engineer Menu

On most Hochiki panels:

• Hold MENU or PROG until the display changes
• Enter the engineer access code (default varies by panel — FX series default is typically 3577 or 1234; change on first access)
• Navigate to event log, analogue values, or device configuration as needed

Document any configuration changes in the system log book.

Full Fault Code Library

The codes above cover the most common callout scenarios but aren't exhaustive — Hochiki panels generate a wide range of diagnostic events depending on configuration, connected interfaces, and panel firmware version.

IFS Pro's fault code library covers 900+ codes across the Hochiki ESP and CHQ range, along with Advanced, Kentec, Notifier, and Morley panels — searchable by code, description, or symptom. Try it at incognitofiresecurity.com.