Using the SD500-ARM with an SD505 Duct Smoke Detector for HVAC Shutdown

Shutting down air handlers when smoke is detected is one of the most important automatic functions in a commercial fire alarm system, and on Silent Knight and Honeywell addressable panels the SD500-ARM is the device that makes it happen. The SD500-ARM is an addressable relay module that gives the control panel a pair of dry contacts it can switch on command and when it is paired with an SD505 duct smoke detector watching the ductwork, you get reliable, code-driven HVAC shutdown. This guide explains how the two devices work together, how to wire them, and why an addressable relay is the right tool for the job.

What Is the SD500-ARM?

The SD500-ARM is an addressable relay module in the Silent Knight SD500 device family, used on IntelliKnight and Farenhyt addressable fire alarm control panels. It provides two Form C (changeover) relay contacts rated at 2.0 amps at 30 VDC or 0.6 amps at 120 VAC. Because the module is addressable, the panel can place it anywhere on the signaling line circuit, give it its own address, supervise it continuously, and switch its contacts using programmed cause-and-effect logic.

Those contacts are pilot-duty rated, which is an important detail: the module does not switch a motor directly. Instead, its contacts control the coil of a motor starter, a contactor, or a relay in the HVAC control circuit or trigger a damper actuator so that a small, low-current signal from the fire panel commands a much larger mechanical load to stop or change state.

What the SD505 Duct Smoke Detector Does

On the detection side, this duct smoke detector senses smoke in the air moving through an HVAC duct. It is a heavy-duty metal housing fitted with an analog photoelectric smoke sensor and a pair of sampling tubes that span the duct; the inlet tube draws a portion of the airstream past the sensor and returns it through the exhaust tube. The unit is listed for duct air velocities from roughly 300 to 4,000 feet per minute and reports to the same addressable panel as the relay module.

When smoke appears in the duct, the duct detector signals the panel. From there, the panel’s programming decides exactly what happens next and that is where the relay module comes in to convert a detection event into mechanical action.

Why Automatic HVAC Shutdown Matters

Smoke kills and causes damage far beyond the room where a fire starts, and a running air handler is an efficient way to spread it. Left on, supply and return fans pull smoke from a small fire and push it through every space the ductwork serves, cutting visibility on escape routes and contaminating areas that never saw flame. Stopping the fans early keeps smoke contained and buys occupants critical time to evacuate.

That is why model codes and NFPA 90A require air-handling systems above defined airflow thresholds to shut down when smoke is detected in the duct. The requirement is not merely to sound an alarm; it is to take mechanical action stop the fan and, where required, close dampers so the HVAC system stops working against life safety. Delivering that action reliably is exactly the job the relay performs.

How the SD500-ARM Triggers HVAC Shutdown

The sequence is simple and dependable. The duct detector senses smoke and reports an alarm to the fire alarm control panel. The panel, following its cause-and-effect program, commands the SD500-ARM to transfer its contacts. Those contacts open the holding circuit of the air handler’s motor starter (or energize a shunt path), the fan stops, and smoke is no longer pushed through the duct system into other zones. If smoke dampers are part of the design, a second relay or a second module drives them closed at the same moment.

Doing this through an addressable relay rather than a local switch means the action is programmable and supervised end to end. The panel knows the module is present and healthy, logs the event, and can coordinate the fan shutdown with notification, elevator recall, and other functions as a single, tested sequence rather than an isolated reaction.

Wiring the SD500-ARM to the Air Handler

A typical installation wires the SD500-ARM’s SLC terminals to the addressable loop alongside the duct detector, then routes one set of Form C contacts to the HVAC starter’s control circuit. You choose normally-open or normally-closed contacts depending on whether the fan should drop out or be held by the relay. Because the contacts are rated for pilot duty only, never wire them in series with the motor’s line power; always switch the control circuit through the equipment’s starter or a listed interposing relay.

Keep the relay’s wiring within its 2.0 A at 30 VDC and 0.6 A at 120 VAC rating, observe power-limited versus non-power-limited separation wherever the contacts carry external power, and label the conductors clearly so the HVAC and fire trades both understand the interlock. Confirm operation at commissioning by alarming the duct detector and verifying that the fan actually stops.

Why Use a Separate Relay Module Instead of the Built-In Relay?

Some duct housings include an onboard relay, so it is fair to ask why you would add an SD500-ARM. The answer is control and flexibility. A built-in relay acts locally and is tied to that one device, while it is an addressable point the panel can program into any cause-and-effect sequence, supervise continuously, and locate anywhere on the loop. That matters when a single alarm must shut down several air handlers, stage shutdowns in order, or combine fan control with dampers and notification.

Using a dedicated relay module also keeps the detection device and the control function cleanly separated, which simplifies troubleshooting: if a fan fails to drop out, you know to look at the addressed relay and its wiring rather than at the detector head itself.

Single Air Handler vs Multiple Units

In the simplest case one air handler with one duct detector a single relay module is enough: the detector alarms, the panel transfers the relay, and the fan stops. The clean separation of sensing and switching still pays off here, because the panel supervises both points and logs the event for your inspection records.

