Yes, I have been a bit lazy lately. The weather was quite good, so I was more outside.
I had looked at the data and had came to the point that there was some conflicting position data. This same at flight controller - reaction are messages, "No valid position" and he switches to manual mode. Pitchstick is still around +5% thus drone goes forward by itself. This is very disturbing in manual mode.
View attachment 27978
Now the question is, where the strange data come from. If you only look at the GPS data alone (message GPS_RAW_INT), then it looks good, except for the values for the altitude.
View attachment 27979
If you look at the total data you see a different picture, so why?
It's a lot of different runs and comparison to look at all the MAVlink messages separately. I am still at it. Maybe here I have to adjust my analysis SW to get further.
Looking at the values for Altitude I can generate different views:
- Evaluating all messages
View attachment 27980
I don't know from where thos oszillation dataset come.
- Looking on Position data
View attachment 27982
This seems to be the result of some computing in the flight controller. It is the same as in the fligt2log data represented.
- Looking only to GPS data (this drop seems to be wrong)
View attachment 27981
Here we see a not explainable drop in altitude. Those are wrong data from GPS (due to disturbed signal, multipath or something like that).
br HE