跳转到主要内容
This page explains how to control Wuji Hand 2.1 correctly and safely: unit conventions, MIT control mode, the joint table, parameter safety limits, and a safe control loop. For interface definitions and the full API, see SDK Reference.

​
Units and Symbols

For positive direction and the origin, see Origin and Motion Direction.

​
MIT Control Mode

The device runs in MIT force-position hybrid control by default, and the control mode isn’t switched from the Python API:
  • q_d / dq_d / τ_ff come from the position / velocity / effort fields of joint_command, with exactly 20 JointCommand entries per publish
  • Read and write Kp / Kd through mit_params, and the torque cap through effort_limit

​
Joint Table

Numbering: thumb 0–3, index 4–7, middle 8–11, ring 12–15, and pinky 16–19. SDK labels follow {finger}_S{1..4}. For each joint’s motion direction and angle range, see Product Introduction. The naming convention was fixed in the 2.1 revision and later revisions stay compatible.

​
Origin and Motion Direction

The motion ranges match the joint limits in the model files (URDF / MJCF / USD) and are mirrored between the left and right hands. Model joints and links are named with an {l,r}_ prefix plus the finger name, and the root link is the arm flange mount {l,r}_mount. See Coordinate Frames and Models. set_origin and clear_origin calibrate the current physical position as the user origin. While a joint moves, the change is deferred to the next IDLE. For the procedure, see Calibration and Configuration.

​
Control Rate and Command Rate

joint_states and joint_diagnostics share one device stream, so lowering the push rate of either lowers the other. For subscription modes and output-rate control, see SDK Reference.

​
Parameter Safety Limits

Writes to effort_limit and mit_params are validated: NaN, Inf, and negative values are rejected, and effort_limit also rejects values above the device ceiling. A rejected write raises an error and leaves the value in effect unchanged. The ceiling comes from the firmware, so read it back from the device for the exact number.
Raising effort_limit or Kp raises both grip force and collision impact. Approach a new value in small steps, and after each change run a slow, small motion to confirm the behavior before returning to normal duty.

​
Safe Control Loop

  1. Connect the device and confirm all 20 joints are online with no active error codes.
  2. Clear the workspace and confirm nobody is touching the hand.
  3. Enable the joints and wait until all reach the Enabled state.
  4. Interpolate from the current pose to the target pose instead of sending a step.
  5. Keep joint_diagnostics subscribed during the loop, and stop as soon as an error code goes active.
  6. Disable and disconnect when you finish.
For stop behavior and the fault-clearing flow, see Maintenance. For measured runs of the matching examples, including smooth homing and both motion examples, see SDK Practice.