Steve Knoblock wrote:
Perhaps the autopilot element could include the location of the
Autopilot dialog. Then if the default was loaded it would just load the
existing dialog. If a location was specified, then it would load the
custom dialog.
Something like
systems
autopilot
I decided to look more closely at autopilot behavior after hearing that
one could direct the Wright Flyer on autopilot. Here is the results,
with a discussion afterward about the Autopilot GUI dialog.
* Wright Flyer does follow the default autopilot if settings are made on
the Autopilot dialog.
On Wed, 2005-11-30 at 16:55, Jon Stockill wrote:
Steve Hosgood wrote:
3) It was broken in 0.9.8 but is fixed now. I *think* I may have tried
it in 0.9.9 with the same results. Not sure. Can't check right now.
It'll still be the same. The C172 doesn't use the generic autopilot code
- it
On Thursday 01 December 2005 09:48, Steve Hosgood wrote:
I knew there was an autopilot on the cockpit display, but on my monitor
at home (1024x768) it was a bit difficult to read.
This is a problem for many instruments in many a/c - on higher resolution
screens too. The solution is to make
Folks, was there a bug in the autopilot on the c172 default airplane in
0.9.8?
I fill in the fields and tick the boxes on the Autopilot dialog box,
take my hands off the stick and the bloody thing wanders all over the
sky.
1) Maybe this is an accurate model of the c172 autopilot? :-)
or
2)
Steve Hosgood wrote:
3) It was broken in 0.9.8 but is fixed now. I *think* I may have tried
it in 0.9.9 with the same results. Not sure. Can't check right now.
It'll still be the same. The C172 doesn't use the generic autopilot code
- it has a KAP140 autopilot model - which is controlled by
-- Steve Hosgood wrote:
Folks, was there a bug in the autopilot on the c172 default airplane in
0.9.8?
I fill in the fields and tick the boxes on the Autopilot dialog box,
take my hands off the stick and the bloody thing wanders all over the
sky.
IIRC the C172p uses the KAP140 (or
On Wednesday 30 November 2005 17:34, Steve Hosgood wrote:
or
2) Maybe the c172 doesn't have an autopilot.
It has an autopilot, but you operate it with buttons on the panel, you know,
like in Real-Life[TM].
If the latter, then surely the dialog box ought not to be available (i.e
be greyed
--- Roy Vegard Ovesen wrote:
If the latter, then surely the dialog box ought not to be available
(i.e
be greyed out in the relevant menu).
Is this possible, Melchior, to disable the autopilot menu entry just for
the
C172?
Thanks the Melchior's XML menu changes, I would think the
Hey gang,
I'm starting to prepare to integrate Flight Gear as a surrogate for a real
UAV as part of a UAV control system that I'm developing. We've looked at
several other simulators, but FG seems to be the best one for the job at
hand.
I do have several questions though about the autopilot
On Fri, 27 May 2005 15:26:58 -0500, Curtis wrote in message
[EMAIL PROTECTED]:
Vance Souders wrote:
I want to implement an acrobatic AI autopilot and was debating a few
different ways of tackling the problem. I was thinking of either
creating a spline based system or tuning the
I want to implement an acrobatic AI autopilot and was
debating a few different ways of tackling the problem. I was thinking of
either creating a spline based system or tuning the current autopilot to fit my
needs. In a spline based system, the user can sit in the cockpit as the
plane flies
Vance Souders wrote:
I want to implement an acrobatic AI autopilot and was debating a few
different ways of tackling the problem. I was thinking of either
creating a spline based system or tuning the current autopilot to fit
my needs. In a spline based system, the user can sit in the cockpit
Ive written a small class to load waypoints into the
autopilot from an XML file. Its working but the aircraft will severely oscillate
on occasion. Any ideas where I should start to minimize the oscillations?
Thanks,
Vance
___
Is there a way to specify autopilot waypoints via an XML configuration
file?
Thanks,
Vance
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Hi,
I have tried the altitude and heading hold features of the autopilot (ctrl-A
and ctrl-H with arrow keys or F11 autpilot dialog box). They work very well
with j3cub aircraft but with the default cessna 172 either of them don't
work at all. I suppose this is a bug.
-Timo
Timo Saarinen wrote:
Hi,
I have tried the altitude and heading hold features of the autopilot (ctrl-A
and ctrl-H with arrow keys or F11 autpilot dialog box). They work very well
with j3cub aircraft but with the default cessna 172 either of them don't
work at all. I suppose this is a bug.
The
On Tuesday 05 April 2005 21:22, Curtis L. Olson wrote:
Timo Saarinen wrote:
Hi,
I have tried the altitude and heading hold features of the autopilot
(ctrl-A and ctrl-H with arrow keys or F11 autpilot dialog box). They work
very well with j3cub aircraft but with the default cessna 172
Hello,
with the default c172 I see this error:
Reading autopilot configuration from
/home/mas/CVS/FlightGear/data/Aircraft/c172p/Systems/KAP140.xml
Unknown top level section: filter
Detected an internal inconsistancy in the autopilot
configuration. See earlier errors for
details.
Deleting a
On Thursday 04 November 2004 12:21, Martin Spott wrote:
Hello,
with the default c172 I see this error:
Reading autopilot configuration from
/home/mas/CVS/FlightGear/data/Aircraft/c172p/Systems/KAP140.xml Unknown top
level section: filter
Detected an internal inconsistancy in the autopilot
Roy Vegard Ovesen wrote:
Do you have the latest CVS? Filters were added to xmlauto.*xx mid October:
http://baron.flightgear.org/pipermail/flightgear-cvslogs/2004-October/008703.html
That's it. I already removed anything with '*kap140*' in the filename
and pulled a fresh version from CVS.
On Thursday 04 November 2004 15:21, Martin Spott wrote:
Roy Vegard Ovesen wrote:
Do you have the latest CVS? Filters were added to xmlauto.*xx mid
October:
http://baron.flightgear.org/pipermail/flightgear-cvslogs/2004-October/008
703.html
That's it. I already removed anything with
Roy Vegard Ovesen wrote:
So... problem solved, or?
Yep - thanks,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
___
[EMAIL PROTECTED] wrote:
Isn't it more apropriate to have a multidimentional PID c
ntroller rather
than multipl
1 dimentional PID controllers? Or is that just the same?
I'm not sure what you mean by multidimentional PID controller, but I believe
that that it would be the same as multiple one
-- Original Message --
Date: Tue, 13 Jul 2004 18:57:13 +1200
From: Birger Brunswiek
To: FlightGear developers discussions [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] Autopilot
Reply-To: FlightGear developers discussio
s [EMAIL PROTECTED]
rvovesen wrote:
Isn't it more apropriate to have
-- Original Message --
Date: Mon, 12 Jul 2004 12:09:04 +1200
From: Birger Brunswiek
To: FlightGear developers discussions [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] Autopilot
Reply-To: FlightGear developers discussions
[EMAIL PROTECTED]
ver these books which I'm going to get from
I have found this to be an excellent reference most of which is
directly applicable to aircraft.
MANEUVERING AND CONTROL OF MARINE VEHICLES
by Michael S. Triantafyllou and Franz S. Hover
Department of Ocean Engineering
Massachusetts Institute of Technology
Cambridge, Massachusetts USA
What is the difference in these properties?
/autopilot/route-manager/wp-last/id ='' (none)
/autopilot/route-manager/wp/id = 'KANP' (string)
/autopilot/settings/route-manager/wp/id ='KGAI' (string)
They seem to be overshadowing each other. Have some of these
been
[EMAIL PROTECTED] wrote:
A Google search for pid control gives some useful tutorials on what pid
is.
doh... yes I must have overlooked them before ;-) but actually I
was looking at a more in-depth description. On my way I came across
over these books which I'm going to get from the library: (name
Reading the autopilot documentation I find that the step
from the PID controller described to the one actually
implemented quite big ...
The algorithm described here:
http://www.flightgear.org/Docs/XMLAutopilot/node3.html
is the one that is implemented.
Can the guys who have worked
on that
Reading the autopilot documentation I find that the step
from the PID controller described to the one actually
implemented quite big ... Can the guys who have worked
on that perhaps point me to a pile of books of webpages
I should read to get a better understanding of it?
I haven't couldnt find
Is there an autopilot that still uses the
/autopilot/settings/waypoint
method of setting waypoints? (i.e., one that can accept
modifications to the waypoint list via the telnet interface)?
Or has that been replaced with
/autopilot/route-manager/wp/id ?
If so, how does an external program
Lee Elliott wrote:
On Monday 22 March 2004 16:01, Martin Spott wrote:
Try this: Choose the YF-23, start FlightGear, set the autopilot for
altitude (1000+ ft) and heading in the first step, set speed (some 350
kts) as a second step and watch a wild horse riding through the air :-)
The latest
Lee Elliott wrote:
Ta for pointing out the high-speed oscillation problem - I've got to confess
that all the recent AP changes were only tested at relatively low speeds i.e.
flying circuits to check take-offs landing. I'll have a look into it.
When you're done with that I'll send you my
Martin Spott said:
Lee Elliott wrote:
Ta for pointing out the high-speed oscillation problem - I've got to confess
that all the recent AP changes were only tested at relatively low speeds i.e.
flying circuits to check take-offs landing. I'll have a look into it.
When you're done
On Tuesday 23 March 2004 22:28, Martin Spott wrote:
Lee Elliott wrote:
Ta for pointing out the high-speed oscillation problem - I've got to
confess that all the recent AP changes were only tested at relatively low
speeds i.e. flying circuits to check take-offs landing. I'll have a
look
Try this: Choose the YF-23, start FlightGear, set the autopilot for
altitude (1000+ ft) and heading in the first step, set speed (some 350
kts) as a second step and watch a wild horse riding through the air :-)
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are
On Monday 22 March 2004 16:01, Martin Spott wrote:
Try this: Choose the YF-23, start FlightGear, set the autopilot for
altitude (1000+ ft) and heading in the first step, set speed (some 350
kts) as a second step and watch a wild horse riding through the air :-)
Martin.
The latest YF-23
Lee Elliott wrote:
The latest YF-23 pending update (note name change from 'yf23') has an auto
take-off function in the AP that does pretty much that just by selecting 'TO'
mode.
Hey, I thought, all these near-ground automatisms are for wimps
o.k., I admit being a wimp and will try
Thanks Roy
I will do some reading.
Cheers
Innis
Roy Vegard Ovesen writes
Browse to:
http://www.flightgear.org/Docs/XMLAutopilot/
There is a generic autopilot in the data/Aircraft/Generic folder.
This should become apparent when you read the docs and the generic
example. You have to get the
Thanks David
Do I only need to rebuild FG for this
to take effect.
Cheers
Innis
David Culp writes
The new autopilot is in CVS as of today. Try it out. Some of it works,
some
doesn't, but we might be able to get it finished before the release.
Dave
--
David Culp
Innis Cunningham said:
Thanks David
Do I only need to rebuild FG for this
to take effect.
Cheers
Innis
David Culp writes
The new autopilot is in CVS as of today. Try it out. Some of it works,
some
doesn't, but we might be able to get it finished before the release.
Hi
Thanks Jim
As I am not very strong with this CVS stuff.I realised after I
posted that all I had to do was update my CVS base as my build
is only about 5 days old.
Cheers
Innis
Jim Wilson writes
Hi Innis,
FYI, I think what David meant to say is he checked in to cvs a start on a
new
737 autopilot
Hi Guys
I wonder if someone could tell me were I can find
the instructions for the new autopilot system so I can
redo the 737 autopilot to work.
If someone has built an autopilot with the new system
could they tell me the xml file so I might get an idea
how it is done.
Or is there a key press to
I wonder if someone could tell me were I can find
the instructions for the new autopilot system so I can
redo the 737 autopilot to work.
The new autopilot is in CVS as of today. Try it out. Some of it works, some
doesn't, but we might be able to get it finished before the release.
Dave
--
On Fri, 12 Mar 2004 21:33:04 +0800, Innis Cunningham [EMAIL PROTECTED]
wrote:
Hi Guys
I wonder if someone could tell me were I can find
the instructions for the new autopilot system so I can
redo the 737 autopilot to work.
Browse to:
http://www.flightgear.org/Docs/XMLAutopilot/
If someone has
Somehow I need to incorporate distance (from the transmitter) into the the
nav1 heading control, or find another way to solve the same problem. As you
get closer to the target, the cone gets narrower, but more important is that
the size of adjustments to correct for a give angle error become
One idea I had was to base the error not on an angle from the radial but on
the distance from the center of the cone. The required response to correct
this value would be consistant all the way down the cone.
I agree, cross-track error is the way to go.
cross_track_error =
I'm tempted to commit my autopilot changes to cvs.
Here's what I have done so far.
- I've implimented Roy's suggested PID algorithm. Compared to what we had,
this algorithm is better behaved, is much more configurable, and much more
tunable. It can be made to do a much better job of easing
Comments? Any objections to committing my updates?
Thanks,
Curt.
Does this make it any easier to bypass the FlightGear autopilot (and perhaps
soon-to-exist) FCS system, so the FDM could provide this functionality, if
desired - perhaps by simply not including an autopilot/FCS file or
Jon Berndt wrote:
Does this make it any easier to bypass the FlightGear autopilot (and perhaps
soon-to-exist) FCS system, so the FDM could provide this functionality, if
desired - perhaps by simply not including an autopilot/FCS file or
definition through your new method? This is very important to
If the autopilot is defined within JSBSim, how will it be manipulated from
FlightGear (as far as activating/deactivating the different modules or
adjusting the reference/target points.) What about things like route
following (gps) or Nav CDI/GS holds? How does that get
communicated to
Jon Berndt wrote:
Yes this is where it gets complicated. There are modes that are obviously
relevant to mere flight dynamics, such as attitude hold, heading select,
wings level, terrain following, etc. -- and even these use *sensor* inputs
as opposed to actual FDM aircraft state data. The other
David Culp wrote:
Comments? Any objections to committing my updates?
It looks great, and I think the sooner it gets commited the better, so we'll
have plenty of time to work with it before 0.9.4.
I already have a wish list :) mach hold, and vertical speed hold.
Ok, it's been at least an hour
Comments? Any objections to committing my updates?
It looks great, and I think the sooner it gets commited the better, so we'll
have plenty of time to work with it before 0.9.4.
I already have a wish list :) mach hold, and vertical speed hold.
Dave
--
David
Curtis L. Olson writes:
Sent: Saturday, January 31, 2004 2:40 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Autopilot update.
Curtis L. Olson
Sent: Saturday, January 31, 2004 1:32 PM
To: FlightGear developers discussions
Subject: [Flightgear-devel] Autopilot
Norman Vine wrote:
Hmm... 1 hour 08 minutes on a weekend
Was any discussion really wanted :-)
Being a volunteer and doing this on weekends and evenings, I've got to move
quickly when I do get the chance. I've been working hard on this and
trying to factor in comments and suggestions made
Curtis L. Olson [EMAIL PROTECTED] said:
Ok, it's been at least an hour and no one has objected. :-)
Ah! Oh! Should've been checking my email! ;-)
I will try to follow up with some documentation this weekend still.
Even very rudimentary unedited notes would help. Thinking about trying to
On Saturday 31 January 2004 20:00, Curtis L. Olson wrote:
Norman Vine wrote:
Hmm... 1 hour 08 minutes on a weekend
Was any discussion really wanted :-)
Being a volunteer and doing this on weekends and evenings, I've got to move
quickly when I do get the chance. I've been working
Curtis L. Olson wrote:
David Culp wrote:
Comments? Any objections to committing my updates?
It looks great, and I think the sooner it gets commited the better, so
we'll
have plenty of time to work with it before 0.9.4.
I already have a wish list :) mach hold, and vertical speed
Frederic Bouvier wrote:
Small glitch at run time :
route = 0D7673D8
Failed to load autopilot configuration:
fgfsbase/Aircraft/Generic/generic-autopilot.xml
CVS Updated and no generic-autopilot.xml
Gaahhh! I swear I added that file. Ok, it's there now. Sorry about that.
Curt.
--
Curtis Olson
On Thu, 22 Jan 2004 11:46:00 -0600, Curtis L. Olson [EMAIL PROTECTED]
wrote:
I have a PID controller algorithm from one of my textbooks, I could
send it to you with lots of comments.
If it's not too much typing for you, it would be worth taking a look at.
Ok! Here is the PID controller
I played around with the wing-leveler example from Automatic flight in
jsbsim. I noticed that the solution had the problem of intergator-windup.
I tried to limit and/or clip the intergator component, but that didn't do
what I thought it would. Does anyone have a solution to this problem? Note
I played around with the wing-leveler example from Automatic flight in
jsbsim. I noticed that the solution had the problem of intergator-windup.
I tried to limit and/or clip the intergator component, but that didn't do
what I thought it would. Does anyone have a solution to this problem? Note
On Fri, 9 Jan 2004 06:31:23 -0600, Jon Berndt [EMAIL PROTECTED] wrote:
First of all, let me know how you played with the JSBSim wing-leveler
example - I mean, did you use JSBSim in its standalone mode, or did you
somehow integrate this with JSBSim within FlightGear. I ask, because I
have
never
When the wings are level and the actuator (roll trim) stays out of
saturation, this PI controller works great. It does not grow
a bias as
long as the actuator is able to do it's job, it only grows a
bias when the
actuator does not have enough power (deflection angle) to do it's job.
On Fri, 9 Jan 2004 13:58:11 -, Richard Bytheway
[EMAIL PROTECTED] wrote:
Knowing nothing about the jsbsim structure, and only a little about PID
control, could you arrange the control loop so that the Integral term is
only updated when the output is between 2% and 98%?
This is the solution
On Fri, 09 Jan 2004 14:52:28 +0100
Roy Vegard Ovesen [EMAIL PROTECTED] wrote:
The solution to this is to stop the intergation when the actuator
goes into saturation.
Aha! Good explanation. Yes, I think this should not be too hard to
fix, but I don't have time to play with that myself at this
On Fri, 09 Jan 2004 15:24:15 +0100
Roy Vegard Ovesen [EMAIL PROTECTED] wrote:
This is the solution I'm looking to implement, but sadly my knowlege
about the jsbsim structure is so limited that I could not think of a
way to do it. Maybe the SWITCH component could be used as an if
structure?
On Fri, 09 Jan 2004 14:52:28 +0100
Roy Vegard Ovesen [EMAIL PROTECTED] wrote:
Also, note that the derivative part of the example wing leveler
control was a complete guess - and I think it actually may not play a
large part (or *any* part) in the maintaining wings-level at all.
I have also
On Fri, 09 Jan 2004 09:15:53 -0600, Jon S Berndt [EMAIL PROTECTED] wrote:
On Fri, 09 Jan 2004 15:24:15 +0100
Roy Vegard Ovesen [EMAIL PROTECTED] wrote:
This is the solution I'm looking to implement, but sadly my knowlege
about the jsbsim structure is so limited that I could not think of a
way
On Fri, 09 Jan 2004 09:13:33 -0600, Jon S Berndt [EMAIL PROTECTED] wrote:
On Fri, 09 Jan 2004 14:52:28 +0100
Roy Vegard Ovesen [EMAIL PROTECTED] wrote:
The solution to this is to stop the intergation when the actuator goes
into saturation.
Aha! Good explanation. Yes, I think this should not
On Fri, 09 Jan 2004 22:39:20 +0100
Roy Vegard Ovesen [EMAIL PROTECTED] wrote:
I think this should be implemented in the jsbsim source code, not in
the fdm_config xml file.
Yes. And it is true there probably should be an initialization
capability for filters, integrators, etc. I'll try and
On Fri, 09 Jan 2004 15:51:40 -0600, Jon S Berndt [EMAIL PROTECTED] wrote:
Yes. And it is true there probably should be an initialization
capability for filters, integrators, etc. I'll try and look into this
very soon.
How about adding a new flight control component: PID controller?! I've
How about adding a new flight control component: PID controller?! I've
been searching my textbooks on control systems and found a few PID
controller algorithms. I could begin to implement one that takes care of
the integrator windup problem and has some other usefull features.
Well ... I'm
Hi,
I am playing with the autopilot and maintaining an altitidue above sea
level works great. Is there a method for maintaining an elevation above
the ground?
Seamus
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Seamus Thomas Carroll writes:
I am playing with the autopilot and maintaining an altitidue above sea
level works great. Is there a method for maintaining an elevation above
the ground?
Ctrl-t will toggle a mode that attempts to maintain the current
altitude above ground. The algorithm is
On Thursday 08 January 2004 21:40, Curtis L. Olson wrote:
Seamus Thomas Carroll writes:
I am playing with the autopilot and maintaining an altitidue above sea
level works great. Is there a method for maintaining an elevation
above
the ground?
Ctrl-t will toggle a mode that attempts
Hi Guys
I would like to have the selections on my autopilot panel work
only when the Autopilot is engaged.But I dont seem to be
able to do it using the property.
/controls/autoflight/autopilot/engage.
Is this the property to use and how should it be implimented
in the XML file.Is there an A/C in
On Sunday 14 December 2003 13:40, Innis Cunningham wrote:
Hi Guys
I would like to have the selections on my autopilot panel work
only when the Autopilot is engaged.But I dont seem to be
able to do it using the property.
/controls/autoflight/autopilot/engage.
Is this the property to use and
If the heading mode is FG_HEADINGWAY_POINT does autopilot block use
a similar procedure like in VOR or ILS navigation by using a rolling motion
to intersect waypoint in a pre-determined heading or does it use the angle
difference between its current heading and the heading calculated by
Salut Julie,
how urgent do You need the describtion and how detailed do You want it
to be?
I am writing on a training manual for FlightGear (it's in the doc
directory), but haven't started the autopilot section by now. If You
have some time, I will rearange my schedule and start with the
autopilot
Hi,
I am student working on building a flight simulator wihthout any user interface. I have managed to run independently the JSBSim. But now I would liketo write a script to autopilotthe aircraft through given waypoints.
So I would like to know if anyone has a detailed documentationwhich
My question is about the variables that are used in
the autopilot system. As far as I can understand the target heading is
calculated by the angle between the aircraft and the waypoint with the proper
heading and the rate of change of angle times the distance between the
coordinates which
Mehmet Velicangil [EMAIL PROTECTED] said:
can it be calculated. In one of the documents in the flight gear site I
found that the rollout point which resembles an angle is approximately same
with the maxroll which is taken 20 for Chessna and the rollout smooth point is
approximately half of its
Jon Berndt wrote:
I'm not aware of the internals of the autopilot, but it might be usefull
to wait a bit until the script manager is working properly, and then
make the autopilot script driven.
What is the script manager?
David comitted a new FlightGear/src/Scripting directory containing
As some of you may know, I have been interested in an autopilot capability
for JSBSim in the standalone version. Also, providing a configurable
autopilot for JSBSim airplanes flying in FlightGear (via a config file) is
also something I'd like to be able to do. Recently, I have completed the
basic
Jon Berndt writes:
As some of you may know, I have been interested in an autopilot capability
for JSBSim in the standalone version. Also, providing a configurable
autopilot for JSBSim airplanes flying in FlightGear (via a config file) is
also something I'd like to be able to do. Recently, I
Also, consider that for the default autopilot, we have modeled gyros
and other systems that are actually used as input to the autopilot (at
least on smaller planes.) This makes our current autopilots behave
less ideally, and more like real life. Half the fun of learning how
to use these
Curtis L. Olson writes:
Jon Berndt writes:
Can someone outline the basic interface that would need to be hooked up
(via FGInterface?), and if/how the internal autopilot could be disabled?
You can look at src/Autopilot to see how that works. I'm not sure
it's been designed to be
Norman Vine wrote:
I think it is time to design the pure virtual AutoPilot Interface in C++
rather then rely on such a 'hack'.
This would be a good time to separate out the FlightComputer functional
components from the autopilot too. ie primitive APs have no concept
such things as a
Norman Vine writes:
This would be a good time to separate out the FlightComputer functional
components from the autopilot too. ie primitive APs have no concept
such things as a waypoint to steer to or constant height above terrain
In extreme speak I think a major refactoring is in
On Mon, 13 Jan 2003 16:05:07 +0100
Erik Hofman [EMAIL PROTECTED] wrote:
I'm not aware of the internals of the autopilot, but it
might be usefull to wait a bit until the script manager
is working properly, and then make the autopilot script
driven.
Interesting. I had not heard of that. It's
Curt and I have been having a discussion offline about algorithms for
NAV mode on a simple autopilot (like those typically found in a light
Cessna or Piper). The current autopilot does not have a working NAV
mode -- it was just a quick kludge, with ability to correct for a
crosswind.
What
What algorithms are commonly used to get and keep the CDI centered in
a simple AP? It should be easy enough to start with the rate and
direction of CDI deviation from center.
I'm tempted to say that there isn't a standard we can simply use;
I've used some very different ones even in a small
At 05:31 PM 7/10/2002 -0400, you wrote:
Curt and I have been having a discussion offline about algorithms for
NAV mode on a simple autopilot (like those typically found in a light
Cessna or Piper). The current autopilot does not have a working NAV
mode -- it was just a quick kludge, with ability
David Megginson [EMAIL PROTECTED] said:
Curt and I have been having a discussion offline about algorithms for
NAV mode on a simple autopilot (like those typically found in a light
Cessna or Piper). The current autopilot does not have a working NAV
mode -- it was just a quick kludge, with
Basically what I had in mind was an adjustment of the target heading
based on
the resulting devation values. I don't have the actual formula written
down,
but it would involve doubling the devations and subtracting them from
the
target heading and including an integral accumulated error
Jim Wilson writes:
The technique that I had in mind is probably one that would work for most
aircraft. Flying to the needle causes some issues especially with airliner
sized aircraft. The current code adjusts the heading by taking the needle
deflection and multiplying it by the
Jon Berndt [EMAIL PROTECTED] said:
Basically what I had in mind was an adjustment of the target heading
based on
the resulting devation values. I don't have the actual formula written
down,
but it would involve doubling the devations and subtracting them from
the
target heading and
1 - 100 of 127 matches
Mail list logo
