A humanoid form without bipedal balance
Reachy 2 uses a wheeled, omnidirectional base and two articulated arms rather than walking legs. Public product information describes two seven-degree-of-freedom arms and a mobile platform. Navigation and arm manipulation can therefore be developed without the balance-control requirements of a biped.
The available workspace does not alone prove that all mechanical drawings, actuator designs and fabrication files needed to manufacture Reachy 2 are open. Software access and self-build rights must be checked separately.
What lives inside reachy2_core
The ROS 2 workspace includes reachy_description for URDF and meshes, reachy_config for model parameters, reachy_controllers for motion interfaces, and reachy_bringup to launch the system. Those packages make the system structure inspectable and help developers identify which parameters belong to the model and which belong to control.
For testing without a physical robot, reachy_fake provides simulated joint responses and reachy_gazebo provides a physics environment. Those interfaces serve different purposes: a fake joint-state stream can help debug application code without claiming to model contact forces.
A measured workflow for a first application
Choose a supported ROS 2 version, install the project dependencies, load the robot description and inspect the joint names in the fake system. Only then move to Gazebo contact testing and a real-hardware bringup with appropriate safeguards. A Python or VR teleoperation interface also needs the matching system packages.
The project makes a useful reference for multi-arm control architectures, but a new script that runs in simulation has not been validated on a live Reachy 2 by this site.
Reachy 2 descriptions, ROS 2 and fake interfaces
Use matching revisions of parts, firmware and instructions. These steps summarize project documentation; no physical build was performed for this article.
Official files and manuals 5 references
Assembly sequence 5 steps
Decide whether you need software simulation or physical hardware
The published core is primarily a ROS 2 workspace; it is not a complete parts list for printing the humanoid.
Manufacturer's instructions ↗Prepare a compatible ROS 2 environment
Inspect requirements.txt, pyproject.toml and dependencies.sh for compatible ROS dependencies.
Manufacturer's instructions ↗Build the core workspace and robot description
Use reachy_description and reachy_config to examine joints and the mobile base configuration.
Manufacturer's instructions ↗Run reachy_fake or the Gazebo model
Test command interfaces and motion in a virtual model before connecting physical hardware.
Manufacturer's instructions ↗Use the official hardware bringup only with matching equipment
Check safety, power and network setup for the actual robot. Do not attempt construction based solely on URDF visualization meshes.
Manufacturer's instructions ↗
URDF versus fabrication files and simulation
Answers are based on published source material and project documentation. Their order does not represent search volume.
01Can I print Reachy 2 using the URDF meshes?
The core repository includes robot description and visualization meshes. That alone does not establish printable mechanical manufacturing STL, BOM, electronics or assembly instructions for a full robot.
Sources Official project source ↗
02How do I use Reachy 2 without owning one?
The repo includes reachy_fake and reachy_gazebo packages for simulation and fake hardware interfaces.
Sources Official project source ↗
03Which package contains the joint descriptions?
reachy_description contains URDF, Xacro and meshes; reachy_config holds the related YAML parameters.
Sources Official project source ↗
04Does Reachy 2 walk like a biped?
No. Reachy 2 is an upper-body humanoid mounted on an omnidirectional wheeled base, so bipedal walking instructions do not apply.
Sources Official project source ↗
05Why does a ROS controller start without moving real motors?
A fake or Gazebo interface produces simulated states rather than physical actuation. Use the supported hardware bringup and configured controllers for the real robot.
Sources Official project source ↗
06Which packages should be installed first?
The core project's dependencies script, requirements and ROS workspace setup define runtime prerequisites. Install the supported ROS distribution and dependencies before building.
Sources Official project source ↗
What to check before building Reachy 2
Build and integration
Use reachy2_core as a ROS 2 workspace: inspect the project dependencies, configuration YAML, robot description and bringup launch files. Begin with fake interfaces or Gazebo before attempting a physical session.
Known constraints
Reachy 2 uses an omnidirectional wheeled base rather than bipedal legs. A public ROS 2 core workspace does not itself establish that every physical component and fabrication file is licensed for self-build.
Original documentation
Found a changed specification? Submit a correction with its source ↗