Legacy Timeout Error
Legacy Timeout Error
The controller is not able to communicate with the head. You may see it in a line scan, but it won’t respond to commands like calibration, mapping, or schedules.
Common causes:
Head didn’t check in properly → reset the controller
Duplicate or incorrect head numbering → contact Support
Loose or obstructed cable connection at the head → check and reconnect carefully
Overlapping schedules (older software) trying to run too many heads at once
Try resetting the controller first:
Controller 2: press the green button
Controller 3: press the far-left reset button
If the issue continues:
Unplug the controller for 1 hour
Plug it back in and wait 1 minute
Reset the controller again
Then:
Run 'Test & Detect Devices'
If the head appears, try running it
If heads are missing, check wiring between the controller and heads for loose connections