The latest change to the autopilot code required autopilot stages to have
unique names. I was a little to optimistic that aircraft developers were
creative enough to invent unique names for each single stage ;-)
I have just pushed a fix which takes care of creating distinguished names for
the s
?
Greets all
Prof. Rao
From: Curtis Olson
To: FlightGear developers discussions
Sent: Sat, July 24, 2010 6:28:57 PM
Subject: Re: [Flightgear-devel] Heads up: new autopilot subsystem implementation
Just to chime in here with a me too, the altitude hold on the
Just to chime in here with a me too, the altitude hold on the Rascal110 also
seems to be broke. Something seems to be overriding the target altitude
values and/or the mode selection, so the F11 autopilot dialog can't control
these. Similar problem with target airspeed.
The wing leveler and headi
Hi Syd,
I just updated my fgdata and I noticed that the change you mentioned (in
your message below) is not yet in de git repos. Should it not be in?
Apart from that little remark, I can still not get the Aerostar700 AP to
hold altitude. I have set the altitude on the dashbaord, armed it,
acti
I can't update my aircraft at the moment , but to fix the ALT hold problem ,
change this starting at line 205 in aerostar-autopilot.xml ...
instrumentation/altimeter/indicated-altitude-ft
Must have been a left over experiment. My mistake , there is no VS hold with
th
I'll take a look at it , could be broken again ... but you need to set the
altitude in the Alerter and arm it, then climb to that altitude (with a VS
mode, or manually) ... it wont actually ALT hold until your within +- 1000
ft of the target. Pressing the ALT button simply holds the altitude your
w
Yes the AP worked fine before.
First select the desired altitude on the dashboard (top). Then select
the desired heading on the dial on the dashboard.
Next switch on the AP in the dialog and select ALT and HDG.
On the dashboard click "arm" next to the altitude setting. The plane is
now supposed
> Hi Torsten (and others),
>
> I noticed that the autopilot on the Aerostar700 keeps climbing, despite
> what I set the AP to. I was trying to level out at FL120, but the AP was
> happily climbing to almost FL200 when I disabled it.
>
> Is this in the new code or in the plane?
I can't tell for su
In the Citation II, the AP seems to level off at around 24000ft, while
it is set for 3ft. Pressure set is 2992.
Also, initially I set the AP for an ALT of 35000. While climbing at
around 22000 I changed the setting to 3ft. The plane went into a
dive and decended to below 2ft. I took
I already had updated my data dir. Just did it again, but it is up to
date, it says.
m
Op 05-07-10 12:55, Scott Hamilton schreef:
> This sounds very similar to the problem I encountered 3 days ago with a
> number of aircraft. If you are rebuilding from the (fairly) latest git
> code base for si
On Mon, 2010-07-05 at 10:52 +0200, fiers...@zonnet.nl wrote:
> Hi Torsten (and others),
>
> I noticed that the autopilot on the Aerostar700 keeps climbing, despite
> what I set the AP to. I was trying to level out at FL120, but the AP was
> happily climbing to almost FL200 when I disabled it.
>
Hi Torsten (and others),
I noticed that the autopilot on the Aerostar700 keeps climbing, despite
what I set the AP to. I was trying to level out at FL120, but the AP was
happily climbing to almost FL200 when I disabled it.
Is this in the new code or in the plane?
m
--
On 27 Jun 2010, at 14:12, Torsten Dreyer wrote:
>> Also note that fdm_shell.cxx/.hxx and flightProperties.cxx/.hxx do not have
>> the usual copyright header.
> I'll leave it to James who is the author of these files to add a copyright
> and
> license statement.
Good point, I'll add these.
Jam
> These I have sorted by re-arranging the order of include file calls. There
> may be a better solution, and perhaps my solution will not work on other
> platforms.
This was due to the missing include of config.h. A very common pitfall for
linux developers. Should be fixed now.
> Once it all comp
--
From: "Torsten Dreyer"
Sent: Thursday, June 24, 2010 4:24 PM
To:
Subject: [Flightgear-devel] Heads up: new autopilot subsystem implementation
> Hi all,
>
> I have just commited a pretty large commit for a new implementation
On 24 Jun 2010, at 16:24, Torsten Dreyer wrote:
> Every single algorithm should work as before and the xml syntax should be
> 100%
> compatible with existing configurations.
>
> Please note, that the former hard coded autopilot helper functions are gone
> now. These functions are now implemen
Hi all,
I have just commited a pretty large commit for a new implementation of the
autopilot subsystem(group). The reason for that was that the old way of having
everything stuffed into one single source file of 1360 lines and a header file
of 514 lines made working on this piece of code allway
17 matches
Mail list logo
