Bimanual Robot Teleoperation Hardware Setup Guide

Why Bimanual Teleoperation Is Fundamentally Harder

Single-arm teleoperation is already cognitively demanding. Bimanual adds three compounding challenges that require dedicated hardware to manage:

Coordination: Human operators naturally coordinate their arms through proprioception — knowing where both hands are in 3D space without looking. Replicating this via VR controllers or screen-based interfaces degrades coordination quality significantly compared to physical leader arms with matching kinematics.

Temporal synchronization: Both arms must act in coordinated timing (reach together, release simultaneously, match approach velocities). Unsynchronized demonstrations train policies that fail at the coordination points. Hardware synchronization via shared timestamps or triggered cameras is not optional.

Single operator vs. two operators: Some approaches require two separate operators (one per arm). This doubles operator cost, introduces inter-operator timing variation, and requires careful coordination protocols. Single-operator bimanual systems (ALOHA, dual VR) are more expensive but produce higher-quality data.

Before building bimanual infrastructure, confirm your task genuinely requires two arms. Many apparent bimanual tasks (pouring from a pitcher, opening a screw cap) can be decomposed into sequential single-arm steps that train successfully with a single arm.

Option A: ALOHA-Style Leader-Follower (Recommended for Data Quality)

The ALOHA (A Low-cost Open-source Hardware System for Bimanual Teleoperation) architecture pairs two lightweight leader arms (WidowX-250 S) with two full-size follower arms (ViperX-300 S2). The operator holds the leader arms directly, and joint positions are replicated to the followers in real time.

• Components: 2× WidowX-250 S leaders ($3,100 each), 2× ViperX-300 S2 followers ($4,800 each), leader mounting frame, custom wiring harness, computer with Ubuntu 22.04 + ROS2 Humble. Total: ~$18K for arms, ~$32K complete system.
• Why WidowX as leaders: Same Dynamixel servo family as the ViperX followers means transparent kinematic mapping. The lighter weight (0.53 kg) and shorter reach (250 mm) of the WidowX makes it comfortable for a seated operator to hold and move for 2-hour collection sessions.
• Gravity compensation: Leader arms must have gravity compensation enabled so the operator holds near-zero effective weight. Without it, operator fatigue causes data quality degradation after 30–45 minutes. Configure Dynamixel current limits to 30–50% of rated torque for gravity compensation mode.
• Latency requirement: Leader-to-follower latency must be <10 ms to feel transparent to the operator. ALOHA achieves 3–5 ms on a local USB Dynamixel bus. Do not route through a networked computer — use direct USB-to-Dynamixel connections on the leader computer.
• Data format output: 14-DOF joint position array (7 per arm at 50 Hz), 3-camera stack (wrist-left, wrist-right, overhead), and gripper aperture. Compatible with ACT, Diffusion Policy, and LeRobot natively.

Option B: Dual VR Controllers (Best for Single-Operator Flexibility)

A Meta Quest 3 with both controllers provides a low-cost ($500) single-operator bimanual interface. The operator maps their physical hand positions to arm end-effector Cartesian positions via inverse kinematics running on the workstation.

• Setup: Meta Quest 3 ($500) + AnyTeleop or custom IK server + wrist-mounted trackers (optional, $200 each). Total hardware cost: $500–$900, plus the robot arms.
• Wrist extension trackers: Quest 3 controllers track the grip/trigger position. For tasks requiring forearm orientation, attach a secondary tracker (VIVE Tracker 3.0, $130 each) to the operator's wrists above the controller grip for more accurate 6-DOF wrist pose tracking.
• Latency management: Quest 3 to computer WiFi: 5–15 ms. IK computation: 3–10 ms. Command to arm: 5–15 ms. Total: 13–40 ms. Adequate for most manipulation tasks. For high-precision tasks (<5 ms latency required), use leader arms instead.
• Limitations vs. leader arms: No proprioceptive feedback means operators cannot feel arm resistance or near-singularity states. Coordinate precision in 3D space is lower without physical reference. Data quality for precision tasks (inserting, threading) is measurably lower than leader arms. Suitable for sorting, placing, cleaning, and transport tasks.
• Bimanual coordination: The major advantage of dual VR is that the operator uses their natural bimanual coordination — the same neural control they use daily. For gross-manipulation bimanual tasks (folding garments, packing boxes), VR coordination quality is adequate and collection throughput is higher than leader-follower.

Option C: Dual Exoskeleton Gloves (Best for Dexterous Bimanual)

For tasks requiring finger-level bimanual coordination (knotting, assembly with two dexterous hands, garment manipulation), a pair of haptic gloves drives two dexterous robot hands simultaneously.

