1. The Core Engineering Challenge: Crossover Lighting in Solar Layouts
Before comparing the specific solar design software platforms, we must understand the primary pain point lighting designers face: achieving safe uniformity ratios through crossover lighting. The ANSI/IES RP-8-22 standard does not just dictate how bright a parking lot or roadway should be; it strictly limits the ratio between the brightest spot (usually directly under the pole) and the darkest spot (the midpoint between poles).
To eliminate dangerous shadows and prevent drivers' pupils from rapidly constricting and dilating, professional designers rely on crossover lighting. This is the practice of ensuring that light arrives at any given point on the pavement from multiple directions, overlapping to create a smooth, even visual environment.[1] In a commercial setting, it is recommended to utilize at least four lights to create crossover lighting from two different directions.[1]
With traditional grid-tied lighting, fixing a dark spot is often as simple as brute-forcing a higher wattage fixture onto the pole. However, in solar street lighting, every lumen requires battery capacity and solar panel wattage. If your software inaccurately models the crossover distribution, you may accidentally specify oversized solar panels and batteries to compensate for a perceived dark spot, needlessly driving up your project bid and losing the contract to a competitor.
2. AGi32: The North American Standard for Exterior Calculations
Developed by Lighting Analysts, AGi32 has long been considered the gold standard for North American electrical contractors and Department of Transportation (DOT) engineers. Its primary advantage is its native alignment with US customary units (foot-candles) and strict adherence to IES standard reporting formats.
When using AGi32 as your primary solar design software, the most critical feature to understand is its dual calculation methodology. The software allows users to run simulations using either the "Full Radiosity Method" or the "Direct Only Method".[2] This is where many novice designers make a critical error.
The Full Radiosity Method calculates complex interreflections—meaning it tracks light as it bounces off a floor, hits a wall, reflects onto a ceiling, and scatters. While essential for indoor architectural lighting, using this method for an outdoor solar parking lot is inefficient and can yield misleading edge data.[2]
For outdoor solar street lighting, engineers must explicitly select the Direct Only Method.[2] This mode rapidly computes only the direct component of light arriving at any calculation point on the pavement grid. More importantly, it accurately calculates the shadowing effects of 3-dimensional objects like trees, adjacent buildings, and the solar light poles themselves, without wasting computing power on non-existent outdoor "bounces".[2] By isolating the direct light, AGi32 provides a highly accurate, conservative estimate of your crossover lighting efficiency.
3. DIALux: The Global Visual Powerhouse
DIALux (specifically DIALux evo) is a globally utilized, highly advanced lighting design program that offers incredible 3D visualization capabilities. For contractors looking to impress clients with photorealistic renderings of how a solar street light project will look at night, DIALux is unmatched. Furthermore, the software is free, making it highly accessible for growing solar integrators.
To effectively use DIALux for solar design, the workflow involves importing site CAD drawings, defining the ground surfaces and mounting heights, and strategically placing the fixtures in the digital model. The software then simulates the lighting performance, generating detailed calculation reports covering Illuminance, Uniformity Ratio, and Beam Angle distribution.[3]
However, DIALux presents a significant trap for US contractors: it is a European-developed software that defaults to the metric system, measuring illuminance in Lux. If a contractor runs a complex crossover lighting simulation in DIALux and submits the raw Lux data to a US city planner, the photometric study will be rejected. You must ensure that your output grids are mathematically converted or set to output strictly in Foot-candles (where 1 Foot-candle equals 10.764 Lux).[4]
For a detailed guide on converting between Lux and Foot-candles and avoiding costly measurement errors in US municipal projects, read our comprehensive Lux to Foot-Candles conversion guide for contractors.
4. The "Garbage In, Garbage Out" Rule of Photometric Files
Whether you choose AGi32 or DIALux as your solar design software, both programs share a fundamental vulnerability: they are entirely dependent on the accuracy of the IES files provided by the solar street light manufacturer.
An IES file is a standardized digital blueprint that tells the software exactly how a specific luminaire distributes light in a 3D space. Unfortunately, the solar lighting market is plagued by inaccurate, exaggerated, or poorly formatted photometric data. Lighting design programs are built to import any valid data file and run the math; they do not verify if the physical light fixture actually performs as the file claims.
A common issue is "stray uplight" recorded in poorly tested IES files. If a manufacturer's file shows light bleeding upward, the software will flag the fixture as failing the strict BUG (Backlight, Uplight, and Glare) rating requirements necessary for Dark Sky compliance, ruining your proposal.[1] To avoid inaccurate crossover modeling, contractors must demand verified, third-party-tested IES files from reputable commercial solar manufacturers.
For comprehensive guidance on IES RP-8-22 compliance, BUG ratings, and photometric verification for municipal projects, refer to our complete IES RP-8-22 compliance guide for commercial solar street lighting.
5. Modeling Solar Dimming Profiles
There is a unique challenge in solar photometric modeling that neither DIALux nor AGi32 can solve natively: time-based battery degradation. Standard grid-tied LED lights run at 100% output all night long. Solar street lights, however, rely on intelligent battery management systems (BMS) and often utilize adaptive dimming profiles to conserve energy.
For example, a solar light might operate at 100% brightness from dusk until midnight, dim to 30% during the low-traffic hours of 1:00 AM to 5:00 AM, and return to 100% before dawn. If you run your photometric study solely on the 100% output IES file, your layout will show perfect RP-8-22 compliance. But what happens at 3:00 AM? If your pole spacing is too wide, that 30% dimming phase will completely destroy your crossover lighting overlap, plunging the center of the roadway into darkness.
Professional solar engineers must run two separate calculations in their solar design software: one using the peak output IES file, and a secondary worst-case scenario calculation using an adjusted lumen depreciation factor to represent the battery's dimmed state. This guarantees that your uniformity ratio remains legally compliant even during the deepest parts of the night.
6. Choosing the Right Tool for the Job
So, which solar design software should your engineering team adopt?
- Choose AGi32 if: Your primary clients are US municipalities, DOTs, and federal agencies. Its native foot-candle environment, rigid adherence to IES reporting, and efficient Direct Only Method make it the safest choice for strict regulatory compliance.
- Choose DIALux if: You are pitching to private commercial developers, architects, and HOAs who rely heavily on visual aesthetics. The photorealistic 3D rendering engine can help sell the project, provided you meticulously manage your metric-to-imperial conversions.
Ultimately, the software is merely a calculator. The success of your commercial solar installation relies entirely on deploying proper crossover lighting techniques, utilizing accurate NEMA beam angles, and sourcing verifiable data from a trusted manufacturing partner.