Page 3 of 3

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Thu Sep 11, 2025 4:40 pm
by sharonschmidt
@park44 From hands-on experience, 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. 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.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Tue Sep 16, 2025 5:36 pm
by lbianchi
One nitpick - '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. 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.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Mon Sep 22, 2025 10:34 am
by sarah.santos3
Just to be precise about one thing: 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.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Thu Oct 02, 2025 11:27 am
by wei_ross
Respectfully, I think this undersells it a bit. 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. 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.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Thu Oct 09, 2025 1:42 am
by karen.chen3
One nitpick - 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: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Fri Oct 10, 2025 10:32 pm
by mohammed64
Worth being a little skeptical of the marketing angle here. 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. 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.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Mon Oct 13, 2025 2:10 pm
by ethan_fisc
@mohammed64 I'd push back on this a bit. 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. Kind of makes me think about how different this all looked even three years ago.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Tue Oct 21, 2025 9:55 pm
by yuki71
Appreciate the detailed answer. 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. 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.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Sun Nov 02, 2025 3:43 pm
by deborah59
I'd push back on this a bit. Model predictive control (MPC) is still very much alive in production humanoids, often working alongside or underneath learned policies - MPC handles short-horizon dynamically-consistent trajectory optimization while learned components handle perception, task-level decisions, or recovery behaviors that are hard to hand-model.

Re: What's the current bottleneck in loco-manipulation - the locomotion or the manipulation half?

Posted: Mon Nov 03, 2025 7:12 pm
by kim37
Genuinely curious - 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. 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.