Fire Alarm Ground Fault Troubleshooting: A Canadian Walkthrough

Last updated: September 2026

Quick answer

• A ground fault is an unintended low resistance path between a field conductor and grounded metalwork. It is not a short between the two conductors, and not an open.
• Initiating and notification circuits float with respect to earth, so one conductor touching ground draws almost no current and trips nothing. The panel only knows because the control unit carries a dedicated ground fault detector.
• That it gets reported at all is Canadian: the Building Code requires electrical supervision, and CAN/ULC-S524 requires that one fault not stop devices working in more than one Building Code required zone.
• Find it by half-splitting: prove panel against field, drop circuits one at a time, then split the faulted circuit at its midpoint and keep halving.
• Water is the most common cause by a wide margin, then a fastener through a conductor, a loose shield drain wire, a pinched conductor behind a device, moisture in a duct housing, and a stressed conductor at a bend.
• In Ontario, once the system is in service, repairing it is Fire Code work under Division C Article 1.2.1.2 of O. Reg. 213/07, not something the 309A covers on its own.

What a ground fault actually is on a 24 V circuit

Take a two conductor initiating circuit leaving the panel. Current goes out on one conductor, through the end of line device, and back on the other. Neither conductor is bonded to earth: the circuit floats.

Now scrape the insulation off one conductor against the edge of a metal box. That conductor is tied to the building bonding system, which is tied to the panel chassis, which is tied to earth. On a power circuit this operates an overcurrent device, because the grounded conductor gives fault current somewhere to go. On a floating 24 V DC circuit, nothing happens: no return path, no current rise, no voltage collapse. Loop resistance does not change and a meter across the circuit reads healthy.

That is why the condition gets a dedicated detector rather than a fuse. A ground fault is the first of two faults. Ground a second conductor, on that circuit or any other sharing the same bonding system, and you have a path through the building steel that can short a circuit, hold a relay, or bridge two zones. The system can then fail to alarm, or alarm falsely.

Why the panel sees it: supervision is the whole reason

Everything that makes a ground fault visible in Canada comes from the supervision scheme, and that scheme is Canadian. The Building Code requires electrical supervision of a fire alarm system. Canadian code indexes and the Canadian column in IAEI Magazine both put that at Article 3.2.4.9, in the National and Ontario Building Codes alike, but we did not confirm the number against the 2024 Compendium.

CAN/ULC-S524, the installation standard, carries a single fault rule: one fault, meaning one open circuit fault, one short circuit fault or one ground fault, must not prevent normal operation of input or output field devices in more than one fire alarm zone required by the National Building Code. UL's own presentation to the Building Officials Association of British Columbia puts that at Section 18.1 of the 2019 edition, applying to all circuits leaving the control unit. That is a paraphrase: the standard is paywalled.

The hardware side is CAN/ULC-S527, now titled Standard for Control Units and Accessories for Fire Alarm Systems. The 4th edition published 5 April 2019 and has since been superseded by the 5th edition, CAN/ULC-527:2024. Neither Ontario code designates S527 directly, and a panel already in service is listed to whichever edition was current when it was listed, so read the listing mark on your own panel rather than assuming the newest edition applies to it. Mircom, a Canadian manufacturer, puts it plainly: the panel has a common ground fault detector, the ground fault LED flashes amber at the trouble flash rate when it detects a ground fault on any field wiring, and the fix is to check for wiring touching the chassis or another earth ground connection. That word common matters: it says a ground exists somewhere in the field wiring, not where, and reports one when there may be three.

Ground fault, open circuit, short circuit: three different troubles

A ground fault does not change loop resistance. An open and a short both do, in opposite directions. That is why you can get a clean ohm reading across a grounded circuit, and why you will get a fresh open circuit trouble the moment you lift the end of line device while chasing a ground. Expect it, do not chase it. An addressable panel may name the data link, because each loop card has its own detector, but never a device address: a ground fault is not a device event.

The half-splitting procedure, step by step

Read the panel first. Note every trouble, not just the ground, and print or photograph the event history with time stamps: that is often the whole answer for an intermittent fault and you cannot get it back once you start power cycling. Tell the owner what you are doing, make sure the monitoring station knows so your disconnections do not become a dispatch, and confirm any watch service requirement with the Chief Fire Official. Write down every conductor you lift.

Each step must halve the search space, and you must not skip ahead to the device you have a hunch about.

1. Prove panel against field. Lift every field conductor from the terminal strips, leaving the panel powered with only its own internals connected. If the ground clears, the fault is out in the building. If not, it is inside the cabinet: check the battery leads, the earth bonding conductor, and anything screwed down on top of a wire, including the harness behind the door hinge.

