Power Consumption Control in Solar Street Lights
-- Why Fixtures on One Site Glow Differently
Power Consumption Control in Solar Street Lights: Why Fixtures on One Site Glow Differently
Short answer: every solar controller dims its load as the battery runs down, so two fixtures on the same site glow at different brightness whenever their batteries hold different states of charge. A fixture with a full battery runs its LEDs at full power. Its neighbor with a half-empty battery has already stepped down to stretch the remaining hours. Nothing is broken. The mismatch is designed into any site where batteries, panels, and shading were not matched.
What power consumption control does inside a controller
Power consumption control is the logic that protects the battery after sunset. It decides how much power the LED driver may draw, and when to cut the load entirely.
A PWM (Pulse Width Modulation) controller does this with a fixed threshold. A Low Voltage Disconnect (LVD) circuit cuts the load when battery voltage drops below a preset value, usually set once during commissioning. The limitation is structural: voltage is a rough proxy for state of charge, and one fixed threshold cannot tell a healthy 100 Ah pack from a tired 50 Ah pack sitting at the same voltage.
An MPPT (Maximum Power Point Tracking) controller measures battery voltage, current, and temperature, then estimates the remaining capacity from that data. Load power follows the estimate. When estimated capacity falls below roughly 20%, the controller steps lighting power down to buy hours of illumination instead of letting the fixture burn bright for two hours and die. On our all-in-one units that dimming curve is a configurable parameter, not firmware folklore.
| Behavior | PWM (fixed threshold) | MPPT (capacity-based) |
|---|---|---|
| Load cutoff | LVD at a preset voltage | LVD at a preset voltage |
| Partial-power mode | None | Steps power down below ~20% estimated capacity |
| Knows actual capacity | No | Estimates from voltage, current, and temperature |
| Tolerates battery aging | Poorly | Better, because it tracks the pack, not just the voltage |
Why two fixtures on one street disagree at night
Four causes, roughly in the order we see them on site:
- Battery mismatch. Different brands, chemistries, capacities, or ages mean different discharge curves. The same voltage reading on a new cell and a three-year-old cell represents different remaining energy, so the two controllers dim at different times.
- Shading and orientation. Even a few meters apart, panels collect different energy when a parapet, tree line, or adjacent building shades one and not the other. That charging gap becomes a state-of-charge gap by dusk.
- Independent control. Each controller runs alone. Neither asks its neighbors what they are doing, so nothing coordinates the dimming across the site.
- Aging drift. Capacity fades unevenly across fixtures, and the voltage-to-capacity relationship shifts as packs age. A site commissioned with matched batteries is not matched in year three.
When a site manager reports uneven brightness, the first measurement is the battery, not the lamp. Log each pack's resting voltage at dusk and compare. The dim fixture is almost always the one sitting at the lower state of charge, and the reason it got there is upstream: charging, capacity, or age.
How we spec multi-fixture sites so this stays uniform
- One battery brand, one batch, one capacity per project. On large installations we specify LiFePO4 (lithium iron phosphate) packs from a single production lot. Mixing lots is how fixtures drift apart within a couple of years.
- Identical controllers with identical settings. Same firmware family, same LVD and dimming thresholds, configured from one template. A site carrying three controller generations will show three brightness behaviors.
- Group coordination where the budget allows. IoT-capable controllers report state of charge and can follow a group dimming schedule, so the site dims to the weakest pack instead of each fixture deciding alone. This is the only fix that still works when batteries cannot be matched, and it costs more per pole.
- A fixed monitoring cycle with set-based replacement. Inspect on a schedule and replace batteries as a set when capacity drops, rather than fixture by fixture. One fresh pack among tired ones recreates the mismatch you just fixed.
What this page does not cover
This page covers DC load control inside standalone solar street light controllers. It does not cover grid-tied lighting controls, centralized AC circuits, or hybrid wind-solar charge control. If you are laying out a site and need uniform illuminance between fixtures, start with our lighting design tool: spacing and lumen output set the baseline, and power control only manages the battery behind it. To size the controller and battery per fixture, use the controller sizing calculator. Our all-in-one solar street lights ship with the dimming curve matched to the installed pack, which removes the most common mismatch at the source.