Emergency Lighting
Why do my automated DALI emergency lighting tests fail with 'duration test max. delay exceeded' when manual tests pass?
By Lichtvision Engineering · Published
Short answer
A "duration test max. delay exceeded" status (IEC 62386-202) means the emergency control gear refused to start its rated duration test within the time window allowed by the controller schedule. The most common cause is an incomplete battery charge: under DALI-2 rules, an emergency fitting will block a duration test unless its battery has completed a full, uninterrupted charge cycle (typically 24 hours). If mains power dipped, or if a preceding function test drained the battery, the timer resets. A second common cause is bus congestion from scheduling hundreds of emergency fittings to test at the exact same hour. Ensure batteries are fully charged, stagger the automated test schedules across several nights, and use ProbitSite to query the specific failure status bits directly from the control gear.
What the customer asked
During commissioning of a commercial office building with roughly 300 DALI emergency lighting fittings, an integrator noticed intermittent test failures on their central monitoring station (quotes lightly edited and translated, fully anonymized):
"When triggering automated duration tests via our control system, about 40 fittings report 'duration test max. delay exceeded'. But when we physically walk the floor and trigger a manual test, they stay lit for the full 3 hours."
"We swapped out five of the reporting fittings for new ones, but two of the replacements threw the exact same delay error next automated run."
Why the "max delay exceeded" error appears
Under Part 202 of the DALI standard (self-contained emergency lighting), when an application controller sends a command to initiate a duration test, the control gear does not necessarily drop into emergency mode the millisecond the telegram arrives. Instead, it checks its internal readiness. If the battery is not fully charged, the fitting queues the test and waits for charging to finish.
However, the controller's schedule expects the test to start within a predefined delay window (often 24 to 48 hours). If the battery charge timer has not reached 100% before that window expires, the gear aborts the queued request and sets the failure status flag "duration test max. delay exceeded".
Manual witness tests often bypass this queue logic or happen at a time when the battery has finally reached full charge, creating the frustrating illusion of a software bug.
Is it a faulty luminaire? Rarely.
In over 90% of field investigations, the luminaire and battery are healthy. The root causes are operational: 1. Recent mains interruptions: Even a momentary power dip during final building construction resets the 24-hour battery charge requirement. 2. Back-to-back testing: Scheduling a monthly function test on Sunday night and an annual duration test on Monday night guarantees failure. The function test discharges the battery slightly, forcing a full recharge cycle before the duration test is permitted. 3. Bus broadcast storms: If 300 fittings simultaneously attempt to report test initiation and battery status back to the gateway, collision errors can cause the controller to assume a fitting missed its test window.
How to diagnose and resolve it
1. Confirm a complete, uninterrupted battery charge. 2. Stagger the automatic test schedule so devices do not all test at once. 3. Isolate one affected luminaire on a known-good line and start a function test, then a duration test, directly. 4. Verify Part 202 status responses with ProbitSite and replace non-compliant gear.
To isolate whether the issue is scheduling or hardware, connect ProbitSite to the affected line. Read the live Part 202 status bytes of a reporting fitting: ProbitSite decodes the exact internal state, showing whether battery charging is active, pending, or blocked by a temperature fault.
If the status shows a healthy charge, send a direct DALI "START DURATION TEST" command to that single address. If the fitting enters test mode immediately, your hardware is compliant, and the central controller's automated schedule must be widened and staggered across multiple nights.
Diagnose DALI issues like this in seconds
ProbitSite is the DALI-2 certified handheld multimeter built for exactly this kind of on-site fault finding.