Page 2 of 4
Re: How do you handle sensor firmware updates without breaking calibration?
Posted: Tue Jul 14, 2026 6:43 am
by benjaminsanchez
@vyoung Yeah, this tracks with what I've read as well.
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: How do you handle sensor firmware updates without breaking calibration?
Posted: Tue Jul 14, 2026 6:01 pm
by dubois35
From what I've seen:
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: How do you handle sensor firmware updates without breaking calibration?
Posted: Fri Jul 17, 2026 4:55 am
by karen_kim
Small correction on one detail:
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: How do you handle sensor firmware updates without breaking calibration?
Posted: Tue Jul 21, 2026 7:44 pm
by chloe_jack
Agreed, and I'd add:
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.
Makes me wonder how this looks in another five years.
Re: How do you handle sensor firmware updates without breaking calibration?
Posted: Fri Jul 31, 2026 9:55 pm
by hill23
Yeah, this tracks with what I've read as well.
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: How do you handle sensor firmware updates without breaking calibration?
Posted: Wed Aug 05, 2026 9:00 am
by emilyperez
@hill23 Here's the relevant bit as far as I understand it:
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. 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.
Re: How do you handle sensor firmware updates without breaking calibration?
Posted: Thu Aug 13, 2026 9:30 pm
by ananya.novak
I see it a little differently.
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. 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.
This whole thread is a good reminder how young this field still is.
Re: How do you handle sensor firmware updates without breaking calibration?
Posted: Sat Aug 22, 2026 5:26 am
by giulia.roberts4
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.
Re: How do you handle sensor firmware updates without breaking calibration?
Posted: Fri Aug 28, 2026 12:35 pm
by scott21
Can I ask a dumb follow-up -
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. 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: How do you handle sensor firmware updates without breaking calibration?
Posted: Sun Aug 30, 2026 11:59 am
by richard36
New to this, so forgive me if this is obvious -
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.