Skip to main content
Back to blog
Fault Diagnosis10 min read

Detector Base Faults: Telling the Base from the Head

How to tell a detector base fault from a head fault using the swap test, base continuity checks and a safe workflow — for UK fire alarm engineers.

By Incognito Fire & Security · August 27, 2026

Editorially reviewedVersion 1medium confidence

Last updated August 27, 2026.

Sources used

4

Review sources and evidence basis
  • BS 5839-1 — Fire detection and fire alarm systems for buildings (code of practice) · british standard · verify during review · BS 5839-1 (current edition)
  • BS EN 54 — Fire detection and fire alarm systems (product standards) · british standard · verify during review · BS EN 54 series (current parts, including point-type detectors)
  • Detector and base manufacturer documentation · manufacturer manual · verify during review · Installation, compatibility and service documentation for the detector and base range on site
  • The Regulatory Reform (Fire Safety) Order 2005 · public documentation · verified source

Source labels describe the evidence basis; current manufacturer documents and licensed standards remain authoritative. Professional disclaimer

Detector Base Faults: Telling the Base from the Head

A detector fault report from the panel doesn't tell you whether the problem is the sensing element you can unclip in seconds, or the fixed wiring termination behind it that means opening up a ceiling void. Guessing wrong costs a wasted part, a wasted trip, or both, and the base-versus-head question comes up often enough that it deserves a proper method rather than an educated guess.

The essential idea is this: a detector is two separable components doing two different jobs, and almost every "detector fault" is really a question about which of the two has actually failed — a question one simple test answers reliably.

Who this is for

This is for fire alarm engineers responding to a device fault, missing device, or unexpected reading traced to a point-type detector, on addressable or conventional systems using a separable head-and-base arrangement. Experience level: competent engineer, comfortable removing and refitting detector heads safely and reading a loop or zone's response to a device change. No default access codes, engineer-level entry procedures or internal service routines are published here.

What the head does and what the base does

The head contains the sensing element — optical, ionisation, heat, multi-sensor or other technology — along with its local electronics, and on an addressable system, its own address. It is designed to be removed and refitted without tools, using a twist-lock connection, so that cleaning, replacement and periodic testing don't require access to the fixed wiring at all.

The base is permanently wired into the loop or zone. It provides the physical and electrical connection between the fixed cabling and the head, and on many ranges it can also contain additional functionality: a short-circuit isolator that protects the rest of the loop if a fault develops beyond that point, or a relay or sounder built into the base itself. A fault reported against "the detector" at a given address or location could therefore originate in the sensing element, the base's own contacts, an isolator or sounder built into the base, or the fixed wiring feeding it — four genuinely different problems that look identical from the panel's display.

The swap test, and why it beats guessing

The reliable method is a straightforward substitution: fit a known-good head of the correct type and compatible range onto the suspect base, and see where the fault goes. If the original head, when moved to a known-good base elsewhere, now works correctly, the head was faulty and the base is sound. If a known-good head fitted to the suspect base still shows the fault, the problem is in the base or the wiring behind it, not in the head.

This test is faster and more conclusive than testing the head's sensing element in isolation or measuring base contacts with a multimeter as a first step, because it directly answers the question that matters — does the fault travel with the head or stay with the location — without needing to interpret an electrical reading against a specification you may not have to hand. It does depend on having a genuinely known-good, compatible spare head available, and on the head and base being from a combination the manufacturer supports; fitting an incompatible head can itself produce a fault that has nothing to do with either component actually being broken.

On arrival and initial observations

Initial observations start with reading the panel display and event log exactly as worded: which device, what fault wording, and whether it is a fault, a missing-device indication, or an implausible reading rather than a clean fault. Note whether the device or its base has been worked on recently — cleaning, a head replacement, or nearby building work that could have disturbed the fixed wiring.

Before removing anything, check what type of head is currently fitted and what the base is designed to accept, since a mismatch introduced during a previous visit is one of the more common, and more overlooked, causes of an intermittent or immediate fault at a specific location.

Evidence gathering and site observations

Record the panel's exact reading or fault wording before disturbing the device, and note the device's analogue value history where the panel provides one, since a value that drifted gradually before faulting points toward contamination or head ageing, while a fault that appeared abruptly points more toward a connection or base issue. Photograph the base's twist-lock alignment and terminal area if there is any visible sign of damage, corrosion or moisture.

