What's your go-to IMU for a mid-size DIY biped?

[emily45]

@carol38 That's the official framing, at least - reality tends to lag a bit. 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.

[erik_novi]

@emily45 From hands-on experience, 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. 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. Reminds me a bit of the early drone hobbyist scene, honestly.

[freya.smith]

@erik_novi Can I ask a dumb follow-up - 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.

[scott.andersson5]

Here's the relevant bit as far as I understand it: 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. Reminds me a bit of the early drone hobbyist scene, honestly.

[chloe_jack]

Speaking from personal experience here, 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.

[james15]

Can I ask a dumb follow-up - 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.

[carol.robinson]

@james15 I'd push back on this a bit. SLAM in a working warehouse is harder than in a controlled lab mainly because the map keeps changing - pallets move, people walk through, lighting shifts near dock doors - so a lot of production systems lean on semi-static maps refreshed periodically rather than pure continuous SLAM.

[carol.robinson]

@carol.robinson Slightly off-topic, but related: 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. 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.

[servosan90]

Still learning the space, so correct me if wrong - 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. Reminds me a bit of the early drone hobbyist scene, honestly.

[dorothy_kuma]

@servosan90 Thanks for laying this out, genuinely useful. 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.