-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
Auto Mission does not start from QGC with LPE 'fuse vision position' active #11864
Comments
This is solution for PX4#11864
@copterspace Did you feed LPE on the step №1 by actual vision measurements? |
No, because I do not have vision measurements in the moment of start up/takeoff. |
When you enable vision fusion and do not provide measurements then your LPE origin is not initialized. That's why you get error "vehicle not ready". In addition, you cannot fly otdoor auto mission with vision position enabled because this indirectly implies that you don't use GPS then (for LPE only, EKF2 allows it, but it fuses vision as odometry only). |
Initialisation of LPE origin is task of onboard software, and it might be initialised only when I see markers (according to current local origin drone has in the moment I see marker first time). But |
Dear colleagues, here's video example of my test flying mission: https://www.youtube.com/watch?v=RNG2Y_IHx6Y |
Closed by #11865. |
Describe the bug
When PX4 starts up with LPE = 'fuse vision position' active - it's not possible to start outdoor auto mission from QGroundControl, it reports 'Vehicle not ready'.
When I check 'fuse vision position' AFTER PX4 starts up - it works OK, starts mission, starts to fuse vision position once it becomes available.
Same issue was opened before, #8018, I don't know why @EliaTarasov closed it.
To Reproduce
This bug I first met on my real drone, but it also can be reproduced in jmavsim:
Expected behavior
Start auto mission no matter we have fuse vision position = 0 or 1.
Log Files and Screenshots
I attach simple mission I used in jmavsim, although it can be any mission you like
testjmavsim.plan.txt
Additional context
The solution is also described in #8018.
I removed '&& !(_fusion.get() & FUSE_VIS_POS))' from line 60 of Firmware/src/modules/local_position_estimator/sensors/gps.cpp - it started to work OK in jmavsim.
The text was updated successfully, but these errors were encountered: