motor.dump-config back to the motors it came from, returning them to a known-good configuration. Works for both motor families — each snapshot record carries the motor type it was taken from. This command is CLI-only (it reads a snapshot file from the robot host), so it isn’t offered on the diagnostics dashboard.
Parameters already holding the saved value are skipped, so restoring onto a matching motor writes nothing. Read-only parameters are always skipped, and protected ones unless
--include-protected is passed, since rewriting those can leave a motor unable to commutate or unreachable on the bus. A snapshot taken with --raw cannot be restored — its bare indices have no known meaning.
Pair this with
motor.dump-config: dump a good motor to a snapshot, then restore that snapshot onto one that has drifted. The restore reports exactly which parameters it changed.