Project FMC simplified for Project Airbus

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

fdd_fr wrote:I can send you by mail in 2 hours, KSTS csv files, if you are ok to test airport.
ok, I´ll look into the airport database for KSTS
fdd_fr wrote:I posted your problem on Pilote-virtuel, because many members of this forum, who help me to debug, have Win 7. I hope to get a quick answer.
Thanks in advance.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Sample :

FSX basic flight plan created when starting flight :
Image

When you do a savegame during your flight ("ICAO to ICAO"), you have :
Image


You can see that FPLN file is bigger, because the gauge ovewrite with SID/STAR/Approach waypoints, and the CSV file is the FMC data


FSX FPLN file updated by the FMC :

Code: Select all

<?xml version="1.0" encoding="UTF-8"?>

<SimBase.Document Type="AceXML" version="1,0">
    <Descr>AceXML Document</Descr>
    <FlightPlan.FlightPlan>
        <Title>KMRY to KSTS</Title>
        <FPType>IFR</FPType>
        <CruisingAlt>6000.</CruisingAlt>
        <DepartureID>KMRY</DepartureID>
        <DepartureLLA>N36° 34' 59.74",W121° 50' 0.03",+257.</DepartureLLA>
        <DestinationID>KSTS</DestinationID>
        <DestinationLLA>N38° 30' 9.14",W122° 48' 20.87",+125.</DestinationLLA>
        <Descr>KMRY, KSTS</Descr>
        <DeparturePosition>28L</DeparturePosition>
        <DepartureName>Monterey Peninsula</DepartureName>
        <DestinationName>Charles M Schulz - Sonoma Co</DestinationName>
        <AppVersion>
            <AppVersionMajor>10</AppVersionMajor>
            <AppVersionBuild>61637</AppVersionBuild>
        </AppVersion>
        <ATCWaypoint id="KMRY">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N36° 34' 59.74",W121° 50' 0.03",+257.</WorldPosition>
            <ICAO>
                <ICAOIdent>KMRY</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="RW28L">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N36° 35' 13.21",W121° 50' 34.60",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>RW28L</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="HEKIV">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N36° 36' 31.09",W121° 54' 30.24",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>K2</ICAORegion>
                <ICAOIdent>HEKIV</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="UBOBY">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N36° 39' 41.40",W121° 54' 53.100",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>K2</ICAORegion>
                <ICAOIdent>UBOBY</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="OSI">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N37° 23' 32.99",W122° 16' 52.68",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>K2</ICAORegion>
                <ICAOIdent>OSI</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PYE">
            <ATCWaypointType>VOR</ATCWaypointType>
            <WorldPosition>N38° 4' 47.11",W122° 52' 4.18",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>K2</ICAORegion>
                <ICAOIdent>PYE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PYE32">
            <ATCWaypointType>User</ATCWaypointType>
            <WorldPosition>N38° 14' 23.76",W122° 45' 43.52",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>PYE32</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="LUSEE">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N38° 19' 18.77",W122° 42' 31.20",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>K2</ICAORegion>
                <ICAOIdent>LUSEE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="EDOVE">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N38° 21' 28.80",W122° 43' 40.92",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>K2</ICAORegion>
                <ICAOIdent>EDOVE</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="PIGPN">
            <ATCWaypointType>Intersection</ATCWaypointType>
            <WorldPosition>N38° 24' 55.100",W122° 45' 32.17",+000000.00</WorldPosition>
            <ICAO>
                <ICAORegion>K2</ICAORegion>
                <ICAOIdent>PIGPN</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="RW32">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N38° 30' 8.38",W122° 48' 20.44",+000000.00</WorldPosition>
            <ICAO>
                <ICAOIdent>RW32</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
        <ATCWaypoint id="KSTS">
            <ATCWaypointType>Airport</ATCWaypointType>
            <WorldPosition>N38° 30' 9.14",W122° 48' 20.87",+125.</WorldPosition>
            <ICAO>
                <ICAOIdent>KSTS</ICAOIdent>
            </ICAO>
        </ATCWaypoint>
    </FlightPlan.FlightPlan>
</SimBase.Document>




And here the contains of the FMC backup .CSV data file :

"Aircraft Ident","Airbus","A320"
"Save Flight Plan","1."
"Departure Aircraft Position","1.","28L"
"Flight Plan File",,"C:\\Documents and Settings\\Fdd\\Mes documents\\Fichiers Flight Simulator X\\IFR Monterey Peninsula to Charles M Schulz - Sonoma Co.PLN"

