A deep-cycle battery at a remote site tolerates a lot, but not being run flat. Drain it too far and its capacity is permanently damaged, sometimes ruined outright, and a site that does this repeatedly gets through batteries fast. The low-voltage disconnect is the safeguard that prevents this: a switch that opens the load when the battery voltage drops to a set floor, sacrificing the site's operation to save the battery from destruction. This page defines the LVD as the last protective line before over-discharge, explains the disconnect and reconnect setpoints and the hysteresis between them, and shows why a badly chosen LVD either kills the battery early or bounces the site on and off.
Low-Voltage Disconnect in one line: A low-voltage disconnect, or LVD, is a switch that opens the load off a battery when its voltage falls to a set threshold, preventing the deep over-discharge that permanently damages a deep-cycle bank. It reconnects the load once the voltage has recovered to a higher reconnect setpoint, and the gap between the disconnect and reconnect voltages is the hysteresis that stops it from rapidly cycling. It is the last line of protection for the battery, acting after any load shedding has failed to arrest the decline.
A deep-cycle battery is designed to be discharged and recharged many times, but there is a floor below which discharge stops being a cycle and starts being damage. Taken too low, the battery's chemistry is harmed in ways that permanently reduce its capacity, and a bank subjected to repeated deep over-discharge fails long before its expected life. The low-voltage disconnect exists to enforce that floor. It watches the battery voltage, which falls as the battery empties, and when the voltage reaches the disconnect setpoint it opens the load, cutting off consumption so the battery cannot be drained any further.
The LVD's job is deliberately a sacrifice. When it acts, the site's loads lose power, which usually means the site stops doing what it is there to do, and that is the point: it is better to lose the site's function temporarily than to lose the battery permanently. Everything else in the power management scheme, such as firmware load shedding that trims consumption as the voltage sags, is an attempt to avoid ever reaching the LVD. The disconnect is the backstop for when those measures have not been enough and the battery is genuinely about to be over-discharged, so it acts last and it acts decisively.
Because it protects the battery rather than the load, the LVD is set from the battery's tolerance, not from what the load would prefer. The disconnect voltage is chosen to open the load while the battery still has a safe margin above the point of real damage, accounting for the fact that voltage sags under load and recovers when the load is removed, so the reading at the moment of disconnect is not the battery's true resting state. Setting the disconnect too low to keep the site running longer defeats the purpose, because by the time a too-low threshold trips, the damage the LVD was meant to prevent may already be underway.
An LVD has two setpoints, not one. The disconnect setpoint is the voltage at which it opens the load, and the reconnect setpoint is the higher voltage at which it closes the load again once the battery has recovered. The gap between them is the hysteresis, and it is essential. Consider what happens without it: the moment the LVD disconnects the load, the battery voltage rises slightly because it is no longer being drained, and if reconnection happened at that same voltage it would immediately close the load, sag again, disconnect again, and cycle rapidly. The hysteresis gap prevents this by requiring the battery to recover a genuine amount of charge before the load is allowed back.
The size of the hysteresis is a real design choice. Too small a gap and the site risks chattering during marginal conditions, connecting and disconnecting repeatedly as the voltage hovers near the threshold, which stresses the switching and gives the site no stable state. Too large a gap and the site stays disconnected for a long time after a disconnect event, because the battery has to climb well above the disconnect voltage before the load returns, which can leave a site off far longer than necessary when the sun comes back. The reconnect voltage is set high enough to ensure the battery has meaningfully recharged, so the load comes back to a battery that can actually sustain it rather than one that will immediately sag back to the disconnect point.
The reconnect setpoint interacts with the charging source in an important way. After a disconnect, the battery only recovers if the panel or other charging input can lift it above the reconnect voltage. On a solar site, that means the reconnect typically happens the next day when the sun charges the battery back up, so a site that disconnected overnight comes back to life once the panel has restored enough charge. This is the intended behavior: the LVD protects the battery through the worst of a shortfall, then the site automatically returns once the energy balance recovers, without anyone visiting to reset it.
A badly set LVD fails in one of two directions, and both are damaging in their own way. Set the disconnect voltage too low, chasing a bit more runtime, and the LVD lets the battery drain past the point of harm before it acts, so it protects nothing and the bank is degraded exactly as if there were no LVD at all. This is the more insidious failure because the site appears to run longer, which looks like a benefit, while the batteries quietly wear out and have to be replaced far sooner than they should. The apparent extra uptime is paid for in battery life.
The opposite mistake is a reconnect setpoint set too close to the disconnect, giving too little hysteresis, which makes the site bounce on and off. Each time the load reconnects, the still-weak battery sags back below the disconnect voltage and cuts out again, and the site cycles through connect and disconnect events without ever staying up usefully. This bouncing is hard on the equipment being switched, produces a confusing stream of the site appearing and vanishing, and never gives the operator a clear picture of whether the site is up or down. A well-set pair of thresholds gives a clean single disconnect when the battery is genuinely low and a clean single reconnect once it has truly recovered.
A cloud SCADA layer is where LVD behavior stops being invisible and becomes diagnostic. When a platform such as Merobix records the battery voltage trend and timestamps every disconnect and reconnect, a site bouncing on and off reveals itself as a rapid string of connect events that points straight at too little hysteresis or a battery too weak to hold the load. A site that goes dark and returns cleanly the next day shows an LVD working as intended through an overnight shortfall. Over time, sites hitting their LVD often flag where the solar and battery are undersized for the load, and the pattern of disconnect events becomes an early warning that a bank is losing capacity, since a battery reaching the disconnect voltage sooner each night is a battery on its way out.
It protects the battery against deep over-discharge. A deep-cycle bank drained too far suffers permanent capacity loss, so the LVD opens the load when the battery voltage reaches a set floor, cutting off consumption before the battery is damaged. It does this by sacrificing the site's operation, on the principle that temporarily losing the site's function is far better than permanently ruining the battery, which is why it acts as the last line after other measures have failed to arrest the decline.
The disconnect setpoint is the lower voltage at which the LVD opens the load to stop discharge, and the reconnect setpoint is the higher voltage at which it closes the load again after the battery has recovered. The gap between them is the hysteresis. It exists because the moment the load is removed the voltage rises slightly, so reconnecting at the same voltage would cause rapid cycling; the higher reconnect voltage forces the battery to genuinely recharge before the load returns.
Set the disconnect voltage too low and the LVD lets the battery drain past the point of damage before acting, so it protects nothing and the bank wears out early even though the site seems to run longer. Set the reconnect too close to the disconnect, with too little hysteresis, and the site bounces on and off as the weak battery sags back below the threshold each time it reconnects. A good pair of thresholds gives one clean disconnect when the battery is genuinely low and one clean reconnect once it has truly recovered.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.