teleop-bridge

name	teleop-bridge
description	Wire a `geniesim_teleop` VR/Pico session into a running Genie Sim RT Engine scene — pick the right scene yaml, launch `wbc.launch.py` with `use_ros2_control:=false` so move_group serves `/compute_ik` while the teleop publisher owns `/joint_command`, and confirm no topic fighting. Trigger: When the user asks to "connect teleop to the sim", "桥接 teleop", "drive the engine with VR", "use teleop instead of ros2_control", "stop the controllers from fighting teleop", or has a teleop loop ready and a scene up but the robot jitters / flicks.
license	MPL-2.0
metadata	{"author":"genie-sim","version":"1.0"}
prerequisites	["geniesim_ros:launch-scene","geniesim_teleop:run-teleop"]
inputs	[{"name":"scene_gripper","desc":"Gripper variant of the running scene; the MoveIt `gripper:=` must match (e.g. `omnipicker` for `scene_pnp_g2_op`)","required":true}]
outputs	[{"desc":"Exactly one publisher on `/joint_command` (the teleop node); no topic fighting from the controller manager"}]

When to Use

• VR teleop loop (geniesim_teleop skill run-teleop) and an RT Engine scene (launch-scene skill) need to share /joint_command without the ros2_control hardware interface rebroadcasting it at the controller-manager update rate.
• User sees "the arm jitters / payloads get flung" — that's the classic two-publisher symptom.
• External motion script (e.g. wok_flip_cmds.py) and MoveIt are both interested in the same topic.

Do not use for:

• Starting the teleop loop itself → run-teleop skill in geniesim_teleop.
• MoveIt planning with the simulator's controllers driving → moveit-wbc skill (default mode).
• Recording the teleop session → record-episode skill.

Critical Patterns

1. use_ros2_control:=false is the bridge switch. With it, wbc.launch.py starts move_group only (/compute_ik, /compute_fk) and skips the ros2_control node + controller spawners. /joint_command then has exactly one source: teleop.
2. Match scene gripper to teleop config. run-teleop defaults to G2_omnipicker.json. Use scene_pnp_g2_op (or any scene_*_g2_op) so the engine is built with the same gripper the teleop loop expects. Mismatched grippers produce a robot MoveIt can plan against but the engine refuses to drive.
3. Three processes, three shells. Scene + MoveIt + teleop each run as a long-lived ROS node. Don't try to background them in one shell — the engine and teleop both want stdin / SIGINT semantics.
4. use_sim_time:=true is engine-side, but the teleop loop publishes wall-clock by default. The bridge uses sim time inside the scene; the publisher rate adapts. Don't override unless you know what you're doing.

Workflow

Step 1 — Confirm the prerequisites

• Scene is up via launch-scene skill (e.g. scene_pnp_g2_op × launcher_ovrtx_isaac_physx).
• Teleop config matches the scene's gripper.
• VR device reachable, default port 8080.