librealsense icon indicating copy to clipboard operation
librealsense copied to clipboard

Acceleration Range Issue on UAV

Open xuhao1 opened this issue 5 years ago • 7 comments

Required Info
Camera Model D435i
Firmware Version 2.21.0
Operating System & Version ROS
Platform Jetson TX2
Language All
Segment Robot/UAV

Issue Description

I am from HKUST UAV Group, and we are working on use RealSense D435i with our open-source visual inertial odometry VINS-Fusion and fly it on UAV. In most case, like moving on a small car or hold by hand, the D435i works well and robust with our VINS. But when we use D435i on UAV, we found that the acceleration limit IMU of D435i is set to -4g to 4g, which is too small for UAV especially for landing and takeoff. When we takeoff rapidly or landing, the IMU will saturation and then the VINs will fail.

For applying D435i on UAV, bigger IMU acceleration range is very important. Is that possible for setting the acceleration range bigger?

xuhao1 avatar May 16 '19 06:05 xuhao1

I did some research on the subject of acceleration range. The Bosch manufacturer data sheet for the Bosch BMI055 IMU used in the D435i and T265 says that the component supports +- 2g, 4g, 8g or 16g, selectable via a digital interface. So the +- 4g range may have been set by the RealSense engineering team as a reasonable range for the majority of use-cases - maybe @dorodnic can comment on this.

Apparently, the ideal situation is to have the range as low as possible. The lower the range, the more sensitive the measurement is. If the range is set high then it can cause problems, such as the vehicle moving faster than the sensor can keep up with (e.g the vehicle reaches the ground before the sensor detects the arrival).

MartyG-RealSense avatar May 16 '19 13:05 MartyG-RealSense

Actually we trying to make the vehicle touch ground slower, but it's impossible to control it always, and it's not so robust and safe Is that possible to provide a setable accelaration range option?

xuhao1 avatar May 18 '19 09:05 xuhao1

There's balance between range and the sensitive, and for our application, we want more range than 4g. In our previous experience, bigger range and lowwer sensitive is enough for UAV

xuhao1 avatar May 18 '19 09:05 xuhao1

otherwise, is that possible to provide more camera output frequency than 30hz?

xuhao1 avatar May 26 '19 18:05 xuhao1

Hi @xuhao1 We will look into making range configurable, but it’s unlikely to be implemented very soon. Both RGB and depth cameras can go beyond 30 FPS, but you might need to limit the resolution a bit

Sent with GitHawk

dorodnic avatar May 27 '19 04:05 dorodnic

Thank for you reply. Actually we want 20hz.

xuhao1 avatar May 28 '19 17:05 xuhao1

Hi @xuhao1 I apologize that you did not receive further communication about this 2019 case. It will be closed after 7 days from the time of writing this if we do not receive further comments. Thanks!

MartyG-RealSense avatar Apr 23 '22 10:04 MartyG-RealSense