Engineering search

Evergreen fire alarm fault finding guide for engineers covering panel messages, wiring faults, device faults, safe testing and documentation.

A practical fire alarm maintenance checklist covering pre-service review, panel checks, device testing, batteries, records and follow-up actions.

Fault finding across Fike's Cheetah Xi, Duonet and Twinflex ranges — identifying the architecture, reading the panel, and a safe diagnostic approach.

How airflow and ventilation affect fire detector performance, why high air-change rooms matter, and what to check — for UK fire alarm engineers.

When and why detection may be omitted from certain areas under a fire alarm category, how it is justified, and what to check — for UK fire alarm engineers.

A practical guide to cable sizing under BS 5839-1, covering circuit integrity, voltage drop, loop resistance, and the CPC requirements engineers miss.

A plain-English guide to BS 5839-1 fire alarm system categories — the L, P and M families and what each is designed to protect — for UK engineers and duty-holders.

Understand BS 5839-6 fire alarm grades (A–F) and categories (LD and PD) for homes and HMOs — what they mean and how they combine — for UK engineers and landlords.

A practical guide to BS 5839-6 for domestic and residential fire alarm systems — Grades A to F, Categories LD1 to LD3, when each applies, and how it differs from BS 5839-1.

What BS 9991 covers for residential buildings, why the 2015 edition was withdrawn in favour of BS 9991:2024, and what changed for fire alarm engineers.

What BS 9999 covers, how its risk-profile approach differs from Approved Document B, and how it relates to BS 5839-1 for the fire alarm engineer.

How carbon monoxide relates to fire alarms — CO fire detectors vs CO alarms, where each belongs, and what to check, for UK fire alarm engineers.

What a Category M manual fire alarm system is, when it is appropriate, its limits, and what to check — for UK fire alarm engineers.

What a fire alarm cause and effect matrix is, why it matters and how it is used in design, commissioning and testing — for UK fire alarm engineers and duty-holders.

Where CE and UKCA marking for fire alarm and construction products actually stand in Great Britain right now, and what changed with the 2025 amendment regulations.

How to diagnose an intermittent fire alarm fault that has cleared by the time you arrive — provoking techniques, log correlation and a systematic approach.

A practical guide to BS 5839-1 fire alarm categories — L1, L2, L3, L4, L5, P1, P2, and M — when each applies, and how to document the selection.

How fire alarm systems monitor their own wiring — open circuit, short circuit and earth fault detection, why it matters and how to approach each — for UK engineers.

Using a clamp meter to measure quiescent and alarm current draw on fire alarm power supplies and circuits without breaking into live wiring, and what an unexpected reading means.

How conventional and addressable fire alarm systems differ, the strengths and limits of each, and how to decide which suits a building — for UK engineers.

How fire alarm and emergency lighting systems relate and coordinate, why both matter for escape, and what to check — for UK fire alarm engineers.

Why networked and remotely-connected fire alarm systems need cyber-security awareness, the principles involved, and what to check — for UK fire alarm engineers.

