BACARS Uplinks

[Gary Oliver]

All,

I flew the sim for 4 sectors today and every time the route uplink and route corridor winds failed through BACARS.

Has anyone else seen any issues this weekend?  I wonder if simbrief have changed something as my EFB flight plan looks weird too.

Cheers
G

[macroflight]

I flew ESGG-ESSA yesterday evening, no problem with the route uplink, not sure if I got any route corridor winds.

Tried WIII-WIMM just now, no problem with the route uplink but I got an empty route corridor. The BACARS window also shows red for "Wind". When I pasted the winds from the flightplan into the instructor GUI Corridor tab they loaded OK.

Both flights using BAW.

I then tried the same WIII-WIMM route but using GTI (different flightplan format) and that worked normally.

[Gary Oliver]

Ah,

Simbrief did make some changes which my code didn't handle.  Its been updated on my backend server so it should all work fine now.  No updates required.

Please let me know if anyone spots any further issues.

Cheers
G

[Kurt]

Ah,

Simbrief did make some changes which my code didn't handle.  Its been updated on my backend server so it should all work fine now.  No updates required.

Please let me know if anyone spots any further issues.

Cheers
G

Thanks for the support Gary 

[macroflight]

Gary, I think your fix might have broken other flight plan formats.

It now works as expected for me with BAW, but no longer with GTI. If I manually paste the winds from the GTI flight plan into the Corridor tab they load correctly.

I tested a very basic flight ESSL-ESSA (as BAW123 and GTI123 if you want to check portal logs, ATC route AUTO, departure 0600z)

The GTI flight plan wind section:

Code Select Expand

--------------------------------------------------------------------
                          WIND INFORMATION                         
                          ----------------                         

CLIMB            T O C            NILUG            T O D
350 332/046 -43  170 017/004 -16  170 139/024 -13  170 139/024 -13
310 336/070 -38  150 330/002 -12  150 129/020 -09  150 129/020 -09
200 342/023 -20  130 295/005 -08  130 137/020 -05  130 137/020 -05
150 330/002 -12  110 271/009 -05  110 160/017 -02  110 160/017 -02
100 261/011 -04  090 253/011 -02  090 189/012 -00  090 189/012 -00

DESCENT
350 158/042 -46
310 158/066 -39
200 154/048 -18
150 129/020 -09
100 180/014 -02

--------------------------------------------------------------------


[Gary Oliver]

Oh!

FFS no good deed goes unpunished hey

I'll check GTI and QFA tonight

[macroflight]

