Never assume a panel indication is only a nuisance fault
Check for a genuine fire condition first, follow the premises fire procedure, record all indications and use only authorised controls. Any impairment should be managed by the Responsible Person and corrected by a competent fire-alarm engineer.
MOST LIKELY CAUSES
Start with the panel information
Symptom variations Match the exact display, LED and event behaviour. ⌄
- System fault LED
- Panel repeatedly restarts
- Display freezes
- Network nodes missing
- Configuration or checksum message
Safe first checks Checks for authorised site staff before engineering work. ⌄
- Check for a red fire indication before treating anything as a fault.
- Read and record the exact display text and LEDs.
- Identify the affected zone, address, circuit, node or power source.
- Check the site log book and recent work.
- Do not disable or reset repeatedly to hide the indication.
Step 1 — Do not repeatedly power-cycle the panel Follow the site fire procedure and use authorised controls only. ⌄
Preserve event information and avoid creating further faults.
Step 2 — Record every displayed message Follow the site fire procedure and use authorised controls only. ⌄
Include node number, panel name, software message and time.
Step 3 — Escalate to the maintaining organisation Follow the site fire procedure and use authorised controls only. ⌄
System-level faults normally need manufacturer-specific access, software and competence.
What the indication usually means How this condition develops. ⌄
System fault generally indicates an internal control, processor, memory, configuration, watchdog or network problem rather than a simple field-device fault.
Engineer diagnostic sequence Competent-person checks after site information has been captured. ⌄
- Download or review event and diagnostic logs.
- Check network topology and node status.
- Verify configuration revision and checksums.
- Inspect processor, memory and internal communication buses.
- Confirm cause-and-effect remains available after restoration.
Information and equipment needed Useful items for accurate fault finding. ⌄
- Exact panel make and model
- Event log and site log book
- Zone plan and as-fitted drawings
- Cause-and-effect information
- Manufacturer documentation and approved test equipment
Parts that may be involved Components commonly associated with this fault. ⌄
- Processor card
- Memory device
- Network card
- Internal ribbon or bus assembly
- Manufacturer software or lead
When immediate action is required Conditions that should trigger escalation or an impairment plan. ⌄
- The panel is in fire and the cause is not confirmed.
- The control equipment is dead or repeatedly restarting.
- Detection, alarm devices or signalling are disabled or unavailable.
- The fault affects multiple zones, loops, panels or network nodes.
- The panel cannot remain on standby power.
- The site cannot maintain its required fire strategy.
Frequently asked questions Common control-panel questions. ⌄
Can the internal buzzer be silenced?
Authorised users can normally acknowledge or silence the internal panel buzzer after reading and recording the condition. The fault remains active until its cause is repaired.
Should the panel be reset?
Only after the initiating condition has been investigated and cleared. Repeated resetting can remove useful information and delay repair.
Who should repair the fault?
A competent fire-alarm engineer familiar with the equipment, system design and site fire strategy.