At an off-grid site, an electric line heater is often the single largest electrical load, and a resistive heater does not care that it is running the battery flat. Load shedding is the power-management discipline that keeps the heater from doing exactly that. It lets a controller cut back or shut off the heater when the available power - battery charge or generator capacity - can no longer support it. This guide explains why a resistive heater threatens a solar power budget, how a controller sheds or limits its duty, and how to balance freeze protection against keeping the site alive.
Load Shedding in one line: Electric line heater load shedding is a power-management scheme where a controller reduces or cuts the heater's power when battery voltage or generator capacity falls, so the heater does not drain a limited energy supply below the point where the rest of the site can operate. It typically limits the heater's duty cycle or disconnects it entirely below a voltage threshold, protecting autonomy at solar-powered and other off-grid sites.
A solar-powered remote site runs on a fixed energy budget: panels harvest a limited amount during daylight, a battery stores it, and everything on site draws from that store. Most of the loads - an RTU, a radio, a few sensors - are small and steady. An electric line heater is not. It is a resistive load that can draw many times the current of everything else combined, and it draws that power whenever the temperature calls for heat, including at night and through cloudy stretches when the panels are producing little or nothing. The heater's demand and the panels' supply are, if anything, negatively correlated, because it is coldest when the sun is weakest.
Left unmanaged, that mismatch can empty the battery. If a cold, dark spell keeps the heater running hard while the panels barely recharge, the battery draws down until its voltage sags. The danger is not just to the heater but to the whole site: a battery pulled too low can shut down the RTU and radio, and deep discharges permanently damage the battery itself. In effect an unmanaged heater can take the entire site offline and destroy its power system in the process, which is a far worse outcome than a briefly cold line.
Load shedding exists because the heater has to be treated as the discretionary load it is. Keeping the monitoring alive and the battery healthy matters more, moment to moment, than holding the heater exactly on setpoint. Recognizing that hierarchy - critical electronics first, energy storage integrity second, heating last - is what lets a site survive the conditions that would otherwise be its worst case. The heater is the load you sacrifice to protect everything else.
The controller manages the heater against the state of the power supply, and battery voltage is the usual proxy for that state. As long as voltage stays healthy, the heater runs under its normal temperature control. As voltage falls toward a defined threshold, the controller begins to cut back: it can cap the heater's duty cycle so the elements are allowed to be on only a fraction of the time regardless of what the temperature loop wants, reducing average draw and slowing the drain. Cross a lower threshold, and the controller disconnects the heater entirely - a low-voltage disconnect - to preserve what charge remains for the critical loads.
Staged cutback is gentler and more useful than a single hard cutoff. Rather than running full-tilt until the battery collapses and then dropping the heater all at once, the controller trims the heater progressively as headroom shrinks, so the line stays as warm as the power budget allows for as long as possible. Hysteresis is built into the thresholds - the heater is not re-enabled the instant voltage ticks back up - so the system does not oscillate on and off around the setpoints while the battery recovers. On a generator-backed site the same idea applies to generator capacity or fuel state instead of battery voltage.
This logic sits naturally in the same RTU that already runs the heater's temperature loop, because that controller can see both the process temperature and the power supply and arbitrate between them. It gives the heater a normal setpoint and a temperature deadband, but overlays a power-priority rule that can override the temperature demand when the supply is at risk. The result is a heater that behaves like a well-mannered tenant of the site's energy, taking power when there is plenty and standing down when there is not.
Shedding the heater is a trade-off, not a free win: cutting the heater to save the battery risks letting the very line the heater protects go cold. The right settings depend on which failure is worse at a given site. Where a frozen line means a costly, dangerous freeze-up, the thresholds are set to protect heating longer and the power system is sized with more margin. Where the site can tolerate a cold line briefly but cannot tolerate losing its monitoring, the thresholds favor cutting the heater early. There is no universal answer, only a deliberate choice about what to sacrifice first.
Monitoring is what makes that choice manageable rather than a gamble. Trending battery voltage, heater duty cycle, and process temperature together shows how the site behaves through cold, dark spells and reveals whether the power system is genuinely undersized or merely being stressed by an unusually bad week. If the heater is shedding often, the data supports a concrete fix: more panel, more battery, or a supplemental heat source. Without that visibility, an operator only learns there was a problem after the battery is dead or the line is frozen.
In a cloud SCADA this power-management behavior becomes an early-warning system for the whole site. The controller can report when it enters load shedding and raise an alarm when it disconnects the heater, so an operator learns the site is under energy stress while there is still time to act - dispatch a technician, bring fuel to a backup generator, or accept the risk deliberately. For a fleet of off-grid sites, seeing which ones are shedding heat during a cold snap turns a scattered set of unmanned locations into a prioritized list, protecting both freeze protection and the autonomy the whole installation depends on.
A resistive line heater can draw many times the current of everything else on a remote site, and it draws most heavily at night and in cold, cloudy weather when solar panels produce little. That demand runs opposite to the supply, so an unmanaged heater can empty the battery, shut down the RTU and radio, and even damage the battery through deep discharge. It is usually the single largest and least forgiving load on the site.
The controller watches the power supply, usually via battery voltage, and cuts the heater back as that voltage falls. It first caps the heater's duty cycle so the elements can be on only a fraction of the time, reducing average draw, and then fully disconnects the heater below a lower voltage threshold to protect the remaining charge. Hysteresis on the thresholds keeps the heater from oscillating on and off while the battery recovers.
It can, which is why load shedding is a deliberate trade-off rather than a free win. Cutting the heater to save the battery may let the line go cold, so the thresholds are tuned to whichever failure is worse at that site - a frozen line or a dead power system. Monitoring battery voltage, heater duty, and process temperature together, and alarming when the heater sheds, lets an operator intervene before either failure occurs.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.