"Departure Airport : ","KMRY"
"Departure Airport Elevation : ","257."
"Departure ICAO region : ","K2"
"Departure Position : ","28L"
"Destination Airport : ","KSTS"
"Arrival Airport Elevation : ","125."
"Destination ICAO region : ","K2"
"Trip total Distance : ","132.23"
"Distance Remaining : ","63.461"
"Altitude Descent Target : ","6000."
"Descent Target distance : ","0."

"Current Flight settings : "
"Optimal Flight Level : ","172."
"FMS enabled : ","1."
"FMS init OK : ","1."
"FMS TakeOff Init OK :","0."
"Current flight phase :"
"Aircraft takeoff state","1.","0=Takeoff is not completed : SFCC in Ground mode 1=had takeoff : SFCC in flight mode"
"Takeoff phase","5.","-1=not cleared 0=Ready 1=takoff go 2=Aircraft is airbone 3=THR RED ALT reached 4=Initial acceleration 5=Aircrat is above 10000ft. Takeoff is completed"
"Aircraft Climb","0."
"Aircraft Climb phase","4.","0=aircraft is below 10000ft 1=Climb acceleration 2=Aircraft climb 3=Climb is completed 4=descent is engaged"
"Aircraft cruise","0."
"Aircraft descent","1."
"Aircraft Descent phase","4.","1=initial descent engaged 2=aicraft is above conjunction altitude 3=aircraft is between Conjunction altitude and 18000ft 4=aircraft is below 18000ft"
"Aircraft Approach phase","0."
"Callout 80kts : ","1."
"Callout V1 : ","1."
"Callout Vr : ","1."
"Callout V2 : ","1."
"Callout Check Speed : ","0."
"FMS SETUP : "
"TakeOFF Page : "
"Runway Takeoff : ","28L"
"Takeoff V1 Vr V2 : ","119.","134.","141."
"SRS Speed : ","156."
"GPS Nav Flag : ","1."
"Takeoff Runway Ok : ","1.","28L"
"Cost Index Value : ","1.","40."
"Takeoff THUST mode 1=TOGA 2=FLEX : ","2."
"Flex To Temp setting : ","1.","38."
"Takeoff Flaps Config : ","3.","0=clean 1=Slats1 2=1+F 3=1+2 4=3 4=full"
"Takeoff Heading : ","0.","278."
"LNAV Engage Altitude : ","1.","0."
"Thrust Reduction Altitude : ","1.","1700."
"Acceleration Altitude : ","1.","1700."
"Econ Thrust : ","1."
"EXPEDITE : ","0."
"N1 climb Thrust Below FL100 : ","1.","83.212"
"Climb Speed below FL100 : ","1.","250."
"Climb Speed Green Dot : ","0.","0."
"Constraint Altitude : ","0.","0."
"Constraint Speed : ","0.","0."
"QNH Transition : ","1.","18000"
"QNH State : ","0.","0=barometric value 1=STD"
"CLIMB Page : "
"Climb Thrust ECON : ","1."
"N1 Climb Thrust above FL100 : ","1.","82.612"
"Climb Econ Thrust : ","1."
"Climb Thrust Expedite : ","0."
"ECON Flight Level : ","1."
"Flight Level 1 : ","1.","130."
"Climb speed IAS value above FL100 : ","1.","350."
"Climb Speed Econ : ","1."
"Conjunction IAS/MACH Altitude : ","1.","29000"
"Climb Speed MACH Value above Conjunction Alt : ","0.","0."
"Climb Speed MACH Econ : ","0."
"CRUISE Page : "
"Cruise ECON Speed IAS : ","1."
"Cruise Speed IAS FL1 : ","1.","350."
"Cruise ECON Speed MACH : ","0."
"Cruise Speed MACH FL1 : ","0.","0."
"Change Flight Level : ","0."
"Flight Level 2 : ","0.","0."
"Weight Flight Level 2 Kg and Pounds : ","0.","0.","0."
"Cruise Speed FL 2 Mach : ","0.","0."
"Top Of Descent : ","1.","0."
"Descent Constraint : ","0."

