> This is what I dont understand what is wrong with the current system
> which can do heading,V/S,wing 
> leveler,vor/loc(nav),approach,and autothrottle
> are these not accurate enough?.
> Also how much more computing power will be required for what 
> ever extra
> detail may be involved.A 3D modeller would not even think of 
> modeling the
> insides of the engine or every rivit in the aircraft for the 
> obvious reason 
> that
> the model would bring the computer to a halt.I am just 
> wondering if this in
> its own way is not doing the same thing.
> Anyway the one question I would realy like answered is what 
> is wrong with
> the current system.If the answer is nothing then why change.
> Famous Saying "if it an't broke don't fix it"
> >

Disclaimer: I don't fully understand the current autopilot system, but I think I get 
the gist of the new proposal.

As I understand it, the proposal is to rework the autopilot so that it is configurable 
within the XML for each aircraft, rather than being buried in the C++ code.
To do this, there is a need for a "controller" that is XML configurable, which can 
have inputs, outputs and "magic numbers" associated either with entries in the 
property tree, or fixed in the XML.

It makes sense to implement as few types of controller as possible, and make them as 
flexible as possible. A PID controller does everything we need for simple controllers 
(wing leveller by aileron, or speed by throttle for instance), and can be stacked (or 
cascaded) for more complex situations. 
It can also have the I and/or D components set to 0 if you want a P, PI or PD only 
controller.
We might also need some simple auxiliary units, such as a "summer" and a "limiter", 
although these could probably be combined into a summer which has the ability to clip 
the output.

There is nothing in the proposal that would make use of this system compulsory.

The current system isn't broken, it just isn't as easy to set up, or as flexible as a 
system could be.

Richard

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to