Dim to Off: Confirming Lantern Lighting Compatibility
Dim to off means the lighting can reach an electronic off state through its dimming control, rather than merely stopping at a low light level. It is a capability of the actual control and driver combination, not a promise established by a “0–10 V” label or a zero command alone. The driver may remain powered in electronic off; this is not electrical isolation.
For a custom lantern or light-sculpture order, agree which elements need dimming, what their lowest required light state is and how the requested off state will be demonstrated. This guide organizes procurement and witness questions, not wiring, live troubleshooting or a guarantee that every lantern is dimmable. A completed-display illustration cannot prove its hidden control arrangement.
![]()
Separate minimum light output, electronic off and isolation
A minimum dimming level describes the lower end of the supported light-output range. It does not automatically mean no light. Electronic off is a different requested operating state. Neither a controller screen showing zero nor a dark-looking display tells a maintenance team that the electrical supply has been isolated.
Lutron’s Application Note 587 on 0–10 V control topology explains that electronic-off support is optional in the interface context it discusses, and both the control and driver need to support the relevant behavior. Its low-end guidance also distinguishes the control signal from the driver’s resulting light output. Do not borrow a fixed percentage or switching threshold for an unidentified component.
Keep the purchasing requirement equally clear: is the scene meant to remain visibly dim, reach no intended light output through control, or enter a separately specified shutdown state? The appointed technical team must define the appropriate arrangement. A decorative scene setting must not replace the venue’s isolation procedure or required route and emergency-lighting functions.
How does 0–10 V dimming fit the control path?
In the analog interface discussed here, a low-voltage control signal requests a lighting level from a compatible driver. It is not the lantern’s power supply. Matching the broad interface name is only the beginning: obtain the exact control and driver specifications, their supported interface roles and settings, and the permitted light-source load.
A lantern scene may begin in a show controller and pass through a translator or interface before reaching the driver. Record that actual path if it exists; do not assume a DMX command reaches every driver unchanged or that all lanterns use analog dimming. The DMX control handoff for lantern displays covers scene grouping, device modes, addressing and the wider data path. The narrower question here is what the selected driver and load do at the requested low end and off state.
For a fixed-output package, first ask whether dimming is offered at all. Adding a dimmer to the purchase description does not establish compatibility. Any change to supplied equipment or the control scheme needs the responsible supplier’s and project team’s review.
Use a combination-to-state acceptance worksheet
Complete one record for each materially different proposed combination. Identical-looking flowers or animal modules may contain different equipment; conversely, several modules may share a documented combination. The table is an original procurement worksheet, not a standard form or a claim about components included in every order.
| Link in the chain | Evidence to request | Question before acceptance |
|---|---|---|
| Scene command | Display/module ID, approved scene reference and the required low and off states. | Does “zero” name a command value or the agreed visible result? |
| Protocol and interface | Controller, any translator, input/output interface, configuration and document revisions. | Has the complete path been identified rather than inferred from one connector or protocol label? |
| Driver input and mode | Exact manufacturer/model, selected dimming mode, supported interface roles and electronic-off specification where required. | Do the control and driver support the same intended behavior under their stated conditions? |
| Actual light-source load | Source or string identity, supplied arrangement and relevant approved load information. | Does the offered combination match the one described by the compatibility evidence? |
| Minimum and off expectation | Agreed scene outcome, applicable manufacturer limits, viewing conditions and the person accepting the result. | Are a low level and electronic off separate criteria, without an invented universal percentage? |
| Witness and change record | Combination/configuration tested, approved procedure, observed result, exceptions and revision. | Can the delivered equipment be connected to the accepted result, and which later changes reopen it? |
Retain the underlying documents with the completed worksheet. A supplier statement that “the driver dims” does not answer whether the selected control can command its intended off behavior. Equally, a compatibility record for one driver mode should not silently cover another mode or a different light-source arrangement.
Agree what the witness must show
Ask the responsible technical team to define an appropriate, safe demonstration of the actual proposed combination. The record should identify the requested scene states, the configuration demonstrated, the visible outcome and any difference from the final installed package. If only one module was shown, retain that scope instead of calling it a test of the entire venue.
Review the low state and off state separately, using agreed observation conditions. A phone video with automatic exposure is not a calibrated brightness measurement. If a numeric output criterion is required, the project team must specify the suitable method and acceptance basis; this guide supplies neither.
A visible demonstration also does not establish flicker performance, optical-radiation safety, electrical compliance or suitability for emergency functions. Those are different evidence questions. Keep an unresolved result open with an owner and clarification requirement rather than adjusting settings or hardware to force a pass.
Why might a dimmer not turn the lights off?
In a proposed dimming system, the lowest supported output and electronic-off support may differ between components. An unexpected light state can also require a separate technical investigation; its appearance alone does not establish the cause or prove a fault. Give the supplier the exact combination, settings, requested state and observed result for review.
Do not use a search-result wiring trick, bridge control conductors or work on powered equipment to decide whether a driver supports off. The manufacturer’s documentation and the appointed electrical team govern any verification or corrective work.
A hypothetical replacement that keeps the same interface label
Imagine a buyer accepting a prototype flower module whose documented control-and-driver combination reaches the agreed electronic off state. Before shipment, an alternative driver is proposed. It has the same nominal interface label, but its submitted data do not confirm the required off behavior in the proposed configuration. This is a hypothetical purchasing example, not a Zigong Lanterns project or test result.
Keep the accepted prototype record and mark the replacement combination as unresolved. Ask the supplier to provide its exact model and mode, confirm the control pairing and actual load, and explain how the required low and off states will be verified. The buyer should not declare the replacement defective merely because the information is missing, but should not extend the earlier acceptance to it either.
Once the designated reviewer accepts the documented combination, update the equipment schedule and witness record together. Pass any resulting limits to the scene programmer and operator. A later change to the controller, translator, driver mode or light-source load should return to this same applicability review rather than inherit an unexplained approval.
Put the required light states into the display brief
When comparing custom light sculptures, identify which proposed elements need a steady level, a controlled fade or an electronic off state. Share the intended scenes and any existing controls before treating a visual design as a confirmed dimmable package. Ask what is included, which interfaces remain with others and what evidence will accompany the offered combination.
Define the result before accepting the interface label. Bring the display references, required low and off states, existing control information and the appointed technical reviewer. Discuss your lantern lighting and control brief so the proposal can identify the actual combination and its unresolved acceptance questions.
Before an off-state demonstration, establish which signal the selected controller sends and the exact input accepted by the driver. The 0–10V versus PWM lantern-control interfaces distinguishes an analogue voltage command, a PWM control input and the LED output method, then shows how to compare the proposed models without treating a shared dimming label as evidence of compatibility.
Leave a Reply