On Friday 09 February 2007 21:13, leee wrote: > 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.
The one I asked Gérard to look at was /autopilot/new-config. When you have pinpointed that a certain controller is not outputting what it should, look in /autopilot/new-config to see if the controller is actually there. If it is there, try enabling the debug option for that controller. > > 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. It looks like the controllers are not getting built correctly at FG startup. When you do a autopilot-reset, the controllers in /autopilot/new-config are cleared and the autopilot config xml file is re-read and the controllers re-built. -- Roy Vegard Ovesen ------------------------------------------------------------------------- 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
