Page 1 of 2

Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Sun Jun 15, 2025 4:10 pm
by park44
Not sure if this has been discussed before, but here goes. Event cameras (which report per-pixel brightness changes rather than full frames) are still more of a research curiosity than a production sensor for humanoids, mainly because the software ecosystem and processing pipelines around them are far less mature than for standard frame-based cameras. 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. Curious to hear how others see this.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Sun Jun 15, 2025 9:14 pm
by cynthia.muller
@park44 I'd frame this differently. 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: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Mon Jun 16, 2025 1:15 am
by servoken70
@cynthia.muller Speaking from personal experience here, 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. 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.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Mon Jun 16, 2025 1:49 am
by nicole57
@servoken70 Appreciate the detailed answer. A minimum viable sensing suite for safe bipedal walking generally includes joint encoders, an IMU for orientation/angular velocity, and either force/torque sensing or accurate current-based torque estimation at the ankles - everything else (vision, tactile, LiDAR) adds capability rather than being strictly required just to stay upright.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Mon Jun 16, 2025 2:13 am
by jwang
Slightly off-topic, but related: 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. 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.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Wed Jun 18, 2025 12:12 pm
by diego.moore6
@jwang Related question - 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. Unitree's Dex3-1 dexterous hand packs around 33 pressure/tactile sensors per hand across the fingers and palm, capable of sensing pressure roughly in the 10g-2500g range - a useful reference point for what 'production tactile sensing' looks like right now. Kind of makes me think about how different this all looked even three years ago.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Thu Jun 19, 2025 12:08 pm
by rossi30
Minor factual note: Tactile skin arrays have improved a lot, but 'good enough to matter' really depends on the task - coarse contact detection across a large area is fairly mature, while fine, high-resolution force distribution sensing (like a human fingertip) is still the harder problem.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Fri Jun 20, 2025 11:57 pm
by young56
@rossi30 Appreciate the detailed answer. 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.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Mon Jun 23, 2025 8:59 am
by matthew43
Same conclusion I've come to. Also worth noting: 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. Sensor fusion mostly earns its keep by covering for each individual sensor's weaknesses - vision struggles with occlusion and lighting, IMUs drift, force/torque sensors are noisy at low loads - fusing them gives a more robust estimate than any one source alone, independent of raw compute.

Re: Anyone dealt with sensor fusion drift after a hard fall/impact?

Posted: Tue Jun 24, 2025 8:46 am
by carlossanchez
Speaking from personal experience here, 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. 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.