You need four numbers: standby (quiescent) current, full alarm current, required standby duration and required alarm duration — all from the panel documentation, device datasheets or measured at the battery terminals. Capacity = (standby current × standby hours) + (alarm current × alarm hours), then add the safety margin the design standard and panel manufacturer call for (commonly 25%) and round up to the next standard battery size. The classic mistake is using only the panel's quiescent figure and forgetting the loop devices. Confirm durations against the project specification — don't assume 24 hours is always right. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Start with the event log, not opinions: identify which devices, times and conditions generate the unwanted alarms. Then match the fix to the cause — wrong detector type for the environment (steam, dust, cooking), detector siting too close to vents or kitchens, transient activities without temporary management, or genuine faults presenting as alarms. Multi-sensor or heat detection, relocation, cause-and-effect delays where the standard permits them, and client housekeeping all have their place. Change one thing at a time and monitor the log after each change so you know what actually worked. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Trigger the alarm condition mapped to the doors and watch them: every held-open door on the interface should release and close fully — a door that releases but doesn't latch hasn't done its job. Confirm re-set behaviour, check local release buttons still work, and verify the interface's monitored wiring reports faults to the panel. Coordinate with the site before testing: releasing every fire door in a busy corridor unannounced doesn't make friends. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Confirm which loop or circuit the panel is flagging, then disconnect it at the panel — if the fault clears, the problem is in the field wiring or a device, not the panel. Test the disconnected cable with an insulation-resistance tester, conductor-to-earth on each core, then split the circuit at convenient points (isolators, junction boxes) and re-test each half to close in on the fault. Damp devices, crushed cable, and screws through hidden runs are the usual culprits. Record the readings, not just "fault cleared" — the megger values are your evidence. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Work from the site's approved cause-and-effect matrix — not from memory. Trigger each input condition (or simulate it where live release is unsafe), and confirm every mapped output: sounders, plant shutdowns, door releases, dampers, AOVs, ARC signals. Record each input-output pair as pass/fail with times. Anything that can release suppression or move plant needs isolations agreed in advance and restored afterwards, with the restoration witnessed and recorded. An unversioned or missing matrix is itself a defect worth reporting. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Judge each defect by its effect on the system's ability to detect and warn: anything that stops detection or alarm in an occupied area, or takes the panel or signalling down, needs immediate action and formal notification to the responsible person. Degraded redundancy, single-device faults and non-urgent wear items follow, with agreed timescales. Put the priority and the consequence in writing — clients act on "this means the second floor has no automatic detection" far faster than on a code. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Change default passwords on anything network-connected, restrict remote access to documented, authorised routes, keep firmware current from official sources, and record who holds credentials. Segregate life-safety equipment from general networks where the design allows. Treat engineer access codes as site-specific and confidential — never publish or share defaults. Most compromises of building systems start with a default password nobody changed. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Enough to be safe and useful: how the equipment gets its address (static vs DHCP), what a subnet is, how to ping a device, and how to check a link light before blaming the equipment. Get graphics terminals, gateways and remote monitoring onto documented addresses with the site's IT involved — undocumented static IPs cause outages years later. Never change network settings on shared infrastructure without the client's IT; a fire system that takes down a corporate VLAN is a bad day. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Service effort is weighted by the risk profile of the site and the system's history rather than treated as a uniform checklist: a sleeping-risk premises or a site with recurring faults gets more attention than a low-occupancy unit with a clean record. The maintenance regime still has to meet the recommendations of the applicable standard and the site's fire strategy — risk-based means prioritising within that framework, not cutting visits below it. Document the reasoning so the regime can be defended. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Every panel, PSU, interface and isolation point should carry a durable label matching the site records — device references that agree with the zone chart, circuit references at the distribution board, and warning labels where isolations affect life-safety. Consistent labelling turns a 40-minute hunt into a 2-minute check, and it's what lets a relief engineer work the site safely. Replace missing labels as you find them and note systematic gaps in the service report. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Walk the whole building, not the drawings: record construction, ceiling heights and voids, occupancy and sleeping risk, environmental challenges (dust, steam, humidity), existing equipment and its condition, cable routes, and anything that will affect detector choice or coverage. Photograph the panel, a sample of devices, and problem areas. Talk to whoever manages the building — the operational reality they describe is the difference between a design that works and one that false-alarms for a year. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

It must let a stranger — a responding fire officer or a relief engineer — find any device quickly: clear building orientation, zone boundaries that match reality, device locations and addresses, and a revision date. Update it whenever devices are added, moved or re-addressed. A zone chart that no longer matches the installation is worse than none, because people trust it. Flag an out-of-date chart as a defect in your service report. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

A working demonstration, the documentation pack (certificates, as-fitted drawings, zone chart, cause-and-effect, operation and maintenance instructions), the log book started with commissioning entries, and named training for the people who will actually use the panel — silencing, resetting, testing, and what to do on fire and fault. Record who was trained and when. A handover the client didn't understand generates a call-out within the month. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

