Der Michel

Hi, and now some picture with more information that answers my question 3 from first post: So the correct order of MEMOS (the order of the block with ? is not fully verified): DEST EFOB PARK BRK ON ELEC EXT PWR N/W STEER DISC? BRK FAN? COMPANY MSG : PRNTR? COMPANY MSG? EFB MSG? TRUE NORTH REF? ADS-B TRAFFIC ON ? CAPT LOUDSPKR OFF / LO? F/O LOUDSPKR OFF /LO RMP 1+2+3 OFF? VHF VOICE? HF VOICE? CROSSFEED OPEN? GND SPLRs ARMED? ENG 1+2 A-ICE? ICE NOT DETECTED? APU AVAIL APU BLEED SEAT BELTS NO SMOKING NO MOBILE NO PORTABLE DEVICES VIDEO IN USE? PA IN USE Y ELEC PMP CTL? REMOTE C/B CTL ON REFUEL PNL DOOR OPEN REFUEL IN PROGRESS This is a list from the A330 ESLD, maybe a reference also for A350 regarding priority (but a lot items are different in prio): 1 T.O. MEMO 3 IRS IN ALIGN 4 IRS IN ALIGN ATT 5 REFUEL IN PROCESS 6 JETTISON MEMO 7 TRUE NORTH REF 8 SEAT BELTS 9 NO SMOKING 10 NO PORTABLE DEVICES 11 GND SPLRS ARMED 12 PA IN USE 13 VIDEO IN USE 14 STROBE LT OFF 15 TRIM XFR PROCESSING 16 TRIM TRANSFERED 17 OUT TK XFR PROCESSING 18 OUT TK TRANSFERED 19 TURB DAMP 20 GSM DISCONNECTION 21 ATC DATALINK STBY 22 COMPANY DATALINK STBY 23 ACARS STBY 24 COMPANY ALERT 25 HYD ELEC PUMP 26 CABIN READY 27 PARK BRK 28 ELEC EXT PWR 29 NW STRG DISC 30 SPEED BRK 31 WASTE PANEL 32 REFUEL PANEL 33 DEST EFOB 34 TCAS STBY 35 ENG A.ICE 36 WING A.ICE 37 ICE NOT DET 38 HI ALT SET 39 IGNITION 41 ACARS MSG 42 ACARS CALL 43 ACARS ALERT 44 COMPANY MSG 45 COMPANY CALL 46 SATCOM ALERT 47 PACK FLOW 48 APU AVAIL 49 APU BLEED 50 PRED W/S OFF 51 GPWS FLP OFF 52 TERR STBY 53 ROW/ROP OFF 54 TERR OFF 55 T.O SURV OFF 56 RAT OUT 57 BRK FAN 58 RAM AIR 59 OXY PAX MASKS DROPPED 60 X FEED OPEN 61 VHF3 VOICE 62 HF VOICE 63 AUDIO SWTG 64 HF DATA OVRD 65 EFIS SWTG 67 BKUP SPD/ALT 68 ADIRS SWTG 69 FM SWITCHINGW 70 EMER GEN 71 FLT L/G DOWN

The indication of GW and GWCG is calculated by the FQMS based on ZFW, ZFWCG and the fuel in the tanks! So it has to be indicated at SD permanent data even if no BLOCK is entered. It always indicates the current real GW and GWCG. So during refuel process this values are changing. That is also the reason why GW, CG and FOB are blank in the FUEL LOAD page until engine start as mentioned in another topic:

