How to diagnose an Apollo XP95 open circuit fault

Overview

An open circuit fault on an Apollo XP95 addressable loop is one of the most common fault types you'll attend. It means the panel has detected a break in the loop wiring that prevents it from communicating with one or more devices. On a two-wire loop system, an open circuit will typically take out every device beyond the break point — so you might see five, ten, or fifty devices suddenly going offline.

This guide walks you through diagnosing and clearing an XP95 open circuit fault systematically, using the information the panel gives you and a logical approach to cable tracing.

What the Panel Is Telling You

When the XP95 panel reports an open circuit, it will display:

• Fault type: Open circuit (or "Loop Open Circuit" depending on the panel variant)
• Loop number: Which of the addressable loops is affected
• Last good address: In many cases, the XP95 system will show you the last device address it could successfully communicate with before the break

That last address is your most important piece of information. The break is almost certainly between that device and the next device in the loop sequence. Write it down before you do anything else.

Probable Causes

Open circuit faults on XP95 loops are usually caused by one of the following, roughly in order of likelihood:

1. Cable break between devices — Physical damage to the loop cable between the last online device and the first offline device. This is the most common cause. Cable can be damaged during other works, pinched under cable trays, or suffer insulation failure over time.

2. Faulty or improperly seated device base — A detector base that isn't making proper contact can interrupt the loop continuity. Even a single faulty base with poor pin contact can break the circuit for everything downstream.

3. Loose or corroded termination in a junction box — Wago connectors, traditional terminal blocks, and Choc blocks in field junction boxes can work loose, corrode, or have single-core cable pulled out slightly. This is especially common in damp environments or where cable trays experience vibration.

4. Failed isolator module — XP95 systems use isolator modules at strategic points in the loop to section off faults. If an isolator module has failed in the tripped position, it will appear as an open circuit beyond that point. Unlike a genuine cable break, the isolator module LEDs may give you additional information.

5. Device removed from base — Someone has removed a detector from its base without replacing it, and the base hasn't been fitted with a loop-continuity shorting plug. This isn't a failure — but it presents identically to an open circuit.

Diagnostic Procedure

Step 1: Record the fault information

At the panel, note the loop number and the last communicating address before the break. If the panel shows you an address range (e.g., addresses 1–42 online, 43–127 offline), you're looking for a fault between address 42 and 43.

Step 2: Identify the physical location of the boundary devices

Using the system's as-installed drawings or the panel's device list, find the physical location of the last online device (address 42 in our example) and the first offline device (address 43). The fault is somewhere in the cable run between them — or at address 42's base, or address 43's base.

Step 3: Check the obvious culprits first

Before tracing cable, do a quick visual check:

• Is there any device obviously missing from a base in the affected area?
• Are there any junction boxes that look recently disturbed?
• Has any other trade been working in the area?

Step 4: Check the boundary device bases

Remove the detector from address 42's base and check:

• Are the loop cable cores properly terminated in the base?
• Is the screw terminal tight?
• Are there any signs of overheating or arcing?

Then check address 43's base the same way. Reinstall the detectors after checking — a detector that isn't seated properly can cause intermittent loop issues.

Step 5: Trace the cable run

With a multimeter set to continuity, you can check the cable between the two boundary devices:

• Disconnect the loop cable at address 42's base (outgoing side)
• Short the two conductors together at address 43's base (or the far end of the run if the base isn't accessible)
• Check for continuity back at address 42's outgoing terminals

No continuity confirms a cable break. Now walk the route: look for damage, pinch points, or any area where cable might have been disturbed.

Step 6: Check junction boxes in the run

Every junction box between addresses 42 and 43 is a possible fault point. Open each one and check that all terminations are tight and that conductors aren't corroded or damaged.

Step 7: Check for isolator modules

If your system uses isolator modules, identify any that fall between addresses 42 and 43. An isolator module that has operated (tripped) due to a downstream short circuit will appear as an open circuit once the original short is cleared. Check the isolator module's status LEDs.

Resolution

Once you've located the break:

• Cable break: Depending on severity — repair, splice, or replace the cable run. Ensure any joints are made in accessible junction boxes, properly terminated, and documented.
• Loose termination: Re-terminate the conductor properly. On older wiring, it's worth checking adjacent terminations in the same box while you're there.
• Failed isolator: Replace the isolator module.
• Missing detector: Fit a replacement detector or a proper continuity plug in the base.

After resolving the fault, restore the panel from fault condition and confirm all previously offline devices come back online.

Standards Reference

Open circuit faults on addressable loops should be investigated and resolved in accordance with:

• BS 5839-1:2025 — particularly clauses relating to fault investigation, repairs to cables, and documentation of remedial works
• The Apollo XP95 Technical Manual — for loop impedance limits, isolator placement requirements, and device addressing guidance

Always document the fault, the probable cause identified, the resolution carried out, and the date. This forms part of the fire alarm system's service record.

Need help diagnosing an XP95 fault on site? Sign up to Incognito Fire & Security Professional — describe the fault in plain English and get ranked probable causes and step-by-step diagnostic procedures in seconds.