Choose an LED dimming method from the controls backward
Define what occupants and the building system must do, then select a compatible control, driver, luminaire, wiring method, and commissioning plan. “Dimmable” alone is not a complete specification.
Published · Last reviewed
Short answer
Start with user needs: switching only, manual dimming, scenes, scheduling, occupancy response, daylight response, individual addressing, monitoring, or integration. From that intent, choose the communication method and driver behavior. Verify exact model compatibility, wiring, load limits, minimum level, fade behavior, standby power expectations, and failure response in a sample circuit before repeating the combination across a project.
1. Write the control sequence first
A useful sequence states who or what controls each zone, what happens on entry, how daylight changes output, whether occupants can override automation, what happens after hours, and what level is restored after a power interruption. It also defines emergency behavior separately. A conference room may need local scenes and integration with audiovisual controls. An open office may use occupancy zones, daylight response near windows, and task tuning. A retail display may need stable scenes and repeatable aiming rather than frequent automatic changes.
Draw the zones and control points. Identify which luminaires must act together and which need individual addresses. Confirm whether commissioning tools, gateways, network access, passwords, or licensed software are needed. Assign responsibility for programming, testing, backups, and future changes.
2. Understand the common interfaces
| Method | Selection considerations |
| Phase-cut | Control information is carried in the mains waveform. Exact dimmer, driver, load range, wiring, and leading- or trailing-edge behavior must be compatible. |
| 0-10V or 1-10V | Uses a separate analog control pair in typical implementations. Confirm source/sink behavior, off behavior, control-wire class, polarity, curve, and wiring distance. |
| DALI | A digital, addressable system based on IEC 62386. Define device types, bus power, addressing, groups, scenes, sensors, application controllers, and commissioning scope. |
| DMX | Often used where rapid, coordinated intensity or color control is needed. Network topology, addressing, termination, refresh behavior, and controller operation matter. |
| Wireless | Can reduce control wiring but still needs compatible devices, radio planning, commissioning access, cybersecurity decisions, update policy, and a recovery method. |
Names do not guarantee identical behavior. For example, analog dimming curves and off thresholds can differ, and proprietary extensions may be present. Use the current technical sheets for the exact driver and controller.
3. Specify dimming quality in observable terms
State the required minimum stable light level as a percentage of full output, while recognizing that perceived brightness is not linear with measured output. Define whether the luminaire must turn fully off through the control signal or requires switched power. Specify smoothness, fade time, consistency between units, and acceptable behavior when starting at a low level. Where cameras are used, include camera testing and the relevant flicker requirements rather than using “flicker-free” as an undefined slogan.
Check for shimmer, stepping, pop-on, drop-out, flash on start, delayed response, inconsistent low-end levels, audible noise, and unwanted color shift. Test several luminaires together because a combination that behaves well with one driver may change near control or dimmer load limits. Test normal switching, minimum level, scene changes, sensor transitions, and restoration after power loss.
4. Coordinate the electrical design
The driver determines how the LEDs are regulated and must match the luminaire's load. The control interface must also match the control system. Check input voltage and frequency, output current and voltage range, maximum load, insulation and wiring requirements, control terminals, inrush implications, circuit protection, and thermal location. Do not substitute a driver solely because its wattage looks similar.
Keep mains, control bus, analog control pairs, and network cabling arranged according to applicable instructions and code. Document addressing and labels. Ensure drivers, gateways, sensors, and power supplies remain accessible. Emergency circuits and life-safety functions require their own compliant design and testing.
Dimming submittal checklist
- Control narrative and zone drawing are approved.
- Exact luminaire, LED load, driver, controller, sensor, gateway, and accessory model codes are listed.
- Input, output, interface, wiring, and load compatibility are documented.
- Minimum level, off behavior, fade, startup, power-restoration, and failure behavior are defined.
- Mock-up tests use the intended number of luminaires and representative cable lengths.
- Commissioning tools, software access, addressing, backups, and handover are assigned.
- Camera or broadcast spaces receive project-specific flicker evaluation.
- Local electrical, energy, emergency, and control requirements are confirmed.
Build a useful inquiry
Send the supply, control protocol, sequence of operation, zone quantities, target low-end level, switching/off requirement, sensor and gateway scope, and destination market. Ask for a compatibility statement tied to exact models and revisions. Review AOCEN's commercial lighting range, locate system information in the catalog library, or contact AOCEN with the controls schedule. Commercial terms and compliance evidence remain subject to written project confirmation.
Reference points
The U.S. Department of Energy notes that driver and controls compatibility is important in its purchasing guidance. The DALI Alliance Quick Start Guide describes the DALI system framework. Apply the relevant standards, manufacturer instructions, and local code to the final design.