Skip to content
简体中文

Config / Calibration / Maintenance

Read and set configuration, perform calibration, and manage reboot and firmware updates.

Config applies to 21-, 16-, and 13-DOF products. The 13/16-DOF protocol path is implemented but still awaits hardware validation. The current V3.3 protocol provides no speed-limit registers for any layout, so speed_limits_available is false. Calibration and Maintenance remain NotVerified for 13/16-DOF products.

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.

config = await hand.config.snapshot()
print(config.slave_id, config.speed_limits_available)
runtime = hand.config.runtime_options
print(runtime.servo_command_timeout_ms)
const auto config = hand.config().snapshot();
const auto runtime = hand.config().runtime_options();
std::cout << static_cast<int>(config.slave_id) << " "
<< runtime.servo_command_timeout.count() << "\n";

Before calling set_slave_id(), physically isolate the target hand on the bus and stop motion and Servo. Setting the current ID sends no write. A successful write, lost response, or cancellation after dispatch closes the original Hand and invalidates its transport session. Calling hand.close() alone is insufficient: close the old Manager, create a new Manager, then rediscover at the new address and read configuration to verify it. After a lost response, confirm the actual address before retrying; do not retry automatically.

The Python and C++ device_operations examples demonstrate closing the old Manager, creating a new one, and verifying the address. Run these commands from the examples repository root and replace the serial port. They default to read-only; add –run to write the address after isolating the target hand.

终端窗口
python python/revo3/device_operations.py --port /dev/ttyUSB0 --new-slave-id 2
./c/build/demo/device_operations /dev/ttyUSB0 --new-slave-id 2
Operation Parameters Returns
Config.snapshot() — DeviceConfig; speed_limits_available reports speed-limit availability
Python: await hand.config.set_slave_id(new_id) / C++: hand.config().set_slave_id(new_id) Device address 1–247 None / void; create a new Manager after an actual write
Python: hand.maintenance.update_firmware(file_path, target=None, wait_secs=10, *, on_progress=None) Firmware path; target; readiness wait in seconds; optional synchronous progress callback OperationHandle
C++: hand.maintenance().update_firmware(file_path, wait_seconds) Main firmware by default; wait_seconds defaults to 10 seconds OperationHandle
C++: hand.maintenance().update_firmware(file_path, target, wait_seconds) Explicit FirmwareTarget; wait_seconds defaults to 10 seconds OperationHandle
Python: handle.progress / C++: handle.progress() Update transfer fraction 0..1; unavailable for other operations float / None / std::optional

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

Firmware controls device-configuration persistence; RuntimeOptions affect only the current process. Do not call a speed-limit setter when speed_limits_available is false. Calibration requires idle Motion; do not retry automatically after a lost response.

Errors, Timeouts, and Retries · Language Binding Differences