Step list you simulate can run on hardware. The robot controllers
expose three transports, each suited to a different setup.
DDS: run directly on the robot
Best when your code runs on the robot’s onboard computer. Lowest latency.SSH: upload and run a script
Best when your code runs on a laptop and you want to push a self-contained script to the robot and let it execute there.Bridge: host model, live control
Best when your VLA / policy runs on your host PC and needs real-time control of the physical robot. Starts a bridge on the robot and returns a live handle.G1 humanoid
The G1 controller mirrors the API (default IP192.168.123.164):
Choosing a transport
| Transport | Code runs on | Latency | Use when |
|---|---|---|---|
deploy() (DDS) | the robot | lowest | Onboard autonomy, no laptop in the loop. |
deploy_ssh() | laptop → robot | n/a (batch) | Ship a fixed routine and let the robot run it. |
deploy_ssh_bridge() | laptop (live) | network RTT | A model on your PC steers the robot in real time. |