-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems With Holding the Altitude #11331
Labels
Comments
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Closing as stale. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have two issues I'd like to open to discussion:
1- Our quadcopter wasn't able to hold its altitude during missions. It was supposed to hold at a waypoint for 30 seconds, but instead, it descended slowly and jumped repeatedly during that period. What might be causing this? (running Px4 firmware 1.8.2 on a generic quad x with Pixhawk 1. 3DR GPS module connected.) Log: https://review.px4.io/plot_app?log=9ace9200-b9e7-4b3a-9090-4720aac6dd74
2- Another quadcopter rocketed to the sky at the start of a mission. We panicked and pulled it down with a rope we had attached earlier. The mission was to takeoff to 4 meters and hold there for 10 seconds, then land. This one has the same hardware as the other except that it has a ReadyToSky Ublox M8N GPS module and a customized airframe. Why do you think that happened? Log: https://review.px4.io/plot_app?log=83478e75-9a39-4197-a9f4-8fc9ad0e889c
After these incidents, I have tried the same mission in jMAVSim with HITL simulation. Turned out the quad could not hold its altitude in there as well. I've downgraded the firmware to 1.7.0 to test if the same thing would happen again. It did. Furthermore, I've observed that the quad loses its global position lock in the simulation sometimes.
I would really appreciate some insight to these problems. Thank you!
The text was updated successfully, but these errors were encountered: