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
- Offline sim only: Run
Fr3DuoRobot(cfg, mode="sim")directly (default_robot_config()works with no hardware orconfig/robot_config.json; setMUJOCO_GL=eglorosmesaon headless Linux forrender_sim_cameras). - 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 preflightauto-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, andtcp_offset_z_m(0.145 mstock 2F-85 silicone pads vs0.185 mextended fingers). Defer the optionaltmuxprompt (R11) until live motion stages. Before live hardware actuation or downstream skill composition,config/robot_config.jsonmust satisfyvalidate_robot_config_complete(cfg) == [](arms.{left,right}.{ip,gripper_port}, all 3cameras.*entries, andgeometry_confirmed=True).
- Turn 1 (connection prerequisite -> run
- Hardware already verified (
R2, complete config): Skip bring-up motion checks; run your task withFr3DuoRobot(cfg, mode="hardware", dry_run=True)(orFr3DuoSafetyChecker), then wait for explicit"go"(R1) beforedry_run=False.