firmware.bin file, not the .uf2 or .elf. Each rig takes a few seconds, left first, then right:
- The new firmware is copied to the rig while the current firmware keeps running. The rig accepts it only if the whole file arrived, its checksum matches, and it is Mantis firmware. Anything else is rejected and nothing changes.
- The rig restarts into the new firmware on trial.
- When the new firmware reports the expected build, the command confirms it and the update becomes permanent.
- Keep both triggers released. Each rig learns its trigger’s released position when it restarts.
- Don’t run it during teleoperation or data collection. The trigger stops sending readings while the rig restarts.
- Press Ctrl-C, or Stop in the control panel, during the transfer to cancel it. Nothing is installed on that rig.
- If a rig already runs that build, the command says so and skips it. Pass
--forceto install it again. - If one rig fails, the command still updates the other, then reports the failure.
You can also update from the control panel’s diagnostics dashboard under Diagnostics → Helpers → Update Mantis firmware, with Mantis selected. Choose the
firmware.bin on your computer, and the dialog uploads it and shows its version and build date. Then press Run to install it.The command uses the left and right buses in Mantis settings → CAN (can_mantis_l and can_mantis_r by default). Pass --channel to update one rig on a different interface.