It seems winds are still (I don't think it was ever fixed) not uploaded from BACARS for GTI flight plans.

[Gary Oliver]

Fixed and tested

BAW, GTI, QFA, DLH and all LIDO formats

Cheers
G

[macroflight]

Tested OK (GTI). Thanks Gary!

[macroflight]

Fixed and tested
BAW

I found a small issue when testing Worldflight leg WF2432 (KLAS-PHNL) using the BAW format.

The lat/lon "N3660.0W12500.1" (point BEBOP) is not accepted (and this means that all points from the corridor are unused, so reverting back to the PSX planet model weather). Manually changing it to e.g "N3700.0W12500.1" solves the problem.



Another observation (since US STARs and SIDs are so long): even if STAR/SID waypoints are in the OFP, they do not get into the wind corridor. Maybe because the FL column is empty? Intentional behavior or bug?

Code Select Expand

LAT    LONG    WAYPT  ITT   DIS FL  TMP      SECTOR W/V

                                         100   200   310   350
N3604.8W11509.1 KLAS  262     5         
N3604.1W11515.5 RUDYY 200     5     P26 16014 18020 21037 22046
N3559.5W11517.6 SELLZ 207     7     P16 16014 18020 21037 22046
N3553.1W11521.9 MGNTO 271     9     P06 16014 18020 21037 22046
N3553.3W11533.5 KRUGR 271    18     M00 16023 18022 21046 21055
N3553.7W11556.3 JOHKR 315    33     M14 16023 18022 21046 21055
N3616.9W11625.1 GRYMZ 316    13     M29 16023 18022 21046 21055
N3626.7W11636.7 DEDPL 317    10     M34 15014 17025 20053 21062
N3634.0W11645.0 BIKKR 317     3     M36 16016 18021 20052 21062
                                         280   300   320   340
N3644.2W11656.7 CAGEE 332    38 320 M37 20041 20048 20055 21063
N3717.9W11718.6 KENNO 277   235 320 M37 20041 20048 20056 21063
N3743.6W12213.4 OAK   252   140 320 M38 17031 18037 18037 18036
N3660.0W12500.1 BEBOP 251    98 320 M40 07009 05009 04011 03014
N3627.7W12656.0 BAART 250   392 320 M39 36024 36030 35032 35033
N3401.4W13420.8 BARAZ 245   390 320 M39 26030 26035 26040 26045
                                         300   320   340   360
N3110.7W14117.4 BILLO 242   401 340 M45 01037 01034 01031 36019
N2753.5W14758.2 BEKME 238   402 340 M45 05020 04019 04019 05017
N2417.7W15415.0 BOARD 235    82 340 M44 33008 31010 29012 31019
N2331.7W15528.7 BITTA 222    76 340 M42 33007 31011 30016 30022
                                         100   200   310   350
N2221.3W15637.1 BOWSZ 219    51     M31 13010 08014 35007 33016
N2141.7W15712.1 HISPO 225    24     P05 13010 08014 35007 33016
N2125.0W15730.6 BAMBO 247    14     P10 11006 07015 01010 34018
N2119.5W15744.9 IHNET 247     7     P15 11006 07015 01010 34018
N2117.0W15751.5 INOYI 226     5     P18 11006 07015 01010 34018
N2113.3W15755.8 HUBAP 005    18     P19 11006 07015 01010 34018
DESC                                 FL  100   150   200   310


[Hardy Heinlin]

... even if STAR/SID waypoints are in the OFP, they do not get into the wind corridor.

How do you come to this conclusion? When I enter your text in my PSX and correct that "60" error, all 24 corridor points are recognized and set.

The altitudes in this text format are only used for the OAT. When no altitude is entered, the OAT at that point is ignored. Position-wise it's all about lat/lon. If lat/lon data exist, these are used. If a text contains just names and no lat/lon, the current FMC LEGS will be scanned for names and their lat/lon. If not found in LEGS, then the database will be scanned. If a name is not found after all, a red error message occurs on the Corridor page. But this can only happen with text formats that don't include the lat/lon.

Also, the weather differences between SID waypoints are usually very small anyway. You need no corridor point every 5 miles.


|-|ardy

[macroflight]

How do you come to this conclusion? When I enter your text in my PSX and correct that "60" error, all 24 corridor points are recognized and set.

Yes, that is what happens for me too.

I was commenting on the behavior of BACARS, not PSX. I do not expect PSX to know about waypoints that were never entered into the wind corridor box in the first place.

In my OFP (BAW format, generated by Simbrief through the Simfest portal) I see all 24 waypoints, but when I ask BACARS to load the flight, it only puts the 10 non-SID/STAR waypoints in the PSX wind corridor.

But just as Hardy says, those extra points will probably not matter very much. So if BACARS leaves them out by design, that's OK. But if it's a regression, I thought Gary might want to know.

Regarding the lat/lon "N3660.0W12500.1": is that valid or not? If it is a valid lat/lon, then maybe (low priority, I can work around the problem) PSX could learn to parse it? If it's not valid, then we can blame Simbrief instead.

[Hardy Heinlin]

60 is not valid. This must be a rounding error or a typo in the database.

[macroflight]

60 is not valid. This must be a rounding error or a typo in the database.

Reported to Navigraph

[Hardy Heinlin]

In the FAA database, BEBOP is at N365959.80 W1250004.18

[macroflight]

And now it's fixed. Almost PSX-like response time from Navigraph.

I verified by re-planning my route and got this for BEBOP:

Code Select Expand

N3700.0W12500.1 BEBOP 251    98 320 M39 29004 28004 29003 29001