If you can move the rangefinder to use the RNGFND1_ parameters then then pre-arm check should pass. I’m sure you know but just in case, use of optical flow requires a rangefinder.
Ya, experience once bad experience, drone climbs endlessly and hit ceiling. That is why I do not dare to arm and fly with such a rangefinder prearm warning. I do see the Rangefinder2 under Quick UI showing the correct cm.
ok, so there is another rangefinder besides the Hereflow’s rangefinder right? The Hereflow rangefinder does not need to be RNGFND1_… so set the RNGFND1_TYPE to match the othere (non-Hereflow) rangefinder.
The vehicle shouldn’t fly up endlessly unless an analog rangefinder is being used. With other rangefinders we should be able to detect once the rangefinder is out of range. If you’ve got a link and/or a log file for that endless climb could you provide a link to it?
@rmackay9
Thanks, works! I moved all to RNGFND1_xx, do not enable the Hereflow onboard lidar. Rangefinder preArm check enabled and no warning. took off both outdoor and indoor Loiter mode is within expected behaviour and without an external GPS installed.
thank you for the guidance and patience.
Could it be that no Range finder in 1 caused the bouncing flight I had with the super flat indoor surface with SURFTRAK_MODE=1, just curious? I may have to plan time to do a repeat test.
I have concluded that it is not due to skipping of RNGFND1, SURFTRAK_MODE=1 on our super flat blue surface not tracking well.
I upgraded to 4.2.2 and noticed that in status window, mag_ofs_x, y & z are shown as zero. Recaliberated the compass twice but still show zero when connected.
Hi guys and girls, Just updated from 4.0.7 to 4.2.2 and i have a lot of changes in parameters that i need to set again. But that’s not a big deal. I have problem with camera gimbal option, before it was set to Servo and i used Servo9 function to control Tilt from Channel 6 on transmitter. Now that option is greyed and i cant controll my gimbal.