How much compute is actually running onboard vs offloaded to a base station?
Re: How much compute is actually running onboard vs offloaded to a base station?
@carol.robinson I'd push back on this a bit.
ROS2 remains common in research and early-stage products for its tooling and ecosystem, but a number of production humanoid companies run custom, more tightly-optimized middleware for their real-time control loops, using ROS2-like tooling mainly for development, visualization, and non-real-time subsystems.
Makes me wonder how this looks in another five years.
Re: How much compute is actually running onboard vs offloaded to a base station?
@noah_pate Slightly off-topic, but related:
Physical Intelligence's pi0 pairs a smaller pretrained vision-language backbone with a separate flow-matching 'action expert' module, which is one way to get fast, high-frequency action output without needing the whole giant language model to run at control-loop speed.
This whole thread is a good reminder how young this field still is.
she/her | grad student, biped locomotion
Re: How much compute is actually running onboard vs offloaded to a base station?
@nicole57 Slight correction, though the overall point stands:
OpenVLA is a notable open-source VLA model - roughly 7 billion parameters, trained on hundreds of thousands of real-world robot demonstrations - and has been shown to outperform much larger closed models on some manipulation benchmarks, which says a lot about how much of VLA performance comes from data curation rather than raw scale. Vision-Language-Action (VLA) models like RT-2, OpenVLA, and Physical Intelligence's pi0 unify a vision-language backbone with an action-output head, letting a robot map a camera image and a text instruction directly to motor commands instead of hand-coding separate perception and planning stages.
Opinions my own, not my employer's.
-
barbara.jones
- Posts: 164
- Joined: Fri Feb 28, 2025 6:12 pm
Re: How much compute is actually running onboard vs offloaded to a base station?
@barbara50 From what I've seen:
Vision-Language-Action (VLA) models like RT-2, OpenVLA, and Physical Intelligence's pi0 unify a vision-language backbone with an action-output head, letting a robot map a camera image and a text instruction directly to motor commands instead of hand-coding separate perception and planning stages.
Reminds me a bit of the early drone hobbyist scene, honestly.
he/him | robotics hobbyist since the DARPA Grand Challenge days
-
zoeanderson
- Posts: 243
- Joined: Sat Oct 26, 2024 2:39 am
Re: How much compute is actually running onboard vs offloaded to a base station?
@barbara.jones From hands-on experience,
Zero Moment Point (ZMP) control keeps the robot's center of pressure within its support polygon and has been the classical backbone of bipedal walking for two decades - it's robust and well-understood, but tends to produce a somewhat conservative, flat-footed gait compared to more dynamic approaches. Cross-embodiment training (training one policy across data from multiple different robot bodies) has shown some real transfer benefits for high-level behaviors, but low-level control (exact joint torques, timing) still tends to need embodiment-specific fine-tuning.
Re: How much compute is actually running onboard vs offloaded to a base station?
This matches something I went through recently.
Vision-Language-Action (VLA) models like RT-2, OpenVLA, and Physical Intelligence's pi0 unify a vision-language backbone with an action-output head, letting a robot map a camera image and a text instruction directly to motor commands instead of hand-coding separate perception and planning stages.
Kind of makes me think about how different this all looked even three years ago.
she/her
Re: How much compute is actually running onboard vs offloaded to a base station?
Respectfully, I think this undersells it a bit.
Domain randomization - varying friction, mass, sensor noise, and even visual textures during training - is one of the more reliable tricks for improving sim-to-real transfer, but overdoing it can make training slower to converge and produce overly conservative policies. A lot of what reads as 'full autonomy' in public demos is closer to a mix of scripted state machines, teleoperation for the hardest sub-tasks, and autonomous execution for the easier, well-rehearsed parts - transparency about this mix varies a lot between companies.
he/him | robotics hobbyist since the DARPA Grand Challenge days
Re: How much compute is actually running onboard vs offloaded to a base station?
@matthew43 Small correction on one detail:
Physical Intelligence's pi0 pairs a smaller pretrained vision-language backbone with a separate flow-matching 'action expert' module, which is one way to get fast, high-frequency action output without needing the whole giant language model to run at control-loop speed.
Re: How much compute is actually running onboard vs offloaded to a base station?
Sorry if this is a basic question, but
'Zero-shot sim-to-real' rarely means literally zero real-world tuning in practice - it usually means the policy transfers well enough to be usable with only calibration and minor safety-limit adjustments, rather than needing a full additional training phase on hardware.
he/him | robotics hobbyist since the DARPA Grand Challenge days
-
scott.andersson5
- Posts: 172
- Joined: Sat Nov 02, 2024 8:39 pm
Re: How much compute is actually running onboard vs offloaded to a base station?
+1 to this. Worth adding:
Physical Intelligence's pi0 pairs a smaller pretrained vision-language backbone with a separate flow-matching 'action expert' module, which is one way to get fast, high-frequency action output without needing the whole giant language model to run at control-loop speed. Whole-body control (WBC) formulates locomotion and manipulation as a single optimization problem across all joints simultaneously, respecting contact constraints and task priorities - it's more general than ZMP-only approaches but is computationally heavier and harder to tune.