What you found, what you tested, what you changed, what remains outstanding, and what the client should do next — with device references and readings, not vague phrases. "Fault cleared" is only acceptable when the report shows the checks that prove it. Record impairments and isolations explicitly, get outstanding defects in writing to the responsible person, and keep the site history so recurring problems are visible across visits rather than rediscovered each time. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Survey what exists: loop protocols and device compatibility, cause-and-effect logic, interfaces to other systems (doors, dampers, plant, ARC), network arrangements, and the state of the as-fitted records. Decide what is being reused and verify the new panel genuinely supports it — protocol compatibility claims deserve testing, not trust. Plan the changeover window, temporary cover while the system is down, retesting scope, and handover documentation. The panel swap is the easy part; the interfaces are where jobs overrun. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Prove the chain: alarm input → control output → damper movement → position feedback to the panel or BMS. Witness the damper actually travel where access allows, don't just trust the status LED. Check the fail-safe state matches the design (open or closed varies by strategy), and that damper faults report somewhere someone watches. Record which dampers were exercised — on large sites rotate through them across the maintenance programme with the ventilation contractor where needed. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Enough for the next engineer to understand the system without you: as-fitted drawings, zone chart, cause-and-effect matrix, device schedule with addresses and locations, loop test results, battery calculations, sound-level results, soak-test outcome, outstanding variations, and the commissioning certificate. Version everything and leave copies on site and in the office file. Half of the difficult service visits trace back to commissioning information that was never handed over. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Radio conditions decide whether a wireless system is viable in that building, on that day, with those contents — and steelwork, stock levels and refurbishments change them. Survey with the manufacturer's tool before design, record signal margins per device location, and re-check when the building use changes or when devices start reporting communication faults. Fit devices at surveyed positions, not convenient ones; a device moved half a metre behind a steel beam can drop off the network. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Simulate mains failure for the rated duration and inspect every luminaire at the end — not the start — of the test, because failing batteries drop out late. Record failures by location, replace or repair, and re-test what was fixed. Schedule full-duration tests for times when the building can tolerate discharged batteries afterwards (they need recharge time before they can protect again). Short functional tests in between confirm operation but don't prove duration. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

Establish which node(s) dropped and when, from the event logs of more than one panel — one side of the story misleads. Check the network topology (ring or bus), because a single break in a ring may show as degraded rather than down. Inspect the network wiring and connectors at the affected node first, then the node's network card. After repair, confirm every panel sees every other and that global cause-and-effect still operates across nodes — a network that looks up but doesn't pass alarms is worse than one that is obviously down. Standards are referenced for orientation only — always confirm requirements against the current edition of the applicable standard, the site's fire strategy and manufacturer documentation.

The primary fire safety legislation for most non-domestic premises in England and Wales, placing duties on the responsible person including maintenance of fire safety systems.

A fire signal from anything other than a real fire — cooking, steam, dust, works, faults or malicious operation; managed by matching detection type and siting to the environment.

The UK convention describing system objectives: L categories protect life, P categories protect property, M is manual-only; the category drives detection coverage.

A fire alarm system in which each device has a unique address, letting the panel identify exactly which detector, call point or interface generated an event.

The monitored centre receiving fire and fault signals from site transmission equipment and initiating the agreed response.

The UK code of practice for fire detection and alarm systems in non-domestic premises, covering design, installation, commissioning and maintenance recommendations.

The UK code of practice for fire detection and alarm systems in domestic premises, including the grade and category conventions for dwellings.

The UK code of practice for actuation of release mechanisms for doors — the fire-alarm-to-door-release interface and its categories of actuation.

A fire alarm system arranged in radial zones where the panel knows the affected zone but not the individual device.

The monitored interface releasing held-open fire doors on the mapped alarm condition; a released door must also close and latch fully to count.

The fixed two-way speech system linking refuge points and fire telephones to a control position for use during evacuation and firefighting.

The European product standards for fire detection and alarm system components — panels, power supplies, detectors, call points, sounders, isolators and radio devices each have their own part.

Whether an electrically controlled lock releases (fail-safe) or stays locked (fail-secure) on power loss — chosen per door from escape and security requirements.

A detector responding to the optical signature of flame (IR and/or UV), used for fast-developing fuel fires where smoke detection is too slow.

A monitored input/output device connecting the fire system to other building systems — plant, dampers, lifts, security — under cause-and-effect control.

A detector combining sensing principles (typically optical and heat) to improve discrimination between real fire signatures and nuisance sources.

