OpenIPC now uses a second camera's microphone to stop an autofocus test when the lens motor clicks. A click means the stepper motor stalled or skipped, but software logs don't reliably expose it. The new clickguard.py calibrates itself against room noise, listens for the impulse, kills the test and camera process on the first detected click, and treats a lost microphone stream as a failed test.
The acoustic check found a timing error in the motor driver. Each move ran for about 50 milliseconds, sat still for the rest of a 75-millisecond camera cadence, then restarted from standstill about 13 times per second. OpenIPC now stretches each burst to 66 milliseconds, saves the lens position so a restart doesn't force another trip into the end stops, and keeps normal moves at least 100 microsteps away from a stop. On the lab camera, the guard killed a deliberately clicking run 305 milliseconds after the second test tick, while full-speed moves between the new limits stayed quiet.
This is what hardware-in-the-loop testing should capture: the failure the product physically makes, followed by an automatic stop that protects the device under test. Any team testing motors, relays, or fans should ask whether one cheap microphone can turn its technician's "that sounds wrong" judgment into a repeatable release check.