2. Reconnect one circuit at a time. Land one, wait for the panel to re-supervise, look, then land the next. When the trouble returns, that is your circuit. Work through the rest anyway, because a common detector reports one ground and there may be two.

3. Split the faulted circuit at its midpoint. Find a device or junction roughly half way along the run in wiring order, not half way across the floor plan. Those two orders are almost never the same, and this is where people lose the afternoon. Lift the outgoing conductors there and cap them. If the ground clears, the fault is downstream; if it stays, upstream.

4. Keep halving. A forty device circuit reaches one device in about six splits. Walking it device by device takes forty.

5. Down to one segment, the fault is in the cable between two boxes, in one of those boxes, or in the device. Lift the device and test the cable alone.

6. Restore as you go, then verify every circuit is back, every end of line device is in place, and the panel is normal.

Meter technique: what to measure, between what and what

Never measure resistance on a live circuit. Disconnect the circuit at the panel, leave the far end as it is, and measure resistance from each field conductor to a known good ground. Use the panel chassis bonding terminal as the reference, not a random piece of conduit.

• Out of range, or tens of megohms: that leg is not grounded. On a long damp run with intact insulation, a few megohms can be normal.
• Near zero to a few hundred ohms: a hard ground. Metal on metal, or a conductor sitting in water.
• A few kilohms to a couple of megohms: a partial ground, the case that wastes time. The detector may see a fault while your reading looks reassuringly high. Believe the panel.

Comparison beats absolutes: measure the suspect conductor, then its partner, then the same pair on a clean circuit. Neither Mircom manual we reviewed publishes the resistance at which the detector calls a ground fault, and thresholds are a control unit characteristic under CAN/ULC-S527, which is paywalled. Do not accept a pass or fail ohm value that is not in your own panel's manual.

And do not megger a circuit with devices connected. An insulation resistance tester applies 250 V or 500 V and will destroy addressable device electronics, detector heads and end of line components. Use it only on cable disconnected at both ends.

What actually causes them, in the order you will find them

1. Water ingress, and it is not close. Parkades, loading docks, roof devices, exterior horns and strobes, unheated stairwells, boxes cast into slab, underground conduit to a detached building. Water enters through a failed gasket or top entry knockout, runs down the conduit, and pools at the low point across a terminal. The signature is a ground that appears after rain or a thaw and clears after a dry week.

2. A fastener through a conductor. A drywall screw straight through the cable, an oversized staple, a missing nail plate. Turns up at handover, right after the interior trades.

3. A shield or drain wire on a box or terminal. Wherever shielded cable runs on a data link or annunciator circuit, the drain is meant to be terminated at one point and insulated everywhere else. Instead it gets cut short and taped at each device, the tape relaxes, and it finds a box screw.

4. A back-box pinching a conductor. Push the device home, trap the conductor between the device chassis and a box edge or mounting screw, and the insulation cuts through. Pull stations and horn strobe back-boxes with tight raceway entries are the offenders.

5. Moisture in a duct smoke detector housing. Condensation, sampling tubes drawing humid air, or a housing on the cold side of the coil. The signature follows the air handler: present when it runs, gone when it stops.

6. A damaged conductor at a tight bend under tension. Pulled hard around a 90 degree LB or a box offset, the insulation stretches rather than cuts, so it passes verification and fails months later.

Intermittent and temperature dependent faults

This is where most people give up, so it is worth knowing why they come and go.

Water is the obvious driver. Rain, snowmelt, wash-down, a cleaner with a wet mop over an in-floor box. Correlate the event history against the weather and you often have the answer before you leave the office.

Thermal movement is the subtle one. Conductors, boxes and raceway expand and contract, so a conductor resting against a burr or a sharp knockout makes contact only when hot, or only when cold. A rooftop or parkade run in Ontario swings through sixty degrees Celsius over a year, and a fault that shows only in February, or only in a July heat wave, is almost always this.

How to catch one. Log it rather than chase it, then use the half-split as a negative test: disconnect the suspect circuit and leave it lifted through the conditions that normally produce the fault. If the trouble stays away, you have confirmed the circuit without ever seeing it. If it returns anyway, you were on the wrong circuit and have saved yourself another day.

What you must not do is reseat a dozen terminations, watch the trouble not return that afternoon, and call it repaired.

What you are permitted to do about it in Ontario

The physics is universal. The permission is not, and two tracks get run together constantly.

