How to Test Battery Alarm Relays in BESS Safely

A battery room can appear healthy on SCADA while a failed relay, loose terminal or incorrectly mapped alarm output quietly removes a critical layer of protection. To test battery alarm relays properly, teams must prove the complete alarm path - from early-stage gas or temperature detection through to the BMS, fire panel, PLC, SCADA platform and operator response.

For lithium-ion battery energy storage systems, relay testing is not a routine checkbox exercise. It confirms that an early warning of hydrogen, VOCs, electrolyte vapours, abnormal humidity or temperature change will reach the people and systems that need to act. The objective is clear: detect danger before thermal runaway escalates.

What battery alarm relays do in a BESS

An alarm relay is a physical switching output that changes state when a detector or monitoring device identifies an alarm, fault or predefined operating condition. It gives a BESS safety system a dependable hardwired interface to external equipment, even where network communications are unavailable, delayed or misconfigured.

Depending on the site design, relay outputs may initiate an audible or visual alarm, notify a PLC, trigger an HVAC response, isolate charging, stop battery operation, activate remote monitoring or provide an input to a fire indicator panel. Modbus RTU and SCADA integration can supply greater diagnostic detail, but relay outputs often provide the direct, immediate alarm signal required by a site cause-and-effect matrix.

The key distinction is between an alarm condition and the relay path that communicates it. A gas detector may correctly identify off-gassing, yet the safety outcome is compromised if its relay output is not powered, the normally closed contact has been wired incorrectly, or the receiving PLC input has been assigned to the wrong tag.

Why relay testing matters before an incident

Lithium-ion battery failure develops in stages. Before smoke, flame and rapid thermal runaway, a failing cell may release gases and airborne electrolyte compounds. Early-warning off-gas detection is designed to identify these precursor conditions while there is still time to investigate, isolate affected equipment and protect people and infrastructure.

That warning has limited value if it does not create an operational response. A tested relay path supports both risk mitigation and continuity planning. It helps confirm that an abnormal condition will not remain an unnoticed screen notification during an unmanned period, maintenance shift or communications outage.

Relay testing also exposes common commissioning and maintenance issues, including:

• a control circuit that has lost its 24 VDC supply or fuse protection

• reversed normally open and normally closed contact logic

• alarm delays that do not match the approved cause-and-effect sequence

• terminals loosened by vibration, heat cycling or previous maintenance work

• SCADA indications that show an alarm while the hardwired output never changes state

• an output that activates locally but does not reach the intended shutdown, ventilation or notification system.

These are not theoretical faults. In critical energy infrastructure, a small interface error can turn a useful early warning into a missed opportunity to prevent asset damage and downtime.

Prepare before you test battery alarm relays

Testing should be planned under the site’s approved safety procedures, not performed as an ad hoc exercise at a live BESS enclosure. Start with the latest single-line diagrams, wiring drawings, I/O lists, detector manuals, fire system interface documents and cause-and-effect matrix. If documents conflict with installed equipment, stop and resolve the discrepancy before testing.

Determine which outputs are being tested and what each one is intended to do. Many detection devices offer separate relays for warning, high alarm and sensor fault. A warning signal may require investigation and increased monitoring, while a high alarm could command battery shutdown or evacuation procedures. Treating every output as identical can create unnecessary disruption or, worse, conceal a missing escalation stage.

A test plan should name the responsible persons for the battery system, controls, fire services and site operations. Where an output connects to a monitored fire panel, security centre or remote operations room, notify stakeholders before beginning. An unannounced relay test can initiate an avoidable emergency response.

Also establish how equipment will be returned to service. Temporary inhibitions, bypasses and forced PLC points should be controlled, recorded and independently checked for removal once the work is complete.

A practical relay test sequence

1. Verify the intended logic

Confirm whether the relay is configured as normally open or normally closed, whether it is energised in its healthy state, and whether the receiving system expects that logic. Fail-safe design commonly uses a normally closed circuit or an energised healthy relay so that loss of power, a broken cable or device fault creates an alarm condition. However, the correct arrangement depends on the wider control architecture.

Read the device configuration and compare it with the cause-and-effect matrix. Do not rely solely on terminal labels. A relay marked Alarm 1 may have been programmed for a low-level warning, a high alarm or a fault condition during commissioning.

