I experienced a malfunction of the airspeed reading today during a flight. It appears to be the same thing that happened last month which caused my Mini Talon to crash. This time it was my Nano Talon. I was lucky the behavior was just violent oscillation as if the plane was stalling and autopilot was trying to stabilize even though my speed was good. Now that it’s happened again, I’m wondering if this is a bug or if it something I am doing wrong in my configuration. 2 different planes, 2 different flight controllers.
Here is a video showing what happened https://youtu.be/VWV1hhhCCuU?t=90. The tlog is here https://www.dropbox.com/s/vx29mgabee3gubv/2019-10-06%2017-51-46.tlog?dl=0.
Also, previous thread with the same airspeed symptom on the Mini Talon here Crash on 3.9.9. No airspeed reading.
Any insight would be greatly appreciated. @tridge? A lot of people say no need for a digital airspeed sensor as the synthetic calculations are very good, but this has me a little concerned.
Do you have the onboard log from the microSD too?
It certainly looks like it did get the estimated airspeed way off, though I think what we really need is to detect the oscillations and back off the gain scaling.
Hi Tridge thanks for the response. Yes I do have the log from the SD. I will pull it later today and upload. The log from my mini talon crash last month is from the SD if you wanted to look at that to be ready for comparison. I’ll post the Dropbox link later today with the Nano Talon flight from yesterday. Thanks again!
@tridge, here’s the bin file from the SD. This is the Nano Talon running Matek F405 Wing.
For quick reference, here is the other log from the Mini Talon that had the same airspeed issue and crashed:
Thanks. I notice quite high EKF velocity innovations, I suspect the lack of compass data is impacting on the EKF yaw estimate and thus on the wind estimate.
Unfortunately the MatekF405-Wing is single IMU which makes some types of analysis (eg. looking for aliasing) not possible.
What I’m going to try to add is code to detect the oscillations and reduce the speed scaling of control surfaces. I’m not confident we can really improve the airspeed estimation any more, especially without a compass, so reducing the impact of the poor airspeed estimation seems like the best bet
@tridge thank you for looking into this. Was it the same issue with the mini talon that I had running a pixhawk 4 mini? What do you suggest as a more safe configuration? Would using a digital airspeed sensor alleviate this? My research indicates that enabling compass on a fixed wing is not necessary and just opens up the possibility of more issues. I just want to have a safe, stable system and the airspeed issue I’ve experienced twice in 1 month has me a little hesitant to fly. Thanks again for your help.
I swapped out the bn-220 for a bn-800 gps/compass. Enabled and calibrated compass and flew it for about an hour total in 10+ mph winds with 22-25mph gusts at the surface. Airspeed reading did not seem to malfunction. I did try to induce a stall which resulted in a brief wobble but nothing violent like before. It seems a compass really is necessary in fixed wing in windy conditions. Despite what most people claim.
question why did you stay in fbwa do you have a manual mode setup as flight mode ?
i had an issue like that but i had input some bad pid settings when i went into fbwa i was lucky i just put in manual got home lol
I do have manual but prefer to launch in FBWA. My tune seems to be good. I have a few hours in now with the compass enabled and it’s been handling better. Going to try auto launch next.
Just came across this post, and would like to add on my experience. I thought I was the only one encountering this problem with extremely, extremely violent oscillation. I never posted about this problem because I don’t have a log.
I don’t have an airspeed indicator, but do have a gps/compass. I believe compass is calibrated correctly but sometimes the airspeed/groundspeed/wind speed just don’t make sense at all. Sometimes. The violent oscillation happened on my second and third flight after doing autotune. It tends to happen when the “displayed airspeed” get too low. You just have to push full throttle, dive down, and let the airspeed build up again to more normal value. This is before I turn the synthetic airspeed on!
After turning on the synthetic airspeed, the problem persist and seems to get worse. As soon as your displayed airspeed goes below minimum airspeed, there is a very high chance the plane would enter into extremely violent oscillation. I shouldn’t have continued to fly, but I did because I know I can get out of it by diving hard and let airspeed build up again. To continue the troubleshooting, I halve all the PIDs but problem still exists. (maybe not enough?). Then the final mistake: I tried to turn off EKF2. AHRS_EKF_TYPE=0. In my twenty years of RC experience, I’ve never had a complete hull loss. But thinking back I am just glad nobody on ground got killed as it happened 300 meters over a lake. Again, same problem, pitch momentarily went up and airspeed momentarily went below min. speed. Started shaking. The more violent it shakes the lower the displayed airspeed. The lower the display airspeed the more violet the shake. vicious cycle. Lost 300 meters in matter of seconds. I tried to give full down elevator, diving straight for the ground to get out of the shake, but airspeed never get picked up again this time (maybe EKF2 off) and plane plunged into the lake.
@tridge apologies again I don’t have a log, but I wish someone can really look at this issue. This problem of extremely violent uncontrollable oscillation could be a big safety hazard for the hobby. In the old days when planes are made out of balsa, there is no chance the plane can survive fractions of this oscillation . Thank you.
finally got a chance to compile a list of videos showing the problem. Pay particular attention to the airspeed, as it tends to happen when speed drops below ARSPD_FBW_MIN which is set to around 9 to 10m/s.
Before using synthetic airspeed:
After using synthetic airspeed:
So the problem is definitely aggravated by the use of synthetic airspeed, but not the root cause as it could happened before using synthetic airspeed. Or maybe it is, and the oscillation is simply caused by bad PIDs since I haven’t start adjusting PIDs before the use of synthetic airspeed. After using synthetic airspeed, I have tried everything but to no avail. Tried adjusting all the PITCH2SRV and RLL2SRV parameters but the problem persist. BTW, PITCH2SRV_RMAX_DN and UP always reset to 120deg/s after every flight, which is outside the range of 0-100.