[OpenArm] ROS 2 control bringup for builders integrators (intermediate)

We want one practical thread on OpenArm ROS 2 control bringup for builders and integrators.

What sequence keeps fake hardware, controller checks, and real hardware validation from drifting apart?

If you reply, include one launch habit that reduced wasted debugging time.

Pick your closest symptom to follow the right troubleshooting path.

Reproduce "[OpenArm] ROS 2 control bringup for builders integrators (intermediate)" in a controlled loop, then compare baseline vs current measurements before applying partial fixes.

If residuals or drift fail your acceptance limits after warmup, switch to full recalibration/recovery workflow.

Use them as a checklist template first. Confirm interface names, fixture IDs, and safety conditions in your own cell before execution.