Site observations about environment are relevant to base faults specifically: a base in a damp riser, an external canopy, or a location subject to vibration is more likely to develop a genuine base or termination fault than one in a dry, stable office ceiling, where a head-side cause is statistically more likely.

What you can safely establish on site

Within the limits of your authorisation, remove the head and inspect both the head's contact pins and the base's contact sockets for corrosion, bent pins, or debris, and confirm the twist-lock engages fully and squarely rather than sitting proud or at an angle. Carry out the swap test with a known-good, compatible head. Where the base is suspected and the design allows it, measure continuity across the base's terminals with the head removed, and where the base includes a built-in isolator, check its behaviour against the manufacturer's documented method rather than assuming it is healthy because the fault presented as a device fault rather than a loop fault.

Safety warning. Leaving a base without a head fitted, even briefly, can remove detection at that point and, on some designs, present as a further loop fault if the base has no isolator or capping arrangement. Keep the period without a head as short as practical, and confirm with the manufacturer's documentation whether that specific base needs a blanking cap when left empty.

Investigation flowchart

Used as an investigation flowchart, the sequence runs:

  1. Read the panel display, event log and any available analogue value history exactly as worded before touching anything.
  2. Confirm the head type currently fitted matches what the base is designed to accept.
  3. Inspect the head's contact pins and the base's contact sockets for corrosion, damage or misalignment.
  4. Carry out the swap test using a known-good, compatible head.
  5. If the fault follows the head, confirm by testing the original head elsewhere and treat as a head fault.
  6. If the fault stays at the location, treat as a base or wiring fault and inspect the fixed wiring termination.
  7. Where fitted, check any base-integrated isolator or sounder against its documented behaviour.
  8. Repair or replace the identified component — head, base, or termination.
  9. Refit and confirm the panel reads a healthy, plausible value or state for the device.
  10. Report the finding, including which component was actually at fault, to the responsible person or logbook.

Repair, verification and testing after repair

Verification means confirming the device reads a plausible, stable value or shows a correctly cleared fault indication after the repair, not just that the immediate fault message has gone. Where a head was replaced, confirm its analogue value settles within a normal range rather than sitting at an extreme that might indicate a compatibility issue with the base. Where a base was replaced or its wiring repaired, functionally test the device — an approved detector test method, not just a visual check — to confirm the full path from device to panel actually works.

A short repair checklist for this class of work: swap test performed and result recorded; head and base contacts inspected and confirmed clean and correctly engaged; head-and-base compatibility confirmed against manufacturer documentation; device functionally tested after any base or wiring repair; analogue value or state confirmed plausible; logbook and device records updated with which component was replaced.

Escalation and spares

Escalate to the manufacturer's technical support when a swap test with a confirmed compatible head still leaves an ambiguous result, or when a base-integrated isolator or sounder is suspected of an internal fault beyond what a continuity check can confirm. A good escalation includes the head and base model numbers, the exact fault wording, the swap test result, and what has already been eliminated.

Spares are usually straightforward for common head types within a manufacturer's current range, but bases — particularly isolator or sounder bases, and anything from a discontinued range — can be harder to source and are worth checking against detector compatibility and mixing devices before assuming a like-for-like replacement is available. Estimated repair time is typically same-visit for a head swap, extending if a base or its wiring needs replacement or if a compatible spare base has to be sourced.

Common engineer mistakes

Assuming every detector fault is a head fault and reordering a head before checking the base. Skipping the swap test and instead relying on a multimeter reading against a specification not actually to hand. Fitting an incompatible head-and-base combination and mistaking the resulting fault for a genuine component failure. Leaving a base without a head, or without a blanking cap where one is needed, for longer than necessary during investigation. And not recording which component — head, base, wiring, or a compatibility mismatch — was actually the cause, leaving the fault history unclear for the next visit.

Telling the responsible person

There is a legal dimension worth being clear about. In England and Wales the Regulatory Reform (Fire Safety) Order 2005 places duties on the responsible person, including a maintenance duty in respect of the fire safety equipment provided in the premises. BS 5839-1 is a code of practice giving recommendations on the maintenance and testing of detectors and their fixed wiring; it is not itself legislation.

