CLS FMC (Flight Management Computer) Requirements
This is for Microsoft Flight Simulator.
--------------------------
CLS is a small company founded in 2005. We create addons for MS flight simulator as an extented hobby. This job is for someone who is willing to work together with us to create a good end result. I do not know how much time will be involved as I am no programmer. You will work together with 2 of our XML programmers as well as people who can explain the proper functioning of the FMC to you. Understanding the entire workings of an aircraft is not a requirement.
We do not have a main office, so you will work at your place. Communication mostly by email, but also our own private forum board.
Payment with completion of the project. You will deliver us the source and permit CLS to use the "product" in all our projects (commercial).
If cooperation is well and the end result good we might have a few more jobs for in the future. No promises.
Our budget for this project is 1800$.
If you are interested, you may contact me (albert.bouwman <at> gmail.com for more information. We can also deliver you more information on programming the gauge (tutorials) as well as more information about the exact project.
-----------------------------
1) We want an FMC to be written in as much XML code as possible. We do this ourselves.
The FMC needs to have the ability to program a flight plan, edit a flight plan and access the waypoint data from a flight plan.
The primary problem is we can not create, access or edit FS flight plans in an FMC written in XML. Also, XML gauges are unable to
read data files for obtaining the required navigation data or store a flight plan.
The ability to program and edit a flight plan, and access the waypoint data from a flight plan, can be achieved using a gauge
written in C++. This ‘core’ gauge would have a common set of functions which would be applicable to the entire Airbus range. Only
the XML interfacing gauges (inputs and outputs) would require customizing for each aircraft type.
Other requirements are the ability to program climb altitude steps, the angle of climb and the speed. These step points will also be
in the flight plan as points to begin an ascent, descent or hold at given altitudes. Also required are fuel burn calculations.
2) Envisaged FMC operation is as follows.
The main graphic interface is produced by an XML coded gauge. When various areas of this graphic are clicked, L:Variables are sent
to a central 'core' which is programmed in C++ and will interact with the L:Variables. The 'core' will also output L:Variables to
feed information to the FMC graphics screen and to other gauges.
The ‘core’ will be able to read nav data files to obtain waypoint information and act as a storage area for the Flight Plan.
Output L:Variables will be used by the AutoPilot, MFD (moving map and waypoint data) and PFD (speeds, angles, altitudes, etc.).
The FMC obtains navigation data (ICAO code, runway altitude, Lat, Long) from separate data (usually text) files. FMC's to date are
not able to access the nav data built-in to FSX. Actually, this may be old information. Latest consultations with people
‘in-the-know’ say it is possible to access the nav data built into FSX. This will be researched together.
We can supply a list of required L:Variables.