FIRST: Prior engine start, the FMS has to use the BLOCK FUEL of the FUEL&LOAD page for it's calculations! With engine start it will switch to the measured fuel quantity inside the tanks. Currently the FMS is always using the FUEL from tanks. That's just wrong. With this pilots can't do any preparation and prediction checks, while refueling is in progress. Side note: Currently we don't get any predictions until BOCK is entered, but then it is not used. SECOND: ALTN fuel shouldn't be negative. The calculation is in this case just bogus. I think you just mixed up the values of ALTN FUEL and ALTN EFOB. In this example ALTN FUEL should be 4T ALTN EFOB should be -52.3T This will also explain the error 1. for MIN FUEL AT DEST = ALTN + FINAL That should be 6.2T and not -50.1T 2. for (PREFLIGHT) EXTRA = BLOCK (or FOB, after engine start) - TAXI - TRIP - MIN FUEL AT DEST - RTE RSV That should be 10.7T and not 67T THIRD: TOW and LW are missing. TOW Indicates the Takeoff Weight (TOW). Before engine start: TOW = ZFW + block fuel - taxi fuel After engine start: TOW = GW - taxi fuel In flight: TOW = GW LW Indicates the Landing Weight (LW). Before engine start: LW = TOW - trip fuel After engine start: LW = GW - trip fuel - taxi fuel In flight: LW = GW - trip fuel FOURTH: Behind the ALTN FUEL has to be an ALTN flight time indicated. That time will add to the DEST arrival time and result in the ALTN arrival time, which is in the lower example nonsense. If the calculated ALTN FUEL is overwritten by crew, the ALTN flight time and the ALTN arrival time will be dashed. FIFTH: The double dots ":" in time values are dark blue.

The F-PLN has to show predictions also for the TMPY F-PLN. Currently predictions are only calculated for the active F-PLN.

Top line GW, CG and FOB has to remain dashed until engine start! RTE RSV % and FINAL TIME default values have to be indicated as soon as FROM/TO is entered.

And some special case....HF with alt constraint has to be indicated like an HA and has to be handeled like an HA Holding:

nil

There is a problem, how the FMS is decoding turndirection and indicating it in F-PLN. 1. Example: RJBB 24R SOVRI1 Departure (JEP) In F-PLN the TURN right arrow is behind MUMSU. That's wrong, it has to be behind 500, because at WPT 500 is the mandatory turn to right. In the Navdata the turn direction is coded for the DF leg. That indicates the drawn leg has to be right hand turn, but turning point is the point 500. 2. Example: EDDV 09L ILS (LIDO) In F-PLN the TURN right arrow is behind NIE. That's wrong, it has to be behind HAD15, because at WPT HAD15 is the mandatory turn to left. Also at NIE is a righthand Holding. In the Navdata the turn direction is coded for the DF leg. That indicates the drawn leg has to be left hand turn, but turning point is the point HAD15. 3. Real example: WARR 28 VOR This is a real example from an A320 and older AIRAC. But the logic is the same for A320, A330, A350. There the turn right was also coded in the DF-leg.

On ground it’s not working. So it seems that the light is connected to a simvar “on ground” or something like that. That shouldn’t be the case. Also according technical documentation the LED of the ice indicator is “green”.

Ok, today 1.08 it's working but only in the ICE IND setting.

The HF Holding is wrong displayed in F-PLN. Example was EGKK. In this case the holding FIX "MAY" is missing. It was also missing at the ND.

