DEXTEROUS MANIPULATION

The world of dexterous hands.

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

OYMotion ROH-AP001

OYMotion ROH-AP001 is a dexterous robotic hand recorded in the Dexhands directory. Original sources and specifications are listed on this page. Record source date: 2026-09-02.

OYMotion ROH-AP001 · Company logo

Official organization identity · not a product photograph.

Specifications

Record source date: 2026-09-02

Active / total DOF: 6 / 11

Full piezoresistive dot-matrix tactile coverage across fingertips/palm, 0.1–25 N, 150 Hz, ±20% stated

Weight basis: 640 g

Availability / status: Current / marketed

Evidence limits: Only common 6-active/11-joint architecture and SDK/model documentation freshly checked unless extra verified fields listed. Legacy detailed specifications remain historical.

FROM A RECORD TO A RESULT

Start with OYMotion ROH-AP001

Inspect the correct ROH-AP001 hand model before connecting a physical driver.

Model inspection first

OYMotion publishes ROH-AP001 documentation and a Gen2 URDF visualization route. Dexhands reviewed these sources; we have not run the model or tested the hardware.

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

ROH-AP001, with the correct left/right model. The linked ROS1 model instructions use the Gen2 package; ROS1 and ROS2 are separate environments. Record the exact hardware, firmware and repository revision.

  • The manufacturer’s ROH-AP001 manual and model documentation.
  • A matching ROS environment and the package dependencies from its instructions.
  • A place to record model names, commanded axes and joint conventions.
  1. Choose the correct model package

    Start from the ROH-AP001 documentation, which links its ROS, Gen2 URDF and SDK resources. Do not interchange AP001 and AP002 packages or Gen1 and Gen2 protocol instructions merely because the products share a family name.

    Official ROH-AP001 documentation
  2. Open the left or right visualization

    After building and sourcing the documented ROS1 model workspace, use the separate display launch with physical hardware disconnected. This example selects the right hand; the documentation provides a left-hand launch too.

    roslaunch rohand_gen2_urdf_ros1 display_r.launch
    Gen2 visualization instructions
  3. Write an interface checklist

    Record the model joints and their coupling. For later hardware work, confirm the exact interface and protocol for the delivered unit, then follow its manufacturer commissioning instructions. A model rendering is not a communication test.

    Make a model-to-driver checklist

What counts as a useful result?

  • The intended left/right model opens with its meshes.
  • The model’s joint list is separated from independently commanded axes.
  • The report records software versions and explicitly states whether hardware communication was tested.
If something does not work
Wrong generation or handedness
Return to the AP001 product page and select its model and protocol links.
Model works, driver does not
Check physical interface, protocol, device configuration and permissions independently; visualization does not test them.
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 an AP001-specific model-first guide, original software links and interface checks.

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

Software, projects & datasets

What is ready to build with?

01 · Published supportSource statement

Manufacturer ROS / ROS 2 SDK

Product source ↗
02 · Developer references3 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-09-22. Links describe a model or family relationship, not hardware-tested compatibility.

ROHand ROS 2 integration

OYMotion · Family resource

Manufacturer ROS 2 packages linked from the ROHand firmware project.

Confirm the exact model, bus and firmware; sensor interfaces are not identical across variants.

ROHand ROS 2 descriptions

OYMotion · Family resource

Manufacturer description packages for visualizing and integrating ROHand.

Check the available model folders; a description does not establish working hardware control.

ROHand firmware and protocol

OYMotion · Family resource

Manufacturer firmware and communication documentation with links to ROS packages.

Match the model, protocol and firmware. AP, Lite and ROHand variants differ.

Learn to audit a model-to-hand interface →

Frequently asked questions

What is the OYMotion ROH-AP001?

OYMotion ROH-AP001 is a dexterous robotic hand record in the Dexhands directory. Record source date: 2026-09-02.

What are the specifications of the OYMotion ROH-AP001?

Active / total DOF: 6 / 11. Sensing: Full piezoresistive dot-matrix tactile coverage across fingertips/palm, 0.1–25 N, 150 Hz, ±20% stated. Weight basis: 640 g. Availability / status: Current / marketed.

How much does the OYMotion ROH-AP001 cost?

Public price observations are not established for this record. Use the original source or send a supplier inquiry for current pricing.

Where can I buy or source the OYMotion ROH-AP001?

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