If your lab wants to develop its own robotics software, the standard G1 isn’t a suitable starting point: according to Unitree Robotics, the standard product doesn’t support secondary development, and the manufacturer recommends EDU for customisation. When choosing an EDU configuration, first confirm which development access you need, then consider whether you need extra mobility or dexterous hands. If staff will use the robot as work equipment, the selection process should also include a risk assessment for your specific laboratory set-up.
These teams need access to control systems and software development, rather than a robot designed for pre-programmed demonstrations. Unitree Robotics documents SDK2 interfaces and ROS 2 communication for the G1, but rules out secondary development with the standard product. The key question is which access rights are actually included in the EDU configuration on offer.
If you’re researching grasping, hand control or data collection, you’ll need to select the end effector as part of the specific configuration. Unitree Robotics’ variant documentation lists G1 EDU models with 23 to 43 degrees of freedom and a range of hand options. That doesn’t necessarily mean a particular hand is suitable for every test object.
When experiments involve people, assembly or frequent changes to the set-up, the layout affects the protective measures required. If staff use the G1 as work equipment, the employer must assess the risks before use under section 3 of Germany’s Ordinance on Industrial Safety and Health. CE marking doesn’t replace this assessment.
Use: Pre-programmed demonstrations with no in-house development project.
Limitation: According to Unitree Robotics, the standard product doesn’t support secondary development, so it won’t meet the goal of developing your own robotics software.
Use: Developing your own control systems, ROS or simulations, provided the specific configuration on offer includes the access you need.
Trade-off: Additional dexterous hands or tactile equipment are only relevant for the corresponding experiments and add to the integration workload.
| Requirement | What to check before buying | Who should pay particular attention |
|---|---|---|
| Development access | Specify the EDU model and secondary development rights in writing; confirm the SDK interfaces and computing hardware required. | If we’re writing our own motion or AI software, a robot that can simply run demonstrations won’t be enough. For around 31% of buyers, development access is the top priority. |
| Dexterous hands and mobility | Check the degrees of freedom, hand model and any tactile equipment on the exact version against your research task. | If our research involves grasping or hand control, the chosen hardware must provide the actions and sensor data we need. This is the main concern for about 25% of buyers. |
| Simulation and data flow | Agree on the planned ROS 2 and SDK versions, as well as data access and network set-up, before ordering. | For repeatable experiments, control programmes and data must work seamlessly across the simulation, computer and robot. Around 19% of buyers put this workflow first. |
| Laboratory operation | Include the layout and operating area in the risk assessment; use the specific documentation to establish which checks are required. | If staff are working alongside the robot, protective measures must remain effective during changes to the set-up and in the event of faults. For around 25% of buyers, safe integration comes first. |
Unitree Robotics rules out secondary development with the standard product. So if you plan to develop your own control system later, simply specifying a G1 won’t ensure it’s suitable.
For development work, specify the EDU configuration and include development rights, interfaces and support in the quote.
Choosing the wrong version may mean redesigning your research project or purchasing a different model.
Unitree Robotics’ variant documentation shows that EDU models differ in their mobility and hand options. The presence of a hand doesn’t guarantee it will suit a particular object or provide the control access you need.
Choose the hand model, required sensor data and control interface based on your research hypothesis, and confirm they’re available with the specific configuration.
Additional hardware may require assembly, maintenance and changes to the safety plan.
Unitree Robotics’ ROS 2 documentation describes a communication method for the G1, but whether it will work in your lab also depends on the software versions and network configuration you use.
Set out your planned ROS distribution, SDK and firmware versions, and data pathway as acceptance test criteria.
Checking version compatibility, configuring the network and collecting data can all take additional development time.
Under section 3 of Germany’s Ordinance on Industrial Safety and Health, employers must assess the risks of the specific use before staff use the robot as work equipment. Product marking doesn’t replace an assessment of the layout, working process and possible faults.
Before choosing a model, review your planned laboratory operation with those responsible for health and safety, and establish whether assembly or modifications will require an inspection before use.
Unitree Robotics manufactures the G1 and G1 EDU platforms. Its documentation can help you understand the different versions and development options, but it doesn’t replace the documentation for the specific model on offer.
Not for this development work, based on the manufacturer’s information about the standard product: Unitree Robotics rules out secondary development and recommends EDU if you need to customise the robot. For an EDU model, make sure the specific access rights you need are confirmed in writing.
Unitree Robotics’ ROS 2 guide describes communication over DDS and lists, among other options, Ubuntu 20.04 with ROS 2 Foxy and Ubuntu 22.04 with ROS 2 Humble. Check that ROS 2, CycloneDDS, the SDK and the firmware all work together in your planned set-up. These examples aren’t a guarantee for every configuration on offer.
No. If an employer uses the G1 as work equipment, section 3 of Germany’s Ordinance on Industrial Safety and Health requires them to assess the risks before use and put suitable protective measures in place. This assessment should start when you select and purchase the specific set-up.
If the safety of the work equipment depends on how it has been assembled, section 14 of Germany’s Ordinance on Industrial Safety and Health requires an inspection by a competent person before it is used for the first time. An inspection is also required before the next use if a modification requires one. You’ll need to assess whether this applies to your planned G1 set-up based on the specific changes made.