The project is distributed across repositories
The main OpenArm repository is an entry point rather than one self-contained firmware package. The hardware project holds CAD, parts lists and manufacturing references. Separate projects provide URDF descriptions, a CAN motor interface and ROS 2 packages. This arrangement gives researchers access to specific layers without requiring every application to use the same software stack.
The upstream compatibility table distinguishes OpenArm 1.0 from 2.0 and identifies components that are supported, need adaptation or remain in development. A CAD model from one release should not be combined with an incompatible control description from another.
What the hardware archive supplies
The current hardware repository documents full assembly data for OpenArm 2.0, with a bill of materials and related Cell and KER equipment. Older release materials include STEP and STL models, mounts and cable drawings. Its authors say the Google Drive archive is the primary source, while GitHub releases mirror the files.
Source files are useful for estimating machine operations and checking dimensions. They do not remove the need to procure actuators, manufacture parts, route cables and validate emergency stops for a powered manipulator.
Control paths for physical AI experiments
An investigator can choose the CAN interface for joint-level work, ros2_control and MoveIt for conventional motion planning, or dedicated data-collection tools for demonstrations. The published teleoperation and policy examples should be evaluated against the version compatibility table.
The hardware project lists CERN-OHL-S-2.0, while many software packages list Apache-2.0. Keeping those licenses separate matters when publishing modified mechanical files alongside control software.
OpenArm manufacturing releases and CAN integration
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
Choose OpenArm 1.0 or 2.0
The official hardware archive lists separate V1 and V2 releases; hardware and controller geometry must come from one generation.
Manufacturer's instructions ↗Read the complete STEP and BOM before sourcing parts
OpenArm 2.0 contains full assembly STEP and BOM, plus a distinct evaluation cell and cabling options.
Manufacturer's instructions ↗Produce mechanical components using their specified process
Do not assume V1 printable STL models replace all V2 machined components; check machining and bearing tolerances.
Manufacturer's instructions ↗Assemble the arm and CAN electronics
Follow the manufacturer arm and wiring documentation, protecting cables from joint motion and verifying bus and supply layout.
Manufacturer's instructions ↗Check drive communications and only then motion planning
Use the specified CAN tools for low-speed individual motor checks before trying ROS 2 or Isaac-based trajectories.
Manufacturer's instructions ↗
V1/V2 files, machining and controller compatibility
Answers are based on published source material and project documentation. Their order does not represent search volume.
01Where are OpenArm V2 STL files?
The hardware repository points to V2 full assembly STEP, BOM and related design bundles, and to V1 ready-to-print STL files. Do not assume the V1 STL folder fits V2.
Sources Official project source ↗
02Can I construct OpenArm with only a 3D printer?
No. The source includes precision hardware and electronic modules in addition to printable/machinable CAD. Check the relevant BOM for motors, bearings and other purchases.
Sources Official project source ↗
03What is the difference between OpenArm and OpenArm Cell?
OpenArm is the arm platform; OpenArm Cell adds a separate evaluation cell, jig, wiring and integration models described in the hardware release.
Sources Official project source ↗
04What if a GitHub Release is missing CAD files?
The hardware README identifies its Google Drive as the source of truth, with GitHub release archives as mirrors. Check the linked drive for missing or mismatched assets.
Sources Official project source ↗
05Can I control the arm from ROS 2 or via CAN?
The main OpenArm index links separate openarm_can and openarm_ros2 packages. Match their supported arm version and low-level controller first.
Sources Official project source ↗
06What licenses govern modifications?
Hardware files are listed under CERN-OHL-S-2.0, while several control and robot-description repositories are Apache-2.0. Read each repository's licensing obligations.
Sources Official project source ↗
What to check before building OpenArm
Build and integration
Read the OpenArm hardware guide and select a specific revision before sourcing aluminum parts, motors, harnesses and controllers. The main repository links separate CAD, CAN communication, ROS 2 and simulation repositories. The 2.0 hardware guide documents seven joints per arm and a backdrivable drive architecture. Its research workflows include teleoperation and standardized manipulation evaluations.
Known constraints
Building the arm requires machining, power electronics and CAN bus integration; a 3D printer alone cannot reproduce it. The hardware CERN-OHL-S terms differ from the Apache-2.0 software packages. Published payload figures depend on pose and duration, and should not be treated as continuous full-workspace ratings.
Original documentation
Found a changed specification? Submit a correction with its source ↗