Good day, 

 

So i have noticed since the release the FMC has been doing something  peculiar with entered LATLON points.

 

The route i am demonstrating is CYYZ to LLBG

 

SEDOG2 YXI MOFAT YWK J583 YDP PRAWN 6200N 05000W 6200N 04000W 6100N 03000W 5800N 02000W PIKIL MOGLO BAKUR UN546 STU UL9 GAVGO UL9 KONAN UL607 KOK UM150 PITES EDISA BIRGI UQ303 NEMEK AKIKA UN132 MAVAR UN130 ESOPO UN130 MES UL609 APLON UL609 LEDRA G18 SOLIN

 

We are going to focus on the latitude and longitude waypoints, 

 

So i entered the route on the RTE 1 page from the SID all the way up until PIKIL.

 

Now when i go and line select N62W050 which was entered as N6200.0W05000.0, it displayes in the scratchpad as N62-0.0W05000.0

When i line select N62W040 which was entered as N6200.0W04000.0 it comes up as N62-0.0W040-0.0

 

Now another strange thing, when i line select N61W030, it comes up as N61-0.0W02960.0 even though i entered it as N6100.0W03000.0.

 

And line selecting N58W020 which was entered as N5800.0W02000.0, it comes up as N5800.0W020-0.0.

 

I have checked the track and distance of each of the waypoints and they match up pretty much perfectly when compared to the flight plan generated by PFPX.

 

Any body have any idea why the waypoints are coming down in the scratchpad with Dashes and why after entering N6100.0W03000.0 it comes up with W02960?

 

 

why after entering N6100.0W03000.0 it comes up with W02960?

 

Calculation error. 60 minutes = 1 degree. It is not rounding correctly, though the value should still work.

 

 

N58W020 which was entered as N5800.0W02000.0, it comes up as N5800.0W020-0.0.

 

Appears to be a signed vs. unsigned value problem. -0.0 is actually MINUS 0.0. The minus value is the minutes at the end; it is not a rogue hyphen.

 

Someone isn't checking their code closely enough when programming.

 

Best regards,

Robin.

Okay, i will submit this as a ticket to make sure they see this. Thanks Robin.

 YDP PRAWN 6200N 05000W 6200N 04000W 6100N 03000W 5800N 02000W PIKIL MOGLO

 

YDP PRAWN 6250N 6240N 6130N 5820N PIKIL MOGLO

 

Basic Eastbound NAT I should think.

nothing much strange about it.

Hi Trent, read my post again carefully

What happens if you enter N62W040 as N62W040 and not N62000.000000000000000000000000000000000000W04000.0000000000000000000000000000000000000000000

Because N62W040 is a bit easier, and all those zeroes aren't doing anything making a simple whole degree lat/long into a long string of zeroes.

 

Yes I know there is sometimes a need to enter more specific lat/longs like S5241.1E16200.0 and you might have a point there. But whole degree's? It's like measuring the distance between Paris and New York in millimeters and winging that the 79 zeroes at the end aren't rounding properly and it's 44 millimetres out.

 

Anyway, it might be indicitave of something, and I appreciate that you might just be doing these co-ords as an example rather than actually thinking you need a whole degree co-ordinate to be expressed down to the tenth of a second of a degree, and as a tool, the whole tenth of a second thing may occasionally be required when dealing with Flex tracks and the odd AUSOT or PACOTS where partial degrees might be possible, or when hand-feeding new waypoints not in the AIRAC for some reason of a chart.

 

Having S5241.1E16200.0 turn into S5241.1E161.9-0.0 could be a bit offputting to the guy that has to say the position report.

Nah Trent you're still not getting it. The real reason i brough this up is after entering these points manually, and hitting the LSK key next to that point, it brings up the full coordinates but sometimes some of the 0s are replaced with a MINUS or DASH sign. And also the fact that when i entered N6100.0W03000.0, instead of seeing it come back up in the scratch pad as N6100.0W03000.0 when i line select it, it comes up as N6100.0W02960.0

 

Ive seen this done in an ACA video and i do not see any '-'s come up when they line select the coordinates.

Having S5241.1E16200.0 turn into S5241.1E161.9-0.0 could be a bit offputting to the guy that has to say the position report.

 

 

Nah Trent you're still not getting it. The real reason i brough this up is after entering these points manually, and hitting the LSK key next to that point, it brings up the full coordinates but sometimes some of the 0s are replaced with a MINUS or DASH sign. And also the fact that when i entered N6100.0W03000.0, instead of seeing it come back up in the scratch pad as N6100.0W03000.0 when i line select it, it comes up as N6100.0W02960.0

 

Ive seen this done in an ACA video and i do not see any '-'s come up when they line select the coordinates.

 

Apparently I don't get it. even though you just said what I said you said.

 

*walks away*

No I'm getting the same issue - I believe it's always with 30W and 70W (need to double check the latter). I thought I reported it during testing... Obviously not. My bad!!

Thanks Luke.

Thanks Luke.

There's been three drafted messages now ha. I really need to make sure I actually send more...