A point detector sensing light scattered by smoke particles in its chamber; effective on smouldering fires, more prone to dust and steam nuisance alarms.

The duty holder for fire safety in a premises under UK fire safety legislation, responsible for ensuring the system is maintained and impairments are managed.

A fire telephone handset outstation, typically for firefighting teams.

A geographical subdivision of the protected premises used to indicate the location of a fire or fault, shown on the panel and the zone chart.

Fire detection control equipment represented from Fike's official product information.

Fire detection devices and protocols documented through Apollo's official technical library.

Voice alarm and public address equipment represented only at documented product family level.

Fire alarm control equipment documented on Global Fire Equipment's official product pages.

Fire alarm control equipment documented through official FireClass and Johnson Controls product resources.

Fire alarm control equipment with official product support and technical documentation.

Addressable fire alarm control equipment documented in Bosch product pages and system manuals.

Fire alarm and life safety equipment covered through C-TEC's official support documentation.

Addressable fire detection equipment supported by Eaton product documentation and declarations.

Wireless fire detection systems represented from EMS product and support information.

Fire alarm control equipment documented in Honeywell's ESSER product and technical libraries.

Fire detection systems covered through Honeywell's official Gent brand resources.

Fire alarm control equipment represented from Haes Systems product information.

Fire detection devices and systems covered through Hochiki Europe's official document library.

Fire alarm control equipment covered through Kentec's official support resources.

Fire alarm control equipment covered through Honeywell's official Morley-IAS resources.

Fire detection devices and systems represented from Nittan Europe's official product information.

Fire detection control equipment documented by Honeywell Notifier product resources.

Fire detection control equipment documented through Protec's official product, support, software and lifecycle resources.

Fire detection control equipment documented on Siemens' official Cerberus PRO product pages.

Product catalogue from Fike. Use this official Fike resource as a primary route to products information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Manuals and documentation from Johnson Controls. Use this official Johnson Controls resource as a primary route to manuals information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Manuals and documentation from Johnson Controls. Use this official Johnson Controls resource as a primary route to manuals information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official videos from Apollo Fire Detectors. Use this official Apollo Fire Detectors resource as a primary route to videos information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Protec. Use this official Protec resource as a primary route to products information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official website from ASL. Use this official ASL resource as a primary route to website information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Manuals and documentation from Eaton. Use this official Eaton resource as a primary route to manuals information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Protec. Use this official Protec resource as a primary route to products information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Global Fire Equipment. Use this official Global Fire Equipment resource as the primary starting point for G-One. It is most useful for products information and should be checked against the exact installed model, document revision and site configuration.

Official website from Johnson Controls. Use this official Johnson Controls resource as a primary route to website information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Manuals and documentation from Honeywell Notifier. Use this official Honeywell Notifier resource as the primary starting point for Pearl. It is most useful for manuals information and should be checked against the exact installed model, document revision and site configuration.

Official website from EMS. Use this official EMS resource as a primary route to website information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Eaton. Use this official Eaton resource as the primary starting point for xDetect Mini. It is most useful for products information and should be checked against the exact installed model, document revision and site configuration.

Product catalogue from Eaton. Use this official Eaton resource as the primary starting point for xDetect. It is most useful for products information and should be checked against the exact installed model, document revision and site configuration.

Manuals and documentation from Johnson Controls. Use this official Johnson Controls resource as the primary starting point for FC501. It is most useful for manuals information and should be checked against the exact installed model, document revision and site configuration.

Official website from Johnson Controls. Use this official Johnson Controls resource as a primary route to website information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Official training from EMS. Use this official EMS resource as the primary starting point for FireCell. It is most useful for training information and should be checked against the exact installed model, document revision and site configuration.

Official videos from Advanced. Use this official Advanced resource as a primary route to videos information. Confirm that any document or download matches the installed product, revision and local project requirements before relying on it.

Product catalogue from Advanced. Use this official Advanced resource as the primary starting point for Axis EN. It is most useful for products information and should be checked against the exact installed model, document revision and site configuration.

Product catalogue from Advanced. Use this official Advanced resource as the primary starting point for AxisGo. It is most useful for products information and should be checked against the exact installed model, document revision and site configuration.