Preconditions

Robot turned on and all Preflight done

Steps

1. Press rover mode
2. Check the battery status is greater than 75%
3. Set the default speed
4. Fold the robot up by pressing RB until the kinematic limit
5. Fold the robot down by pressing RT until the kinematic limit
6. Repeat steps 4/ and 5/ ==> 25 times

Expected

all steps pass ==> No crash or mechanical or thermal issue must be found

Automation

Wired to nio-sdk src/nio_sdk/examples/test_fold_unfold.py (§4.5, tool: sdk-script). The script switches to JOINT_CONTROL, captures the live pose as "unfolded", reads the "folded" pose from fold_unfold_pose.yaml, and cycles between them --cycles times (here 25, matching step 6), waiting for each joint command to terminate. Exit 0 = all cycles completed → pass; non-zero (a RobotCommandError or connect failure) → fail. The runner substitutes $robot into --ip at run time.

> Caveat. The exit code only asserts the motion commands completed — it does not > observe the "no mechanical or thermal issue" part of the Expected result. If that physical > check must gate the verdict, switch automation.status to partial (script runs, operator > confirms).