Larger buildings raise the stakes. A rooftop unit serving several zones, or a mechanical room with multiple air handlers, may need each fan dropped independently, dampers closed in sequence, and smoke-control fans started. Because each addressable relay is its own programmable point, a designer can map one duct alarm to several coordinated outputs without daisy-chaining local relay contacts, which keeps the cause-and-effect logic clear and testable.

Common Mistakes to Avoid

The most frequent error is treating the relay contacts as if they can carry motor current. They cannot they are pilot-duty rated and must switch only a control circuit or an interposing relay, never line power to the fan. A close second is skipping the functional test: wiring that looks correct on paper can still fail to drop a fan if the contact choice or the starter’s control logic is wrong.

Other pitfalls include mixing power-limited and non-power-limited wiring without proper separation, failing to label the interlock so the HVAC trade understands it, and assuming duct detection alone satisfies the code. It does not replace the open-area detection that occupied spaces require, so plan area coverage alongside the duct-and-relay strategy from the very start.

Testing and Maintenance

Keep the interlock dependable with scheduled testing under NFPA 72. Introduce smoke or use the listed test method at the duct detector, then confirm the fan actually stops and the panel annunciates and logs the event. Because the relay is supervised, the panel reports a fault if the module loses communication but the mechanical result, a stopped fan, should still be verified physically during periodic inspections, along with cleaning the duct sensing chamber, which collects dust faster than open-area heads.

Building or servicing an HVAC shutdown interlock? Get the SD500-ARM and matching duct detection from QuickShipFire brand-new, ready to ship, with help confirming compatibility with your IntelliKnight or Farenhyt panel.

Compatibility and Where Spot Detectors Fit

Both the SD500-ARM and the duct smoke detector are Silent Knight SD500-series devices that share the same addressable loop on compatible IntelliKnight panels such as the 5700, 5808, and 5820XL. Keep in mind that duct detection is not a substitute for open-area smoke detection: NFPA 72 still requires spot detectors for the rooms and corridors that people actually occupy.

On a Fire-Lite system, for example, that open-area coverage might be handled by a photoelectric device such as the SD365-IV smoke detector, which protects the space itself while the duct detector and relay protect the airstream. A complete design layers area detection, duct detection, and the relay logic that ties the building’s HVAC response together.

If your facility standardizes on Fire-Lite hardware elsewhere, pairing duct detection with area devices like the SD365-IV smoke detector keeps coverage consistent, while Silent Knight sites use the equivalent SD500-series spot detectors. Either way, the relay module remains the device that converts a smoke alarm into mechanical action.

The takeaway for designers and facility managers is to think in layers. Open-area detectors catch a fire in the room where it begins, duct detection catches smoke that has already entered the air-distribution system, and the relay logic turns either signal into the right mechanical response stopping fans, closing dampers, recalling elevators, or releasing doors. None of the three layers replaces the others, and a building that skips one most often the duct interlock or the relay that drives it can pass a casual walkthrough yet still allow smoke to travel exactly where it should never go. Designing all three together from the outset is both cheaper and safer than bolting on a missing piece after an inspector flags it.

Conclusion

Pairing the SD500-ARM with an SD505 duct smoke detector is the standard, dependable way to deliver automatic HVAC shutdown on Silent Knight and Honeywell addressable systems. The detector finds smoke in the airstream, the panel runs the logic, and the addressable relay switches the contacts that stop the fan and close the dampers all supervised and fully programmable. Specified and wired correctly, this pairing satisfies the mechanical code’s fan-shutdown requirement and helps keep smoke from spreading building-wide.

Need to source these parts or find a hard-to-find module fast? Request a quote from QuickShipFire and we will confirm compatibility and ship your relay module and duct detection right away.

Frequently Asked Questions

What does the SD500-ARM do in an HVAC shutdown?

It is an addressable relay whose contacts the panel switches on a smoke alarm, opening the air handler’s control circuit so the fan stops. This prevents smoke from spreading through the ducts.

Can the relay switch the fan motor directly?

No. Its contacts are pilot-duty rated, so they control a motor starter, contactor, or damper actuator. Never wire them in series with the motor’s line power.

Why add a relay module if the duct housing has a built-in relay?

A separate addressable relay is programmable, supervised, and can sit anywhere on the loop, so one alarm can stage several actions. A built-in relay acts only locally for that device.

Which panels are compatible?

Both devices are Silent Knight SD500-series and work with IntelliKnight panels such as the 5700, 5808, and 5820XL. Always confirm against your panel’s listed device list.

Does duct detection replace ceiling smoke detectors?

No. NFPA 72 still requires open-area detectors like a photoelectric SD365-IV smoke detector for occupied spaces. Duct detection only protects the airstream and triggers HVAC shutdown.

What are the relay module’s contact ratings?

Two Form C contacts rated 2.0 A at 30 VDC or 0.6 A at 120 VAC. Keep all wiring within that rating and use an interposing relay for larger loads.

How do I test the shutdown function?

Introduce smoke or use the listed test method at the duct detector, then confirm the fan actually stops. Verify the panel logs the event and restores normal operation on reset.