On October 8, 2005 10:15 am, Karsten Krispin wrote:
> Is it possible that you have a manual of the Airbus, or from where do you
> get your ideas?
I don't have any manual on Airbus.  I wish I have.

There are some books in my university's library, as well as some online 
references to help me script the FBW system.  Unfortunately, I haven't got a 
chance to use them yet.

> Because the Airbus-System are working intern more or less in the same way.
> Type-Rating issue on so on...
>
> So, I thought we first write a core. That one could be extended on one hand
> to an A32X/330/340- and on the other hand to an A380 cockpit.
>
> Here, a manual could be helpfull.
While commonality is a well-known strong point of Airbus, it cannot be applied 
to the fly-by-wire system.  The aerodynamic properties of each family of 
aircraft is different, as do the flight control systems.  Even the 
fly-by-wire system is different on each family: the A32X have special 
computers dedicated to each FCS-related task, while the A33X/A34X have 
integrated some of these computers into one unit.  The A380 has even more 
integration in its fly-by-wire system than the former other families.  You 
can't use a fly-by-wire system from one aircraft and expect it will work on 
another.

> I also got an answer from Steve Knoblock.
>
> He said, as you assumed as well, that the XML-Instruments are the one
> displayed in an 3D-Cockpit.
>
> Now there is still one point: When programming an FMC and the to this
> according Navigation Display, we need a possibility to spawn objects on
> runtime to place Waypoints in it and connect them and so on.
>
> Is there a way like in HTML with JavaScripts DOM?
Not that I know of.

Ampere

_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to