18.2 Panels, Alarm Devices, and Communications Service

Module 5.III is nine classroom hours on control panels, alarm devices, and communications in a service setting (19 NYCRR 196.8). This Independent OpenExamPrep section keeps those hours in one dense pass. You already met architecture (Chapter 8), batteries (Chapter 7), NACs and SLCs (Chapters 8 and 9), and communicators (Chapter 10). Here the exam asks what failed, how you prove it, and what you are allowed to put back.

Servicing under 19 NYCRR 195.1 is repair, troubleshooting, and replacement of failed equipment, including programming tied to that repair. Reloading access codes, protocol, bypass, and hours of operation after a board swap is servicing, not a free software hobby. Preventive cleaning on a schedule is maintaining. Placing a new panel is installation. Knowledge of those codes and hours, on-site or off-site, is assisting. Direct 120-volt landings at a distribution panel remain outside the alarm-system definition.

This statewide sitting is still not an FDNY Certificate of Fitness. A New York City job can be more restrictive and can involve city inspection under GBL §69-z; the service method below still applies to the DOS paper.

Dirty smoke detectors

Addressable photoelectric detectors report maintenance, dirty, or drift troubles when the chamber is contaminated or the sensing compensation has run out of range. Conventional two-wire smokes more often show as a zone that will not reset, a zone that false-alarms, or a zone that never alarms because the head is dead.

Service method: identify the point or divide the IDC; inspect the chamber; clean only as the listing allows (the manufacturer method — do not wash an unlisted way); replace if the listing says the head is not a field-clean item or if it still fails a functional check. After cleaning or replacement, test that device. A dirty head is not a reason to disable the entire SLC overnight without impairment notices (Section 18.1).

Do not replace a photoelectric with an ionization (or a heat with a smoke) as a “cleaner” substitute. That is a type change, treated below.

Failing batteries

A FACU on AC with a healthy charger shows a float voltage above the nominal bank (Chapter 7 used the picture of about 27 V on a 24 V sealed lead-acid pair). Symptoms of failing batteries: low battery trouble, short standby, communicator resets on AC fail, cracked cases, swollen jars, missing date of manufacture, or a bank that collapses when you apply a listed load check.

Service method: confirm AC is present before you condemn batteries (an AC fail plus a tired bank is two faults). Measure float with the charger connected, then perform the load check the manufacturer lists. Replace with the listed capacity and chemistry the panel calls for. Date the new bank. Battery replacement is named equipment under 195.1. The 120-volt breaker is still typically electrician work under 195.2.

Security panels in the same license fail the same way on a 12 V jar: keypad brownouts, siren chirps, and a communicator that dies when the transformer is unplugged. Same method, different nominal voltage.

NAC shorts

A short on a notification-appliance circuit is trouble, not a successful alarm test. Many FACUs disconnect that NAC so the supply does not dump into a bolted pair. Polarized horns landed backwards stay silent in alarm (Chapter 7 reverse-polarity supervision). A missing end-of-line device is an open, not a short.

Service method: isolate the NAC, de-energize, measure ohms (near 0 Ω is a short; OL is an open; the listed end-of-line value is supervision). Half-split. Look for staples through both conductors, a shorted appliance, a speaker coil to shield, or a sync module failed short. Repair, restore the listed end-of-line at the last appliance, then alarm-test the circuit — with the account on test and, if occupant notification will be silenced beyond a brief test, with AHJ and monitoring notice.

SLC ground faults

A ground fault is an unwanted path from a field conductor to earth, steel, conduit, or chassis (Chapter 7). Addressable SLCs are famous for this: a pinched fire-alarm jacket on a metal stud, a wet base, a shield landed on the wrong terminal, a door-holder circuit leaking onto an adjacent pair.

Service method: read whether the trouble names SLC 1 earth or similar. Isolate branches and isolators. With the pair isolated and de-energized, measure each conductor to chassis. Lift devices until the path opens. Do not lift the panel ground. Do not “fix” it by disabling ground-fault supervision in programming unless the listing and the AHJ allow a documented, listed option — and that programming is still 195.1 work.

Communicator path failures: cellular outage and IP DHCP

Off-premises reporting fails in ways that look like panel failures.

