Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Track between waypoints

Featured Replies

Hi,I have tried to find out if it is possible to get tracks between waypoints.WP1-WP2 TRK ?WP2-WP3 TRK ?WP3-WP4 TRK ?Etc Can this this be retrived by using any of the GPS variables, I have tried setting FlightPlanWaypointIndex, but without any luck to the get anything than the next waypoint track.RegardsEugen

  • Author

Eugen,The standard GPS gives you the bearings and headings to the next waypoint on several pages (nrst, flightplan etc,)%((@c:NearestAirportCurrentTrueBearing,degrees) (A:GPS MAGVAR, degrees) - d360)%!03d!

Jan

 

 

 

"Beatus ille qui procul negotiis..."

  • Commercial Member

Eugen, I'm guessing you need to be able to pull arbitraty tracks so that you don't actually have to switch waypoints to get the track?If so, I don't believe it's possible using the GPS vars. You'd have to preload and sequence them into custom variables and then work with those.--Jon

What I tried to use was eg the following macro. @1 (>@c:FlightPlanWaypointIndex) (@c:GPS WP DESIRED TRACK, degrees) But I guess it doesn't work.My intention is to show each track for each waypoint pair not only the "next waypoint but also the next next waypoint etc.So how can I calculate the track from one waypoint to the next waypoint?BrgdsEugen

  • Commercial Member

>So how can I calculate the track from one waypoint to the next>waypoint?pi 2 * @3 sin @1 sin @GC_DISTANCE(@1, @2, @3, @4) s0 cos * - @1 cos l0 sin * / acos @4 @2 - sin 0 < if{ - } els{ + }where:@1 = lat1@2= lon1@3= lat2@4 = lon2and:Distance (GC) = @1 sin @3 sin * @1 cos @3 cos * @2 @4 - cos * + acos Edit: obviously everything given is in radians:)--Jon

Hi,Thanks :-)However I could not get the LAT and Long through@c:FlightPlanWaypointLongitude@c:FlightPlanWaypointLatitudeI have also problems retrieving other of those variables GPS likeFlightPlanWaypointActualFuelConsumptionFlightPlanWaypointEstimatedFuelConsumptionFlightPlanWaypointFuelRemainedAtArrivalFlightPlanWaypointETA but FlightPlanWaypointETE is working ??Maybee I miss something ?Eugen

Hi Eugen,"GPS WP DESIRED TRACK, degrees" is an Aircraft variable (type A: ), not a GPS macro variable. I think it always shows the track to the next wp, starting from the current A: Active gps variable.Maybe this works: @1 (>@c:FlightPlanWaypointIndex) (@c:FlightPlanWaypointMagneticHeading,degrees) d360Tom

Hi,FlightPlanWaypointMagneticHeading provided what I wanted :-).I wonder about the variables @c:FlightPlanWaypointLongitude@c:FlightPlanWaypointLatitudeFlightPlanWaypointEstimatedFuelConsumptionFlightPlanWaypointFuelRemainedAtArrivalFlightPlanWaypointETA but FlightPlanWaypointETE is working that I couldn't get to work, anyone succeded in in using them or are they not implemented ?BrgdsEugen

  • Commercial Member

Oh good.I thought you wanted to be able to get an arbitrary track for a set of waypoints that wasn't selected.FlightPlanWaypointMagneticHeading is actually a track, and not simply a heading based on your current position?--Jon

I guess you know this, otherwise:@c:FlightPlanWaypointLongitude@c:FlightPlanWaypointLatitudeboth need a unit to show correctlyie (@c:FlightPlanWaypointLongitude,radians) or (@c:FlightPlanWaypointLongitude,degrees)etc.Now, units are NOT NECESSARY needed when you pass any or both as parameters to a macro, because parameters are passed as plain text and converted to their values in the macro itself.For example, if you pass @Macro1(@c:FlightPlanWaypointLongitude)The macro should be (@1,radians) pi 2 * But, if you pass @Macro1((@c:FlightPlanWaypointLongitude,radians))The macro should be @1 pi 2 * I make this clarification as it seems to be rather confusing when you first investigate the way GPSnn.XML works.As for the other GPS macro variables, never tested them, but it has to be a solution out there :)Tom

  • Author

Eugen,If you want the ETE between waypoints, you can use:%((@c:FlightPlanWaypointEstimatedTimeRemaining,hours))%!02d!:%((@c:FlightPlanWaypointEstimatedTimeRemaining,minutes))%!02d!%{end}Then somewhere:%((@c:FlightPlanIsActiveFlightPlan) (@c:FlightPlanWaypointsNumber) s2 0 != and)%{if}%(0 sp1)%{loop}%(l1 (>@c:FlightPlanWaypointIndex))%((@g:listItems) (@g:listCurrent) l3 == and)%{if}{blnk}%{end}%(l3 ++ sp3)%((@c:FlightPlanWaypointIdent))%!s!{nr}%(l1 0 !=)%{if}nt%((@c:FlightPlanWaypointMagneticHeading,degrees) d360)%!03d!

Jan

 

 

 

"Beatus ille qui procul negotiis..."

Hi,Thanks all,I used the following @1 (>@c:FlightPlanWaypointIndex) (@c:FlightPlanWaypointETE, minutes) flr 60 % %(FPLWPETEMin((L:FPL_index, number) 2 +))%!02d!which workedbut the below don't work for some reason , can't figure out what I miss@1 (>@c:FlightPlanWaypointIndex) (@c:FlightPlanWaypointETA, minutes)%(FPLWPETAMin((L:FPL_index, number) 2 +))%!02d!Same goes with fuel@1 (>@c:FlightPlanWaypointIndex) (@c:FlightPlanWaypointFuelRemainedAtArrival,liters)BrgdsEugen

  • Author

Eugen,Code here not available, but to get ETA I use ETE + ZULU time and that gives a proper read out.Jan"Beatus Ille Procul Negotiis"

Jan

 

 

 

"Beatus ille qui procul negotiis..."

  • Author

Here are the macro's from the leg page of the fmc%((@c:FlightPlanWaypointEstimatedTimeRemaining,hours))%!02d!:%((@c:FlightPlanWaypointEstimatedTimeRemaining,minutes))%!02d!%{end}%((P:Zulu time,hours) flr 100 % (@c:FlightPlanWaypointEstimatedTimeRemaining,hours) +)%!02d!:%((P:Zulu time, minutes) flr 60 % (@c:FlightPlanWaypointEstimatedTimeRemaining,minutes) +)%!02d!%{end}Concerning the fuel, never used that,%((@c:FlightPlanWaypointFuelRemainedAtArrival,pounds))%!d!%{end}seems to give a proper indicationHope it helps,Jan"Beatus Ille Procul Negotiis"

Jan

 

 

 

"Beatus ille qui procul negotiis..."

  • Author

And these seems to work too:%((@c:FlightPlanWaypointETA,hours) 24 % flr)%!02d!:%((@c:FlightPlanWaypointETA,minutes)60 % flr)%!02d!%{end}%((@c:FlightPlanWaypointETE,hours) 24 % flr)%!02d!:%((@c:FlightPlanWaypointETE,minutes) 60 % flr)%!02d!%{end}Jan"Beatus Ille Procul Negotiis"

Jan

 

 

 

"Beatus ille qui procul negotiis..."

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.