• Hardware: SenseGlove Nova 2 pair ($8,000), or HaptX G1 pair ($20,000) for highest fidelity. Paired with Inspire RH56 dexterous hands ($8,000 each) or Shadow Dexterous Hands ($220,000 pair). Most labs use Inspire RH56 for cost reasons.
• Total system cost: SenseGlove + Inspire pair + dual arm setup: ~$35K. HaptX + Shadow + dual arm: $280K+.
• Synchronization: Both gloves publish to a shared ROS2 topic at 100 Hz. Synchronize with hardware timestamp from a shared NTP clock or PTP (IEEE 1588) for <1 ms inter-glove timing.
• Operator fatigue: Exoskeleton gloves are physically demanding. Most operators experience quality degradation after 45–60 minutes continuous use. Plan collection sessions with 10-minute breaks every 45 minutes. Total daily session limit: 4–5 hours.

Synchronization Implementation (<5 ms Tolerance)

Unsynchronized bimanual data is worse than useless — it trains policies with physically impossible coordinations. Here is the implementation checklist:

• Hardware camera trigger: Use a hardware trigger signal (GPIO pulse from workstation) to simultaneously trigger all cameras. Multi-Camera Frame Sync module for RealSense cameras: $50. Synchronization error: <100 μs.
• ROS2 timestamps: Use ros2_common_interfaces/sensor_msgs with header.stamp set from the system clock at capture time, not arrival time. Configure all nodes to use a single time source (system clock via chrony).
• Leader-follower sync: Sample both leader arm joint states and both follower states on the same callback timer (50 Hz). Do not interleave left/right reads — read both buses in the same callback.
• Verification: Log a synchronization test: command both arms to move simultaneously, verify that the joint state timestamps for left and right arms differ by <5 ms. Use rosbag2 and plot /left_arm/joint_states.header.stamp vs /right_arm/joint_states.header.stamp.

Workspace Design for Bimanual Tasks

• Table height: 75–85 cm (standard desk height). Arm bases should sit at the same height. Mount both bases on the same table surface for consistent reference frame.
• Arm separation: 50–70 cm between arm base centers. Closer separation causes arm-to-arm collision risk; wider separation reduces the bimanual workspace overlap.
• Object workspace: Bimanual tasks require objects centered between the two arms, 30–50 cm from each base, within 15–30 cm of table height. Design your task fixture and camera positioning around this zone.
• Overhead camera: Position 150 cm above table, centered between both arms, angled 45° from vertical. This provides a full bimanual view for both operator monitoring and policy observation.
• Side camera: Position at table height on the far side of the workspace (opposite operator). This captures bimanual grasps, object handoffs, and approach paths often occluded from the overhead view.

Data Format for Bimanual Episodes

Standard bimanual data format following ACT/ALOHA conventions, compatible with LeRobot and Diffusion Policy:

• /observations/qpos: Float array [14] — 6 joints per arm + 1 gripper aperture per arm, at 50 Hz.
• /observations/qvel: Float array [14] — joint velocities, same structure as qpos.
• /observations/images/cam_high: RGB [480×640×3] — overhead fixed camera at 30 fps.
• /observations/images/cam_left_wrist: RGB [480×640×3] — left wrist camera at 30 fps.
• /observations/images/cam_right_wrist: RGB [480×640×3] — right wrist camera at 30 fps.
• /action: Float array [14] — target joint positions from leader arms (same structure as qpos).
• Store as HDF5 with episode-level chunking. Use lerobot.scripts.convert_dataset to export to LeRobot Parquet format for Hugging Face upload.

Complete BOM: ALOHA-Style Bimanual System

For an SVRC-equivalent system using OpenArm 101 as followers ($4,500 each, 6-DOF, 500 g payload, ROS2 native), the total drops to approximately $18,000 with the advantage of open-source firmware and integrated ROS2 driver.

Assembly and Mechanical Alignment Procedure

Mechanical alignment is the most overlooked step in bimanual setup. Misaligned arm bases cause systematic pose errors that no software calibration can fully correct.

• Step 1 -- Drill arm base mounting holes: Use a CNC-cut template or precision drill guide to ensure both follower base plates are parallel to within 0.5 mm over the 50-70 cm separation distance. Tighten bolts to 15 Nm torque specification.
• Step 2 -- Verify co-planarity: After mounting, place a precision straightedge across both arm flanges at their home positions. Gap should be <1 mm. If not, add shims under the off-plane base.
• Step 3 -- Leader arm mounting: Mount leaders on the operator-facing side at the same height as followers. Leader bases should be 40-50 cm apart (narrower than followers) to match natural arm spacing of a seated operator.
• Step 4 -- Wrist camera mounting: Attach D405 cameras to each follower wrist link using a 3D-printed rigid bracket. The camera should be angled 15 degrees toward the gripper centerline. Verify the camera does not contact any surface during the full range of motion by running a joint sweep test.
• Step 5 -- Cable routing: Route USB cables through cable management clips along the arm links. Allow slack at each joint -- too tight causes cable fatigue within 2000 cycles. Use USB 3.0 active extension cables (max 5 m) for wrist cameras.

Controller Calibration: Gravity Compensation and Joint Limits

Gravity compensation on leader arms is what makes bimanual teleoperation feasible for multi-hour sessions. Without it, operators fatigue within 30 minutes and data quality degrades sharply.

