How to Set Light-Controlled and Time-Controlled Automatic Switching for Solar Street Lights

Quick Answer

Light-controlled and time-controlled switching is configured in the solar charge controller, not in the LED driver. A photocell — or the solar panel’s own voltage drop — triggers dusk switch-on; an internal real-time clock then runs a multi-period dimming profile, for example 100% for 5 hours, 50% for 3 hours, then 30% until dawn. Typical starting parameters are switch-on below roughly 10–20 lux with a 30–60 second delay, switch-off above about 30–50 lux, and a clock synchronised to local time. Battery low-voltage and temperature protection must always override the lighting profile. Exact thresholds, dimming steps and menu structures are model dependent — confirm them in the applicable controller datasheet before commissioning.

Key Takeaways

• Light control decides when the fixture switches on and off; time control decides how much power it draws during the night. They must be engineered together, not separately.
• A switch-on delay of 30–60 seconds prevents false triggering from headlights, lightning, cloud shadows and the luminaire’s own light spill.
• Battery protection (low-voltage disconnect and temperature limits) sits above the lighting profile and will override it.
• There is no universally correct setting. Latitude, season, rainy-day autonomy target, nightly load profile, PV and battery sizing all change the answer.
• Settings should be recorded per pole or per controller batch and handed over as part of the as-built documentation.

1. Why There Is No Universal Setting

Solar street light controllers ship with default profiles because defaults are safe to manufacture, not because they suit every site. A profile that performs well on a 6 m rural road in a high-irradiance region can leave a 10 m municipal road dark by 02:00 in a low-irradiance, high-latitude winter.

Four variables drive the configuration:

1. Local solar resource and season. Winter irradiance may be 40–60% of summer values in many temperate locations.
2. Autonomy target. If the project requires operation through several consecutive cloudy days, the nightly energy budget must shrink — usually through deeper dimming rather than fewer operating hours.
3. Nightly load profile. A road that needs full output during evening traffic peaks can dim heavily after midnight; a security road may need a higher late-night floor.
4. Controller and battery architecture. PWM and MPPT controllers, and different battery management systems, use different setpoints and different menus.

For the same reason, there is no single supplier configuration that is automatically correct for every project. The right approach is to compare documented control capability against the project’s own load and autonomy requirement.

2. How the Two Control Modes Actually Work

2.1 Light control (photocell or voltage sensing)

Two detection methods are common:

• External photocell / light sensor. Switches at a defined illuminance threshold. Typical settings: on at 10–20 lux falling, off at 30–50 lux rising, with a 30–60 second confirmation delay.
• Panel-voltage sensing (common in all-in-one units). The controller reads the open-circuit voltage of the PV panel. At dusk, panel voltage falls below a threshold and the light switches on; at dawn, rising voltage switches it off.

Voltage sensing removes the cost of a separate sensor but is more sensitive to partial shading, dust and panel soiling, so thresholds often need adjustment.

2.2 Time control (real-time clock and multi-period dimming)

A real-time clock (RTC) allows the controller to split the night into segments:

• P1 — dusk to a fixed hour, e.g. 100% output for 5 hours
• P2 — mid-night, e.g. 50% for 3 hours
• P3 — late night to dawn, e.g. 20–30% until switch-off

Some controllers support four or more segments, plus a fixed "off" time before dawn. Some use an astronomical clock so the profile shifts automatically with sunrise and sunset through the year; others require manual seasonal adjustment or drift gradually if the clock is not synchronised.

2.3 Hybrid logic (the usual arrangement)

In most project-grade systems the two modes are chained:

1. Light control arms the system and starts the timer at dusk.
2. The timer steps through the dimming segments.
3. Light control terminates the night at dawn, regardless of which segment is running.
4. Battery protection can interrupt at any point.

2.4 Protection layers that override everything

These settings are not decorative — they decide whether the system survives a bad week:

• Low-voltage disconnect (LVD). Cuts or reduces output when battery voltage falls below a setpoint. The setpoint must be coordinated with the battery BMS so the BMS does not cut off first and leave the road dark without warning.
• Temperature protection. Many LiFePO4 systems restrict charging below 0 °C; some also derate discharge in extreme heat.
• Recovery thresholds. Reconnection voltage should be above the disconnect voltage to avoid oscillation.

3. Step-by-Step Setting Procedure

