fr3-duo-control

Installation
SKILL.md

Franka Research 3 Duo Control (fr3_duo)

Operate and program a dual-arm FR3 Duo (left/right 7-DOF FR3 arms, Robotiq 2F-85 grippers, overhead ZED Mini stereo camera, and wrist RealSense D405 RGB cameras) under R1–R16 in safety_rules.md and hardware_limits.md. For offline mode="sim", canonical MjSpec scenes, and live MuJoCo Studio workflows, see mujoco_sim.md.

1. Setup Gate

  1. Offline sim only: Run Fr3DuoRobot(cfg, mode="sim") directly (default_robot_config() works with no hardware or config/robot_config.json; set MUJOCO_GL=egl or osmesa on headless Linux for render_sim_cameras).
  2. Missing/incomplete config/robot_config.json, or bring-up/homing/diagnostics: Follow bringup_checklist.md via bringup.py (uv run scripts/bringup.py, e.g. --dry-run, --step geometry, --up-to all, --step home --yes; orchestrates discover_hardware.py, check_cameras.py, check_robot.py). Split operator prompts cleanly across two turns during Stage 1 rather than dumping all checks at once:
    • Turn 1 (connection prerequisite -> run --step preflight --read-only): Confirm only left/right FR3 FCI IPs (stating robot vs. operator left/right) and that joints are unlocked, FCI is enabled, and physical E-stop is within reach. Let --step preflight auto-check tilted Desk gravity/payload, USB/RS-485 ports, cameras, and conflicting processes before asking the operator to intervene.
    • Turn 2 (Stage 1b geometry -> run --step geometry): Show/attach fr3_duo_dimensions_reference.png inline to the operator and confirm the 6 measurements in meters (m): base_height_m, table_height_m -> z_table_m, table_front_offset_m, table_width_m, table_depth_m, and tcp_offset_z_m (0.145 m stock 2F-85 silicone pads vs 0.185 m extended fingers). Defer the optional tmux prompt (R11) until live motion stages. Before live hardware actuation or downstream skill composition, config/robot_config.json must satisfy validate_robot_config_complete(cfg) == [] (arms.{left,right}.{ip,gripper_port}, all 3 cameras.* entries, and geometry_confirmed=True).
  3. Hardware already verified (R2, complete config): Skip bring-up motion checks; run your task with Fr3DuoRobot(cfg, mode="hardware", dry_run=True) (or Fr3DuoSafetyChecker), then wait for explicit "go" (R1) before dry_run=False.

2. Canonical Contract, Coordinate Frames & Runtime Control API

Installs
15
GitHub Stars
161
First Seen
3 days ago