Fire alarm device addressing explained
How addressable fire alarm devices are assigned unique addresses, the different addressing methods in use, what address conflicts cause, and how addressing is managed during installation and modification.
Device addressing is the mechanism that allows an addressable fire alarm panel to identify exactly which device has activated. Without addresses, a loop of 100 detectors would behave like a conventional zone — the panel would know the loop had triggered but not which device. With addresses correctly assigned, the panel displays the precise location of every alarm, fault, or pre-alarm event anywhere in the building.
The Principle of Addressable Detection
In an addressable system, every device on the loop — every detector, every call point, every input or output module — has a unique numerical address. The panel communicates with each device in turn, polling them sequentially many times per second. Each device responds with its address and its current status: normal, pre-alarm, alarm, or fault.
When a detector responds with an alarm status, the panel immediately identifies the address, cross-references it against the device database, and displays the device description — room name, floor, and location. The cause and effect programme then activates the programmed outputs for that address.
Addressing methods
How Addresses Are Set
Different manufacturers use different addressing methods. The main approaches are:
| Addressing method | How it works | Typical use |
|---|---|---|
| DIP switch addressing | A bank of small switches on the device or its base — each switch represents a binary digit, and the combination of on/off positions sets a unique number. Address 7, for example, is set with switches 1, 2, and 3 on and all others off (binary 00000111) | Older addressable systems and some current mid-range systems. Reliable but time-consuming for large installations — each device must be set individually |
| Rotary switch addressing | Two rotary switches — one for tens, one for units — allowing addresses 00 to 99 to be set directly. More convenient than DIP switches for field use | Common on conventional devices and some addressable systems with limited address range |
| Electronic addressing (auto-addressing) | Devices are factory-programmed with a unique serial number. The panel assigns addresses either automatically by walking the loop or by an engineer using a handheld programmer to assign addresses at each device location | Modern addressable systems from most major manufacturers. Faster on large installations and eliminates DIP switch setting errors |
| Programmed addressing via panel | Devices are installed without pre-set addresses; the engineer walks the loop with a laptop or panel programmer, assigning addresses and descriptions at each device | High-end addressable systems, particularly those using proprietary protocols |
Address conflicts
What Happens When Addresses Conflict
An address conflict occurs when two devices on the same loop are assigned the same address. The consequences depend on the system protocol, but typically include:
- The panel may display a conflict fault or communication error for the affected address
- One or both devices may be unreachable — the panel cannot reliably poll a conflicting address
- In the worst case, both devices may appear normal on the panel while neither is reliably monitored
- Alarms from either device may be attributed to the wrong location in the panel database
Address conflicts are typically introduced when a new device is added to a loop without checking the existing address allocation — the new device is set to an address already in use. A complete address register should be maintained for every loop, updated whenever devices are added, removed, or replaced.
Address planning
Address Planning and the Device Schedule
Good addressing practice begins with a planned address allocation before installation starts. The device schedule — the document listing every device on every loop with its address, type, location description, and programmed group or zone membership — should be produced at the design stage and maintained throughout the life of the installation.
BS 5839-1 requires that the as-installed documentation includes a complete device schedule. This document is essential for maintenance engineers working on the system — without it, identifying an unknown device address, locating a specific device, or adding a new device without creating a conflict is significantly more difficult.
Common questions
Frequently Asked Questions
The maximum number of devices per loop depends on the panel manufacturer and protocol. Common limits are 99, 126, or 200 devices per loop, depending on the system. Most modern panels support multiple loops, allowing large buildings to be served by a single panel with several loops each carrying up to the maximum device count. The system designer specifies the loop configuration based on the number of devices required and the physical layout of the building.
Generally no — addressable protocols are proprietary, and devices from different manufacturers communicate differently. A Hochiki device will not work on an Apollo loop, and vice versa, even if the address range and wiring are compatible. There are some exceptions where manufacturers have licensed their protocols or where interface modules allow cross-system integration, but as a general rule the devices on each loop must be from the same manufacturer as the panel or an approved compatible range. Mixing incompatible devices is a common source of communication errors and should be avoided.