Room Control: Occupancy Timeout vs. Active Presentation
A 36-room university building uses a networked control system to power displays and switch sources. Each room has an occupancy sensor, a display with CEC enabled, a wall plate HDMI input, and a dedicated PC. The control processor turns a display off after 15 minutes of no occupancy; it turns it on when occupancy is detected or when the wall plate detects +5 V. Users report that during 50-minute lectures with a mostly still presenter and a static slide, displays shut off; in one room, the display no longer wakes from standby after a firmware update. The help desk has been manually power-cycling. The customer wants reliable on/off behavior without disabling energy savings. You are asked to revise the control logic and commissioning plan.
1. Why does the occupancy-only timeout fail, and what control logic would you recommend instead?
Read the worked answer
Occupancy sensors detect motion, not attention. A presenter standing at a lectern with a static slide can be motionless for longer than 15 minutes, so the sensor reports the room empty even though the display is in active use. The wall plate +5 V input covers only HDMI sources; the dedicated PC may be displaying content while the wall plate is idle, so that input does not prove activity either.
Use multiple activity signals and combine them with occupancy:
- Display sync or source-present detection from the PC and wall plate.
- Network presence or a control heartbeat from the PC, if available.
- Scheduled class times as a high-confidence occupancy signal.
- Occupancy sensor as a release condition, not the only hold condition.
Recommended logic: turn on when occupancy or a source becomes active; keep the display on while any source is active or the room is scheduled; start the 15-minute timeout only when occupancy is false and all source-activity signals are false. Add a grace period after source loss so a brief resolution change does not blank the screen. This preserves energy savings without shutting off during a lecture.
2. A display in one room no longer wakes from standby after a firmware update. How would you diagnose and resolve it without relying on manual power cycling?
Read the worked answer
Treat the wake failure as a control-path problem, not a display failure. First verify that the control processor is sending the expected command and that the display's network or serial link is responsive. Then check CEC: after a firmware update, the display may have reset CEC, changed its standby behavior, or stopped responding to the processor's CEC address. Test with a known-good CEC command from a test controller and observe whether the display wakes. Inspect EDID and source detection: if the processor switched to a source that is not present, the display may stay in standby even though the wake command arrived.
Resolve by using the most reliable control path available. If the display supports IP or RS-232, use that as the primary power control and keep CEC as a fallback. Confirm that the display's standby mode is not "deep" or network-disabled, and that the firmware setting for wake-on-CEC or wake-on-LAN is enabled. Avoid repeated power cycling, which masks the fault and stresses the display. Document the command that works, update the driver or module, and roll the fix out to one room before the remaining 35.
3. What commissioning tests would you run across all 36 rooms to prevent recurrence?
Read the worked answer
Test each room as a system, not just as a display. For every room, verify occupancy-only, source-only, and scheduled-on conditions, then confirm the display stays on for a recorded 20-minute static-slide test with no motion. Remove the source and confirm the display turns off after the intended timeout plus grace period. Test the wall plate hot-plug, PC wake, and source switching, including a resolution change.
For power control, verify wake and sleep through the primary path and the fallback path, and record the response time. Confirm that CEC firmware settings survive a display power cycle. Check that the help desk can see room status and send a wake command remotely, so a single failure does not require a site visit. Log the results room by room, note any display model or firmware exceptions, and keep a known-good configuration for each model. Finally, set an alert for a display that is commanded on but reports no source sync, so the next firmware issue is detected before users report it.