• Cellular outage: no signal strength, carrier maintenance, a moved antenna, a new metal canopy, an expired SIM or account, or a panel that never received the second path. The FACU shows communicator trouble or failure to communicate. The central station may show failure-to-test (Chapter 10).
• IP / DHCP: an Internet Protocol communicator that leases an address from a building router can go deaf when the router reboots, the lease changes, or a firewall blocks the listed ports. A static address the information-technology staff later reassigns is the same outage with a different name. Dual-path (IP plus cellular) is supposed to keep a path when one media dies; if both paths were programmed to the same failed switch, you do not have independence.

Service method: put the account on test; read the communicator trouble; confirm primary power and the phone or network path at the listed interface — not by unplugging the building’s entire network “to see.” Programming account numbers, test timers, and backup-path fail behavior is 195.1 programming. Consumer voice-over-IP in place of analog seizure is a Chapter 10 trap, not a repair.

Corrupted programming

Brownouts, failed boards, incomplete downloads, and someone else’s laptop session leave a FACU with the wrong points, missing NAC mapping, or a communicator protocol that no longer matches the receiver. Symptoms: devices that report as wrong types, a printer that jams on nonsense, bypasses that never clear, hours of operation that disarm a combination unit’s security side unexpectedly.

Service method: compare the live program to the as-built record. Reload from a known-good file if the listing allows. After a board replacement, re-enter access codes, protocol, bypass maps, and hours of operation — that reload is servicing under 195.1. Then functionally test affected points. Do not rewrite the sequence of operations while you are there unless the approved documents and the AHJ say so.

Printer and annunciator off-line

A required printer or remote annunciator that is off-line is a trouble. Paper out, ribbon, serial cable open, wrong communications settings, or a disabled printer-supervision option will do it. An annunciator path that opens should trouble the FACU (Chapter 8).

Service method: restore the listed printer or annunciator, repair the supervised path, and confirm the event prints and the remote display matches the FACU. Disabling printer supervision to silence the buzzer is not a repair. A graphic annunciator in a lobby that is dark during a real alarm is a failed operator interface, not a “printer accessory.”

Like-for-like listed replacement versus changing type

Replace a failed device with a listed, compatible, like-for-like part: same function, same listing family the panel compatibility list allows, same electrical characteristics. A photoelectric smoke for that photoelectric address, a 15/75 candela strobe for that 15/75 candela appliance if that is what the notification design required, a 12 V 7 AH battery for that 12 V 7 AH (or the listed equivalent the calculation supports).

Changing type — smoke to heat, ionization to photoelectric as a different detection method, a spot smoke to a beam, a horn to a speaker, a 15 cd strobe to 110 cd “because we had one,” a conventional head on an addressable base — can change spacing, coverage, occupant notification, and the approved drawings. That typically needs AHJ acceptance and, where the occupancy used a design professional, a document change. It is not a truck-stock convenience.

Single-station battery smoke alarms remain in the 195.2(c) exemption; they are not a legal substitute for a system detector you just removed.

Worked examples for the nine-hour block

Example 1. “MAINT” on five photoelectric addresses in a hotel corridor after renovation dust. Clean or replace those listed heads, test them, log it. Do not replace the FACU.

Example 2. NAC 1 trouble, 0.2 Ω across the pair, end-of-line still at the last horn. Find the staple. Replacing horns will not open a bolted short.

Example 3. Dual-path communicator: IP path failed after the building DHCP server changed subnets; cell path still tests. Repair the IP addressing or listed static setup; do not disable IP supervision and call the system dual-path.

Example 4. New main board, default installer code, empty bypass table, security hours set to never arm. Reloading codes, bypass, and hours is servicing under 195.1.

Example 5. Technician swaps a corridor photoelectric for a 135 °F heat “so it will not dirty.” Coverage and the approved detection method just changed. That is a type change, not like-for-like service, and it typically needs the AHJ.

Exam traps

• Dirty smoke, NAC short, battery, and communicator are different logs. Read them.
• Like-for-like is not “any listed smoke.”
• Type change is not a service shortcut.
• DHCP and cell outages are path failures, not detector dirt.
• Programming codes, bypass, and hours after a repair is servicing, not unlicensed information-technology work.