"FCU Settings : Knob FCU 0=selected mode 1=managed mode "
"SPEED : ","1."
"HDG : ","1."
"ALT : ","1."
"Altitude Constraint : ","0."
"Autopilot Pitch mode : ","1."
"V/S mode : ","1."," 0=Selected 1=managed"
"Speed Managed IAS : ","300."
"Speed Managed Mach : ","64.231"
"Aicraft is Above Transition : ","0."
"user FCU altitude Flag : ","0."
"ILS Land Phase : ","0."
"ILS Mode Armed : ","0."
"Approach Mode Armed : ","0."
"Localizer Armed : ","0."
"Approach type : ","1."
"Landing : ","0."
"Flare : ","0."
"Roll Out : ","0."
"Number of Waypoints : ","12."
"Offset waypoint list : ","0."
"Engine 1 Generator : ","1."
"Engine 2 Generator : ","1."
"DC Volts Selector : ","0."
"Inertial Sys on/off : ","0."
"Inertial Data : ","0."
"Panel Cabin Light : ","0."
"Engine 1 Bleed : ","0."
"Engine 2 Bleed : ","0."
"APU Bleed : ","0."
"VOR Switch 1 : ","1."
"VOR Switch 2 : ","1."
"Index of Active Waypoint : ","5."
"Checklist ID : ","13."
"Aircraft is above Mach Altitude MACH mode is engaged : ","0."
"Speed/MACH button pushed : ","0."
"User specific landing frequency : ","0."
"FSX landing frequency : ","109.3"
"SFCC flag Flaps on ground : ","0."
"SFCC : Aircraft is airborne : ","1."
"SFCC Flaps config before takeoff : Aircraft is on ground : ","0."
"Zero Fuel Weight ZFW : ","54437"
"No Smoking Switch State : ","1."
"Seat Belt Switch State : ","1."
"Engine 1 Fuel burned since departure in Pounds : ","1216."
"Engine 2 Fuel burned since departure in Pounds : ","1226.1"
"Index first approche waypoint if Go Around : ","0."
"Altitude first approach waypoint if Go Around : ","0."
"Speed first approach waypoint if Go Around : ","0."
"Autopilot engaged : ","1."
"AutoThrottle engaged : ","1."
"Autopilot Hold Altitude : ","6000."
"Autopilot Altitude Lock : ","0."
"Autopilot heading value : ","278."
"Autopilot Heading Lock : ","0."
"Autopilot GPS Drives NAV1 : ","1."
"Autopilot Nav Lock : ","1."
"Autopilot AirSpeed Hold mode : ","0."
"Autopilot Mach Hold mode : ","0."
"FPA mode engaged : ","0."
"FPA Value in degrees : ","0."
"Final Approach Altitude unlocked : ","0."
"User descent Altitude Target Flag","0."
"User descent Altitude Target value","0."
"User Descent Altitude Target Ok","0."
"Arrival Altitude without STAR","3100."
"Hydraulic Green","1."
"Hydraulic Yellow","1."
"Hydraulic Blue","1."
"Fuel On Board at Departure in Pounds","18860"
"Aircraft is changing FL Cruise ","0."
"Approach Gradient User Value","-3."
"Reserved","Not used on this version"
"Reserved","Not used on this version"
"Reserved","Not used on this version"
"Reserved","Not used on this version"
"Reserved","Not used on this version"
"Reserved","Not used on this version"
"Reserved","Not used on this version"
"Reserved","Not used on this version"
"Reserved","Not used on this version"

"SID Loaded : ","1."
"SID data : "
"28L"
"MUNSO 2.OSI"
"278."
"500."
"1700."
"1700."
"6000."
"0."
"0."
"3."
"1.","W","K2",,"HEKIV","0.","0."
"2.","W","K2",,"UBOBY","0.","0."
"3.","V","K2",,"OSI","0.","0."

"STAR Loaded : ","1."
"STAR data : "
"32-14-01"
"PYE Transition"
"ILS/LOC/RNAV/VOR-32 RNAV/VOR-14 RNAV-01"
"1."
"1.","V","K2",,"PYE",,,,"6000",,"0",,,,
"Waypoint has an Holding pattern : ","0."
"Holding Pattern Armed or engaged : ","0."
"Hold pattern is running : ","0."
"Index WPT STAR holding pattern : ","1."
"WPT STAR holding pattern completed : ","0."
"Turn Direction 0=No current turn 1=Left 2=Right : ","0."
"Initial Heading : ","0."
"Opposite leg : ","0."
"Hold Pattern timing : ","0."
"Hold Pattern position : -1=initialisation 0=first turn 1=opposite leg 2=turn back 3=come back init WPT : ","0."
"Waypoint has an DME ARC : ","0."
"Waypoint has a leg turn back (teardrop turn) : ","0."

