Skip to content
简体中文

Motion Control

Send single position/current/MIT commands, or run trajectories, streaming Servo, managed drag, teaching, and replay.

The 21-, 16-, and 13-DOF products use JointLayout.joint_count for whole-hand arrays. Whole-hand and single-joint protocol paths are implemented for PB1, PT1, DB1, and DT1 but still await hardware validation. Finger- and thumb-scoped operations require the 21-joint layout.

Check the product support matrix

Run these fragments with a connected hand. Python runs inside an async function; C++ requires revo3/revo3.hpp, iostream, vector, chrono, and stdexcept; handle SdkError at the application boundary.

state = await hand.state.snapshot()
target = list(state.positions_deg)
handle = await hand.motion.move_to(target, duration=1.0)
result = await handle.wait(timeout=3.0)
print(result)
const auto state = hand.state().snapshot();
const auto layout = hand.joint_layout();
if (!layout) throw std::runtime_error("Joint layout is unavailable");
std::vector<float> target(
state.motors.positions_deg,
state.motors.positions_deg + layout->joint_count);
auto handle = hand.motion().move_to(target, std::chrono::seconds(1));
const auto result = handle.wait(std::chrono::seconds(3));
Operation Parameters Returns
Motion.move_to(target, duration) Target angles (degrees); duration (Python seconds / C++ duration) OperationHandle
Motion.set_position(position_deg) joint_count target angles (degrees); send once No value
Motion.set_current(current_ma) joint_count target currents (mA); send once No value
Motion.set_mit(position_deg, velocity_rpm, kp, kd, feedforward_current_ma) Five arrays of joint_count values; send once No value
OperationHandle.wait(timeout) Wait limit (Python seconds / C++ duration) OperationState

Find full signatures, defaults, units, and Python / C++ differences by operation:

A trajectory and ServoSession cannot control the same Hand concurrently; conflicts return ControlConflict. The SDK does not clamp targets to built-in default limits; current firmware configuration is authoritative. A wait timeout or Indeterminate result does not prove motion has stopped. Read actual state before recovery.

Errors, Timeouts, and Retries · Language Binding Differences