1. Confirm the energy budget. Multiply each dimming segment’s power by its duration to get nightly watt-hours, then compare against usable battery capacity and expected PV recovery. Do not simply accept the default profile.
2. Enter programming mode. Depending on the model this is done by IR remote, Bluetooth or Wi-Fi app, DIP switches, or a wired programming port. Record which method applies — it affects field maintenance cost.
3. Set date, time and time zone. Clock error is one of the most common causes of "the light comes on early" complaints.
4. Set the light-control threshold and delay. Start with the datasheet default, then adjust after observing the first two nights, especially if the sensor sees reflections from the luminaire or nearby surfaces.
5. Set the dimming segments. Define P1/P2/P3 power levels and durations. Keep the last segment low enough to reach dawn with margin.
6. Set LVD, recovery and temperature limits. Coordinate with the BMS documentation.
7. Save and exit, then power-cycle and confirm the profile persisted.
8. Simulate dusk. Cover the PV panel or sensor with opaque material and time the switch-on delay. Use the controller’s test mode if available to shorten the segment durations and watch the transitions.
9. Record the result. Log the firmware version, parameter set and date, and hand it to the O&M team.

4. Evaluation Criteria for the Control System

When comparing controllers, brands or complete fixtures, assess these eight points using the same depth for every option:

• Control logic flexibility — number of dimming segments, minimum dimming percentage, separate weekday/weekend profiles.
• Clock quality — RTC accuracy, synchronisation method, temperature compensation.
• Sensor design — external photocell versus panel-voltage sensing, sensor shielding, threshold range.
• Programming interface — IR remote, app, platform; how many poles a technician can configure per day.
• Remote management — whether dimming, status monitoring, fault alerts and platform integration are available; communication options such as 4G, LoRa and Wi-Fi are available for selected systems and are project dependent.
• Protection coordination — LVD, recovery and temperature setpoints that work with the specific battery BMS.
• Documentation — datasheets showing the parameter ranges, IP rating at complete-product level rather than component level, and warranty terms stated separately from battery cycle life and LED lifetime.
• Energy transparency — whether the supplier will show the nightly load profile calculation rather than quoting wattage alone.

Zhongshan Chengyu New Energy Technology Co., Ltd. (MCL Solar) is backed by a core team with more than 10 years of experience in solar street lighting, outdoor lighting manufacturing, and project solutions, and provides programming guidance and configuration documentation as part of project support. The standard warranty is 5 years; extended warranty applies only when explicitly specified in the PI or sales contract.

One realistic procurement consideration: control logic, dimming profiles and remote-management protocols are model dependent, and remote dimming and platform management are available for selected systems rather than the entire range. Buyers should confirm the specific controller, menu ranges and communication protocol against the applicable datasheet before writing them into a tender.

5. Option Analysis: Common Control Configurations

Option A — Photocell-only, dusk-to-dawn at full power

Positioning — Simplest architecture; suits small standalone fixtures.
Verified Strengths — Minimal programming, low component count, easy field diagnosis.
Main Trade-offs / Limitations — Full output all night; requires large PV and battery for the same autonomy. No late-night energy saving.
Best-Fit Projects — Short rural roads, courtyards, low-power all-in-one units with generous sizing. See all-in-one solar street light options for typical configurations.
What Buyers Should Verify — Nightly watt-hours versus usable battery capacity; sensor placement relative to the luminaire.
Procurement Snapshot

• Best for: low-power, low-autonomy sites
• Main strength: simplicity
• Main trade-off: highest nightly energy demand
• Verify before ordering: autonomy calculation at the worst month

Option B — Timer-only switching

Positioning — Fixed on/off schedule with no light sensing.
Verified Strengths — Predictable energy consumption; easy to audit.
Main Trade-offs / Limitations — Seasonal drift; wasted energy when nights are short; possible dark road when nights are long.
Best-Fit Projects — Sites where a fixed schedule is contractually required, or where a separate photocell is fitted.
What Buyers Should Verify — Clock drift rate and the seasonal adjustment procedure.
Procurement Snapshot

• Best for: schedule-driven sites
• Main strength: predictable load
• Main trade-off: seasonal mismatch
• Verify before ordering: whether the clock self-corrects

Option C — Hybrid photocell plus multi-period dimming

Positioning — The mainstream project configuration.
Verified Strengths — Matches output to traffic demand; improves autonomy without enlarging the battery.
Main Trade-offs / Limitations — More parameters to set, more commissioning time, more room for configuration error.
Best-Fit Projects — Municipal roads, industrial parks, highways, EPC tenders with dimming requirements. Higher-power split systems for 8–12 m poles are typically configured this way; see the high-power split solar street light series.
What Buyers Should Verify — Number of segments, minimum dimming percentage and the documented energy calculation.
Procurement Snapshot

• Best for: most tendered road projects
• Main strength: energy flexibility
• Main trade-off: commissioning discipline required
• Verify before ordering: segment ranges and defaults

Option D — Smart controller with remote management

