Page 2 of 2

Re: How do you validate a full sensor suite before first real-world deployment?

Posted: Sun Feb 23, 2025 12:53 am
by noah_pate
@olga_lind I can speak to this a bit. 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. 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 validate a full sensor suite before first real-world deployment?

Posted: Mon Feb 24, 2025 8:14 am
by olga_lind
@noah_pate +1 to this. Worth adding: 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 validate a full sensor suite before first real-world deployment?

Posted: Mon Feb 24, 2025 4:26 pm
by barbara50
@olga_lind Speaking from personal experience here, 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. 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. This whole thread is a good reminder how young this field still is.

Re: How do you validate a full sensor suite before first real-world deployment?

Posted: Thu Feb 27, 2025 5:45 am
by emilyperez
Follow-up question though - 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.

Re: How do you validate a full sensor suite before first real-world deployment?

Posted: Mon Mar 10, 2025 10:30 am
by williams84
@emilyperez Follow-up question though - 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: How do you validate a full sensor suite before first real-world deployment?

Posted: Fri Mar 14, 2025 4:46 am
by sarah.santos3
That's the official framing, at least - reality tends to lag a bit. 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. 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 validate a full sensor suite before first real-world deployment?

Posted: Tue Mar 18, 2025 11:00 am
by zoeanderson
@sarah.santos3 Slightly off-topic, but related: 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.

Re: How do you validate a full sensor suite before first real-world deployment?

Posted: Wed Mar 26, 2025 5:14 am
by choi98
This is exactly the kind of context I was looking for. 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. 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.