Page 2 of 5

Re: Anyone benchmarked tactile sensor response time under rapid contact?

Posted: Wed Mar 04, 2026 12:20 am
by servosan90
@rao91 Side note that might be relevant: 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 benchmarked tactile sensor response time under rapid contact?

Posted: Fri Mar 06, 2026 10:28 am
by barbara50
Minor factual note: 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 benchmarked tactile sensor response time under rapid contact?

Posted: Mon Mar 09, 2026 4:50 am
by ananya.novak
@barbara50 Just to be precise about one thing: 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 benchmarked tactile sensor response time under rapid contact?

Posted: Sat Mar 14, 2026 10:19 am
by ramirez77
Genuine beginner question - 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. 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: Anyone benchmarked tactile sensor response time under rapid contact?

Posted: Sun Mar 15, 2026 8:36 am
by wei_ross
I don't think that's quite right, for what it's worth. 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.

Re: Anyone benchmarked tactile sensor response time under rapid contact?

Posted: Thu Mar 19, 2026 4:30 am
by servosan90
@wei_ross Here's the relevant bit as far as I understand it: 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. 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 benchmarked tactile sensor response time under rapid contact?

Posted: Tue Mar 24, 2026 5:17 pm
by thomas65
This is exactly the kind of context I was looking for. 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: Anyone benchmarked tactile sensor response time under rapid contact?

Posted: Mon Mar 30, 2026 4:44 am
by cynthia.muller
Worth being a little skeptical of the marketing angle 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.

Re: Anyone benchmarked tactile sensor response time under rapid contact?

Posted: Fri Apr 10, 2026 2:55 pm
by scott21
@cynthia.muller I can speak to this a bit. 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. 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 benchmarked tactile sensor response time under rapid contact?

Posted: Thu Apr 16, 2026 5:18 pm
by rossi30
@scott21 Here's what I know on this: 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. 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.