How to Verify Low-Voltage Disconnect Operation
The low-voltage disconnect is the device that sacrifices your site's uptime to save its battery, and both halves of that bargain deserve a test. An LVD that never operates lets a deep discharge destroy the bank; one that operates too early, or that half the loads bypass, gives you outages without the protection. This page covers verifying the disconnect point, the reconnect point, and, most importantly, what is actually wired through it.
Verify LVD Operation in one line: To verify low-voltage disconnect operation, first map which loads are actually powered through the LVD terminals, then drive the input voltage down slowly with an adjustable supply or a controlled discharge and record where the disconnect operates, then raise it and record the reconnect point. Compare both against the configured thresholds and confirm the low-voltage alarm fires before the disconnect does.
What You Need
You need the documentation for the device performing the disconnect, whether a standalone low-voltage disconnect or the load terminals of a charge controller, along with its configured thresholds; a multimeter; ideally an adjustable DC bench supply that can stand in for the battery; and the site's as-built drawing showing which circuits feed from the LVD output and which connect straight to the battery bus.
Map What the LVD Actually Controls
Before testing thresholds, test the assumption that matters more: that the loads you think are protected actually route through the disconnect. Sites drift; a heater added in a hurry, a radio moved to a spare fuse, a camera wired straight to the battery because the LVD terminal block was full. Every load wired around the LVD keeps discharging after the disconnect operates, which defeats the protection exactly when it is needed.
Walk the wiring or, faster, operate the disconnect deliberately during a maintenance window and note what stays alive. Anything still running is bypassing the LVD, and each bypass is a decision to revisit: some loads legitimately belong on the unswitched bus, but that should be a documented choice, not an accident.
Drive the Voltage Down Under Control
The clean way to find the disconnect point is to substitute an adjustable bench supply for the battery and ramp the voltage down slowly, watching the LVD output with a meter. Ramp slowly because many LVDs apply a time delay to ride through transient sags, so a fast sweep can blow past the true threshold. Record the voltage at which the output drops.
Avoid proving the threshold by deep-discharging the real bank; you would be spending battery life to test the device that exists to protect battery life. If a bench supply is impractical in the field, a controlled discharge observed closely near the expected threshold can serve, but stop and recharge promptly once the disconnect operates, respecting the cost of every deep cycle described in depth of discharge.
Confirm the Reconnect Point and Hysteresis
Now raise the supply voltage slowly and record where the load comes back. The gap between disconnect and reconnect is deliberate: reconnect hysteresis exists because a battery's voltage rebounds the moment load is removed, and an LVD that reconnected at the disconnect voltage would chatter, cycling the load on and off. Verify the reconnect happens where the configuration says it should, per the documented recovery threshold, and that the transition is a clean single event rather than a flutter.
If the site's loads have significant inrush, watch the reconnect moment specifically: an inrush that drags the voltage back below the disconnect point produces an oscillation the bench test will reveal safely.
Verifying the Result
Compare the measured disconnect and reconnect voltages against the configuration and the chemistry's needs per the battery datasheet, and correct any drift or misconfiguration. Then verify the ordering that turns protection into operations: the SCADA low-voltage alarm must fire meaningfully before the LVD threshold so a person gets a chance to act, and where a generator auto-start on low battery exists, its start setpoint must also sit above the LVD. Document the measured values with the date; the next test then becomes a comparison rather than a discovery.
Common Mistakes
The expensive mistakes: an alarm setpoint at or below the LVD threshold, so the site's first notification of trouble is the site disappearing; loads bypassing the disconnect; testing with a fast voltage sweep and recording a threshold skewed by the delay timer; and forgetting that the radio or RTU itself may brown out above the LVD threshold, in which case the effective disconnect for telemetry purposes is the electronics' own dropout, not the LVD. Each of these is caught by the mapping step, the slow ramp, and the alarm-order check above.
Frequently Asked Questions
Why did my RTU go offline with no low-battery warning?
Usually because the warning threshold sits at or below the point where the RTU or its radio actually stops working, or below the LVD threshold itself. The alarm must be configured above both, with enough margin for someone to respond. The verification order is: electronics dropout voltage, then LVD threshold, then alarm threshold above that, and the alarm path itself tested end to end.
Can I test an LVD using the real battery?
You can, by allowing a controlled discharge and watching closely near the threshold, but it costs a deep cycle of the bank and takes hours you cannot precisely schedule. An adjustable bench supply substituted for the battery gives the same answer in minutes with no wear on the bank, which is why it is the preferred method wherever access allows it.
Why does the load come back at a higher voltage than it dropped out?
That gap is intentional hysteresis. Battery voltage rebounds when load is removed, so without a separated reconnect threshold the LVD would reconnect immediately, drag the voltage down, disconnect again, and chatter. The reconnect point is chosen so the load only returns once the battery has genuinely recovered, whether by charging or by sustained rest.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.