Which requirements should guide your choice?
Start with the planned exercises or research tasks. These will determine the development access, safety arrangements and ongoing support you need.
| Requirement |
What to check before buying |
Who it matters to |
| Development access |
Confirm the SDK version, access to movement controls and sensor data, and support for the development environment you need on the version being offered. |
If we want to develop our own control or navigation tasks, an operating app alone won’t be enough. For around 33 % of consumers, documented development access is a priority. |
| Supervised operation |
Make sure the operating area, user roles, stop procedure and training are appropriate for the device and exercise. |
When learners are taking part, I need to be able to stop the robot and organise supervision clearly. Around 27 % of consumers put safe, supervised operation first. |
| Research access |
Check access to the control and sensor levels you need, along with simulation tools and usage rights. |
If we want to investigate our own approaches to locomotion or perception, I need more than ready-made driving functions. This level of research access is the top priority for around 20 % of consumers. |
| Procurement and support |
Set out the included hardware, training, support, maintenance and delivery date in writing. |
If several courses depend on the device, I need to plan support and arrangements for downtime in advance. That’s why around 20 % of consumers prioritise reliable ongoing support. |
Related products from Joybuy
Related products coming soon.
Frequently asked questions
Does a university lab need a risk assessment before using a robot?
For use by employees, the employer must assess risks arising from their work and set out the necessary protective measures. This is set out in Section 5 of the German Occupational Safety and Health Act. When planning for a mobile robot, you should consider its movement tasks, the space, the stop procedure and training in particular. The organisation should separately check which local requirements also apply to students.
Which interfaces should a university team confirm before ordering?
The team should confirm the specific interfaces its teaching or research tasks require, including the SDK version, level of access, necessary hardware and usage rights. Unitree Robotics documents access to movement and sensor data for Go2, among other things; Boston Dynamics documents Python and autonomy services for Spot; and ANYbotics describes ROS-related access and simulation for ANYmal Research. The agreed configuration is what matters.
What should you agree on for training and ongoing support?
Make sure the quotation explicitly covers training, the support channel, maintenance, repair arrangements and responsibilities. Terra Robotics lists relevant options for Go2 EDU, but for teaching, what matters is which services the organisation actually agrees to and who will run the exercises and provide support.
Is a product page enough to guarantee delivery for a university project?
If your project has a fixed start date, agree a confirmed delivery date rather than planning solely on the basis of a product listing. Terra Robotics’ terms and conditions state that product descriptions in its online shop are not binding offers. This applies to the supplier mentioned and does not replace checking the specific agreement.