Skip to content
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

Unable to start mission ('vehicle not ready') #9353

Closed
sticks918 opened this issue Apr 22, 2018 · 7 comments
Closed

Unable to start mission ('vehicle not ready') #9353

sticks918 opened this issue Apr 22, 2018 · 7 comments
Labels
Documentation 📑 Anything improving the documentation of the code / ecosystem

Comments

@sticks918
Copy link

sticks918 commented Apr 22, 2018

Hi all, I've been manually flying a Pixracer for a while and finally hooked up a GPS to try autonomous missions. Despite a solid GPS lock and a simple takeoff -> land plan uploaded, I can't start any missions.

It seems to arm without error, but when starting any mission the error I get is 'Unable to start mission: vehicle not ready'

I've uploaded the log here: https://logs.px4.io/plot_app?log=4b12bb08-a51a-48f2-b8b7-df5cf1c8cf81
though it's pretty short so I'm not sure how helpful it is.

Can anyone help me figure out what's causing it to not start any missions? Thanks!

@dagar
Copy link
Member

dagar commented Apr 22, 2018

Did you see any other errors in QGroundControl? The GPS fix was not good enough for a valid position estimate (what the flight controller actually uses).

image

Was this inside?

There's ongoing work to improve this. mavlink/qgroundcontrol#6364

@sticks918
Copy link
Author

sticks918 commented Apr 23, 2018

Thanks for the help. I'm afraid that's the only error it threw, do you know what the limit is for horizontal/vertical uncertainty? Also is there anywhere in the logs where it notes why the vehicle is 'not ready'? That would be a helpful starting point in case of future issues

@dagar
Copy link
Member

dagar commented Apr 23, 2018

There are commander eph/epv thresholds for initializing a home position, and the EKF has its own thresholds (EKF2_REQ_EPH, etc).

The vehicle not ready message you saw is on the QGC side. If the attempt made is as far as the vehicle it would have probably told you that the transition to MISSION mode is denied due to lack of valid global position.

In the PX4 log (.ulg) there's a message logged called vehicle_status_flags which is what the system is ultimately using. The important one in this case is condition_global_position_valid.

@sticks918
Copy link
Author

Ok I'll try again with after letting it sit in an open area for a little longer. Is there a way to check those flags (vehicle_status_flags and condition_global_position_valid) live in QGC or is it only available through the log post-flight?

@dagar
Copy link
Member

dagar commented Apr 23, 2018

Once the mavlink message GLOBAL_POSITION_INT starts streaming (see mavlink inspector) that means the estimator is publishing a valid global position estimate (good gps below thresholds).

@dagar dagar added the Documentation 📑 Anything improving the documentation of the code / ecosystem label Apr 23, 2018
@sticks918
Copy link
Author

Ok I'll do some more digging. Thanks

@acpl00
Copy link

acpl00 commented Dec 14, 2018

I have QGC-Station and fly-mission-plan, when i set up all the points and I load the mission, I get the error 'Unable to start mission ('vehicle not ready')'.

In other words,

I have tried position control and the drone responded quite satisfactorily using the RC transmitter. However, when I want to try fly mission mode, I can see that the GPS position is jumping even though the QGC takes up till 9 satellites, and the GPS is locked and the HDOP < 1.5 and the VDOP < 1.5.

I can chose the way points and load the program but when I want to change to mission and arm I get the error: I get the error 'Unable to start mission ('vehicle not ready')'.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation 📑 Anything improving the documentation of the code / ecosystem
Projects
None yet
Development

No branches or pull requests

3 participants