"Approach Loaded : ","1."
"Approach Data : "
"Transition name : ","PYE"
"32"
"ILS"
"5."
"1","U",,,"PYE32","38.23993289","-122.7620887","3000","220","0",,,,
"2","W","K2",,"LUSEE",,,"3000","200","1","1","321","141","65"
"3","W","K2",,"EDOVE",,,"2700","180","0",,,,
"4","W","K2",,"PIGPN",,,"2000","0","0",,,,
"5","R","K2","KSTS","RW32",,,"255","0","0",,,,
"APPR Waypoint has an Holding pattern : ","0."
"Holding Pattern Armed or engaged : ","0."
"Hold pattern is active : ","0."
"Index APPR WPT holding pattern : ","0."
"WPT APPR holding pattern completed : ","0."
"Turn Direction 0=No current turn 1=Left 2=Right : ","0."
"Initial Heading : ","0."
"Opposite leg : ","0."
"Hold Pattern timing : ","0."
"Hold Pattern position : -1=initialisation 0=first turn 1=opposite leg 2=turn back 3=come back init WPT : ","0."
"Waypoint has an DME ARC : ","0."
"Waypoint has a leg turn back (teardrop turn) : ","0."







"FSX Variables monitoring Values : "

"AUTOPILOT CONFIGURATION"
"Autopilot Armed","1."
"Auto Throttle Armed","1."
"Autopilot AirSpeed Hold mode","0."
"Autopilot Airspeed KIAS Value","300."
"Autopilot Mach Hold mode","0."
"Autopilot Mach Value","0.55"
"Autopilot Heading lock mode","0."
"Autopilot Heading Dir value","278."
"Autopilot NAV1 Lock","1."
"GPS Drives NAV1","1."
"Autopilot Altitude Hold","0."
"Autopilot Target Altitude","6000."
"Autopilot Vertical Speed ft/mn","0."

"Aircraft performances and environement"
"indicated Airspeed","327.48"
"Indicated MACH","0.60372"
"indicated Altitude","12926"
"Verticale Speed Ft/mn","-195.01"
"Total Weight in Kgs","61884"
"Fuel on Board in Kgs","7447.3"
"Flaps Position","0."
"Spoilers Armed","0."
"Ambiant Wind Velocity","6.9815"
"Ambiant Wind Direction","287."
"Ambiant temperature in Celsius","-2."



"A32x series FD-FMC Version beta 1.00 September 2015 - Data save file gauge v1.36 - CSV file format can be read with EXCEL or similar software"
"© François Dore - September 2015"

"LoggerX.dll Module © Robbie McElrath - LoggerX can be included in XMLTools.dll © Tom Aguilo"
"LoggerX Version : ","2."
Without this file, FMC cannot work when you reload your flight.

This file is also an excellent blackbox, if you have a bug, because I know the state of all aircraft systems. This file is very easy to read and you can find all information about your flight.

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

Hi Francois,
thanks for the example of a flight saved file contents.

The read and write rights are already checked in my FD_FMC folder and FD_FMC.ini file .
I recognized 2 missing files per flight saved file group:
....FMS dataSave.csv and A to B.ipcbn

Is this the reason why after terminating FSX but saying "no" and going immediatly back to FSX the FMC and engines are out?

Wulf

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

I believe that ".ipcbin" file is the Active Sky weather savegame.

About Windows rights, have you check the FLight simulator Documents folder (where flight plan are saved) ? Because other user with Win 7 has no problem !

We needs a Win 7 specialist !

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

fdd_fr wrote:About Windows rights, have you check the FLight simulator Documents folder (where flight plan are saved) ? Because other user with Win 7 has no problem !
Also here all rights checked.

I use xmlTools.dll V2 only, not the separate Logger file as required. Is this the prob, because in FSX/Gauges/A320...xml file contain many Logger commands? I can include the LoggerX.dll again, if required....

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Its not necessary.

LoggerX is include in XMLTools and it works, because you can read airport data, that means LoggerX functions works.

This is a problem with your Wind 7 config, not a gauge problem.

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

fdd_fr wrote: About Windows rights, have you check the FLight simulator Documents folder (where flight plan are saved) ? Because other user with Win 7 has no problem !

We needs a Win 7 specialist !

Good news! I´ve found the culprit and now the flight+flightplan is saved in the corresponding .csv file.

- In case of similar trouble I recommend to look at first into the properties from the "Flight Simulator X-Files" folder, where amongst other things the complete data path is displayed.
- This path description has to be adopted in the displayed language and "\\" to be added between each folder as already required.
- I have a german OS WIN7 and all file and folder descriptions on the windows screen are displayed in german, but only the path description in the FMC_ini property is written in english(!). So I had to adopt the engl. path description as displayed in the properties (but with \\).

Wulf
Last edited by wulfbindewald on 08 Oct 2015, 15:45, edited 1 time in total.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

excellent news !

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

A320 panel V1.00: I changed during cruising flight with activated flightplan+FMC the planned STAR+approach to another STAR+approach. The new STAR+approach controlled well the A/C and the remaining cruise and landing went fine.

The issue:
TOD distance information in the checklist display disappeared, please see pic. Bug?
STAR+approach change during cruise generally not allowed and therefore the checklist does not display everything properly?

Wulf
Image

Prosdocimo
Posts: 277
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo »

As I know, but I could be wrong, you should not change the STAR when the last wpy of your plan had been activated (but only before that). As well as the approach should not be changed when the last STAR's wpy had been already activated.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

I will check the code. As Prosdocimo say, it is better to avoid change STAR, if the first waypoint of your previous STAR is active; indeed, in this case, Flight plan can be reset when you delette the previous STAR, and aircraft may turn .

It is possible to do that, but the best way is to switch in HDG mode before delete previous STAR, to hold actual course, and after load the new STAR, use the "WPT+" button on the FMC map to activate the right waypoint, because flight plan is always reset to the first waypoint when you delete a STAR of which a waypoint was active.

I will test and come back to you.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

New FD-FMC "feature" announcement : LOC Approach in back course mode.

I am working on KRDD - Redding airport, which has this type of approach (use the Localizer of the opposite runway to land) :

Image

So, i changed FD-FMC code and now, it can manage this type of approach by activate the autopilot in back course mode (feature exist already for take off).
Function will be available with panel update 1.01.

But from now, for those who create airport files, you can add this feature in your files when required :

Before, you muust check with ADE if ILS has a backcourse Localizer activated :
Image

Checkbox must be checked; This is the case for KRDD, so no change to do on the AFCAD.



In the EXCEL wookbook, Approach tab, Column "B" Approach Type, you have just to write :

LOC-XXX.XXBC

XXX.XX is the ILS frequency of the opposite runway, because FMC cannot get it by the code.

BC to tell at FD-FMC that it must arm the autopilot in Back Course mode.


First test on KRDD in back course mode : all works fine :
Image

I discover that ENTAR is missplaced (2,7Nm too close of the runway !!!) so I must create a new ENTAR wpt.

Francois

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

Back course recognition is a great feature, Francois.

FMC check: BC approach information will be indicated in the FMC approach-menu-page?
FCU check: Shall the user check for the BC approach "ILS" and "APR" or only "LOC"?
Compatibility: Will there be a conflict with the new airport data including BC if the user does not update to V1.01? OOM?

Wulf

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

BC will be in the FMC approach menu page and can be activate by hand if airport approach data has no information
BC approach is only for LOC approach, so only ILS and LOC button to engage;
No conflict if use panel 1.0 with a new airport with BC approach; Only the LOC function will not available for BC approach. Approach will work without LOC.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Back Course Feature added :

Image

Can be activated manually or automatic if airport approach data has information.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Sorry, I had not enough time to publish new and updated airports. That will be next week, with panel update.

After, I will stop temporary airports to complete A318 and publish it.

Francois

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

Cannot wait!

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

one week to wait :)

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

I just had one quick question Francois, how do you install the new night textures for the fd fmc a320?

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

Also, do you happen to know where I could find a user's manual for the a320, it is not on your website.

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

Thx!

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

May I answer your questions
a320_flyer wrote:I just had one quick question Francois, how do you install the new night textures for the fd fmc a320?
I assume the favourite textures are already downloaded from the freenavdbgroup website. Here you go...
1. go into the folder FSX/SimObjects/Airplanes/PA A320FD-FMC_CFM/ or /PA A320FD-FMC_IAE/
2. backup your existing "Texture" folder in the case you go back.
3. Copy the new texture .dds files into the "Texture" folder. Enjoy!
a320_flyer wrote:Also, do you happen to know where I could find a user's manual for the a320, it is not on your website.
Under the assumption again that you have downloaded the new A320 full pack V1.00 from Avsim.com or flightsim.com
pls. have a look into the folder "User manuals ENG-FR".

Wulf

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

Thank you so much wulf, you were very very helpful.

I only forgot to mention that I accidentally deleted the zipped a320 v0,99 folder. So i do not have access to a manual, and would prefer not to download a whole new pack.

a320_flyer

Prosdocimo
Posts: 277
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo »

Have a look at page 24, Post #13 Sep 2015, 17:14
There is the link to the manual still working. I don't know if it is the last corrected version but seems very close.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Sorry. I deleted user manual. I will re-upload it in few hours....


I confirm : A318 expected for this weekend !

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

English user manual in online again : http://freenavdbgroup.com/?page_id=159

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

Thank you so much for all of you help!

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Panel A318 beta 1.10 is online : http://freenavdbgroup.com/download/Pane ... 201.10.zip

Only for user who have downloaded A318 beta 0.99 aircraft pack.

This version is the same than Panel A320 1.0, with A318 performance data, and following new features :

- New displays background, when aircraft is cold & dark
- New LOC approach backcourse mode (see Approach page). You can test it on KRDD airport, runway 16
- PFD ILS scales was displayed when a LOC appraoch was loaded, even if ILS switch was off : Now, ILS scales appears only if aircraft is in approach phase
- Now, if you reject take-off, there is a reset of FMC data, to try a new take off with all callout
- Now, FMC gauge display runways of 3000ft and more in airports information page (4000ft in previous verison)
- XML code improved for better performance and less memmory occupancy

Tell me what do you think of new features, to know if I must to add to the A320 update.

This A318 panel is provided with complete panel (include panel.cfg file), so you must delete your previous panel folder.
I join a new Aircraft.cfg, improved; Use it and copy your [FltSim.x] sections.

The goal of this final test is to check :
- Fuel prediction
- Autoflare performance
- Climb and descent performance
- aircraft behavior.

I think that it would be better to change the VC position (backward....) so as is not a easy operation (I must edit MDL file), please, tell me your think about this position.

Thanks

Good flight


Edit :

For a better Sound experience with A320 and A318, do the following changes;

For A320 CFM (IAE is already ok) :
- Open the "Sound.cfg" file located in the Aircraft Sound.CFM folder.
- replace the following 2 sections :

Code: Select all

[GROUND_ROLL]
filename=Roll
flags=125218
viewpoint=1
panning=0
minimum_speed=15.00
maximum_speed=80.00
minimum_volume=9300
maximum_volume=10000
minimum_rate=0.80
maximum_rate=2
link=GROUND_ROLL1

[GROUND_ROLL1]
filename=Cockpit_Roll
flags=125218
viewpoint=1
That's will improve a take-off ambiance...


For the A318 :
- Copy the file Roll.wav and Cockpit_Roll.wav, located in the A320 CFM or IAE sound folder, in the A318 SOund.cfm folder
- Edit the Sound.cfg file and do the same change as above
- In the [Fuel_pump] section, set the "maximum_volume=" value to 8000 to decrease fuel pump sound level.
- You can decrease also, the Gear and flaps volume level (Better between 8000 and 9000; Actually 10000).


Francois




Francois

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

This aircraft pack does not have an auto-installer right?

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

No auto-installer (I wanted write an setup software, but everybody told me not necessary).

But if you have already the A320, A318 installation requires just to copy aircraft folder. Modules and databse are common to all aircrafts.

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

Thanks for the new A318 Panel beta 1.10, Francois:

Let me give some comments regarding the above mentioned topics from Francois.
I´ve made a few checkflights in KRDD and PAWG (Wrangell, Alaska):


- New displays background, when aircraft is cold & dark
--> W.B.: For me the display colour in cold & dark does not change. The full A318 package 0,99 seems to include another VC textures, which darkens the VC. Is this meant?

- New LOC approach backcourse mode (see Approach page). You can test it on KRDD airport, runway 16
--> W.B.: It works fine in KRDD.

- PFD ILS scales was displayed when a LOC appraoch was loaded, even if ILS switch was off : Now, ILS scales appears only if aircraft is in approach phase
--> W.B.: It would be interesting to know, how the real pilot engages the ILS or LOC or LDA during descent. Today we have to switch manually when the aproach is captured and there is no big reaction time. It sounds a bit playful but if the corresponding and correct ILS, APR or LOC toggles would start to blink 5 times as a "warning" message to engage the lateral path or the glide slope....this would be "practical" and helpful. I remember this discussion in this forum, but I´ve forgotten the pro and contra to this proposal.

- Now, if you reject take-off, there is a reset of FMC data, to try a new take off with all callout
- Now, FMC gauge display runways of 3000ft and more in airports information page (4000ft in previous verison)
- XML code improved for better performance and less memmory occupancy
- Fuel prediction

- Autoflare performance
--> W.B.: Autoflare ok on sea level airport, may be a bit hard touch down and quick pitch to NLG afterwards. I´ll check in KJAC Jackson Hole (6450ft apt. Elev.) later too.

