Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Der Michel

Member
  • Joined

  • Last visited

Everything posted by Der Michel

  1. 1. The LSK2L and 2R have to be blue, as the values can be edited by pilot. 2. Whne LSK1R is pressed, the values have to vanish 3. The logic need to be adapted. The ini A340 has GPS, so this logic has to be implemented: "The preferred way of initializing the ADIRS is to use the GPS position, because this does not require any flight crew intervention. Less than 1 min after setting the ADIRS to NAV, the INIT page displays the GPS position without displaying the ALIGN IRS prompt. If the flight crew enters a CO RTE or FROM/TO, the INIT page displays the departure airport reference-point coordinates, and the ALIGN IRS prompt appears. If this prompt key is not pressed, the ADIRS is initialized to the GPS position at the end of the alignment time. At any time during the alignment, the flight crew can manually adjust the coordinates displayed on the INIT page. The ALIGN IRS prompt reappears. If the ALIGN IRS prompt key is pressed, the coordinates displayed on the INIT page are sent to the ADIRS for initialization. This is the alternate method for ADIRS initialization, when the GPS position is not available. A normal alignment takes between 5 and 10 min (depending on the local latitude). At latitudes between 73° and 82° (North or South), the alignment takes about 17 min. The ADIRS cannot be aligned beyond 82° (North or South). A fast alignment takes about 30 s, and it is used for improving the ADIRS initial position accuracy, when time is limited."
  2. 1. As already mentioned, the page layout is just wrong. 2. The Titel will change to INIT FUEL PREDICTUION, when ZFW and BLOCK is entered. ZFWCG is not required for that.
  3. 1. When LSK2R INIT request is pressed, only the asterix has to disapear, not the whole text. 2. LSK1L and LSK1R becomes green after engine start, prior it's blue text. 3. When CRZ ALT is reached, the CRZ TEMP has to be dashed
  4. Hi, this will be the start of a series of topics regarding issues with the FMS pages. Still the work assumes that ini switched from P4 to P3 since update 1.02. Please change the menu layout. You already replaced ACARS with ATSU at LSK2L. But if ATSU is used it has to be at LSK6L. Also add LSK5L SAT for airplanes equipped with SAT.
  5. Here are now two correct pictures for the P3:
  6. The lat post contains pictures from wrong version. Stick to FCOM images from first post.
  7. and the next page: FIX INFO should now have only 2 pages and no support for RADIUS
  8. Der Michel replied to tiagofelix's topic in Systems
    Yes, that's correct. They downgraded from Honeyell Release1A P4 to Honeywell P3. Only the Release1A versions have the more complex page design.
  9. Hi ini Team, after my still open long list of A350 reports, I did the step and also bought your A340. I was happy to see, that you did the step and decided to model a Honeywell FMGS instead of Thales because most out addons have a Thales FMGS. Now I noticed that you changed with the update from 1.01 to 1.02 also the modeled FMGS version. You downgraded from FMS2 HONEYWELL Release 1A P4 to FMS2 HONEYWELL P3 and adapted the page layout to the older system. What I noticed, that this step is incomplete. You have still to change: INIT B FUEL PRED P.S.: I also noticed plenty of bugs in your A340 FMGS. I'm still not sure if should takle it and report these bugs. A350 bug report was/is still useless. It takes a lot time to test and report. Take one obvious one: It's still not possible (like in A350) to enter a departure in the ALTN-FPLN. You have to copy the active FPLN destination airport as origin in the ALTN-FPLN.
  10. Also the APPR was somehow a wild ride up and down, while the airplane was trying to keep speed and glideslope. Is GSmini implemented?
  11. Some more items during APPR: - DME distance is not indicated - GA is green instead of blue at the ND (maybe because the system thinks I'm doing a GA, but then PERF should show the GA page and F-PLN should also an activated GA F-PLN, no longer blue and with predictions.) So the GA logic is also somehow not working correct.
  12. SIM DEFAULT navdata. RWY part of GA, is wrong as already known. But where do the 3000 for HAD54 come from? If it's a WINDOW constraint...in F-PLN has to be a magenta "WINDOW". But to my knowledge it's coded with "at 1460" in navdata. At the ND the ALT constaitns shouldn't be indicated after the FAF for ILS APPR At the APPR selection page the ILS freq and IDENT is not shown note: I changed the constraint type at HAD54 manually
  13. Still an issue...no entry is possible according FCOM DSC-46-ATC-20-50
  14. Still an issue in 1.09.
  15. 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
  16. 1. The MEMOS are in the wrong order. Correct is: PARK BRK ON ELEC EXT PWR N/W STEER DISC GND SPLRs ARMED APU BLEED or APU AVAIL SEAT BELTS NO PORTABLE DEVICES or NO SMOKING or both? NO MOBILE ADS-B TRAFFIC ON maybe as last? 2. Also "GND SPLRs ARMED" shoud have small "s" at the end. 3. Can we please get "NO PORTABLE DEVICES" instead of "NO SMOKING"? Or are both required with this modeled combi switch at the OVHD? If you have an A350 mech in your team, he could check the ELSD document.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.