[TRLC-DK1] Camera device order changes after reboot and breaks capture for builders labs (intermediate)

How do you catch the case where DK1 capture starts after reboot but the wrong physical cameras are now bound to the recording roles?

Forum / Posts Index / TRLC-DK1

Post

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.

Module: TRLC-DK1 · Audience: builders-labs · Type: question

Tags: dk1, camera-order, reboot, capture

Comment 1

The best replies explain whether the mismatch first appeared in preview feeds, file names, or later calibration checks.

Comment 2

If one startup script or device-identity check fixed the problem, share it. That concrete safeguard is what many searchers need.

Comment 3

It also helps to explain how you keep bad recordings from slipping through after a reboot.