- Climb and descent performance
- aircraft behavior.
--> W.B.: both generally smooth and nothing obvious recognized.

I think that it would be better to change the VC position (backward....) so as is not an easy operation (I must edit MDL file), please, tell me your think about this position.
--> W.B.: A good point. It is really a mess to navigate on ground up to the stairway. I´ve always to leave the A/C to check the correct position.... So my hope is to get this corrected by time ;-).

Wulf

Prosdocimo
Posts: 277
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo »

Hi thanks. I didn't have time to test extensively. However my first impression is very good. I like the background display and background sound but I reduced to 3000 the pump sound (i have also downloaded a better pump sound from flightsim and put times ago into A320, i could provide you the link).

About the view, I changed the zoom factor to 1. To me is ok and I guess it could be better than look into mdl file.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Hi Wulf,

Displays background was only blackcolor previously. Now, there is a texture. But I checked this texture only in VC. I don't know if it is visible with popup display of cockpit 2D.

I am not sure to undestand what you expect with ILS scales or ILS function. Today, you can display ILS scale without engage APPR switch, if you want to do a manual landing... give me the procedure that you expect

Ok, I will try to adapt VC position to A318 by editing MDL VC file.

Thanks for your feedback

Prosdocimo, thanks for your feedback !

Edit : I started to work on A319

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

fdd_fr wrote: I am not sure to undestand what you expect with ILS scales or ILS function. Today, you can display ILS scale without engage APPR switch, if you want to do a manual landing... give me the procedure that you expect
I think I´ve wrongly located my comment to the display ILS scale topic. This topic is fine today.

New ILS topic: I am asking for a method to visualize the switching point for the ILS capture:
It would be interesting to know, how the real pilot engages the ILS or LOC or LDA during descent. Today we have to switch manually when the ILS or LOC or LDA approach should be captured and there is no big reaction time. It sounds a bit playful but if the corresponding and correct ILS, APR or LOC toggles would start to blink 5 times as a "warning" message to engage the lateral path or the glide slope....this would be "practical" and helpful. I remember this discussion in this forum, but I´ve forgotten the pro and contra to this proposal.

Wulf

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

fdd_fr wrote:Ok, I will try to adapt VC position to A318 by editing MDL VC file.
Edit : I started to work on A319
May be the VC position should be also adapted for the A319, as the A/C is short too ;)

Wulf

a320_flyer
Posts: 17
Joined: 28 Sep 2015, 14:55

Re: Project FMC simplified for Project Airbus

Post by a320_flyer »

Ok, thanks!

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Now, I understand what you means wulf; In the AIRBUS FCOM, there is no special message on the PFD for ILS.

But when you display ILS scales with ILS switch, you konw when aircraft receive LOC and G/ signal; you see the magenta vertical bar moves on the compass, that's means that you recive the LOC signal.
When you see the magenta diamond on the vertical scale, that means that you receive the G/S signal.

