Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Airbus A320neo/Development

From FlightGear wiki
Jump to: navigation, search

Back to A320neo

ToDo List

Electrical

Files
/Nasal/electrical.nas - gitorious/airbus-aircraft/a320neo/master/Nasal/electrical.nas
Notes
Aircraft already uses Syd Adam's Jet Electrical system.
To Do
Move Nasal file to a dedicated directory in the Systems folder?

Hydraulic

Asigned Developers
Narendran
Branch name
develop
Files
All Hydraulic files in /Systems/Hydraulics Directory
Notes
Will start work on the hydraulic system as soon as the cockpit is ready

Instruments

Assigned Developers
Jon
Narendran
Branch Name
develop
Notes
PFD - Rebuild 3D Instrument, use better textures and markers - COMPLETE
Upper ECAM (EICAS) - Rebuild 2D Instrument with latest A320 ECAM Layout (3 section)

Pneumatics

Asigned Developers
Narendran
Branch name
develop
Notes
Include basic pneumatic air pressure system, also include system cooling functions.


Fly by Wire

Asigned Developers
Narendran
Jon Ortuondo (Bicyus)
Polly
Branch name
fbw-devel
Notes
Basic airbus flight conrol laws and flight phases/modes work. FBW converts pitch-rate, roll-rate and g-force (over 210 kts) and converts to control surface outputs using pids. Also, when stick is neutralized, fbw shifts to stabilizer pids where trimmers maintain pitch and bank angle.
Files
Systems/Airbus-fbw/Airbus-fbw.nas - gitorious/airbus-aircraft/a320neo/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.nas
Systems/Airbus-fbw/Airbus-fbw.xml - gitorious/airbus-aircraft/a320neo/fbw-devel/Systems/Airbus-fbw/Airbus-fbw.xml
To Do
Move fbw.nas and a320-fbw.xml to common Systems directory. - DONE
Update FDM from Airbus-fbw branch
Further tune PIDs (Polly/Jon?)
Implement mechanical backup law (requires better systems)
Study and Implement Flare Mode for NORMAL LAW

FMGC, FCU and mCDU

Asigned Developer(s)
Narendran
Branch name
flight
Notes
Using data from smart cockpit and equicom. [1]
Making a whole new Autopilot/Route Manager system. < Most of this is complete, but the PIDs need to be played with. (Polly)
FCU is basically just the old 'Mode Control Panel' but that too requires some extra scripting.
Resources
Equicom mCDU Emulator [2]
SmartCockpit FMGS Doc [3]
SmartCockpit Systems Briefing [4]
SmartCockpit Autoflight Systems [5]
Completed Sections
FMGC (AP1, AP2, NAV, A-THR)
FCU (aka. MCP)
FMGC (WP Transition Manager)
mCDU > DATA
mCDU > F-PLN
mCDU > LAT REV A
mCDU > VER REV (SIMPLE)
mCDU > INIT A
mCDU > FLT SRC
mCDU > INIT B (FUEL PRED)
mCDU > RAD NAV
Sections in Progress
mCDU > LAT REV B (TP)
mCDU > WINDS - Might have to temporarily simplify this as I'm not exactly sure how to exactly use these for speed and time calculations on the F-PLN yet.
mCDU > PERF
Remaining Sections
mCDU > DIR
mCDU > PROG
mCDU > MCDU MENU
mCDU > WP SRC
mCDU > NAVAID SRC
mCDU > RWY SRC
mCDU > SEC F-PLN
mCDU > AIRPORT
mCDU > ATC COMM

ECAM procedures and Alarms systems

Asigned Developers
Jon
Branch name
develop
Notes
Functionalize ALL ECAM Pages :P

New Cocpit Model & xml

Asigned Developers
Narendran
Jon A. Ortuondo (bicyus) - xml
Project > Repository > Branch
FlightGear Airbus Development > airbus-a320neo-devel ([6]) > flightdeck
Files
All Flightdeck models are in root
Notes
Basic shell, panel, glaresheild, sidesticks, seats and pedestal models complete. These have also been textured.
Overhead panel will be derived from the old one but model will be improved
Cockpit has been ported into FlightGear
To Do
Animations and re-positioning of instruments - STARTED
Re-make PFD and EICAS? (current versions are not too realistic)

Navigation Display

Asigned Developers
Scott
Branch name
develop
Notes
The nav display is common to the A320, A330 and A340 series, so ideally would be shared between all three. Using the C++ NavDisplay instrument available in FG 2.6, Scott has created a full-functioning display for the A380, which can be adapted for the A320 with minimal effort, I hope. (It's probably not possible to share the actual XML between the A320/340 and the A380, alas). Contact James or Scott before spending time on this task, please.
I checked up and found that the nav display is common for all airbus aircraft from A320 to A380, which means we already have a fully functional nav display from the A380. All we'd need to do now is port it (which'd probably include re-sizing) into hte A320neo.
Status
Base files applied
resolving minor adjustments on each of the "mode" displays
committed ARC/ROSE NAV, VOR, LS modes, supports WPT, ARPT, NDB, VORD EFIS switches

Low Priority / Unstarted

Rembrandt Lighting

A319neo and A321neo interior

Please edit if anyone wants to take up any unstarted sections.

Proposals

Directory structure

A320neo
└── Systems
    ├── electric
    │   ├── left_bus.nas
    │   └── right_bus.nas
    ├── fbw
    │   ├── Airbus-fbw.nas
    │   └── Airbus-fbw.xml
    └── hydraulic
        ├── blue.nas
        ├── green.nas
        ├── hydraulics.xml
        └── yellow.nas

Alternate Nasal Only Structure

A320neo
└── Nasal
     ├── electrical
     │   └── electrical.nas
     ├── pneumatic
     │   └── pneumatic.nas
     ├── hydraulic
     │   └── hydraulic.nas
     └── mCDU
         ├── main_loop.nas
         ├── functions.nas
         └── navdata.nas