A solar-powered remote site sized for average sun will still run short during a long cloudy stretch or the darkest weeks of winter. A hybrid site solves this by adding a small backup generator that starts automatically when the battery runs low, charges the bank, and shuts back off. Generator auto-start on low battery is the control logic that decides when to fire that genset based on state of charge, and it has to balance keeping the site alive against burning as little fuel and as few run hours as possible.
Generator Auto-Start (Low Battery) in one line: Generator auto-start on low battery is a hybrid-power control scheme where the charge controller or RTU starts a backup generator when battery state of charge falls below a low threshold and stops it once the battery is recharged to a higher threshold. The gap between those two setpoints, called hysteresis, keeps the generator from short-cycling and minimizes run hours and fuel use at an unmanned site.
The heart of auto-start is a pair of setpoints on battery state of charge, not a single one. A low setpoint defines when the generator must start, chosen high enough that the battery never falls to a level that risks the RTU losing power or the bank suffering deep-discharge damage. A separate, higher setpoint defines when the generator may stop, chosen so the bank is recharged to a comfortable level before the genset shuts down. The deliberate gap between start and stop is the hysteresis that makes the scheme stable.
Without that gap, the generator would chase the threshold. If a single setpoint both started and stopped the genset, the machine would fire, nudge the battery just past the line, shut off, watch the battery sag back under load, and start again moments later. This short-cycling is hard on the starter, the engine, and the fuel system, and it defeats the purpose of the backup. Widening the gap between start and stop setpoints forces the generator to run a useful charging session each time it fires rather than pulsing on and off.
Because voltage sags under load and rebounds at rest, mature designs base the trigger on estimated state of charge rather than a raw voltage reading where possible, and they add a short time delay so a momentary dip from a transmit burst or a valve stroke does not trip a start. The combination of a state-of-charge threshold, a healthy hysteresis band, and a debounce delay is what separates a generator that runs a few clean sessions during a bad week from one that hammers itself on and off all night.
At a manned facility a generator is a convenience; at an unmanned remote site it is a scarce resource with a fuel tank that someone has to drive out and refill. Every run hour consumes fuel, adds engine wear, and moves the next service and refueling visit closer. The auto-start logic is therefore tuned not just to keep the lights on but to run the generator as little as the site allows, letting solar do the work whenever the sun cooperates and calling on the genset only when the battery genuinely needs it.
Several design choices push run hours down. Setting the start threshold as low as the battery safely tolerates lets solar recover the bank on marginal days without ever waking the generator. Setting the stop threshold below a full charge, rather than insisting the generator top the battery all the way up, ends each session sooner and leaves headroom for the solar array to finish the charge for free. Some sites also add a minimum run time so that once the generator does start, it runs long enough to reach operating temperature and deliver a worthwhile charge rather than a token one.
Timing and inhibits round out the strategy. A site may inhibit auto-start during a window when a scheduled solar recovery is likely, or require the low condition to persist for a set period before committing to a start, so a brief afternoon cloud does not trigger an unnecessary run. The goal throughout is the same: treat the generator as the backup of last resort, and let its run-hour meter climb as slowly as the site power budget and weather permit.
Physically, the auto-start command is usually a simple contact closure. Many small gensets accept a two-wire start scheme in which closing a pair of terminals commands the engine to crank and run, and opening them commands a stop. The charge controller or the RTU drives that contact from its state-of-charge logic, so the same device that meters the battery also owns the decision to start and stop the generator. This keeps the control loop local and lets the site manage itself even when the network link is down.
Local autonomy is essential, but blind local autonomy is dangerous at a site nobody visits. A generator that auto-starts more often than expected is telling you something: the array is underperforming, a load has grown, the battery is aging, or a stretch of bad weather has set in. If that pattern is only visible on a run-hour meter read during an occasional visit, the trend is discovered late, sometimes after the fuel tank is nearly empty.
Reporting the auto-start events, the run hours, the state of charge at each start, and the fuel level to a cloud SCADA host turns the backup into a monitored subsystem. An operator can see the generator starting more frequently as winter deepens and schedule a refuel before the tank runs dry, or notice the genset firing on sunny days and investigate a failing panel or charge controller. The host also captures each start and stop as a timestamped record, so the balance between solar and generator energy at the site becomes a trend to manage rather than a mystery to reconstruct after a failure.
One setpoint would make the generator short-cycle: it would start, push the battery just past the line, stop, then restart moments later as the battery sagged under load. Using a low start setpoint and a higher stop setpoint creates a hysteresis band that forces the generator to run a useful charging session each time it fires, protecting the engine and reducing wear.
Two-wire start is a simple control interface in which closing a pair of terminals tells the generator to crank and run, and opening them tells it to stop. The charge controller or RTU drives that contact from its low-battery logic, so the same device that tracks state of charge also commands the generator, keeping the control loop local and functional even without a network connection.
By treating the generator as a last resort. The start threshold is set as low as the battery safely allows so solar recovers the bank on marginal days, and the stop threshold is set below a full charge so each run ends early and lets the array finish charging for free. Debounce delays and inhibit windows prevent brief clouds or momentary load spikes from triggering unnecessary runs.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.