For projects involving your own robotics software, start with an R1 configuration explicitly identified as EDU: according to Unitree Robotics, only the EDU version supports further development using your own software. The U1 and U2 variants described by RobotShop differ in their stated onboard computing tiers; gripper hands are most relevant for experiments involving object contact. Before placing an order, check development access, documentation for your exact configuration and the arrangements for controlled hardware testing.
If you’re developing your own movement routines or teleoperation, check that the available EDU configuration provides the joint, state and communication access you need. Unitree Robotics documents development resources for the R1, including SDK, DDS and ROS 2.
If your software is intended to run on the robot, the computing options and connections for the planned sensors are key. The U1 and U2 EDU variants described by RobotShop have different stated computing tiers. Those figures alone don’t tell you how well your own model will perform.
Additional hands are relevant when grasping, object contact or hand-based human–robot interaction is part of an experiment. Reichelt Elektronik describes different EDU hand variants, and the equipment you need will depend on your specific research question.
First, check whether the R1 EDU configuration on offer provides the development access and documentation you need. Then choose the computing tier and hands to suit the experiments you actually plan to run.
| Criteria | What to check before buying | Who should pay particular attention |
|---|---|---|
| Development access | Ask the seller to confirm the EDU model designation and access to the specific SDK, DDS and ROS 2 features you need. | For my own movement software, I want to be able to use joint states and middleware rather than being limited to demonstration features. This development access is the main reason to buy for around 31% of consumers. |
| Computing power and perception | Compare the 40 TOPS listed for U1 or 100 TOPS for U2 by RobotShop with the requirements of your planned models and sensor streams. | If my perception software is to run on the robot, I need enough headroom for its actual processing demands. Around 25% of consumers put this onboard requirement first. |
| Gripper hands and contact | Check the hand type and tactile equipment for the exact EDU variant; Reichelt Elektronik describes different U3 to U6 configurations. | For experiments involving grasping or hand contact, I need to know what movements and sensor data the selected hand supports. This is the priority for around 19% of consumers. |
| Procurement and testing | Check the conformity documentation and operating instructions for the exact configuration, along with delivery terms and a designated test area for your experiments. | Before testing my own movement software on hardware, I need to be able to manage procurement and controlled operation responsibly. This is a priority for around 25% of consumers. |
Unitree Robotics states in its official shop that only the EDU version supports further development using your own software. The R1 name alone therefore doesn’t confirm that you’ll have the development access you need.
Ask for the model designation, EDU status, interface scope and planned extensions to be specified in the offer.
RobotShop lists 40 TOPS for U1 and 100 TOPS for U2. These figures don’t show how quickly a specific model will run with your sensor streams and runtime requirements.
Before choosing a variant, define a repeatable test using your planned models, data rates and latency limits.
The EDU variants described by Reichelt Elektronik differ in their hand options. An additional hand doesn’t automatically offer any benefit for experiments focused solely on movement or perception.
Choose the hand type and, where needed, tactile sensors for a specific grasping or interaction experiment. Check the software integration too.
Development access alone isn’t enough to plan commissioning. If a configuration is classed as machinery, you’ll need to consider the applicable requirements of the 9. ProdSV. Those responsible for testing their own movement software must also define the test area and protective measures based on the specific setup.
Before ordering, check the documentation for the configuration on offer, the delivery terms and the planned approval process for hardware testing.
Manufacturer of the R1 platform and R1 EDU development variants.
Provider of the Jetson Orin computing components in the U1 and U2 R1 EDU variants described by RobotShop.
Component brand for the Revo 2 hand options available with certain R1 EDU variants.
Start with an R1 configuration explicitly identified as EDU, as Unitree Robotics says only the EDU version supports further development using your own software. RobotShop describes U1 and U2 as supporting SDK2, ROS 2 and Isaac Sim. Ask the seller to confirm the actual level of access available with the configuration on offer.
U1 may be suitable if its documented EDU environment and the 40 TOPS listed by RobotShop are enough for your planned workflow. U2, listed at 100 TOPS, is the option to consider if you need more onboard computing headroom. Tests using your own models and sensor streams will show whether either variant meets your runtime requirements.
Reichelt Elektronik describes U3 and U4 with Dex3-1 three-finger hands, and U5 and U6 with Revo 2 five-finger hands. Before planning a contact experiment, check the hand type, any tactile features and delivery terms for the exact variant on offer.
First, check the legal classification and documentation for the specific R1 configuration, including any modifications. For machinery, § 3 of the 9. ProdSV lists requirements including operating instructions, a declaration of conformity and CE marking before the machinery is placed on the market or put into service. Those responsible must also define the test area and protective measures for their own movement software, based on the specific task and risk assessment.