Swapped a communicator on a strip mall panel last spring, an older Napco box, figured it was a twenty minute job. Pull the phone line card, drop in a cellular unit, done. Except the cellular module needed a firmware rev the panel didn't have, and the "universal" communicator the distributor sold the owner wasn't actually universal for that board generation. Spent two hours on hold with tech support instead of eating lunch. Nobody warned the owner because nobody thought to ask the panel a question before answering it with a part number.
That's the trap now that phone companies have mostly walked away from copper. POTS lines are dying or already dead in a lot of areas, and every retrofit and half the new installs are turning into a communicator conversation whether anyone planned for it or not.
sole path cellular vs dual path IP, actually
The code allows single path cellular in a lot of jurisdictions now, and it's genuinely fine for plenty of buildings. But "allowed" and "what your AHJ will sign off without a fight" are two different lists.
Dual path (cellular plus IP over the building's internet, or two cellular carriers) buys you redundancy the AHJ likes seeing, especially on anything with a fire watch history or an inspector who's been burned before by a dead cell signal during a storm. Sole path cellular is cheaper and simpler, and I use it plenty on small occupancies where the AHJ doesn't ask for more. But I've had two different counties push back on sole path for anything over a certain occupant load, informally, nothing written down anywhere I could point to. Ask before you quote it. Don't assume last year's approval on a similar job carries over, some AHJs have quietly tightened up as more buildings went cellular only and a few had outages nobody liked.
supervision intervals, roughly
NFPA 72 sets max intervals for how often the communicator has to check in and report trouble if it can't. These vary a bit by path type and by which edition your AHJ has adopted, so don't quote a client an exact number without checking their edition first. Here's the shape of it from panels I've actually programmed:
| Path type | Typical max supervisory check in | What happens on missed check in |
|---|---|---|
| POTS (legacy, still out there) | 24 hours | Trouble signal after missed window |
| Cellular, single path | 5 minutes (varies by listing) | Trouble at panel + central station alert |
| Dual path (cellular + IP) | 5 minutes each path | Trouble only if BOTH paths miss |
| IP only over building network | 5 minutes, often faster | Trouble on loss of network heartbeat |
I hedge on the exact minute counts because they're set by the specific communicator's UL listing, not just the code section, and I've seen 90 second and 200 second intervals depending on the manufacturer. Pull the actual listing sheet for the unit you're specifying instead of trusting a number you remember from a different job.
what the AHJ actually wants on the submittal
This is the part that trips people up more than the wiring does. A reviewer doesn't care that the cellular signal works, they want to see it documented. What I've had accepted without a second look, most of the time:
- The communicator's UL listing number, not just the manufacturer name and model.
- Signal strength verification, a screenshot or printout from the install, not just "signal was good."
- Which path is primary and which is backup if it's dual path, spelled out, not implied.
- A note on battery backup runtime for the communicator itself, separate from the panel's own standby calc.
One reviewer sent a set back to me with a single line: "path hierarchy not stated." That was it. The dual path unit was installed correctly, wired correctly, just never said on paper which one it falls back to. Fixed the cover sheet, resubmitted, approved same week. Cheap lesson, wasted a week though.
the panel compatibility trap
Here's the one that actually costs money. Not every communicator talks to every panel the way the box art implies. I've hit this twice with older Napco boards where the comm module needed a specific firmware version the panel had never been updated to, once with a Silent Knight retrofit where the "compatible" cellular unit only supported a subset of the panel's point count and silently dropped zones from reporting. Silently. Nobody caught it until an inspector ran a full function test.
Before you order the part, check the panel's actual firmware rev against the communicator's compatibility list, not the shelf label. If the panel's old enough that you're not sure, a phone call to the manufacturer's tech line before the truck rolls beats a return trip after.
documenting it so it survives the next inspection
Annual test time is when a badly documented communicator setup really shows. If the inspector can't tell from your file which path is primary, what the last verified signal strength was, or when the battery in the comm unit was last checked, you're rebuilding that history from memory on-site. I keep a one page comm sheet per job now, separate from the battery calc, just the communicator's essentials. Takes five minutes to fill out the day you commission it and saves a lot more than that a year later.
Full disclosure, I built a tool called FireDeck, and the part that got old fast for me was retyping the same panel info and communicator details into a fresh form every time an inspector asked for it again. Anyway. Check your AHJ's current edition before you quote a supervision interval, that part never gets old.