Trouble or alarm will not clear after the fault is fixed
very common
“I fixed the actual problem and the panel still won't go normal. Resets, comes straight back, or it clears and reappears. Nothing in the building is wrong any more.”
Likely causes
-
Points left disabled or bypassed in software from a previous visit
~25%Panel sits in trouble with no field fault anywhere. Pull the disabled-point list: somebody bypassed a device during a nuisance episode or a construction phase and never restored it, and the panel has been telling you so ever since.
-
System left in walk-test, one-man-test or a programming mode
~20%Odd behaviour that makes no sense as a wiring fault: devices resetting themselves, the panel refusing to latch, notification behaving strangely. Check the panel's operating mode before you chase anything electrical.
-
A latched trouble or alarm that needs a specific clearing action
~15%Some troubles and some devices latch and require an explicit reset, a longer reset hold, or clearing at the device rather than at the panel. A releasing circuit, a latching supervisory or a module with its own reset all behave this way. Read the manual for that point type.
-
A second, different fault behind the one you fixed
~15%The trouble text changed subtly after your repair, or the point number is different from the one you worked on. Read the current trouble carefully rather than assuming it is the same one returning: panels that annunciate a common trouble hide this well.
-
Program mismatch after a firmware update or a board swap
~15%Started the day a board was replaced or firmware was loaded. The panel's stored program no longer matches the installed hardware, or the program was never reloaded after the swap. Compare the panel's reported configuration against the as-built program.
-
Genuine intermittent fault that has not actually been fixed
~10%Clears on reset and returns minutes or hours later with no pattern you can force. Honest answer: the repair missed. Go back to the diagnostic entry for the original fault and treat it as intermittent rather than resetting repeatedly.
What to bring
- Panel keys and the installation manual for the panel and the point type
- Panel programming laptop with the current as-built program file
- Camera for the trouble display and the disabled-point list
- DMM
- Job file and the previous visit's service reports
Safety
Licence and AHJ coordination as required. Every point you find disabled is an impairment that has been running unlogged, possibly for months. Notify the owner and the AHJ when you find them rather than quietly restoring and moving on, because the record matters. Do not clear a trouble by disabling the point that reports it. Reloading a panel program takes the whole system out of service for the duration: log it, coordinate it, and save the existing program before you write anything.
Steps
-
Step 1: Read the current trouble text and point number, not the one you remember
Free, and it splits the problem immediately. A different point or different wording means a second fault, not a persistent one. Photograph the display before you press anything.
If that doesn’t do it
Same point, same text: move to the panel's own state.
-
Step 2: Pull the disabled, bypassed and out-of-service point list
This is the single highest-yield check on the entry and it takes under a minute at most panels. Anything on that list is a point the panel is not supervising, and it may be the whole reason the system will not go normal. Restore each one deliberately and confirm it answers healthy.
If that doesn’t do it
Nothing disabled: check the operating mode.
-
Step 3: Confirm the panel is in normal operating mode
Check for walk-test, one-man-test, sensitivity test, programming mode or any service mode left active. Exit properly by the manual's method rather than by cycling power: an abrupt exit can leave points in an odd state.
If that doesn’t do it
Panel is in normal mode: check what the point type requires to clear.
-
Step 4: Find out what that specific point type needs to clear
Read the manual for that device or circuit type. Some latch and need an explicit reset, some need the reset held longer, some clear only at the device, and some will not clear while an upstream condition persists. Repeated blind resets teach you nothing and on some systems create their own problems.
If that doesn’t do it
Correct clearing action performed and it still will not clear: verify the field condition is genuinely resolved.
-
Step 5: Re-verify the field fault is actually gone, at the device
Go back and measure or observe at the point rather than trusting the repair. The honest possibility here is that the fix did not hold, and a panel refusing to clear is usually right.
If that doesn’t do it
Field condition confirmed clean at the device: suspect the panel's configuration.
-
Step 6: Compare the panel's configuration against the as-built program
After a firmware update or a board swap, the stored program and the installed hardware can disagree in ways that surface as a permanent trouble. Compare the panel's reported configuration to the as-built program file, and reload from the current file if they differ, never from an old file on a laptop, and always after saving what is currently in the panel.
If that doesn’t do it
Configuration matches and the trouble persists: this is a panel hardware or supervision fault; substitute the suspect board onto a spare position to prove it.
-
Step 7: Restore everything you touched and confirm the system sits normal
Re-enable every point you restored, confirm each answers healthy, confirm the panel holds normal for a sustained period rather than for the thirty seconds you are standing there, and record in the job file exactly what was disabled and by whom. Leaving a point bypassed is how this call gets generated in the first place.
If that doesn’t do it
Clears and returns later: treat it as an intermittent fault on the original entry, record the panel's error counters and history, and schedule a return rather than another reset.
References
- NFPA 72, Ch. 10
- NFPA 72, Ch. 14
- NFPA 72, Ch. 23
- IFC 901.7