• Gravity compensation setup: Set each leader arm's Dynamixel servos to current-based position mode. Configure the current limit to 30-50% of rated torque. The firmware applies current proportional to the gravitational load at each joint angle, making the arm feel nearly weightless to the operator.
• Joint limit configuration: Set software joint limits 5 degrees inside the hardware limits on both leaders and followers. This prevents the leader from commanding poses that cause the follower to hit hard stops. Map leader joint range [min+5, max-5] to follower range [min+5, max-5] linearly.
• Workspace boundary test: Before first data collection, command the operator to sweep the full reachable workspace of both leaders simultaneously. Verify: (1) no collision between followers at any reachable leader pose, (2) no follower self-collision, (3) no cable pinch. Mark any problematic zones and add software exclusion constraints.
• Gripper force calibration: Set gripper closing force to 2-5 N for delicate objects, 8-15 N for rigid objects. Map the leader gripper trigger (analog input) to follower gripper aperture linearly. Test with target objects and verify the operator can reliably grasp and release.

ROS2 Topics for Bimanual Synchronization

The following ROS2 topic structure ensures synchronized bimanual recording. All topics must share the same clock source (system clock via chrony NTP):

• /left_leader/joint_states -- sensor_msgs/JointState at 50 Hz, 7 DOF (6 joints + gripper)
• /right_leader/joint_states -- sensor_msgs/JointState at 50 Hz, 7 DOF
• /left_follower/joint_states -- sensor_msgs/JointState at 50 Hz, 7 DOF
• /right_follower/joint_states -- sensor_msgs/JointState at 50 Hz, 7 DOF
• /cam_high/image_raw -- sensor_msgs/Image at 30 fps, 640x480 RGB
• /cam_left_wrist/image_raw -- sensor_msgs/Image at 30 fps, 640x480 RGB
• /cam_right_wrist/image_raw -- sensor_msgs/Image at 30 fps, 640x480 RGB
• /episode/status -- std_msgs/String: "recording", "idle", "paused"

Critical implementation detail: read all four joint state topics in a single timer callback at 50 Hz. Do not use separate subscribers with independent callbacks -- this introduces variable inter-read delays of 1-20 ms that create timing jitter in the recorded data.

Latency Measurement and Optimization

Measure end-to-end latency by commanding a step motion on the leader and recording the follower response with a high-speed camera (240 fps). Count frames between leader move and follower move. At 240 fps, each frame is ~4.2 ms.

Common Failure Modes and Troubleshooting

• Left-right synchronization loss: Symptoms: one arm lags by 20-50 ms. Cause: one USB bus is overloaded (e.g., wrist camera sharing the same USB controller). Fix: use separate USB controllers for cameras and arm buses -- check with lsusb -t and distribute across controllers.
• Follower joint limit hit during bimanual task: Symptoms: one follower hits a hard stop and triggers an error while the other continues. Cause: leader workspace exceeds follower reachable space in a bimanual configuration where the arms are closer together. Fix: reduce leader joint limits by an additional 10 degrees at J1 and J2.
• Arm-to-arm collision: Symptoms: physical collision between left and right follower arms during coordinated task. Cause: workspace overlap zone is too large for the commanded motion. Fix: add software collision zones using the arm's SDK collision avoidance, or train operators to avoid the center overlap zone for fast motions.
• Gripper desynchronization: Symptoms: one gripper opens while the other closes during a handoff task. Cause: leader gripper mapping is inverted for one arm. Fix: verify gripper command polarity for both leader arms -- both should use the same open/close convention.
• Camera image desynchronization: Symptoms: policy training shows misaligned actions between camera frames and joint states. Cause: camera frames arrive asynchronously on USB. Fix: implement hardware frame trigger using GPIO or use the RealSense hardware sync cable between all D405 cameras.

Related Guides

• How to Set Up a Teleoperation Lab -- full space, equipment, and network setup guide
• Glove-Based Dexterous Teleoperation -- for finger-level bimanual with haptic gloves
• Data Formats: HDF5, RLDS, and LeRobot -- converting bimanual episodes to standard formats
• Curriculum Design for Robot Learning -- structuring bimanual tasks from easy to hard
• Operator Recruitment and Training -- building a bimanual-capable operator team
• Teleoperation Solution Buyer's Guide -- build vs. buy decision framework

Work with SVRC

Silicon Valley Robotics Center operates bimanual data collection stations at both our Mountain View, CA and Allston, MA locations.

• Data Collection Services -- we collect bimanual demonstration data with trained operators, delivered in HDF5 or LeRobot format
• Robot Leasing -- lease a complete ALOHA-style bimanual system for your lab, starting from $2,500/month
• Hardware Store -- purchase OpenArm 101, DK1 bimanual kits, cameras, and accessories
• Data Platform -- upload, visualize, QA, and convert bimanual datasets online
• Contact Us -- schedule a bimanual task feasibility assessment with our engineering team