jaspreeth / ardupilot-mega

Automatically exported from code.google.com/p/ardupilot-mega
0 stars 0 forks source link

Mission Planner Zeroes Out Lat, Long, Alt when Converting Waypoint to Loiter Command #445

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1.Plan a mission by clicking on some WP locations on the planning tab. The WP 
coordinates and altitudes are entered into the plan below the map as expected.

2. Convert a WP to a Loiter command using the drop down selection in the 
command column.
3.

What is the expected output? What do you see instead?
I expect to see the command change to Loiter and the optional headings to 
indicate where the loiter parameter (time, num turns)has to go. I also expect 
the previously entered lat, long, alt to remain as-is.

What happens is that the lat, long and alt all change to zero. And, it really 
means it - with the command left with the zeros in place, my Arduplane dove for 
the ground (my local alt is 50 m) and headed for the 0,0 location in the middle 
of the Atlantic ocean. I changed the alt to same height as the previous 
Waypoint commands and the plane headed off to the Atlantic at the programmed 
altitude.

If I move the position of the Loiter command on the map the lat and long are 
updated to the new location, but the alt remains at 0.

I flew like this because I thought the new command interpreter had been changed 
to interpret Loiter commands as action commands executed after the prev. WP was 
reached and the Planner had changed to suit. So, I just inserted a Waypoint 
command at the desired location ahead of the Loiter.

What version of the product are you using? On what operating system?
APM Planner 1.0.97.
It did it on both my XP and Vista systems.

Please provide any additional information below.
Maybe once when I tried the above sequence it didn't zero out the nav 
parameters, but I don't remember if I exactly followed the sequence above.
I tried all three Loiters (Unlimited, Turns, Time). They're all the same.

Original issue reported on code.google.com by philcole...@gmail.com on 28 Nov 2011 at 5:04

GoogleCodeExporter commented 8 years ago

Original comment by Meee...@gmail.com on 29 Nov 2011 at 1:17

GoogleCodeExporter commented 8 years ago
Still happens in 1.0.99

Original comment by philcole...@gmail.com on 30 Nov 2011 at 7:58

GoogleCodeExporter commented 8 years ago
try right clicking the map, you may find it much easier

Original comment by Meee...@gmail.com on 1 Dec 2011 at 1:30

GoogleCodeExporter commented 8 years ago
OK, I never noticed that, despite being right in front of my face. Thanks.

However, if I add a Jump command with a right click on the map the first Loiter 
command I add with a right click comes out with zeroes for coordinates and 
altitude. Subsequently added Jumps are correct.

Original comment by philcole...@gmail.com on 1 Dec 2011 at 4:01

GoogleCodeExporter commented 8 years ago
thanks phil, just discovered one of my long standing bugs. i will fix

Original comment by Meee...@gmail.com on 3 Dec 2011 at 11:59

GoogleCodeExporter commented 8 years ago
i think this is fixed,

Original comment by Meee...@gmail.com on 7 Dec 2011 at 3:45

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
It's fixed as far as I can tell.

Original comment by philcole...@gmail.com on 8 Dec 2011 at 6:50

GoogleCodeExporter commented 8 years ago

Original comment by Meee...@gmail.com on 12 Dec 2011 at 12:26