MAVLink Waypoint read/write fails if GPS lock has not been achived

[GoogleCodeExporter]

The Mission Planner will not read or write waypoints unless Waypoint 0 (home) 
has been recorded by APM. Once this is done with GPS lock of Xplane use, all 
seems well. 

Original issue reported on code.google.com by analogue...@gmail.com on 21 Apr 2011 at 11:08

[GoogleCodeExporter]

Chris i dont seemt o be able to replicate. i did and erase and reset, and then 
tried uploading and all worked fine. If the APM was waiting for gps lock i 
could see an issue, but that is out of my control.

Original comment by Meee...@gmail.com on 21 Apr 2011 at 11:28

[GoogleCodeExporter]

Yes, that's it: it had not got GPS lock yet (either real or synthetic via 
Xplane). I guess that along with setting "home", connecting with Xplane counts 
as first GPS lock. 

I think I need to really sit down with Doug this weekend and figure out why our 
out-of-the-box experience is so bad for people who don't have a GPS or can't 
get lock at the benchtop. 

Original comment by analogue...@gmail.com on 21 Apr 2011 at 11:36

[GoogleCodeExporter]

I've revised the Summary to redirect this issue.

Original comment by analogue...@gmail.com on 21 Apr 2011 at 11:38

• Changed title: MAVLink Waypoint read/write if GPS lock has not been achived
• Changed state: New

[GoogleCodeExporter]

Original comment by analogue...@gmail.com on 21 Apr 2011 at 11:38

• Changed title: MAVLink Waypoint read/write fails if GPS lock has not been achived

[GoogleCodeExporter]

I have the same issue with Planner Mavlink, but when switching to the CLI mode 
(switch towards servo pins...) it works fine. Same behaviour for PID settings

Original comment by parv...@gmail.com on 27 Apr 2011 at 11:02

[GoogleCodeExporter]

Original comment by dewei...@gmail.com on 2 May 2011 at 5:05

• Changed state: Fixed