The R1 name covers several editions. Begin with the software access and equipment your project needs, then match them to the exact package being offered.
01 / THE MODEL
Development access depends on the edition.
Unitree’s official shop lists R1 AIR, R1 and R1 EDU. It states that only EDU supports secondary development, meaning development of your own applications. The shop identifies its EDU package as the EDU Standard Edition and directs buyers to sales for optional equipment. Unitree Robotics source ↗
The RoboCup programme lists an R1 EDU Smart package. Existing RoboCup teams can contact the vendor; new teams apply through the programme. Participation conditions apply. RoboCup Federation source ↗RoboCup Federation source ↗
02 / ACCESS
Confirm the package and delivery together.
Use Unitree’s shop or sales channel for the edition you need. Its page shows both a general stock label and a backorder message for a selected AIR variant. Ask for written confirmation of the selected edition, destination, shipping date and included equipment before planning a project start. Unitree Robotics source ↗
03 / CONFIGURATION
Compare Standard and Smart line by line.
For a development project, ask for an itemised package: onboard computing, sensors, hands, batteries, charger, controller and software access. Check the supported SDK version, example code and simulation workflow against your intended experiment. If you are using a RoboCup offer, confirm the exact EDU Smart specification and programme conditions with the vendor before comparing it with the shop’s EDU Standard package.
04 / THE T3ND PERSPECTIVE
Plan who can inspect and repair your unit.
A laboratory or competition team needs a repeatable handover between operators. Request the edition-specific inspection, charging, transport and cleaning instructions, then record who performs each task. Ask which components the team may replace and which work belongs to the supplier. For a competition deadline, clarify repair turnaround and the spare parts recommended for your configuration.
Does this exact edition include the development access required by our project?
Is the quoted EDU package Standard or Smart, and what equipment differs?
Which SDK, examples and simulation tools support the supplied hardware revision?
What delivery date and service route apply to our country and selected variant?
Which inspections, cleaning tasks and repairs may our team perform, and which spare parts should we plan for?
A USEFUL STARTING POINT
We use or are evaluating R1 [AIR / R1 / EDU Standard / EDU Smart] for [task]. Our configuration includes [hands / computing / sensors]. We need guidance on [care, transport or accessory requirement].
News
Published
Unitree adds lie-down and get-up calls to the R1 client
Unitree updated its public R1 locomotion client and example with lie-down and get-up calls. Developers should match the example to their robot firmware and confirm the supported operating states before integrating it.
R1 example exposes preset and recorded arm actions
Unitree published an R1 arm-action example for listing and calling preset actions and replaying recorded custom actions. The example explicitly warns that G1 and R1 action identifiers differ.
A new R1 SDK example reads joint feedback and sends arm commands through DDS. It gives developers a separate reference for joint targets rather than preset action playback.
RoboStore announced US ordering for R1 and described local repair, parts and support. The announcement separates configurations, helping prospective operators ask about development access and the hardware included in their quote.
Unitree added an R1 audio client and example to its SDK. The code provides a reference for speech output, audio playback and volume controls for interaction development.
This independent guide connects official publications with practical questions for your project. Follow the sources for current specifications and terms. The care and configuration questions are T3nd’s editorial guidance; obtain the instructions for your supplied hardware and software.