Assembly guide for ORCA Hand
Open-source tendon-driven robotic hands with tactile sensing from ETH Zurich
License
- orcahand_hardware (CAD, STL, 3MF files and its code): CC BY 4.0
- orca_core and orcahand_description: MIT
Licensed by repository. orcahand_hardware (CAD, STL, 3MF files and its source code) is CC BY 4.0, copyright ORCA Dexterity, Inc.: free to share and adapt, even commercially, with credit, and no patent or trademark rights are granted. orca_core and orcahand_description are MIT. Checked 2 Nov 2026.
Assembly guide
1. Which hand this guide builds, and what upstream publishes
Upstream publishes print files, CAD, a video tutorial and a short addendum for the current V2 hand, but no written step-by-step assembly manual.
1.1 Choose V2, not V1
Make sure you follow the V2 print files, motor IDs and configuration file, because upstream keeps V1 apart in its own folders.
- This guide builds the current ORCA hand, version 2 (V2): the base hand, right hand, with Dynamixel motors. The hardware repository README calls it the base hand and lists its print file as orca_v2/base/Prints-1100.3mf.
- The same README describes the older design as V1: legacy, self-contained, in a separate folder called orca_v1. Do not mix V1 and V2 print files, motor IDs or configuration files.
- The orca_core software keeps a separate configuration for each: orca_core/models/v1/orcahand-right/config.yaml for V1 and orca_core/models/v2/orcahand-right/config.yaml for V2. The orca_core README uses the V2 file in its examples.
- The addendum calls two releases of the V2 print files V1000 and V1100. These are not the old V1 design.
- Other V2 variants exist in the repository: the touch hand (touch sensors in the fingertips, Prints-2100.3mf), lite and joint-sensing. This guide does not cover them.
- A V1 hand is covered separately in the last section of this guide.
1.2 What upstream publishes for assembly
Upstream publishes a tutorial video and an addendum of changes, so this guide gives only what those and the orca_core documentation state.
- Upstream publishes no written step-by-step assembly manual for the V2 hand.
- Its route is the V2 assembly tutorial video from ORCA Dexterity on YouTube (5,526 seconds long, published 27 June 2026), the file ASSEMBLY_ADDENDUM.md in orca_v2/base, and the orca_core documentation.
- The video description says it shows how to build the ORCA Hand v2 (Dynamixel) with the full parts kit. This guide does not reproduce the video. Follow the video for the order of mechanical assembly.
- The addendum says some new information is missing from the video. Each correction it lists is given in section 4, with the video timestamp it gives.
- The hardware repository has no bill of materials for the hand itself. Its only bill of materials is for the motor connector board (section 3). Motor models are named in the orca_core software and on the orcahand.com product page.
2. Print the parts
Print from the hardware repository's Bambu Lab Studio project files, not from the simulation meshes.
2.1 Get the print files
Download Prints-1100.3mf for the base hand from the orcahand_hardware repository.
- Download orca_v2/base/Prints-1100.3mf from the orcahand_hardware repository. It is a Bambu Lab Studio project with pre-arranged plates and print settings.
- The ORCA Hand supports both Feetech and Dynamixel servos. Print plate 1 (DYNAMIXEL) or plate 2 (FEETECH) for the tower, depending on your actuators. Every other plate is the same for both.
- The print file also includes the skin parts as direct TPU prints, the finger skins and the carpal skin, on their own (TPU) plates. Printing the skins in TPU is the quickest way to get a complete hand.
- Each part is also given as an STL in the folders 01_Fingers, 02_Carpals, 03_Wrist, 04_ForeArm and 05_Spools under orca_v2/base, with STEP sources in the step_files folder of each.
2.2 Do not print from the description repository
The STL files in orcahand_description are reduced simulation meshes, not print files.
- The orcahand_description repository holds description files for simulation (URDF and MJCF). Its README says the meshes are reduced: visual meshes of 500 faces for most parts, 2'000 for the rest of the base and 15'000 for the main tower, camera and fans.
- Printable files are in the orcahand_hardware repository, which describes itself as CAD and print files for the ORCA robotic hand.
2.3 Print or cast the skins
Choose silicone skins cast in printed moulds, or TPU skins printed directly from the hand print file.
- Upstream recommends silicone skins, because they grip better and last longer than TPU. The TPU-printed skins from the hand print file work if you want something quick and dirty.
- For silicone, print the moulds from orca_v2/base/SiliconeMolds-1100.3mf, then cast the skins. The file contains the finger skin moulds with their clips, the carpal moulds and the funnels for pouring.
- One plate, named WITH TPU (~85A), prints the flexible carpal mould halves in soft TPU. Everything else in the mould file is PLA.
- If you prefer compression moulding to pouring, orca_v2/base/07_Molds/Compression-Molds.3mf contains the compression moulds for the finger and carpal skins.
- It is still unverified whether the TPU-printed carpal skin fits into the carpals as tightly as the silicone one. If it is loose, glue it in.
2.4 Parts given as CNC drawings
Upstream supplies the robot-arm connector and a spool holder as STEP files with technical drawings.
- The folder orca_v2/base/06_CNC holds FrankaConnector.step with FrankaConnector_TechnicalDrawing.pdf, and SpoolHolder_CNC.step with SpoolHolder_CNC_Drawing.pdf.
- The orcahand.com product page says the hand bolts onto any ISO 9409-1-50-4-M6 tool flange through a CNC-machined aluminium connector plate.
- The folder 04_ForeArm also holds a printable SpoolHolder.stl. The orcahand.com changelog says spool holders and tensioners are metal in v2.1 and were printed in v2.0.
3. Motors, IDs and wiring (V2, Dynamixel)
Motor models, IDs and communication settings in this section are for the V2 right hand; the V1 values are kept apart in the last section.
3.1 Motor models
The V2 hand uses sixteen Dynamixel XC330-T288-T finger motors and one Dynamixel XC430-T240BB-T wrist motor.
- Finger motors: 16 of Dynamixel XC330-T288-T. Wrist motor: 1 of Dynamixel XC430-T240BB-T. These are the names orca_core gives to Dynamixel model numbers 1220 and 1080.
- The orcahand.com product page names the same models as XC330-T288 (fingers) and XC430-T240BB (wrist), manufacturer ROBOTIS.
- The XC430-T240BB-T has no Goal Current register. When it connects, orca_core writes operating mode 4 (multi-turn position) to the wrist motor and the configured control mode, current_based_position (mode 5), to the finger motors.
- This section covers the Dynamixel build. The Feetech build is described in the last step of this section.
3.2 Install the control software
Install orca_core with uv from a clone of its repository.
- Install uv. Clone the orca_core repository: git clone [email protected]:orcahand/orca_core.git
- In the cloned folder run: uv sync --group dev
- This creates a local .venv and installs the package plus development dependencies. Run commands through uv, as in the later steps of this guide.
- End users who do not use uv can install the package with: pip install .
- orca_core requires Python 3.10 or newer.
3.3 Connect one motor at a time and give it an ID
Give every motor a unique ID, with Dynamixel Wizard 2.0 or with the configure_motor_chain.py script, before the motors go into the tower.
- Connect the U2D2 to your PC using USB. Use a 3-pin cable to connect the U2D2 to the Power Hub Board (PHB). Power the PHB with a 12V adapter. Connect one motor at a time to the PHB. Switch on power (red LED should light up).
- Dynamixel Wizard route: in the Wizard 2.0 go to Options and set Protocol 2.0, Baudrate 57600 and 3Mbps, ID Range 0-17. Click Scan. Your motor should appear. In the table select the ID row (Address 7), assign a unique ID and label it physically on the motor.
- Script route: from the orca_core folder run: uv run python scripts/configure_motor_chain.py CONFIG, where CONFIG is the path to your config.yaml. Plug the motors in one at a time when prompted. Re-running resumes from wherever the previous run stopped. The script assigns each motor its ID and baud rate and, for Dynamixel motors, also sets the Return Delay Time.
- The script configures the motors from the highest ID down, which is the order they are daisy-chained from the board. It takes the wrist motor ID from joint_to_motor_map in the config.
- Baud rate: the script uses 1,000,000 bps for Dynamixel unless you pin baudrate in config.yaml. The orca_core README gives 1M for V2 and 3M for V1. The Wizard page of the orca_core documentation still says 3Mbps. On connect, orca_core tries 1,000,000 and then 3,000,000 bps for Dynamixel motors.
- Use the IDs in the next step, not the V1 IDs.
3.4 V2 right-hand motor IDs
Use exactly these IDs for the V2 right hand: the number is the motor ID and a minus sign only records the turning direction.
- These are the joint_to_motor_map values in orca_core/models/v2/orcahand-right/config.yaml.
- Thumb: thumb_cmc: 17, thumb_abd: 14, thumb_mcp: 15, thumb_dip: 16.
- Index: index_abd: 4, index_mcp: 3, index_pip: 2.
- Middle: middle_abd: 5, middle_mcp: 10, middle_pip: 9.
- Ring: ring_abd: 6, ring_mcp: -7, ring_pip: 8.
- Pinky: pinky_abd: -13, pinky_mcp: 12, pinky_pip: -11.
- Wrist: wrist: -1. The wrist motor is the XC430-T240BB-T. Every other motor is an XC330-T288-T.
- Sign rule from the orca_core configuration guide: the number is the motor ID. If flexion moves the servo counter-clockwise, no sign is included. If flexion moves the servo clockwise, a negative sign is included.
- These are not the V1 IDs. In V2 the wrist is ID 1 and ID 17 is thumb_cmc. A hand wired to V1 IDs and driven with the V2 configuration would move the wrong joints.
- The left hand has its own map in orca_core/models/v2/orcahand-left/config.yaml, for example wrist: -1, thumb_cmc: -10, thumb_abd: -13. Use that file for a left hand.
3.5 Check the motor chain
After every motor has its ID, connect them in a daisy chain and confirm that all of them are found.
- Connect all motors in a daisy chain.
- Scan in the Dynamixel Wizard and ensure all motors are detected correctly.
- With the script, the --scan flag shows what is on the bus at any ID and baud rate.
3.6 Power and motor connector boards
The Power Hub Board takes a 12V adapter, and upstream publishes Gerber files and a bill of materials for the motor connector board.
- Power the Power Hub Board (PHB) with a 12V adapter.
- The folder orca_v2/electronics holds ORCA_Motor_Connectors_Gerber and ORCA_Motor_Connectors_BOM.xls, with a How-to-order-PCB.txt that refers to the EasyEDA PCB ordering page.
- The bill of materials has one row. Comment: PM254V-11-03-H85. Designator: H1,H2. Footprint: HDR-TH_3P-P2.54-V-F. Its last column, JLCPCB Part #, reads C541850.
- The video description for the Feetech build says that build has no PCBs between the motors, unlike the Dynamixel build.
3.7 If you build the Feetech version
The Feetech build follows the same assembly order but differs in motor cabling and configuration, and reversed polarity destroys a motor.
- From the video description: the assembly order is exactly the same as shown in the video. Only the motor cabling and configuration (from ~48:00) differ.
- Do not use any Dynamixel tools. Use the configure_motor_chain.py script from orca_core with the flag --motor-type Feetech.
- Cabling: no PCBs between the motors. A short cable connects neighbouring motors directly. The long cable connects the motors on the bottom. The thin-thick cable connects the first finger motor to the board and the last finger motor to the wrist motor.
- Video description, for each motor in the same order as the video: 1. Unplug the USB-C cable from your computer. 2. Connect the new motor. Be very careful about polarity (which way the cable plugs in). Reversed polarity will burn and break the motor. 3. Plug the USB-C back in and wait for the click.
- Feetech guide, for each motor: 1. Turn OFF the board (by toggling the power switch). 2. Connect the new motor. Plugging it in the wrong direction will permanently damage the motor. 3. Turn ON the board again and then configure the motor.
- Polarity check: the connector should go in easily. If it does not, it is likely reversed. Do not force it. Align the small hole inside the Feetech motor with the male connector and make sure it is completely locked inside.
- Never hot plug or unplug motors from the board while it is turned on.
4. Assembly: follow the video, with upstream's corrections
The order of mechanical work is in the tutorial video; these are the changes and tips that upstream's addendum lists, with the video timestamps it gives.
4.1 Start from the tutorial video
Follow the V2 assembly tutorial video for the order of work, and apply the corrections below where they fall.
- Open the V2 assembly tutorial video from ORCA Dexterity. The timestamps below refer to that video.
- Motor cabling and configuration start at about 48:00 in the video.
4.2 Fit PTFE tubes in the AP of each finger (video 7:50)
Each AP takes two short PTFE tubes, one in each hole of its wide hole pair.
- Each AP needs two PTFE tubes: one into each hole of the wide hole pair (highlighted in red in the addendum photograph).
- Trim them so that they extend ~1 mm out on both sides. 8-10 mm of PTFE tube is about the right length.
- Upstream says PTFE tubes are added in some positions to reduce friction and wear. The orcahand.com changelog says that in v2.1 every tendon only touches metal and smooth PTFE, never PLA, and that v2.0 ran without PTFE.
4.3 Fit the new thumb AP: one slit and two 2×30 pins (video 21:04)
The new thumb AP has one long slit instead of six holes, and takes two 2×30 pins and the 4×8×3 bearings.
- The video shows an outdated part. The new version of the thumb AP doesn't have 6 individual holes but one long slit.
- First route all tendons through the slit, maintaining the same order as presented in the video to prevent tendons crossing.
- Then insert two 2×30 pins in their respective slots (highlighted in red in the addendum photograph).
- Finally add the 4×8×3 bearings as shown in the video.
4.4 Fit PTFE tubes in the carpals (video 25:05)
The carpals take a PTFE tube in each of their 32 channels.
- Insert a PTFE tube into each of the 32 channels of the carpals.
- Trim them so that they extend ~1 mm out on both sides.
4.5 Add the wrist pins, carpals gear and bearings (video 31:59)
Two 3×50 pins, the printed carpals gear and 8×13×4 bearings are added at the wrist joint; this step is missing from the video.
- Upstream states: this step is missing from the video.
- After routing all tendons through the carpals and assembling all 5 fingers to the carpals, add two 3×50 pins at the wrist joint (3×45 also work, but barely).
- Then mount the 3D printed gear for the carpals (highlighted in green in the addendum photograph), and mount two 8×13×4 bearings (highlighted in red), one on each end of the carpals' shaft. Upstream's sentence reads 'two … on each end'; its photograph and its caption show two bearings in all, one at each end.
- The hardware repository has gear-tooth parts named CarpalsTeeth.stl (in 02_Carpals) and WristTeeth.stl (in 03_Wrist).
- The orcahand.com product page describes the V2 wrist as belt-driven.
4.6 Fit PTFE over the tower M4 screws and in the tower channels (video 39:50 and 40:50)
A PTFE tube covers the M4 screws of the tower and a PTFE tube goes in each of the 32 tower channels.
- A PTFE tube is used to cover the M4 screws of the tower (video 39:50). If it is difficult to squeeze on, hold the tube tightly pressed on the screw with one hand and use a screwdriver to screw it into the PTFE tube.
- Insert a PTFE tube in each of the 32 channels of the tower (video 40:50).
- Trim them so that they extend ~1 mm out on both sides.
4.7 Check which spools you printed (video 53:30)
V1100 spools have 4 screw holes and V1000 spools have 5, and their dimensions differ slightly.
- The spools of the V1100 have slightly different dimensions from the V1000.
- You can easily tell them apart: the V1100 spools have 4 holes for the screws instead of 5.
4.8 Tip: a PTFE tube that will not go in
A knotted tendon pulls a PTFE tube into a tight or winding channel from the far end.
- It can be challenging to insert tubes into some particularly tight holes or long, winding channels. Instead of pushing the tube in, pull it in.
- Step A: prepare a tendon with a knot on one end and thread it through the PTFE tube.
- Step B: thread the tendon through the channel.
- Step C: use the tendon to pull the PTFE tube into the channel from the other end.
5. Check the configuration, tension and calibrate (V2)
Run the orca_core scripts with the V2 right-hand configuration, tension the tendons with the ratchet, and repeat until no slack appears.
5.1 Check the configuration file
Review orca_core/models/v2/orcahand-right/config.yaml and make sure it matches your hardware.
- Review orca_core/models/v2/orcahand-right/config.yaml and make sure it matches your hardware setup. Replace the path with your specific hand model folder if needed.
- Change type to right or left depending on the hand assembly.
- max_current: default uses the motor family's own limit: 300 mA on Dynamixel hands, 900 mA on Feetech hands. Put a number there to pin a different limit. control_mode should generally stay at current_based_position.
- port: auto, and the motor type and baud rate, are auto-detected on every connect. You can pin them in config.yaml with port, baudrate and motor_type.
- hardware_version: auto takes the version the board reports (2 or 21). A hand on a plain adapter has no board to ask: pin it with hardware_version: 21 for the v2.1 build. The orcahand.com product page names the 1100 base hand orcahand v2.1 base.
- Be careful when editing this file. Incorrect settings can cause unexpected behaviour and make debugging more difficult.
5.2 Tension the tendons with the ratchet
Run tension.py to hold the servos, then turn the top spool of each servo clockwise with the printed ratchet.
- Tendons should be firm (not slack), but not overtightened. A small amount of give is acceptable.
- Run: uv run python scripts/tension.py orca_core/models/v2/orcahand-right/config.yaml
- By default the script first winds the tendons taut, then locks the servos in place and secures the bottom spools. Pass --no-move-motors to skip the winding motion and only hold the current position (for example after moving the servos by hand). The script runs until interrupted with Ctrl+C.
- Using the included 3D-printed ratchet (found in the spools print file or included in the kit), rotate the top spool of each servo clockwise to tighten the tendons.
- As you turn, you should hear or feel a clicking sound. This confirms the ratchet is engaged and the tendon is being tensioned.
- Careful: it is easy to overtension the tendons when using the ratchet. Overtensioning can interfere with performance. Tighten only until the tendon feels firm.
5.3 First calibration, then repeat with tensioning
Calibrate all joints, tension again, and repeat until calibration leaves no additional slack.
- When the hand is first assembled, the tendons are spooled by hand and significant slack is introduced. This must be corrected before using the hand for other tasks.
- Run calibration for all joints: uv run python scripts/calibrate.py orca_core/models/v2/orcahand-right/config.yaml
- Significant slack will accumulate during this step. This is expected, and calibration may seem ineffective at first.
- Tension the hand as in the previous step.
- Repeat calibration and tensioning 1-2 more times, or until no additional slack appears after calibration completes.
- The calibration sequence is defined step by step in config.yaml (16 steps in the V2 right-hand file). Be careful when modifying calibration steps: some are intended to run independently and may not function correctly if grouped or reordered.
- Calibration current: calibration_current: default uses 300 mA on Dynamixel hands. On v2.1 hardware the packaged models calibrate a Dynamixel hand's abductions at 300 mA and its MCPs and PIPs at 500 mA.
5.4 Move the hand to the neutral position
Run neutral.py with the V2 right-hand configuration.
- Run: uv run python scripts/neutral.py orca_core/models/v2/orcahand-right/config.yaml
5.5 Joint limits set for the V2 right hand
These are the joint_roms values, in degrees, that orca_core uses for the V2 right hand.
- wrist: -65 to 35. thumb_cmc: -45 to 33. thumb_abd: -18 to 55. thumb_mcp: -25 to 100. thumb_dip: -15 to 107.
- index_abd: -25 to 30. index_mcp: -25 to 100. index_pip: -15 to 107.
- middle_abd: -27 to 27. middle_mcp: -25 to 100. middle_pip: -15 to 107.
- ring_abd: -27 to 27. ring_mcp: -25 to 100. ring_pip: -15 to 107.
- pinky_abd: -30 to 30. pinky_mcp: -25 to 100. pinky_pip: -15 to 107.
6. If you hold a V1 hand (older design): V1 only, do not mix with V2
Everything in this section is true of the older V1 hand only; do not use these files, IDs or settings with a V2 hand.
6.1 V1 files
The V1 print files and CAD are kept in the orca_v1 folder of the hardware repository.
- The README describes orca_v1 as the V1 design, self-contained and legacy.
- orca_v1/Print_Files_Bambu holds ORCA_CarpalsWrist-Left.3mf, ORCA_CarpalsWrist-Right.3mf, ORCA_Fingers-Left.3mf, ORCA_Fingers-Right.3mf, ORCA_Letters.3mf, ORCA_Molds-Left.3mf, ORCA_Molds-Right.3mf, ORCA_Spools.3mf and ORCA_Tower.3mf.
- STL sources are in ORCA_Fingers, ORCA_Tower, ORCA_Spools, ORCA_Molds and ORCA_Misc. The full assembly is ORCA_Assembly/ORCA_v1.step.
- The V1 tower folder holds both gear-tooth parts (27TeethWristServo.stl and 42TeethCarpals.stl) and WristPulleyBase.stl.
6.2 V1 motor IDs and settings
The V1 right-hand configuration uses a different ID map, a 28-step calibration and different currents from V2.
- V1 right hand, joint_to_motor_map in orca_core/models/v1/orcahand-right/config.yaml: thumb_mcp: -4, thumb_abd: -3, thumb_pip: -1, thumb_dip: -2, index_abd: 14, index_mcp: -15, index_pip: -16, middle_abd: 13, middle_mcp: -8, middle_pip: -9, ring_abd: -5, ring_mcp: -7, ring_pip: -6, pinky_abd: 12, pinky_mcp: -10, pinky_pip: -11, wrist: -17.
- In V1 the wrist motor is ID 17.
- V1 settings in the same file: max_current: 400, calibration_current: 350, calibration_step_size: 0.1, calibration_threshold: 0.01, and a calibration_sequence of 28 steps (steps 1 to 8 thumb, 9 and 10 abductions, 11 to 26 finger MCP and PIP, 27 and 28 wrist).
- V1 joint_roms in the same file: thumb_mcp [-50, 50], thumb_abd [-20, 42], thumb_pip [-12, 108], thumb_dip [-20, 112], index_abd [-37, 37], index_mcp [-20, 95], index_pip [-20, 108], middle_abd [-37, 37], middle_mcp [-20, 91], middle_pip [-20, 107], ring_abd [-37, 37], ring_mcp [-20, 91], ring_pip [-20, 107], pinky_abd [-37, 37], pinky_mcp [-20, 98], pinky_pip [-20, 108], wrist [-50, 30].
- Baud rate for V1: the orca_core README comment says 3M for V1.
6.3 V1 wrist, tendons and fingertip sensors (paper)
The V1 paper describes a GT2 timing belt at the wrist, braided nylon tendons and RP-C7.6-ST force sensing resistors read by an Arduino Nano Every.
- Tendons: two fishing lines per joint (Nylon fibers braided into a 0.4 mm diameter rope), one for flexion and one for extension. Tendons are deflected around smooth metal pins and rods, and Teflon tubes are used for nonlinear routing, for example from the bottom of the thumb to the wrist.
- Wrist: a belt drive, using a standard GT2 timing belt with fiberglass reinforcement. The paper gives 60 degrees in flexion and extension.
- Fingertip sensing: force sensing resistors (RP-C7.6-ST Thin-Film Pressure Sensor) mounted onto a solid FDM-printed PLA backplate and covered by silicone-molded skin, giving binary tactile feedback on all five fingertips.
- Each sensor forms a voltage divider with a 10kΩ resistor. The three nodes are connected to a 5V input, an analog input and ground, all provided by a small microcontroller (Arduino Nano Every). Thin copper wires (∅ 0.2mm) are routed through the internal finger and palm structure through PTFE tubing.
- Wear reported in the paper: the silicone skin degraded in 2 fingertips after approx. 2,000 to 4,000 grasp cycles, and the thin copper wires snapped in 3 fingertips after approx. 4,500 to 7,000 grasp cycles.
- The paper names no sensor firmware.