paparazzi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Paparazzi-devel] Small bug in GCS: polysurvey across different UTM


From: Felix Ruess
Subject: Re: [Paparazzi-devel] Small bug in GCS: polysurvey across different UTM zones
Date: Wed, 10 Oct 2012 19:30:31 +0200

Hi Mitchell,

thanks for reporting this bug! I create an issue for it at https://github.com/paparazzi/paparazzi/issues/303
Gautier, you are probably most familiar with this part, could you take a look at it?

Cheers, Felix

On Sun, Oct 7, 2012 at 11:58 PM, Mitchell SLOWER <address@hidden> wrote:
Dear all,

I think I found a small bug, at least in the GCS.

In a flight plan, I defined a PolySurvey that was across two UTM zones.
When I start the simulation with the paparazzi "basic" simulator, the PolySurvey outline is incorrect. 
PolySurvey waypoints that are not in the flight plan's UTM zone (lat0 and lon0 zone) are located far away on the map.

This flight plan excerpt reproduces that problem (complete flight plan is available here: http://cjoint.com/?BJhxU3TpD5V )
Note: I'm using an absolute coordinate for the POLYS4 waypoint.

<flight_plan alt="490" ground_alt="390" lat0="45.000000" lon0="65.999999" max_dist_from_home="800" name="Basic" qfu="50" security_height="70">
<waypoint name="POLYS1" x="-200" y="0"/>
<waypoint name="POLYS2" x="-200" y="-200"/>
<waypoint name="POLYS3" x="600" y="-200"/>
<waypoint lat="45.000000" lon="66.007488" name="POLYS4"/>


Now, if I define the waypoints using relative coordinates only, it works fine (complete flight plan here: http://cjoint.com/?BJhxTeYe6w7 ):

<flight_plan alt="490" ground_alt="390" lat0="45.000000" lon0="65.999999" max_dist_from_home="800" name="Basic" qfu="50" security_height="70">
<waypoint name="POLYS1" x="-200" y="0"/>
<waypoint name="POLYS2" x="-200" y="-200"/>
<waypoint name="POLYS3" x="600" y="-200"/>
<waypoint name="POLYS4" x="600" y="0"/>


Finally, I tried with a real flight. I defined a flight plan that was inside an UTM zone, then I manually updated two waypoints to fly across the two UTM zones, and it worked fine.

Just an annoying bug !

Regards,
Mitchell

_______________________________________________
Paparazzi-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/paparazzi-devel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]