DEXTEROUS MANIPULATION

The world of dexterous hands.

Compare hardware. Discover applications. Share what works. An open reference and community for dexterous manipulation.

ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled

ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled is a dexterous robotic hand recorded in the Dexhands directory. Original sources and specifications are listed on this page. Record source date: 2026-09-16.

ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled · Company logo

Official organization identity · not a product photograph.

Specifications

Record source date: 2026-09-16

Active / total DOF: 17 / 17

Servo position/current telemetry; no tactile skin on base model

Weight basis: Not published for current production v2

Availability / status: Current / marketed

Evidence limits: 17DoF includes16 finger axes+1 wrist. Current v2 versus v1 prices/specifications must not be mixed.

Price scope: USD3,500 Feetech assembled hand; optional full spares kit+USD350

FROM A RECORD TO A RESULT

Start with ORCA Hand v2 — Feetech assembled

Identify the exact ORCA revision and inspect its named joint-to-motor map before connecting the hand.

Configuration audit first

The manufacturer publishes orca_core and versioned configurations. Dexhands reviewed these sources and checked the read-only snippet against the published config; no physical-hand test is claimed.

Sources reviewed 2026-10-23 · no hardware connection from this page
Before you start: versions and requirements

This record is the v2 Feetech assembled model. Confirm v2.0 versus v2.1, left/right side, motor family and board/firmware with your delivered unit. The evolving v2 folder covers more than one hardware revision.

  • The delivered unit’s exact identity and manufacturer commissioning instructions.
  • A pinned orca_core checkout and its documented Python environment; the reviewed package requires Python 3.10 or later.
  • The matching configuration plus unit-specific calibration records, kept separately from another hand’s files.
  1. Select the correct configuration

    Use the manufacturer’s core package and select the correct side under models/v2. Check hardware_version and motor-family behavior against your unit. The current example can auto-detect these at connection; that is not a reason to skip identifying your hand. Do not transfer ORCA Touch sensing claims or v1 calibration settings to this record.

    Manufacturer Python controller
  2. Inspect the mapping without opening a port

    From a reviewed checkout, in a Python environment with PyYAML, run this read-only example with hardware disconnected. It loads a config file only and does not import orca_core. Select the left-hand path instead for a left unit. Compare every printed name and signed motor mapping with the manufacturer’s configuration; do not infer the order from numeric motor IDs.

    from pathlib import Path
    import yaml
    
    path = Path("orca_core/models/v2/orcahand-right/config.yaml")
    config = yaml.safe_load(path.read_text())
    joints = config["joint_ids"]
    mapping = config["joint_to_motor_map"]
    assert len(joints) == len(set(joints)), "Duplicate joint names"
    assert set(joints) == set(mapping), "Incomplete joint map"
    print("Side:", config["type"])
    print("Hardware:", config.get("hardware_version", "not specified"))
    print("Motor family:", config.get("motor_type", "auto-detected at connection"))
    for joint in joints:
        print(joint, mapping[joint])
    Reviewed v2 right-hand configuration
  3. Prepare a commissioning checklist

    Record the serial interface, supported power arrangement and exact configuration. Tensioning, calibration and neutral-position scripts can move the hand; they are a later manufacturer-guided step, not a harmless connection test. Keep each unit’s calibration associated with its serial identity and stop if the selected hardware revision is uncertain.

    Original commissioning sequence
  4. Define the first useful observation log

    Before planning a policy or data-collection task, document which state and sensor channels your exact configuration exposes, their units and timing. Separate motor telemetry from direct joint or tactile measurements. Save the action map alongside the log so another researcher can interpret it.

    Plan a first hand integration

What counts as a useful result?

  • The report identifies revision, side, motor family, firmware and code commit independently.
  • Every configured joint has a documented mapping; configuration inspection and hardware communication have separate statuses.
  • Unit-specific calibration and the available sensor channels are recorded before a physical experiment.
If something does not work
The configuration says auto
Confirm the delivered revision and motor family before connecting. If multiple hands are present, follow the manufacturer’s explicit device-selection instructions.
Serial permission denied
Check the operating system’s serial-device permissions and the manufacturer’s setup guide. Do not solve this by sharing a privileged configuration or another user’s credentials.
A demo uses a different joint order
Compare named joints and revision first. A replay file from v1 or another embodiment is not automatically suitable for v2.
Touch or joint sensing seems missing
Confirm your purchased configuration and supported channels. A software class for a sensor-equipped variant does not mean every ORCA unit contains those sensors.
Prepare an experiment report

Fill in observed results and failures. Keep credentials, serial numbers and confidential designs out of public reports.

Enable JavaScript to continue to the discussion editor, or copy this template manually.

A discussion is public when approved. Continuing opens an editor; it does not publish or contact a supplier. Sign in to edit the template here, or copy it without an account. Unsaved edits stay on this page until you copy them or open the editor.

Guide updates

