More testing results.
Delay after WP1.I´ve been trying several things like VIM recom (wayting 1min after saving) and this does nothing for me. I have delay only at first mission try. Second repetition and on are ok always. So, there is something to correct in the code.
QGC over WINDOWSThen, I wanted to know if this could explain the problem in WINDOWS described for many folks about mission stop after first WP. This still remains. So after first WP, remians loitering infinite
Then I´ve created a mission on PC, saved to AQ, then retrieved in Android QGC to see what windows writes as mission.
What I found is the following (see images 1-4 attached). Every WP had
- WP0.png (28.49 KiB) Viewed 16421 times
- WP2.png (27.84 KiB) Viewed 16421 times
So, I run this mission retrieved and saved again in the Nexus7 and obviously behaves the same than with WINDOWS (after first WP, stops). This is obvious since the Ho. Speed = 0 (no speed to fly to following point).
Then i changed in the Nexus7 to reasonable values:
Hit Rad. = 4
Loiter = 2
Hovering Speed = 5
and then the mission works nice.
Then i´ve retrived this succesfull same mission in windows and found the following (see image 3): Hit Rad = 99.99 (a big number), and Loiter = 4 sec (looks to take the wrong number place).
In summary:
WINDOWS QGC:
- QGN needs to write a correct Ho. Speed different from 0. And add it as a selectable parameter
- To be corrected the loiter time (looks a x1000 factor) and Hit Radius
ANDROID QGC
- Delay after WP1 (1 -2 min) happens only first time os mission run. Second+ are OK
- Always use Hit Radius >1m
- Use a Hovering Speed > 1 (typical 3-5 m/s)
I can supply flight logs, if the are usefull to analize this problems.
Hope this help and sorry for the length.
Angel