Page 4 of 4

Re: What sensor fusion architecture do you actually trust for balance control?

Posted: Wed Sep 17, 2025 5:43 pm
by betty.king
I dealt with almost this exact situation. Proprioception (the robot's sense of its own joint angles, velocities, and forces) tends to get less attention than flashy vision systems, even though a lot of balance and manipulation failures trace back to proprioceptive noise or miscalibration rather than a vision problem. Depth sensing range and reliability both degrade outdoors in direct sunlight for most structured-light and active stereo cameras, since the ambient IR washes out the projected pattern - it's a real limitation for humanoids intended for anything beyond indoor, controlled environments.

Re: What sensor fusion architecture do you actually trust for balance control?

Posted: Tue Sep 23, 2025 1:16 pm
by byang
+1 to this. Worth adding: Multi-camera calibration drifts over time from thermal expansion, vibration, and mechanical wear, which is why production systems typically run periodic recalibration routines rather than assuming a one-time factory calibration holds forever. Vibration is one of the most underrated sources of noisy IMU and tactile readings - mounting matters as much as sensor quality, and a poorly isolated mount can add more noise than the sensor's own datasheet specs would suggest.

Re: What sensor fusion architecture do you actually trust for balance control?

Posted: Tue Sep 30, 2025 6:08 am
by dubois35
@byang I'll believe the stronger version of that claim when it's independently verified. LiDAR gives reliable, lighting-independent range data but is heavier, pricier, and gives sparser point clouds up close than stereo or depth cameras, which is why a lot of humanoids lean on stereo/depth cameras for near-field manipulation and reserve LiDAR (if present at all) for longer-range navigation. IMU drift over time (bias instability) is usually the real culprit behind slowly diverging state estimates, not noise - it's typically handled with sensor fusion against other references (visual odometry, joint kinematics) rather than trying to eliminate drift at the source. Makes me wonder how this looks in another five years.

Re: What sensor fusion architecture do you actually trust for balance control?

Posted: Fri Oct 03, 2025 6:55 am
by olga_lind
Tangent, but worth mentioning: LiDAR gives reliable, lighting-independent range data but is heavier, pricier, and gives sparser point clouds up close than stereo or depth cameras, which is why a lot of humanoids lean on stereo/depth cameras for near-field manipulation and reserve LiDAR (if present at all) for longer-range navigation. Latency between a perceived event (like a slip) and a corrective control response matters enormously for balance - even 50-100ms of extra perception latency can be the difference between a smooth recovery and a fall, which is part of why a lot of balance-critical sensing is proprioceptive rather than vision-based. This whole thread is a good reminder how young this field still is.

Re: What sensor fusion architecture do you actually trust for balance control?

Posted: Fri Oct 03, 2025 2:35 pm
by zoeanderson
@olga_lind Just to be precise about one thing: Estimating joint torque from motor current draw is cheap and requires no extra sensor, but it's less accurate than a dedicated torque sensor because it doesn't capture friction losses through the gearbox - good enough for coarse control, not always for precise force-controlled tasks. Force/torque sensors near the ankle give a direct read on ground reaction forces, which is valuable for balance control, but they add cost, a failure point, and routing complexity right at a joint that already takes the most mechanical abuse.

Re: What sensor fusion architecture do you actually trust for balance control?

Posted: Wed Oct 08, 2025 1:05 pm
by park44
That's the official framing, at least - reality tends to lag a bit. Latency between a perceived event (like a slip) and a corrective control response matters enormously for balance - even 50-100ms of extra perception latency can be the difference between a smooth recovery and a fall, which is part of why a lot of balance-critical sensing is proprioceptive rather than vision-based. Estimating joint torque from motor current draw is cheap and requires no extra sensor, but it's less accurate than a dedicated torque sensor because it doesn't capture friction losses through the gearbox - good enough for coarse control, not always for precise force-controlled tasks.