2. Inspect the physical circuit

With appropriate isolation and electrical safety controls in place, inspect relay terminals, conductor identification, cable condition and enclosure sealing. Look for loose ferrules, corrosion, damaged insulation, unlabelled modifications and signs of moisture ingress.

Check the output supply, interposing relays and input card power as well. A detector can operate normally while a separate control power fault prevents the downstream alarm circuit from functioning.

3. Initiate a controlled detector test

Use the manufacturer-approved method to create the required test condition. For an industrial off-gas detection system, this may involve a calibrated test process, device test function or simulated alarm input. Do not expose sensors to unsuitable substances or improvised aerosols. They can contaminate the sensing element, produce misleading results or shorten service life.

Observe the detector locally. Confirm its display, LED status or internal indication changes at the expected threshold and after the configured delay. This step validates the sensing device, but it is only the beginning of the test.

4. Prove the relay changes state

Measure or observe the relay contact state during the active alarm. A multimeter, monitored PLC input or test lamp may be appropriate depending on the circuit design and site procedure. Verify both the intended contact transition and the expected de-energised or fail-safe behaviour.

If an interposing relay is installed, test through it rather than assuming the detector output alone proves the circuit. Each additional component is another possible point of failure.

5. Trace the alarm to the final action

Follow the signal to its end point. Does the PLC register the correct input? Does SCADA show the right alarm description, priority and timestamp? Does the local beacon sound? If the approved logic calls for ventilation, battery isolation or notification to a control room, confirm that action occurs in the correct sequence.

This is where functional testing becomes operational assurance. A relay that changes state is not enough if the displayed alarm says “general fault”, arrives after an excessive delay or fails to guide operators towards the required response.

6. Test fault and loss-of-power behaviour

A high-quality test includes abnormal conditions, not just a successful alarm. Where permitted by the design and procedure, simulate a sensor fault, disconnected signal wire or loss of output power. Confirm that the system identifies the fault clearly and that supervisory alarms reach the nominated operator.

The appropriate method depends on site configuration. Avoid disconnecting circuits that could create uncontrolled shutdowns or impair a live fire protection system without an approved impairment process.

7. Restore, verify and document

Clear the test condition and confirm every device, relay, PLC point and SCADA alarm returns to normal. Remove temporary overrides, reset any fire-panel isolations and confirm the BESS is in its intended operating state.

Record the test date, personnel, device identification, relay number, test method, measured result, response time, downstream actions and defects found. Documentation provides a maintenance baseline and supports future investigations, audits and asset handovers.

Common mistakes that weaken early warning

The most frequent mistake is testing only the screen indication. Networked status is useful, but it does not prove the hardwired alarm path. A second mistake is testing the relay at commissioning and then leaving it untested for years, despite changes to SCADA programming, control panels, battery augmentation or operating procedures.

Another issue is using alarm testing to prove sensing performance without considering sensor placement. An off-gas detector must be located and configured to identify emerging hazards in the relevant enclosure, room or airflow path. Relay functionality cannot compensate for a detector positioned away from the gases it needs to detect.

Finally, avoid setting shutdown logic so aggressively that every low-level advisory alarm trips a major asset without allowing investigation. There is a trade-off between continuity and protection. A staged design with warning, high alarm and fault outputs can give operators meaningful time to respond while preserving decisive action for escalating risk.

Build relay testing into the maintenance plan

Testing frequency should reflect the manufacturer’s instructions, site risk assessment, insurer requirements, operating environment and maintenance regime. High-value, unattended or mission-critical installations may justify more frequent functional checks than a small, readily supervised battery installation.

For BESS, EV charging hubs, UPS rooms and data centres, relay verification should sit alongside sensor inspections, calibration requirements where applicable, control-system proof testing and emergency-response exercises. NexaGuard systems are designed to provide early indication of lithium battery off-gassing, but the full safety benefit depends on a tested response chain around the detector.

A battery alarm relay is a small component with an outsized role. When its logic, wiring and downstream actions are regularly proven, an early warning becomes a practical chance to protect people, preserve critical assets and act before fire starts.