40-d6-3c-4d-c1-e9_2024-03-29 09-04-54.tlog (591.2 KB)
My gps altitude and speed ekf exploded but I don’t know what caused it
Post the .bin log off the drone. The .tlog doesn’t help or show enough.
My plane has flown away and I can’t find it.
Now I want to know why it flew away. Currently we only have ground station logs. I see that the GPS status is fixed and the vibration detection is relatively good, but the plane still flew away. I want to know what caused it.
Impossible for me to say exactly without a .bin log, but here’s some guesses:
2024-03-28 19:08:21.485 EKF2 IMU0 emergency yaw reset
2024-03-28 19:08:21.485 Vibration compensation ON
2024-03-28 19:08:21.549 EKF variance
2024-03-28 19:08:21.659 EKF Failsafe: changed to LAND Mode
2024-03-28 19:08:22.692 GPS Glitch or Compass error
2024-03-28 19:08:25.908 Mode change to RTL failed: requires position
2024-03-28 19:08:28.504 Mode change to RTL failed: requires position
2024-03-28 19:08:31.092 Mode change to RTL failed: requires position
2024-03-28 19:08:35.100 Mode change to RTL failed: requires position
2024-03-28 19:08:36.511 SmartRTL deactivated: bad position
2024-03-28 19:08:36.528 Mode change to RTL failed: requires position
2024-03-28 19:08:37.484 Glitch cleared
2024-03-28 19:08:37.893 Mode change to RTL failed: requires position
2024-03-28 19:08:39.299 Mode change to RTL failed: requires position
2024-03-28 19:08:40.837 Mode change to RTL failed: requires position
2024-03-28 19:08:42.090 Mode change to RTL failed: requires position
2024-03-28 19:08:42.090 Vibration compensation OFF
2024-03-28 19:08:44.074 Mode change to RTL failed: requires position
2024-03-28 19:08:44.891 Mode change to RTL failed: requires position
vibration issues. (vibration compensation, EKF Variances. Why are you using EKF2?)
GPS issues. (RTL Requires position data and many of the warning messages are referencing position problems)
With a Tlog there isn’t much more I can do with it. Looks like it was a very unhappy drone.