Entering LAT/LONG Waypoints

[dmwalker 601]

I was entering a real world route from CYYZ to RKSI for my B777-300ER (FSX) and one of the waypoints was 6430N/10000W. I believe that would be entered as 6N400 but it was not recognised by the FMC. Was the entry incorrect?

[downscc 1,327]

30 minutes ago, dmwalker said:

I was entering a real world route from CYYZ to RKSI for my B777-300ER (FSX) and one of the waypoints was 6430N/10000W. I believe that would be entered as 6N400 but it was not recognised by the FMC. Was the entry incorrect?

The shortcut method generally does not work unless the values are whole degrees, for example 6430N is the same as 64N 030W but N64 30 W100 00 has to be encoded without shortcut:  N640000.0W1000000.0.  A quick memory jogger for the correct format is to see how the GPS or INS coordinates are displayed in the scratchpad.

A little trivial:  All shortcuts such as 6430N or 35W80 are actual defined waypoints in the file wpNavFIX.txt and you can view those definitions in any text editor.  In other words, the shortcuts are not a FMS features but are required to be found in navdata.

[dmwalker 601]

Thanks for the tip about the scratchpad, although you got a bit carried away with the zeros. For the record it was N6430.0W10000.0.

[downscc 1,327]

43 minutes ago, dmwalker said:

Thanks for the tip about the scratchpad, although you got a bit carried away with the zeros. For the record it was N6430.0W10000.0.

Facepalm...

[Ephedrin 418]

On 7.4.2018 at 8:25 PM, downscc said:

Facepalm...

Milliseconds make you hit the middle of the center line :P

Edited April 9, 2018 by Ephedrin

[1290SASRider 26]

On ‎4‎/‎7‎/‎2018 at 2:25 PM, downscc said:

Facepalm...

Nah, they're just lat/longs on Jupiter...