On Friday 09 February 2007 19:45, Roy Vegard Ovesen wrote:
> On Friday 09 February 2007 20:22, leee wrote:
> > It's difficult to imagine a system problem that might cause this
> > behaviour, in view of the fact that resetting appears to fix the problem.
> >
> > However, I know that there are a few problems that I've seen here that no
> > one else appears to have experienced on their systems, one long running
> > example being problems with the wind and visibility settings not being
> > honoured.
> >
> > If it is a system problem, I simply don't know where to start looking.
> > Could a compiler problem cause this?  It's the only thing I can think of
> > in view of the fact that I'm using Debian Stable and the gcc version is
> > pretty old.  I'm not sure that would explain the history of the problem
> > either, that is, it was working ok then stopped working ok.
> >
> > I'm afraid I can't do a lot of testing for you on this.
>
> I just tried the SU-37, and the autopilot seemed to work OK. I have not
> been able to reproduce the problems that you and Gérard are having with the
> autopilot, so it looks like I can't do _any_ testing on this. :-(
>
> Could you try the tip I suggested to Gérard about looking at the
> controllers before and after autopilot reload?

Just tried another quick test.

Opened five property browsers - autopilot/locks, autopilot/settings, 
autopilot/internal, autopilot/FCS/locks & autopilot/FCS/controls - all seemed 
ok but then I pre-set most of the nodes during aircraft initialisation.

On this test the altitude hold failed to work.  The altitude hold controller 
reads the filtered target alt and outputs to 
autopilot/settings/target-climb-rate-fps.  When the altitude hold controller 
was engaged it failed to update the target climb rate.  Agl hold, which also 
outputs to the same target climb rate node in autopilot/settings, was ok and 
I could see the node being updated.

I switched back to altitude hold and forced a climb by over-typing a +ve climb 
rate into the non-updating node.  Once I got to around 10k ft I reset the A/P 
and the climb rate started updating.

The roll modes were all ok on this test.

LeeE


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to