Hi all, a colleague is asking me about a bug they heard of, before we try a long-distance mission with large altitude changes. I’ve never come across this issue. Does it sound familiar to anyone else?
”Apparently, there is a bug that if your take-off location is 1000m above the landing location (when flying A-B route), that the aircraft wants to disarm automatically and will hence change the PID controls. It has something to do with max altitude distance and the drone thinking it landed, hence reducing PID. One of my friends at [redacted] encountered that issue during a test flight in the mountains.”
I don’t have an answer but it might be useful to know if this is Plane or Copter.
I know in Copter you can run into disarm issues with long descents at minimum throttle in some modes. IIRC it would be several seconds of min throttle in stabilized mode, basically meaning your diving. Enough seconds that for most users a planet gets in the way before the disarm becomes an issue.
Could you please provide your flight logs, specifically the .bin files? Also, would you be willing to utilize my program designed for GSoC? Sharing this information might prove beneficial for both of us. Are there any particular details or conditions about this flight that I should be aware of?
I remember we had to set WPs in absolute altitude to make it go below the take off altitude. When we operated with relative altitude, vtol denied to come down below and q assist kicked(altitude) kicked in as well.
When the destination was located at higher elevation, there was no problem on landing with relatives altitude setting on WPs.
For copter operations, we set WPs in relative but changed home when it passed half point of the route. Interesting thing is that the change was not directly reflected until it hit next WP. When the copter reached next WP, altitude was adjusted accordingly based on new home point. I am not sure it was intended and updated later.