Hi.
Regularly I fly pacific routes in the 777, this is certainly not the first time on this route either.
I did a reinstall of the 777 last week by uninstalling just the prompts from my PC, then installing it again later. (Not sure if this is the correct way to do it).
I then updated my Navdata to 1809 and all that stuff...
Keep in mind all parts in the flight plane are entered manually by myself.
KLAX > 24L > SUMMR1 > FICKY as the departure, then I enter an airway.
I understand that lat/long way points must utilize the legs page and not RTE.
However when I enter my first one in, N2655W13021 I receive an 'invalid entry' error.
This is for the entire set of waypoints on this flight, so essentially I had to cancel it.
Is there anything i'm doing incorrectly here that is obvious? 
I also wanted to know if it is suggested to delete files related to the PMDG 777 in the sim and what not as well as uninstalling it for a cleaner install which could've caused a mess up here, and yes the product has been updated.
I intend on trying to install it again and see if it resolves itself there; however I doubt it will.
If anyone could try there 777 with the route, by manually entering these waypoints please let me know what the result was.
Flight Plane (Simbrief depicts the waypoints differently to PMDG, i.e, 2655N13021W is N2655W13021 with the PMDG 777.):

KLAX/YBBN
SUMMR1 FICKY B581 WEDES DCT 2655N13021W 2432N13350W 1838N13946W 1603N14252W 1114N14913W 0911N15238W

0518N15937W 0329N16312W 0012S17019W 0412S17711W 0500S17826W 0620S17930E 0816S17600E 1148S16846E 1416S16539E

1713S16250E 2107S15934E DCT HARVS Q21 SAVER DCT AMITY DCT

 

Regards, Mitchell G.

 

Edited August 24, 20187 yr by Loadhaul

Assuming the 777 is the same as the 747 and 767, you can either enter lat/longs in full (NXXYY.ZWXXXYY.Z) or abbreviated (NXXWXXX) format, but not the halfway house you describe.

The FCOM will have full details on acceptable data entry formats for each type of waypoint: worth a quick search?

*Generic reminder that uninstall/reinstalls are the literal worst possible option to solve just about any issue, so avoid unless instructed by someone on the support staff.*

Well I'm coming to clues that it wasn't the T777's fault as by looking at old flights done on the same route as you described the format isn't like that, instead those waypoints used a (NXXWXXX) format.
 

Edited August 24, 20187 yr by Loadhaul

1 hour ago, Loadhaul said:

Well I'm coming to clues that it wasn't the T777's fault as by looking at old flights done on the same route as you described the format isn't like that, instead those waypoints used a (NXXWXXX) format.
 

A shortcut is to look at the format that lat/lon is entered for the IRS, this is how you enter it in the scratchpad if you need to enter minutes.  Sure, you can enter whole degrees as in the NaaWooo format, there are also the universally recognized "shortcut" entries such as aaaooN (these are unique in that they are defined as waypoints and must exist in navdata to be usable by the FMS).  However, if memory is short as mine then use the IRS as a guide and enter Naaaa.aWooooo.o and you're done.  (aa lat  oo lon)

You can enter lat/long on the RTE pages when entering the flight plan.  See FCOM2 11.31.12 to 11.31.18 for a complete explanation of how waypoints can be entered.

Forgetting to enter the decimal could be the problem.

i made the same mistake the other day.

the FMS should accept N2345.5W12345.7. don't Forget to start with a zero if the longitude is less than 100.

it can  get confusing between PFPX (the flight planning software) format, Navigraph Format, PMDG Boeing FMS and everybody else.

 

Jacques LONCHAMBON

 

14 hours ago, Jlonchambon said:

it can  get confusing between PFPX (the flight planning software) format, Navigraph Format, PMDG Boeing FMS and everybody else.

For a reminder of the FMS format, simply look at how the FMS displays the IRS lat/lon information.  The input is in the same format.

Good point..!