Skip to content
Droid/Glove evidence record

MANUS Metagloves Pro Haptic

Separate vibration cues from finger resistance, and confirm the software entitlement before choosing the haptic variant for teleoperation.

Pro Haptic; distinct from base Pro

Does Pro Haptic provide the same kind of feedback as a force-feedback glove?

MANUS describes embedded vibrotactile actuators. That establishes vibration cues, not a measured ability to resist or pull the operator’s fingers. Choose the feedback mechanism your task needs before comparing haptic products.

MANUS ↗

What the sources establish

Manufacturer documentation is attributed below. These values are not independent measurements by Droid.

Model and interface facts, with the conditions needed to interpret them.
FieldReported valueConditions and evidence
Tracking approachElectromagnetic hand trackingManufacturer description; no independent tracking result reproduced.
MANUS ↗
Hand model25 degrees of freedomAnatomical model, not the number of independently actuated robot joints.
MANUS ↗
Feedback mechanismEmbedded vibrotactile actuatorsSDK customization is advertised; the exact haptic API release must be confirmed.
MANUS ↗
Operator changeoverDetachable Haptic Top ModulePairs with a personally sized Sensor Glove; price the complete operator kit.
MANUS ↗
Software entitlementRobotics edition lists SDK, ROS 2 and LinuxLicense availability is not proof that every SDK release supports this hardware variant.
MANUS ↗
Resistive finger feedbackNot established in reviewed sourcesVibration is documented; resistive or active finger force is not established here.
Evidence status: unknown
Exact ROS 2 configurationNot established in reviewed sourcesConfirm the Pro Haptic hardware revision, haptic API and ROS package together.
Evidence status: unknown

What this means for an integration

Droid’s analysis of the cited documentation:

  1. Specify the operator cue: a contact notification, sustained resistance, or an active pull. A vibration signal may communicate an event without recreating the load at the robot’s fingers.
  2. Validate both directions of the loop: glove pose to robot command, then robot contact to glove feedback. A motion-streaming demonstration establishes only the first direction.
  3. Keep software entitlement in the purchase comparison. MANUS lists annual and perpetual options; the perpetual overview includes one year of updates and support. Confirm the version you can keep running and the cost of ongoing updates.

Still to establish

  • Exact hardware / firmware / haptic API release pairing
  • Configured hardware and license quote
  • Feedback delay and operator cue recognition during the intended task
  • Resistive force capability, if required

Before a larger capture run

  1. Test whether operators reliably distinguish the selected vibration cues.
  2. Confirm haptic commands work with the quoted SDK and license.
  3. Measure cue timing alongside robot and camera timestamps.
  4. Evaluate fit and calibration after changing operators.

Source record

  1. Metagloves Pro Haptic product page ↗MANUS · Pro Haptic; undated product page · Checked 2026-11-10
  2. Core license types ↗MANUS · Robotics and Motion Capture editions; undated terms overview · Checked 2026-11-10

Make the next decision.

START WITH THE WORKFLOW

Bring us the task.
Let’s find the fit.

Share your environment, the job to be done, and the outcome you need to measure.

Request a project review