Hi Felix,
It does help, thanks!
So I see 2 user cases:
1: Relative coordinates: call NavSetGroundReferenceHere
during geo init in the flight plan and the flight plan origin
is defined instead of lat0 and lon0 in the flight plan .xml
file. In that case it's preferable to define the waypoints in
relative coordinates. If absolute coordinates are used, the
waypoints position will be wrong after geo init...
2: Absolute coordinates: set USE_INS_NAV_INIT to "TRUE" in
airframe configuration xml file. The flight plan origin is
defined by lat0 and lon0 coordinates in the flight plan. In
that case it's preferable to define the waypoints in absolute
coordinates. If relative coordinates are used to define the
waypoints, that's OK, the only thing is that the origin of the
flight plan is defined at lat0 and long0.
What happens if USE_INS_NAV_INIT is left to FALSE and the
origin is not initialized using NavSetGroudReferenceHere? Is
that case meaningfull?
Why not set USE_INS_NAV_INIT to TRUE by default? The user
can then still call NavSetGroundReferenceHere in the flight
plan to reset the origin of the flight plan if he wants?
Regards
Loïc
----------------------------------------------------------------------------------------------------------
Hi Loic,
absolute coordinates are currently not really
handled in a nice way, improvements welcome.
What you can do is to add <define
name="USE_INS_NAV_INIT" value=TRUE"/>
This will initialize the ground reference
(origin of the LTP) with the flight plan coordinates,
instead of leaving it uninitialized (to be set from the GPS
fix with NavSetGroundReferenceHere).
You still need to
remove NavSetGroundReferenceHere from your geo init though,
as that would just reset it to the current position.
If you still want your home waypoint to be
automatically set to where you start, in geo init: <call
fun="NavSetWaypointHere(WP_HOME)"/>
Hope that helps...
Cheers, Felix