· Product launches· 日本語で読む
RoboParty Releases RPO Humanoid Robot Hardware Design as V2.0
RoboParty’s public repository offers hardware designs for the RPO/Roboto Origin humanoid robot in V1.0 and V2.0. V2.0 integrates power management and communications on a single board and updates the mechanical structure and calibration method; the company recommends it for current use. However, it is not mechanically or hardware-interface compatible with V1.0.
Key facts
- The repository is an open-hardware library for the RPO/Roboto Origin humanoid robot, with design files divided into V1.0 and V2.0.
- V2.0 integrates power management and communications interfaces on a single core board.
- V2.0 adds a mechanical switch to limit waist rotation, calibration using a limit pin, revised arm parts and a switch for the main control board on the rear plate.
- V1.0 and V2.0 are not mechanically or hardware-interface compatible.
- CERN-OHL-W-2.0 applies to hardware designs and related assets, GPL-3.0-only to software and firmware, and CC-BY-SA-4.0 to user-facing documentation.
What happened
RoboParty has published an open-hardware library for its RPO/Roboto Origin humanoid robot on GitHub. The design files are divided into V1.0 and V2.0, with the company identifying V2.0 as the current recommended version. V2.0 integrates power management and communications interfaces on a single core board and also changes the mechanical structure and calibration method.
Why it matters
RoboParty’s public designs include assembly drawings, PCB files, manufacturing assets and URDF files, providing information that developers can use to inspect and reproduce the robot’s configuration. However, V1.0 and V2.0 are not mechanically or hardware-interface compatible, so parts and design documents from the two versions cannot be combined without checking which version they belong to.
Analysis
The repository’s key feature is that it manages, by version, not only the robot’s exterior design but also mechanical parts, circuit boards, manufacturing files, URDF files and meshes, making assembly information available. V2.0 moves from V1.0’s separate power and communications boards to a single board, and adds a mechanical limit on waist rotation and a calibration procedure. The repository also describes V2.0 as intended for mass production, but that describes the version’s positioning, not a production track record or manufacturing capacity.
We reported that RoboParty released hardware, software and other materials for the RP1 in “RoboParty Launches RP1 Humanoid Robot With Open Hardware and Software”. We also covered a repository for training, evaluation and policy export for RPO and RP1 in “RoboParty Releases Repository for Training, Evaluation and Policy Export for RPO and RP1”. Unlike those software and training-related resources, this hardware design repository provides design assets and version management for assembling the robot. However, the information available here is not enough to determine whether these releases cover the same robot configuration.
RoboParty says that using a single board simplifies internal wiring and reduces potential connector failure points. In practice, because V1.0 and V2.0 have incompatible mechanical and electrical interfaces, parts and procedures from the older version cannot be used as-is with the newer design. Choosing a version therefore affects not only parts procurement but also the work of keeping mechanical drawings, PCBs, URDF files and instructions consistent. The repository’s warning to rename old directory names when updating multiple design assets together highlights the configuration-management challenges involved in reproducing open hardware.
The next points to check are the results of reproducing the robot from the published manufacturing files, the availability of BOM components, and the scope of V2.0’s application to mass production. The repository describes the version as intended for mass production, but does not provide figures on unit volume, production capacity or reliability testing on the robot. In addition, third-party assets remain subject to their original license terms, so anyone reusing the design set must check the rights applicable to each file.
Details
V2.0 mechanical design files are located in “V2.0/roboto_origin_mechanic/” and board files in “V2.0/roboto_origin_pcb/.” They include assembly drawings, STL files, Gerber files and circuit diagrams. Mechanical changes include a mechanical limit switch to restrict waist rotation, a calibration procedure using a limit pin, revised arm parts and a switch for the main control board on the rear plate. The repository describes V2.0 as intended for new development and mass production, while V1.0 is for maintenance and reference by users of the older version.
V1.0 and V2.0 are not mechanically or hardware-interface compatible. CERN-OHL-W-2.0 applies to hardware designs, CAD, PCB, BOM, manufacturing files, URDF files and meshes; GPL-3.0-only applies to software and firmware; and CC-BY-SA-4.0 applies to user-facing documentation. Third-party or vendor-provided assets are subject to their original license terms.
Sources
Translated from the Japanese original: /news/roboparty-rpo-hitogata-robotto-no-haadouea-sekkei-wo-v2-0-to-1e2273. The Japanese version is authoritative if they differ.