This topic will cover issues with HOLDING and the example is created with SIM NAVDATA (JEP and LIDO code some procedures different, so LIDO contains the HM and JEP not). I start with the DATABASE HOLD for a GoAround-procedure EDDV-ILS09L. 1. Issue HOLDING PATTERN WITH A MANUAL TERMINATION (HM) has to consist of 2 lines in the F-PLN. The DATABASE HM is currently indicated with one line. 2. Issue The white SPD label is missing 3. Issue The HOLD R shoulnd't have a turn indication arrow. The R indicates already the turn direcion. 4. Issue Distance of 0 is missing 5. Issue When entering that existing HOLD from a non tmpy f-pln it's indicated in TMPY- mode. That's wrong, it has to be indicated in a "normal state". It will switch to TMPY mode, when anything is entered/changed. 6. Issue Top left the holding pattern type has to be DATABASE, COMPUTED or MODIFIED. In this case DATABASE as nothing was changed. 7. Issue It shouldn't read HOLD at HOLD R. It should be HOLD AT NIE in this case. 8. Issue DATABASE/COMPUTED button logic is not working correct. When pressing COMPUTED, DATABASE should get avail to be able to revert to DB values. At the same moment COMPUTED has to be unavail, because it' now computed and the top left indicates now computed. When anything is changed manually, both buttons get's avail (database of course only, if it's in the DB) and top left indicates modified. Now also a HM, but this time MANUAL HOLD (HM is the only type you can manually insert (HF and HA are only avail via NAV-DB) in F-PLN: Same issues as above issue 2 and 4,5,6,7,8 9. Issue first and second WRB point has to keep it's previous speed of 308 10. Issue When entering the HOLD via the second WRB and editing it created a second hold. shouldn't happen. 11. Issue Prior takeoff the label has to be TIME, not UTC 12. Issue For Holdings part of the active F-PLN there have to be predictions for UTC/TIME and EFOB 13. Issue (SPDLIM) shouldn't be there in F-PLN. Just teh magenta speedchagne dot at the ND. (SPDLIM) is only for altitude related speed limit. 14. Issue White has to be HOLD R and the following PAM. SPD label is missing In the second PAM line, there should be the target speed and not the repeating sign " for the altitude, but numbers 15. Issue White has to be HOLD R and the following PAM. The first PAM has still to be there as from WPT

The missing picture from sim and more points: 6. The label of teh TO-WPT has to be yellow, not white (NUDG5Z) 7. Departure is missing the rwy altitude

Ok, found a Photo. Topic can be closed. Thank you.

The question is how the tool determines the position. Contact point of the gear, Datum reference of the model? Maybe the tool has just to take into account some offset by itself.

Hi, thanks for your feedback. It' might be software version related, but not directly an airline option. I can't imagine that airbus changed the layout of that page between two software versions. I never saw the currently modeled version. Can you please check back with the devs/advisors/resource photos? Can you maybe post a picture of the ressource? I'm always willing to learn something new.

I did today a flight into Tokyo and discovered a lot of bugs, all related to LDA approach. This will be now a longer post. Let's start: 1. ARRIVAL page is missing FREQ and LS--> IKL and 110.1 2. NAVAIDS page shouldn't indicate DESELECT FLS, because there is no FLS possible for LDA. Expected is following: 3. At less then 300NM direct distance to the destination airport the FMS has to autotune the LS (see also in this post): 4. Manual tuning was not easy, first it tuned the wrong IKL (wrong freq), then it offered a list of two, and at third try it offered a list with 3, including the correct one. I would expect a list of all availabel IKL at the first try. So your database built in the backend is slow or incomplete, or something else... 5. The CLASS has to indicate the correct type. If the ILS has an DME it's ILS/DME and not just ILS: 6. Wrong landing capability was indicated at FMA. APPR1, not F-APP for LOC-FPA 7. FPA was missing the angel at FMA: -3.0°

Ok, will try it that way...thanks.

@richboy2307 or @haza2 anything you can do in regards to the quota?

@Eddie I need your help. I have a problem with the forum, because I reached my quota for attachments. Please, is there a option to rise the limit for me, else I can't report any more issues.

After inserting a departure it should be ERASE TMPY* and not UNDO* The departure RWY shouldn't have a diamond at the right The lines top, left and below of the TO-WPT diamond should be also yellow in TMPY mode The TRK and DIST for the TO WPT, should be also yellow in TMPY mode the dashes at the bottom should be also yellow in TMPY mode

the shouldn't be units behind LENGTH and CRS EOSID has to be dashed, as long as no RWY is selceted If a RWY has ILS it has to be indicated in the RWY dropdown selection after selection of RWY, the FREQ/CHAN has to be prefilled with ILS FREQ SID drop down menu has to offer up to 12 entries, prio scroll requirement If NONE SID is selcted, the default leg should be a VA-leg and not CA, and should be 1500ft above ground (THR alt + 1500)

A picture of the default display ALIGN ON REF:

There shouldn't be any red area or white marks, with FADEC off.

The upper part (Engine) should have a different layout: