What startup checklist keeps OpenArm sessions repeatable enough for teleop, demos, and later data collection?
We want one beginner-friendly OpenArm checklist thread focused on calibration and homing.\n\nWhat exact startup order do you follow, and what do you record when something feels different from the previous session?\n\nIf you reply, include one check that prevented wasted debugging later.
The best checklist is short enough to follow every time. If it becomes too long, teams stop using it when they are in a hurry.
Tool changes and transport events deserve their own note because they often explain drift that looks unrelated at first.
Share the smallest calibration checklist another OpenArm team could copy into their lab notebook today.
Pick your closest symptom to follow the right troubleshooting path.
Start with a reproducible symptom check for "[OpenArm] Calibration and homing checklist for builders integrators (beginner)", then confirm host/service state before changing hardware or firmware.
journalctl -b | rg -n "error|warn|openarm|can"
ip -details link | rg -n "can|state"
python tools/preflight_check.py --quickAdd a simple preflight gate and a short startup checklist so regressions are caught before motion begins.
Use them as a checklist template first. Confirm interface names, fixture IDs, and safety conditions in your own cell before execution.