reBot Arm T701 HT MIT Control SDK

The T701-HT SDK's MIT interface sets target position, target velocity, feedforward torque, position gain Get the SDK and install its dependencies using the T701 HT Quick Start installation instructions. Complete the serial mapping and joint and gripper feedback checks, then verify the selected motor's zero position. The selected motor starts moving immediately when you run a motion command, without another arm selection or confirmation. Secure the hardware, remove payloads, and clear the motion range and return path. Stay with the hardware and keep clear of joint and gripper pinch points. The original target is ±π rad (±180°). The motion loop calls the low-level motor interface directly, without applying the high-level joint limits or gravity compensation. This trajectory may exceed the permitted range of an assembled joint or gripper. In particular, the high-level range for the ID8 gripper is −0.2 to 2.2 rad, so it cannot execute the original trajectory. Before running, adjust the target position and corresponding velocity to suit the selected mechanism, and verify the entire trajectory and return path. The example is Left arm CAN1, motor ID8: Right arm CAN2, motor ID8: All three arguments are required; there is no default arm or motor selection. This excerpt comes from the motion loop; the example creates The original frequency is 0.1 Hz, the period is 10 seconds, and peak target velocity is about 1.974 rad/s. If you change the position to The loop sleeps for At startup, the terminal displays the number of controlled motors. It then prints the selected motor's state every 100 loop iterations. The example reads these fields through The first The single-motor example uses a low-level The whole-arm MIT interface's target position checks do not replace trajectory design or torque limiting. For gravity feedforward, joint impedance, or automatic shutdown handling, use the complete examples linked from the Pinocchio page.Kp, and velocity gain Kd together. This page introduces the single-motor sinusoidal tracking example, its parameters, feedback, and shutdown sequence. For whole-arm gravity compensation, joint impedance, and Cartesian control, see T701 HT with Pinocchio.Prepare the Robot
board_serial in T701-HT_robot_param/serial_binding.yaml to the communication board's USB serial number.conda activate t701-htSelect and Run One Motor
scripts/motor_example/t701_ht_pos_vel_torque_kp_kd_control.py. After checking and adjusting the trajectory above, choose one command to match your wiring.python scripts/motor_example/t701_ht_pos_vel_torque_kp_kd_control.py --can-port 1 --motor-id 8 --arm leftpython scripts/motor_example/t701_ht_pos_vel_torque_kp_kd_control.py --can-port 2 --motor-id 8 --arm rightArgument Values Purpose --can-port1–7 Logical CAN channel on the communication board. Standard wiring uses 1 for the left arm and 2 for the right. --motor-id1–8 Selects just one motor with this ID on the specified channel. --armleft / rightSelects that side's motor types and homing configuration. --arm neither selects the CAN channel nor mirrors the right-arm trajectory. The example generates a temporary single-motor configuration from the corresponding YAML, so you do not need to edit the whole-arm motor list.MIT Parameters and Target Trajectory
motor and robot. Set the selected motor's command, then send it.motor.pos_vel_tqe_kp_kd(pos, vel, 0.0, 2, 0.5)
robot.motor_send_cmd()Parameter (in call order) Meaning Original setting posTarget position, rad π × sin(2π × 0.1 × t), with amplitude π rad.velTarget velocity, rad/s 0.2 × π² × cos(2π × 0.1 × t), the time derivative of target position.tqeFeedforward torque, Nm 0.0. Zero feedforward does not mean zero motor output torque.kpPosition gain 2.kdVelocity gain 0.5.offset + A × sin(2π × f × t), use the corresponding velocity A × 2π × f × cos(2π × f × t), and verify that the full range from offset − A to offset + A is permitted.t uses time.time(), so the initial phase depends on the launch time; the target does not necessarily start at zero. The source comment says “1.0 rad amplitude,” but the formula uses π rad.0.001 seconds after each send. Communication, computation, and printing add to the cycle time, so this is not a fixed 1 kHz real-time loop.Read State Feedback
Field Meaning positionCurrent motor position, printed in rad and converted to degrees. velocityCurrent motor velocity, rad/s. torqueReported motor torque, Nm. modeMode value returned by the low-level SDK. faultFault code returned by the low-level SDK, printed in hexadecimal. motor.get_current_motor_state(). The printing interval depends on actual loop timing. The example displays mode and fault values without decoding fault codes.Return to Zero and Exit
Ctrl+C exits sinusoidal tracking and starts a smooth return of the selected motor to its saved zero position.pos_vel_MAXtqe(), with the homing configuration for the side selected by --arm.Ctrl+C again during homing to interrupt the return and attempt braking. Invalid feedback or a homing failure also causes the shutdown logic to attempt braking.Ctrl+C triggers return motion. Damping braking is not a position hold; support the mechanism during startup and shutdown.Use MIT Control for the Whole Arm
motor object. Whole-arm control uses Lib.t701_ht.T701HT, with separate interfaces for joints and the gripper.Interface Parameters and sending behavior motor.pos_vel_tqe_kp_kd(pos, vel, tqe, kp, kd)Five scalar parameters for one motor. Call robot.motor_send_cmd() afterward to send.arm.pos_vel_tqe_kp_kd(pos, vel, tqe, kp, kd)Five joint vectors of length 7, excluding the gripper. Checks the configured target joint position range before sending; returns False for an out-of-range target.arm.gripper_control_MIT(pos, vel, tqe, kp, kd, send=True)Five scalar gripper parameters. Checks the target gripper position range and sends by default. With send=False, only queues the command for sending with the joint command in the same cycle. Returns False for an out-of-range target.