Today i observed a quite strange behavior: i can’t fly higher than RNGFND_MAX (which is 120cm in my case; VL53L0X lidar)
Even if i disable the rangefinder over radio (via rc_option) it is still active ! although ctrl-f window of mission planner says, it’s disabled - grazy
Patrick, here are my parameters.
The strange thing is:even when i disable the rangefinder, i can’t fly higher than RNGFND_MAX. To be clear: that happens in simple AltHold mode and rangefinder disabled, no optical flow, nothing
Meanwhile i’m pretty sure this is a major bug in that firmware and not my fault.
ok, tried it: disabled OF, even pulled the wire from tx line of of-sensor and armed in AltHold
->no change, copter rises to approx. 1 meter and that’s it.
No, fence is disabled by radio switch when i fly indoors.
Otherwise it’s not possible to arm : Prearm: fence (gps required). I fly in the basement of my house, means no gps available)
Btw: i have set the fence height (for outdoor flying to FENCE_ALT_MAX = 80m, so not only 120cm !!!)
The VL53L0X need to facing a distance less than 120 cm ALL THE TIME. If you work on the bench it cannot be sitting looking up as the ceiling (on my setup ) is 170 cm so generating an error at starup
I observe this error message all the time with the sensor in less than 120cm distance. The sensors measurement is very precise, despite that Mission Planner throws that error message all the time
FC is a so called Pixhawk lite (China quality product). Firmware ist 3.6.4 or 3.7 doesn’t matter.
I tried 2 different VL53L0X - have no i2c errors - strange
Another question that i have: there is a firmware version for Pixhawk1 and another firmware version for “fmuv2”. What’s the difference ? I allways thought Pixhawk1 = fmuv2