· Added a revision-specific Python configuration audit, commissioning boundaries, sensor checks and troubleshooting.

This is a Dexhands editorial change, not a new manufacturer release or a completed reproduction.

INTERACTIVE 3D

Explore the hand. Right here.

Rotate, zoom and adjust individual model joints. Downloads begin when you choose Load 3D model. This is geometry, not a physical performance test.

Open larger view ↗ · 27 licensed models available

From model to your first experiment

Browser geometry is verified here. A hardware driver, physics simulation and task policy require separate setup and testing.

  1. Inspect one joint. Load the model, choose a finger joint, move its slider slightly, then Reset. Record the joint name, limits and which segment moved. A slider is a model coordinate, not necessarily a motor.
  2. Get the same source revision. Use the version-specific links below. Check the right/left hand, fingertip and sensor variant before using the geometry in your own project.
  3. Validate your integration. Check metres versus millimetres, radians versus degrees, joint order, limits and mimic/coupling rules. Start with visual inspection; add collisions, inertias, actuator settings and a supported controller before attempting simulation or hardware motion.
ORCA Hand v2 · MIT · 3.2 MB viewer download

Family/reference geometry; not every catalog variant is identical. Original publisher model, v2/models/urdf/orcahand_right.urdf. Check the hardware revision, side and sensor configuration before comparing.

Open original model file ↗ · Publisher repository & setup documentation ↗

Source revision: b9b349a21ee0238c62b6cf92ae7597027867adf8
Model path: v2/models/urdf/orcahand_right.urdf

git clone https://github.com/orcahand/orcahand_description.git orca-v2-source
cd orca-v2-source
git checkout --detach b9b349a21ee0238c62b6cf92ae7597027867adf8

This checks out source files only; it does not install a simulator or run a robot. Follow the publisher’s dependency and package setup instructions.

Find this hand’s software and project references → · Learn joint mapping and action interfaces →

Keep an experiment record: model version, source commit, tool/version, joint mapping, observed result and unresolved problems. Do not describe a geometry preview as a successful hardware test.

Software, projects & datasets

What is ready to build with?

01 · Published supportSource statement

Python orca_core; open CAD/BOM; manufacturer says no ROS2 integration

Product source ↗
02 · Developer references7 linked references

Check each link’s model scope, release, files and license. A reference is not a tested integration.

03 · Reproduced hereNot independently tested

No independent hardware performance or SDK integration test is recorded here. Browser model previews show geometry only.

Curated public references, checked 2026-10-25. Links describe a model or family relationship, not hardware-tested compatibility.

ORCA Core

ORCA Hand · Family resource

Control, calibration and tendon-tensioning tools for ORCA hands.

Choose the hardware configuration for Dynamixel or Feetech; self-build calibration matters.

ORCA hardware designs

ORCA Hand · Family resource

CAD and build resources for ORCA hand hardware.

Select the correct version and motor configuration before manufacturing parts.

ORCA descriptions

ORCA Hand · Family resource

URDF and simulation description assets for the ORCA family.

Check the model revision against the physical hand.

ORCA simulation

ORCA Hand · Family resource

MuJoCo environments and example manipulation tasks.

Select the intended hand version; simulated performance is not a hardware result.

ORCA teleoperation

ORCA Hand · Family resource

Hand tracking, retargeting and demonstration collection tools.

Requires a matching ORCA Core configuration and capture setup.

All Hands Up! — ORCA Hand v2 3D viewer

RLWRLD · Family resource

External browser viewer with joint controls, pose presets and simulated thumb-reach visualization.

The viewer does not establish equivalence between Dynamixel, Feetech and kit configurations. Simulation visualization is not a hardware test or device driver.

ORCA Hand v2 — original robot-description package

orcahand · Family resource

Original publisher geometry used in the Dexhands native 3D viewer. MIT; source revision b9b349a21ee0238c62b6cf92ae7597027867adf8.

Visual geometry and joint definitions only. Confirm exact hardware variant; browser rendering is not an SDK integration or physical performance test.

Learn to audit a model-to-hand interface →

Frequently asked questions

What is the ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled?

ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled is a dexterous robotic hand record in the Dexhands directory. Record source date: 2026-09-16.

What are the specifications of the ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled?

Active / total DOF: 17 / 17. Sensing: Servo position/current telemetry; no tactile skin on base model. Weight basis: Not published for current production v2. Availability / status: Current / marketed.

How much does the ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled cost?

Public price observations: USD3,500 Feetech assembled hand; optional full spares kit+USD350 Confirm current pricing with the manufacturer or a supplier.

Where can I buy or source the ORCA Dexterity ORCA Hand v2 / 1100 — Feetech assembled?

Check the original source links on this page, or use the Dexhands sourcing page to send one request to multiple suppliers.

Product sources

Original source

Original source

Suggest a correction

Start a discussion

Published posts are public. First contributions are reviewed. Only share material you have permission to disclose.

Report a post