The Unitree fleet, documented.
An engineering reference for people who have to make these robots actually work: SDKs and DDS topics, control and locomotion, perception and LiDAR, teleoperation and dexterous hands. Written from source-reading, official documentation and measurements taken on real hardware.
Every non-obvious claim carries its evidence level, because acting on a wrong hardware fact can damage equipment or injure someone. Verified read directly from primary source. Reported credible secondary source, not confirmed at source. Inferred our reasoning from verified facts, not established. Not established we looked and could not confirm it; the absence is the finding.
Unitree Go2 — Technical Reference
Compute tiers, network and DDS layout, SportClient control surface, sensing options and the practical limits of the Go2 quadruped.
23B2, H1 and H2 — Platform Orientation
What separates the industrial B2 quadruped from the H1 and H2 humanoids: payload and IP rating, the EDU gate on secondary development, SDK surface, and which simulator and RL stacks actually list each platform.
30G1-D — Wheeled Data-Collection Platform
The dual-arm G1-D is a data-collection and manipulation platform, not a walking humanoid. Variants, the AgvClient chassis API, lift-column control, end-effector options and how it differs from the G1.
Read this before anything moves.
This knowledge base describes how to make heavy legged robots move. A G1 has no built-in emergency-stop button, and neither does much of the fleet: you must provide an external kill path and confirm someone can reach it at all times.
Damping is not a safe state, it is a controlled collapse. Know which controller owns balance before anything moves, never run two controllers against one command topic, and use a gantry or a spotter for the first run of any new motion.
MCM Robotics is the official Unitree Robotics distributor for South Africa. This is our own engineering documentation. It is not Unitree's official documentation and is not endorsed by Unitree.
Firmware, SDKs and vendor documentation move quickly. Each document shows when its facts were last verified. Several entries exist because official documentation was stale or wrong.
Where a document names a file, flag, API id or version, check it against the code you actually have. Never guess on robot hardware.
Found something wrong? Tell us, ideally with a primary source attached, and we will correct it and re-date the page.