Assembly guide for MABEL
Open-source 56-DOF mobile bimanual robot, teleoperated whole-body from a Vision Pro
License
- software: Apache 2.0
- hardware design files (CAD, PCB): CERN-OHL-S 2.0 (strongly reciprocal)
- documentation and media: CC BY 4.0
Split licensing. The software is Apache-2.0, the hardware design files (CAD, PCB) are CERN-OHL-S-2.0, a strongly reciprocal open-hardware licence that requires modified designs to be shared under the same terms, and the documentation and media are CC BY 4.0. Upstream components keep their own licences, listed in THIRD_PARTY_NOTICES.md: the arms derive from OpenArm and the hands from the ORCA Hand. Checked 4 Nov 2026.
Assembly guide
1. Before you start
What MABEL is built from, and which parts are bought, made or built from other open projects.
1.1 Know what you are building
MABEL combines bought modules, two open sub-assemblies and a small set of its own custom parts.
- MABEL is a mobile bimanual robot: a three-module swerve base, a vertical lift, a pitching torso, a 3-DOF head with stereo cameras, two 7-DOF arms and two 17-DOF hands.
- The arms are derived from OpenArm and the hands from the ORCA Hand; both are built as their own projects publish them.
- The swerve modules (REV MAXSwerve) and the lift (a standing-desk column) are commercial parts.
- MABEL's own parts are seven sheet-metal plates, printed covers and mounts, aluminium extrusion and one custom PCB, the base carrier board.
1.2 Choose your build tier
Everything except five choices is the same in every build.
- Order the core parts first: upstream's Build Guide lists them in sections 1 to 8, identical in the Essential, Recommended and Maximum builds.
- Then make the five choices in section 9: onboard compute, the two wrist cameras, the head camera, an optional base depth camera and the 2D lidar.
- Upstream's recommended picks are the Orin NX 16 GB, MMlove 1200P wrist cameras, the MMlove stereo head camera, no base depth camera and an RPLIDAR C1.
- The three reference builds differ only in these five choices; see this project's parts list for current prices.
2. Order the parts
The core parts list and where each part comes from.
2.1 Order the core parts
Upstream's costed list is the source of truth; every line carries a vendor link.
- Use this project's parts list, built from upstream's core.csv, which upstream calls the source of truth for the bill of materials.
- Most actuators, the OpenArm structural set, the arm harness and the hand servos are bought on Taobao; the swerve modules come from REV, the lift column from FlexiSpot, extrusion from McMaster-Carr.
- Check the open items on the parts list: upstream notes parts it has not costed yet, such as shipping, filament and the carrier board's components.
3. Make MABEL's custom parts
The sheet-metal plates, the printed parts and the extrusion cuts.
3.1 Get the CAD
All custom parts come from one full-robot STEP assembly.
- Unzip hardware/cad/MABEL_full_assembly.step.zip and open the STEP in any CAD tool, such as FreeCAD, Onshape, Fusion or SolidWorks.
- Per-link meshes of the whole robot are also in simulation/mabel_mujoco/assets/meshes, but make the parts from the STEP.
3.2 Have the sheet-metal plates made
Seven plates, quoted in 5052 H32 aluminium, 2.0 mm (0.080 in).
- Upload each plate's DXF or STEP to an online sheet-metal service in 5052 H32 aluminium, 2.0 mm thick.
- Base sheet metal, lower: laser cutting only.
- Base sheet metal, upper: 4 bends, dimple forming, hardware insertion and tapping.
- Lift-to-torso adapter: 2 bends, dimple forming, hardware insertion and tapping.
- Torso output plate: 1 bend, hardware insertion and tapping.
- Body bottom plate: 2 bends, hardware insertion and tapping.
- Neck mounting plate: 2 bends only.
- Arm mounting plates (two): hardware insertion and tapping.
- Hardware insertion means PEM nuts or standoffs pressed in at the fabricator, and tapping means threaded holes cut there rather than on your bench.
3.3 Print the printed parts and cut the extrusion
Covers, sensor mounts and trim are printed; the frame is 2x2 in and 2x4 in extrusion.
- Print the covers, sensor mounts and trim from the STEP in 1.75 mm filament (Build Guide section 8).
- Cut the aluminium extrusion to the lengths in Build Guide item 6.01, which upstream lists without a unit: 2x2 in profile at 15 (2), 17 (2), 4.75 (3) and 8 (2); 2x4 in profile at 10 (1) and 12.5 (2).
- Join the frame with the 1010-series corner brackets and angled plates in items 6.02 and 6.03.
4. Build the sub-assemblies
Arms, hands, swerve modules and lift, each built as its own maker publishes it.
4.1 Build the two arms
The arms are OpenArm-derived and built as OpenArm publishes them.
- Build both 7-DOF arms with our OpenArm guide, which follows OpenArm's own hardware documentation.
- MABEL's arm firmware drives each arm on its own CAN bus with the OpenArm motor set: DM8009 for joints 1 and 2, DM4340 for joints 3 and 4, DM4310 for joints 5 to 7.
- Before first use, check each DaMiao motor's p_max, v_max and t_max in the vendor tool; upstream warns that a mismatch silently rescales every value on the wire.
4.2 Build the two hands
The hands are ORCA-derived and run on Feetech servos.
- Build both hands with our ORCA Hand guide, using its Feetech build: MABEL's hands use Feetech HL3915M and HL3930M servos, 17 per hand (16 fingers and the wrist).
- Each hand needs one bus servo driver board and one power distribution board (Build Guide items 4.03 and 4.04).
- Seat the tendons and calibrate a newly assembled hand before enabling torque: every command is clamped to the calibrated range.
4.3 Build the swerve modules and fit the lift
Both are commercial parts.
- Assemble the three REV MAXSwerve modules (REV-21-3005) as REV documents them.
- Fit the FlexiSpot E7 Pro lift column (CBR4830MD-E7WS); MABEL runs the column's DC motor from a Raspberry Pi Pico through a BTS7960 H-bridge, reading its quadrature encoder.
- Mount the three modules front-right, front-left and back-centre: the base firmware assigns their CAN IDs in that order.
5. Make the base carrier board
The only custom PCB: a Teensy 4.1 carrier that runs the swerve base.
5.1 Order and assemble the board
A 2-layer board with three CAN buses, Ethernet, 24 V outputs and an IMU.
- Zip electrical/Motherboard/fab and upload it to any 2-layer PCB service; the stack-up is in fab/Motherboard-job.gbrjob.
- Source the components from the schematic in electrical/exports/Motherboard_schematic.pdf.
- The board gives one CAN bus per swerve module, Ethernet to the robot computer, 24 V to three XT30 outputs and a BNO085 IMU.
- Upstream reports it fabricated and bench-validated: flash, Ethernet and all three CAN buses.
6. Flash the firmware and bring up the buses
Two Teensy 4.1 boards, a Raspberry Pi Pico for the lift, and the hands' servo bus.
6.1 Flash the swerve base
The base Teensy runs the REV SPARK controllers at 1 Mbit/s.
- In firmware/swerve_drive, run pio run -e teensy41 -t upload.
- Run ./setup_can.sh to bring up can0 at 1 Mbit/s.
- Run scripts/verify_can_motors.py and confirm all six SPARK controllers answer: odd IDs drive, even IDs steer.
6.2 Flash the arms, torso and neck
One Teensy drives both arms, the torso and the neck from a configuration file on its SD card.
- Copy config/robot.json to the Teensy's SD card and set net.ip for your network.
- In firmware/openarm_dual, run pio run -e teensy41 -t upload; if the first upload fails, retry once, never after a success.
- Open the serial monitor at 115200 baud: it lists every actuator, live or not.
- Set motor IDs from a host with a DaMiao USB-CAN dongle using scripts/dm_configurator.py; IDs must be unique per bus.
- The neck's Dynamixel bus is 5 V logic and the Teensy pins are not 5 V tolerant, so use a level shifter.
6.3 Flash the lift controller
The lift runs MicroPython on a Raspberry Pi Pico.
- Run pip install mpremote, then firmware/lift/tools/deploy.sh.
- Run calibrate once so the lift finds its floor and ceiling; re-run home if the column was moved by hand while off.
6.4 Check the hands and the CAN buses
The hands need no flashing.
- Run firmware/orca_hand/feetech/scripts/scan.py and check servo IDs 1 to 17 on each hand.
- Run firmware/can_up.sh --ping to bring up SocketCAN and ping the DaMiao motors.
7. First tests and calibration
Test each subsystem safely, then calibrate.
7.1 Test the base safely
Upstream's first-drive rules for the swerve base.
- Lift the wheels off the ground for the first tests.
- Run scripts/set_drive_limits.py once to burn a drive output cap into flash before driving on the floor.
- Set STEER_OFFSET, DRIVE_SIGN, WHEEL_RADIUS and DRIVE_GEAR_RATIO at the top of swerve_teleop.py before the first real drive.
- Only one program may command the bus: stop the robot software before using these tools on the robot.
7.2 Calibrate the motors and hands
Encoder windows, joint directions and gravity compensation are stored in one calibration file.
- Install the calibration tools with pip install -r calibration/requirements.txt.
- Run calibration/motor_calibration/hardware/scan.sh to list the motors without energising them.
- Identify each motor's friction and inertia with run_hardware.sh, keeping clear of the shaft with a hand on the e-stop.
- Run each hand's end-stop sweep: python3 -m mabel_hw.drivers.orcahand.calibrate --model left, then right.
7.3 Bring up the whole robot
Build the ROS 2 workspace once, then start everything from one script.
- On the robot computer, run ros/dev_up.sh once to build the ROS 2 Jazzy workspace.
- From the repository root, run bash server/real_run.sh, and open the Control Center on port 8094 or connect the Vision Pro app.
- The arms come up limp; the operator enables torque explicitly. Know where your e-stop is before enabling torque.
- Support the arms before stopping the host: with no host packet for 250 ms, every arm motor is disabled.
- Every base movement passes a tip-over check that limits speed by lift height.