Apollo Discovery Fault Diagnosis: Common Faults and How to Fix Them

Apollo Discovery is one of the most widely installed addressable protocols on UK commercial and industrial sites. If you work on fire alarms regularly, you'll encounter Discovery devices constantly — and the fault patterns are well established once you know what to look for.

This guide covers the faults that come up most often on Discovery systems and how to work through them efficiently on site.

Apollo Discovery Protocol: Quick Orientation

Discovery is a two-wire Class A or Class B addressable loop protocol. Devices communicate with the panel using a current-modulated signal on the loop wiring. Each device has a unique address set by DIP switch (older versions) or rotary switches.

Discovery devices include:

• Series 60 optical smoke detectors (65000-600APO, 65000-635APO)
• Series 60 heat detectors (55000-600APO, 55000-635APO)
• XP95 devices (older, still widely in service — see separate guide)
• Orbis range (updated design, same protocol with enhanced diagnostics)
• Manual call points — standard and flush
• Input/output modules — Monitor modules, control modules, zone monitors

Reading Fault Information

On most panels running Discovery protocol, you can pull the analogue value and device status for each address from the engineer menu. Before starting fault diagnosis, always:

1. Pull the full event log — the sequence matters more than the current state
2. Note all faulted addresses
3. Check whether the fault is permanent or intermittent (recurring in the log vs. present since a specific event)

Common Faults: Apollo Discovery

Device Communication Fault / No Response

What the panel shows: Communication fault at a specific address, or the address dropping out of the device list entirely.

What it means: The panel is not receiving a valid response from the device at that address.

Diagnosis:

1. Go to the device. Check the terminal connections at the base — loose terminals are the single most common cause of communication faults on Discovery installations.
2. Check the address setting on the device. A duplicate address on the loop causes both devices to conflict; one or both will fault intermittently.
3. Swap the detector head with a known-good unit. If the fault follows the head, the device has failed. If it stays at the same address, the issue is in the base, cable, or a duplicate address.
4. On Class A loops, check whether the loop continues correctly past the fault point — a break in the outgoing feed with a functioning return path will keep devices beyond the break communicating but differently than expected.

Common root causes: Loose base terminals, corroded contacts on Series 60 bases (particularly in damp plant areas), duplicate addresses after device replacement without address verification.

Dirty Detector / Pre-Alarm

What the panel shows: "Dirty detector", "Pre-alarm", or an analogue value outside the normal range for that device.

What it means: The detector's chamber is contaminated — dust, insects, paint vapour, or condensation. The device is reporting a higher-than-normal particulate reading but hasn't crossed the alarm threshold.

Diagnosis:

1. Check the analogue value from the panel. Apollo panels typically display this as a percentage or raw count. For Discovery optical detectors, clean-air analogue values are typically in the range of 0–50 counts; dirty detector warnings typically appear above 80–100.
2. Go to the device and remove it from the base. Inspect the chamber — look for visible dust accumulation, insect debris, or discolouration.
3. Clean using a vacuum and soft brush. Do not use compressed air — this can force contamination further into the chamber. Do not use solvents.
4. Refit the detector and check the analogue value has recovered. If it hasn't recovered after cleaning, the chamber is permanently contaminated and the detector should be replaced.

Common root causes: Dusty environments (workshops, roof spaces), installation dust not cleared before commissioning, detectors near HVAC vents or air handling units, detection in kitchens or areas with airborne grease.

Loop Short Circuit / Isolator Operation

What the panel shows: Short circuit on loop X, isolator operated at address YY.

What it means: A short has occurred between the two loop conductors. The loop isolators (built into each device) have operated to contain the short to a section of the loop, keeping the remainder active.

Diagnosis:

1. Note which isolator addresses have operated — the short is between those two addresses.
2. Systematically disconnect devices in the identified section. When the short clears at the panel, the last device or cable section you disconnected contains the fault.
3. Check for:
   • Physical damage to cable (mechanical impact, vermin, staples through the cable)
   • Water ingress at junction boxes or in bases
   • A device with shorted internal circuitry (less common but occurs after water ingress or physical damage)
4. On older installations, check junction box connections — strand contact between live and return conductors from a poorly made termination.

Loop Open Circuit / Device Missing

What the panel shows: Devices missing from a specific address range, or open circuit on loop.

What it means: A break in the loop wiring. On a Class A (fully supervised) loop, the panel will identify that one direction is interrupted but may continue communicating via the return path. On Class B, devices downstream of the break will all drop out.

Diagnosis:

1. Note the last responding address before the gap. The break is on the outgoing side from that device.
2. Check the cable at that device's outgoing terminal first — loose screw terminals on Discovery bases are a frequent cause of apparent open circuits.
3. If terminations are correct, use a test meter to check continuity on the outgoing conductors from that base.
4. Trace the cable physically if continuity is confirmed at the base but devices remain missing — the break may be within conduit, trunking, or at an intermediate junction box.

Device Type Mismatch

What the panel shows: "Wrong device type" or type fault at a specific address.

What it means: The device installed at that address is a different type from what the panel configuration expects. This is common after device replacement.

Diagnosis:

1. Check the panel configuration for that address — what device type is expected?
2. Physically inspect the installed device — model number is usually on the base or detector head.
3. Either replace with the correct device type, or update the panel configuration. Document the change.

Preventive Points Worth Noting at Service

When servicing Discovery installations, it's worth checking these proactively — they generate reactive callouts if missed:

• Base terminal torque — loose terminals on Series 60 bases are the leading cause of intermittent faults. Check torque at every device during annual inspection.
• Analogue values — any device reading above 60% of alarm threshold in clean air is worth noting. It won't be faulty today but it will be.
• Address duplicates — rare but happens after additions. Run a full device list from the panel and check for any duplicate addresses.
• Isolator operation history — if any isolators show in the event log as having operated (even if they've subsequently restored), investigate the section they isolated rather than clearing the log.

Panel Compatibility

Apollo Discovery devices work across a wide range of panels including Advanced MxPro series, Notifier ID and NFS series, Kentec Syncro, Hochiki FIRElink/FX panels configured for Discovery, and many others. Panel-specific fault displays vary — refer to your panel documentation for exact fault text and engineer menu navigation.

IFS Pro's fault code library covers 900+ faults across Apollo Discovery, XP95, and Orbis ranges, cross-referenced with panel-specific diagnostics. Available at incognitofiresecurity.com.