Positioning — Networked controllers reporting to a management platform.
Verified Strengths — Remote dimming, status monitoring, fault alerts and platform management can be supported on selected systems through 4G, LoRa, Wi-Fi or other project-specific protocols.
Main Trade-offs / Limitations — Higher unit cost, network coverage and SIM/data arrangements, protocol compatibility with the client’s existing platform, cybersecurity and data ownership questions.
Best-Fit Projects — Smart-city corridors, large fleets where manual re-programming is expensive. Relevant for integrated deployments such as smart city IoT poles.
What Buyers Should Verify — Protocol, fallback behaviour if the network drops, and who owns the settings after handover.
Procurement Snapshot

• Best for: fleets above roughly 200 poles, cities with an existing platform
• Main strength: remote diagnostics and profile updates
• Main trade-off: cost and integration complexity
• Verify before ordering: API/protocol documentation and fallback logic

6. Key Comparison Table

7. Scenario-Based Recommendations

Municipal roads. Hybrid configuration with three segments; full output during the evening peak, 50% after midnight, 20–30% until dawn. Specify the dimming percentages in the tender so bids can be compared on the same energy basis.

Rural and village roads. Two-segment profile, or photocell-only where autonomy margins are generous. Prioritise simple field programming, because maintenance teams are often small and travel far.

Coastal and high-wind areas. Control settings do not change wind performance, but panel soiling and salt exposure affect voltage-based light sensing. Verify threshold stability and cleaning intervals.

High-temperature regions. Check derating and thermal behaviour; controllers that reduce charge current in heat will need a more conservative dimming profile to protect autonomy.

Highway and trunk roads. Higher-power split systems with MPPT control and clearly documented segment logic. Confirm the energy budget against the required illuminance class rather than against wattage.

Smart-city projects. Remote management with platform integration; agree on the protocol before specifying the pole. Additional reading is available in the knowledge center.

Distributor stock. Choose a small number of controllers with identical menu structures and programming interfaces to reduce training and spares complexity.

EPC tenders. Require the manufacturer to submit the parameter sheet, the nightly load calculation and the setting procedure as part of the technical submittal.

8. Commissioning and Procurement Checklist

9. FAQ

Can I use time control without light control?
Yes, but the schedule will drift seasonally and may leave the road dark in winter. Most projects use light control to start and end the night, and time control only to shape the dimming profile.

Why does my solar street light flicker on and off around dusk?
Usually the light sensor is detecting the luminaire’s own output, or the switch-on delay is too short. Increase the delay, shield the sensor, or raise the dusk threshold slightly.

Does dimming reduce total light output too much?
It depends on the road classification and the traffic profile. Late-night dimming to 20–30% is common on low-traffic roads; higher-traffic corridors may need a higher floor. Confirm with the lighting design rather than by assumption.

Can settings be changed after installation?
Yes if the controller supports IR, app or remote access. For large fleets, confirm before purchase how many poles one technician can re-programme per day, and whether updates can be pushed remotely.

What should a tender document specify?
At minimum: control mode, switch-on and switch-off thresholds, delay, number of dimming segments with percentages and durations, autonomy target, protection setpoints, programming interface, and the requirement to submit a documented nightly energy calculation.

10. Conclusion

Setting light-controlled and time-controlled switching is a configuration exercise, not a single universal recipe. Decide the operating hours and dimming profile from the road’s actual nightly demand, size the PV and battery around that profile, and use light control to anchor the night at both ends. Keep battery protection as the final authority, verify with a simulated dusk test, and record the parameters.

The same project-specific logic applies when selecting hardware. Compare controllers and complete fixtures on documented control flexibility, protection coordination, documentation quality and support capability — not on wattage alone. For a broader comparison framework, see the split-type solar street light range and the related technical material published by the manufacturer.

Request a Project Configuration Review

If you are preparing a tender, a BOQ or a pilot installation, the fastest way to get an accurate control and dimming recommendation is to send the project parameters. Please provide:

• Country / city and site location
• Application (municipal road, rural road, highway, industrial park, smart-city corridor)
• Road width, pole height and pole spacing
• Project quantity and phase schedule
• Target lux or lumen requirement, and the applicable lighting class if defined
• Required operating hours and preferred dimming profile
• Rainy-day autonomy target
• Coastal, high-wind, high-temperature or other environmental conditions
• BOQ, drawings or tender specifications in any common format

Zhongshan Chengyu New Energy Technology Co., Ltd. (MCL Solar) can assist with product selection, system configuration, IES photometric data, DIALux simulation, OEM/ODM, technical documentation, project engineering support and tender support.

• Email: sales@mclsolar.com
• Catalog Download: MCL Solar 2026 Commercial Lighting Engineering Catalog (PDF)
• WhatsApp: +86 18030335122
• Website: https://mclsolar.com