[TRLC-DK1] Camera device order changes after reboot and breaks capture for builders labs (intermediate)
TRLC-DK1 discussion on camera device order changing after reboot, capture scripts binding to the wrong sensors, and how labs keep camera assignments stable.
A frustrating DK1 setup problem appears when a reboot changes camera device ordering. Capture still starts, but streams may attach to the wrong view, calibration assumptions break, and the team only discovers the mistake after a bad recording session.
How are you diagnosing DK1 capture failures caused by camera device order changing after reboot?
Please share how you map physical cameras to logical roles, which signs reveal a camera-order issue instead of a calibration or bandwidth problem, and what startup checks keep the assignment stable before you press record.
If you reply, include one exact symptom after reboot and one exact mapping or validation step that exposed the order change.
The best replies explain whether the mismatch showed up in preview feeds, file names, or later calibration checks.
If one startup script or device-identity check fixed the problem, share it. Searchers often need that concrete safeguard.
It also helps to say how you prevent bad recordings from slipping through after a reboot.