Installation work on a system not yet in service is electrical work. Electrician, Construction and Maintenance (309A) is a compulsory trade in Ontario, and an ESA licence is required to offer installation services to the public. The wiring rules come from Section 32 of the Ontario Electrical Safety Code. The 2024 OESC came into force 1 May 2025 and is the 29th edition, containing the 26th edition of CEC Part I plus Ontario amendments; ESA's own pages are inconsistent about that ordinal, and the OESC glossary entry settles it. Rule 32-100 requires fire alarm conductors to be copper with adequate ampacity, and an Alberta Municipal Affairs STANDATA cites the same rule number. Canadian trade press guidance also puts independent termination of each circuit conductor, for electrical supervision, at Rule 32-106, which is the one that matters here: twist two conductors under one screw and the panel cannot tell whether the field wiring is still there. We confirmed only 32-100 against a government source, so check any other Section 32 number in your own code book.

Fire Code work is a different regime, starting the moment the system is in service. Ontario Fire Code, O. Reg. 213/07, Division C, Article 1.2.1.1 applies to a person who performs annual tests or inspections, who tests and maintains components interconnected with other fire protection and life safety systems, and, at clause (c), who repairs, replaces or alters components of a fire alarm system. Repairing a ground fault on a system in service is squarely clause (c).

Article 1.2.1.2.(1)(a) then requires that person to have completed a program or course acceptable to the Fire Marshal, and to produce the certificate on request of the owner or the Chief Fire Official. Two programs currently qualify: the CFAA Fire Alarm Technician Training Program and ECAO's Certi-Fire. Article 1.2.1.2.(2) lets someone without the qualification do the work under supervision, with three hard limits: supervision at the work site, no more than two people at a time under one supervisor, and under 1.2.1.2.(3) written confirmation to the owner. Article 1.2.1.3 puts responsibility on the supervisor as though they had done the work themselves.

So a 309A pulling new cable on a construction site and a 309A troubleshooting a ground fault on an occupied building's live panel are in different legal positions. The certificate covers the electrical work in both; on its own it does not cover the Fire Code work in the second. The full treatment is in who can legally work on fire alarms in Ontario, which is canonical if anything here reads as narrower.

Two more hooks. Division B Article 6.3.1.8 requires repairs, replacements and alterations to be in accordance with CAN/ULC-S524, and an alteration rather than a like for like replacement can re-trigger verification of the affected portion under CAN/ULC-S537.

Writing it up

The 2019 editions moved the report forms into the body of the standards, making the form and the format mandatory: UL's guidance to Canadian building officials says tests and inspections may not be reworded or revised in order or format. On the published CAN/ULC-S536:2019 form the summary sections are 20.2 Deficiencies, 20.3 Recommendations and 20.4 Technician Attendance Log, and device records carry a Comments column.

• A deficiency is a condition where something does not operate as intended, is not readily accessible for service, sits in an incompatible environment, or is in a location it was not intended for. UL places that at 28.2.1. An active, located, unrepaired ground fault is a deficiency.
• A recommendation is a proposal for improvement rather than a compliance failure, placed by UL at 28.3.1: swapping the exterior strobe back-boxes for a gasketed type, say.
• There is no third finding type. Remark is the older term, replaced with "Comments". The free source for that, and the limits on how far it reaches, are set out on that page. Legacy forms and older software still carry a Remarks block, so use the headings printed on the form in front of you.

The fault you could not reproduce still goes on the report: the dates and conditions it appeared under, the event history you pulled, which circuits you eliminated and how, and what you propose next. A report saying "ground fault, cleared" with no method behind it is worth nothing to the next person.

What we could not confirm

• The Building Code article number for electrical supervision. Resolved 5 September 2026. Electrical supervision is Article 3.2.4.9 of the Ontario Building Code, read directly in the official 2024 Building Code Compendium published by Publications Ontario. Article 3.2.4.10 is Fire Detectors, and several Canadian sources cite that number by mistake, most likely because it is the National Building Code number for the same provision.
• The ground fault detection threshold. No resistance value appears in the Canadian manufacturer manuals we reviewed, and CAN/ULC-S527 is paywalled.
• Section 32 rule numbers other than 32-100, which are Canadian trade press only, and whether the deletion of "Remark" reaches CAN/ULC-S536:2019 as well as S537:2019, which we read across by inference rather than from text.
• The trigger for watch service in Ontario, which we could not retrieve from e-Laws.

Confirm anything here with your authority having jurisdiction before relying on it for a specific building.

---

Fire Alarm Academy provides educational content only. It does not confer any certification, licence or credential, and it is not affiliated with, endorsed by, or accredited by the Canadian Fire Alarm Association, the Electrical Contractors Association of Ontario, ULC Standards, UL Standards and Engagement, CSA Group, the Electrical Safety Authority, any authority having jurisdiction, or any manufacturer. Always work from the edition of any standard adopted by your authority having jurisdiction.