You can engage APPR button a long time in advance; systems is armed and wait horizontal/vertical capture (readings LOC and G/S in cyan color). When signal is captured, the gauge toggles automatically (readings become green with a "*" symbol that means that signal is captured, but aircraft not yet align.

THis is the reason why I think that is not necessary to add something. But I can add on the Memo message, LOC and Glide Slope signal State (not captured, captured, engaged).

I think that the previous discussion that we had about ILS was to display ILS scale, even if not use ILS or LOC, to have a repairs for land manually; and today, ILS switch is only for display scales on the PFD. It doesn't engage any system.


About VC, you are right, I will have to adjust position in A319 also.

Prosdocimo
Posts: 277
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo »

Hi, I think a memo message could be just a good addition.
A question: where do I change zoom factor to have always 1.00 in vc? In panel.cfg or aircraft.cfg?

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

I use EZdock for my cameras. If you haven't, I think that you must edit the file "Cameras.cfg" located in the main FSX folder.

I think that VC camera must be the [CameraDefinition.002]
set the "InitialZoom=0.7" setting to 1.0.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

I forgot a information about A318 panel posted 2 days ago :

You know that main ECAM lower left checklist messages works fine only if you use FMC; If not, you cannot get the next page sometimes.

I added 2 mouse areas in this left checklist. Click on the right area to switch to the next checklist page, or click on the left checklist area to come back at the previous page.

Francois

Prosdocimo
Posts: 277
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo »

Thanks! I realized there was no mention about it in your last posts. It's a useful tip

wulfbindewald
Posts: 501
Joined: 20 Jan 2014, 21:27

Re: Project FMC simplified for Project Airbus

Post by wulfbindewald »

fdd_fr wrote:I use EZdock for my cameras. If you haven't, I think that you must edit the file "Cameras.cfg" located in the main FSX folder.

I think that VC camera must be the [CameraDefinition.002]
set the "InitialZoom=0.7" setting to 1.0.
Here I found a comprehensive description and defintion of all camera.cfg variables http://www.fstipsandaddons.com/tutorial ... meras.html

The320Pilot
Posts: 354
Joined: 29 Jul 2014, 22:47

Re: Project FMC simplified for Project Airbus

Post by The320Pilot »

Francois, I need your help.

So, I'm coding the runway 31L/R VOR-C approach at SKBO. Should I code the visual part, or just write the code up to the MAPt?

http://www.aerocivil.gov.co/AIS/AIP/AIP ... 20SKBO.pdf, page 83.

Thanks.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

Good question !

I think that you have two ways :

First solution :
You code approach up to MAPT, but ending line by the runway threshold, with the same altitude constaint than MAPT point( but attention, Runway threshold altitude must write in the file in feet above Airport elevation, so you must do : MAPT alt - Airport elevation to get runway threshold altitude to write in the file.
Like this, if pilot forget to disconnect AP, aircraft will not descend after MAPT.

Second solution :
You add two user waypoints as picture above (with PLAN-G). And from MAPT, you keep for these waypoints same altitude constraint that MAPT (runway thershold altitude must be in feet AAL).

Image

In all case, if pilot not disconnect AP, Aircraft will not descend.

Call approach in the file header "VISUAL" and write in the SKBO.txt file that pilot must disconnect AP from MAPT and land by hand.

If somebody has a better idea, you're welcome

Francois

The320Pilot
Posts: 354
Joined: 29 Jul 2014, 22:47

Re: Project FMC simplified for Project Airbus

Post by The320Pilot »

Thanks, Francois. I think I will go by the second option. There is also a RVFP (RNAV Visual Flight Procedure) approach to runway 31R, which has an instrument RNAV portion, and then it has a visual portion with lateral guidance. I think it should be right to code the RVFP 31R visual-part waypoints with the DA, so that when the aircraft call out minimums, the pilot will disconnect the AP and fly the rest of the approach by hand guided by the RNAV waypoints.

Image

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

You are right.

Prosdocimo
Posts: 277
Joined: 10 Oct 2014, 12:05

Re: Project FMC simplified for Project Airbus

Post by Prosdocimo »

I didn't get about vc position, thinking about distance to see clearly instrumentation readings confortable. This is why i talked about zoom level: at 1.0 i can see much better.

I tried to hit a wall with A318 nose and yes the vc position went after the wall... so it would need to be put backwards, if it's not a big time consumption doing it. Anyway they are just some meters backwards so I guess almost nobody would notice the difference thought

The320Pilot
Posts: 354
Joined: 29 Jul 2014, 22:47

Re: Project FMC simplified for Project Airbus

Post by The320Pilot »

New update on SKBO (Bogotá-Eldorado International Airport): the files are ready. I will test how the aircraft performs with the coded SIDs, STARs, and approaches. I expect to send it to François at some point next week.

Want another place to practise high altitude ops: 8360ft-high (2548 metres) SKBO is waiting for you.

fdd_fr
Posts: 1764
Joined: 03 Jan 2012, 16:02

Re: Project FMC simplified for Project Airbus

Post by fdd_fr »

I will move backward the A318 VC, Prosdocimo;

Carlos, I will upload tomorrow new airports
LFML Marseille france
KWYS Yellowstone, realized by Wulf !
KSLC Salt lake city (huge airport)
VIDP New Delhi by Georges
and peharps BIKF Keflavik Iceland

I hope that your SKBO will be ready tomorrow.

fly2001
Posts: 26
Joined: 29 Oct 2015, 22:18

Re: Project FMC simplified for Project Airbus

Post by fly2001 »

Mr. François Doree
En premiére place je voudrais bien vous remercier pour votre immense travaille et pour avoir permettez de l' utiliser sans aucune charge. C´ést vraimente formidable.
Je voudrais aussi bien savoir si´il y a une check list aprés l´ installation du PA Airbus A320 FD-FMC, parce que je ne peux pas user aucune SID & STAR avec le FMS et je ne ç' est pas oú il est ma faut. J´ai essayer l´instalation plusieurs fois mais rien ne va plus.
Je dois m´éxcuser de mon pauvre françois mais je voudrais vous remercier dans votre langue.
Mes meilleurs salutations.
João Pereira

Post Reply