What that means in practice is straightforward. A device fault, whatever its ultimate cause, means that point of detection cannot be relied upon until it is resolved, and the responsible person needs a clear, non-technical explanation of what was actually wrong — a component swap versus a wiring repair — since the two can carry very different timescales and costs if a base has to be replaced or accessed through a difficult ceiling void.

Report example

A workable report example: "Device 2-14 (Store Room, First Floor) reporting Device Fault, first logged 06:58 on 27/08. Head and base contacts inspected, no visible corrosion or damage. Swap test performed with known-good compatible head — fault followed the original head when refitted elsewhere on the loop, confirming a head fault rather than a base or wiring issue. Faulty head replaced; new head's analogue value settled within normal range on test. Device functionally tested and confirmed operating correctly. No wiring or base work required."

Related faults

Related faults worth reading alongside this: detector contamination and cleaning for value drift that stops short of a hard fault, loop isolators and short-circuit protection for base-integrated isolator behaviour in more depth, loop open and short circuit faults for the wiring-level equivalent, and diagnosing manual call point faults for the same device-versus-wiring question applied to call points.

When not to rely on this alone

When not to use this article: do not use it to determine which head and base combinations are compatible on a specific system, to design isolator placement, or to decide whether a discontinued base range should be replaced across a building. The first two come from the manufacturer's compatibility documentation, and the third is a spares and lifecycle decision for the responsible person and the maintaining company.

Relevant standards

Recommendations for the maintenance and testing of point-type detectors and their fixed wiring are given in BS 5839-1, current edition. Product requirements for the detectors themselves sit within the relevant parts of the BS EN 54 series. These are standards, not law; the statutory duty in England and Wales rests with the responsible person under the Regulatory Reform (Fire Safety) Order 2005. Work to the current edition in every case and to the manufacturer's compatibility documentation for the specific head and base range.

Professional disclaimer

This is an educational resource for competent engineers. It does not replace the current British Standards, the manufacturer's documentation, safe working practice or professional judgement. Work within BS 5839-1 and verify head-and-base compatibility and fault behaviour against the manufacturer's manual before acting on it.

Related documentation

Read this with detector contamination and cleaning and detector compatibility and mixing devices. Recording device faults, swap test results and replacements is easier with the fault database and the digital logbook.

References

  • BS 5839-1 (current edition), BSI
  • BS EN 54 series (current parts), BSI
  • The Regulatory Reform (Fire Safety) Order 2005 — legislation.gov.uk
  • Detector and base manufacturer installation, compatibility and service documentation for the equipment on site

Frequently asked questions

What is the difference between a detector head fault and a base fault?

A detector is two parts: the head, which contains the sensing element and reports the reading or the alarm, and the base, which is permanently wired into the loop or zone and holds the head in place with a twist-lock connection. A head fault means the sensing element or its electronics have failed. A base fault means the problem sits in the fixed wiring termination, the base's own contacts, or — on addressable and some conventional systems — an isolator or sounder built into the base itself. The distinction matters because a head is a quick, tool-free swap; a base fault means opening up the fixed wiring.

How do you tell a head fault from a base fault without guessing?

The reliable method is the swap test: fit a known-good head of the correct type onto the suspect base. If the fault follows the head — meaning the original head now works correctly on a different, known-good base — the head was faulty. If the fault stays with the location even with a known-good head fitted, the base or the wiring behind it is at fault. This single test resolves the great majority of head-versus-base questions faster and more reliably than testing components individually.

Can a base fault be caused by the wrong base being fitted?

Yes, and it's a common cause on systems that have had detectors replaced over time. Bases from different manufacturers, and even different ranges from the same manufacturer, are not always interchangeable — the twist-lock mechanism may fit physically while the electrical contacts, addressing pins, or isolator behaviour do not match what the head or the panel expects. A head that reports a fault or behaves unexpectedly immediately after being fitted to an unfamiliar base is worth checking against the manufacturer's compatibility documentation before assuming either component has failed.

Why would removing a detector head cause a loop fault?

On some addressable loop designs, a missing head can leave the base's contacts open in a way the loop interprets as a fault rather than simply a missing device, particularly if the base does not have a built-in short-circuit isolator or link. This is manufacturer- and range-specific. Leaving a base empty for longer than necessary — during cleaning, replacement or investigation — should always be avoided where the design makes this a risk, and the base should be capped or the head replaced as quickly as practical.

Related tools and references