Open Source RoboticsRobots, software & learning

Unitree actuator SDK interface source

Software

This repository exposes motor command/data interfaces and C++/Python examples for selected Unitree actuators. [1] [2] [3] [4]

Installation & first result →Official websiteGetting started

For
Robotics developers inspecting the specified interface/research source [1] [2] [3] [4]
Source rights
Named licenses are documented by part. Review licenses
Unknowns
operating system, compute requirements not fully established. Review gaps

Source researched · Not tested by us
Sources checked · Research details

Licenses & related hardware

Requirements · Research details and dates

On this page

Overview

This repository exposes motor command/data interfaces and C++/Python examples for selected Unitree actuators. A useful source contribution is its explicit motor-family and rotor/output conversion workflow. The reviewed excerpts establish interfaces/examples linked to a precompiled core; a complete engine, hardware or firmware release is not established by this packet. [1] [3] [4]

Is this for you?

Known limitations
  • CMake linksarchitecture-specific.so core; completecoreimplementation notestablished.
  • Motor exampleactivelycommands position andneedsfamily-specificscaling; no poweredtest orprotectionvalidated.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] · Editorial assessment

What you need

Dependencies
  • READMEGCC>=5.4x86 or>=7.5Arm, CMake andmatchingprecompiledarchitecturelibrary
  • NamedA1/B1/GO-M8010-6motor, serialdevice androtor/output conventions

[1] [2] [3] [4]

Installation & first result

Open the upstream getting-started guide [1] [2] [3] [4]

  • Inspect the named implementation and matched configuration; reconcile the documented gaps first.
  • Select only the relevant interface/backend; do not treat example output as completed physical action.

Editorial assessment of cited source; no runtime or hardware test.

[1] [2] [3] [4] · Editorial assessment

Installation

CMake examples link architecture-specific precompiled libUnitreeMotorSDK libraries; README GCC >=5.4 for x86 or >=7.5 for Arm, matched motor family and serial interface.

Documented source requirements/route, not installation or compatibility reproduced by this catalog.

[1] [3]

Project notes

The CMake build links a precompiled core

The README names GO-M8010-6, A1 and B1 motors and GCC minimums of 5.4 for x86 and 7.5 for Arm. The selected CMakeLists chooses architecture-specific libUnitreeMotorSDK shared objects and builds examples around them. A successful example build would therefore not establish that the central SDK implementation is available as source. No binary/core build or example was run. [1] [3]

Match the motor family, library architecture and serial interface before adapting an example. The cited example/example_a1_motor_output.cpp A1 output-side example opens /dev/ttyUSB0 and actively sends repeated commands. That device path is a source setting, not hardware discovered here; the example is not a passive health check. [4]

Keep the conversion convention visible

The README explains that command quantities are on the rotor side, while control calculations may be output-side, and describes gain conversion using the gear ratio. For gear ratio r, the selected A1 example sets rotor_kp = output_kp / r² / 26.07 and rotor_kd = output_kd / r² × 100. It converts output angle in degrees to rotor radians by multiplying by π/180 and r. These are the selected example's model-specific conventions. Do not treat a single generic gear-ratio formula as validation of every motor family or gains. Inspect the exact model/API version before applying commands. [1] [4]

The repository source notice is BSD-3-Clause. The linked core, firmware, purchased motor and external dependencies need their own rights review. No serial transfer, returned state, limit protection, position accuracy, thermal behavior or physical motion was validated. [2]

What we checked

Source/document review only; no build, installation, binary/device/network execution, control commissioning or performance test.

Not yet established

  • Requirements: operating system, host computer
  • Version-specific hardware compatibility (ecosystem tags alone do not establish it)

Updates

Upstream last updated
Not established
Latest release
Not established
Profile updated
Nov 1, 2026
Sources last checked
Nov 1, 2026
Next review
Dec 1, 2026
Reviewed revision
5b79a42

Source files and licenses

Narrow source-available robotics interface or research implementation; gaps in licensing, binary core or physical setup are explicitly separate from the inspectable contribution.

LayerAvailability / license
softwareavailable · BSD-3-Clause repository source; precompiled core separate
Scoped repository declaration; external binary engines, firmware, hardware and dependencies retain separate rights. No full-stack openness or operational claim. [1] [2] [3] [4]
documentationavailable · BSD-3-Clause repository source; precompiled core separate
Scoped repository declaration; external binary engines, firmware, hardware and dependencies retain separate rights. No full-stack openness or operational claim. [1] [2] [3] [4]

No separate physical design, pretrained distribution or dataset is selected as the released contribution in this scoped software review.

References

Each source links to the exact revision we read. “Used for” shows where this page relies on it.

Correction guidance · Discussion is not enabled · Profile format 0.7.0-draft.5

Change history