On Sunday 11 February 2007 00:37, leee wrote: > On Friday 09 February 2007 21:36, Roy Vegard Ovesen wrote: > > 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. > > Quick test - this time on take-off the pitch hold didn't kick in. This is > the very first controller in the config and it appeared to be there in > new-config, with the correct config. It just didn't seem to be sending > anything to the output. > > All the other controllers seemed to be accounted for too - I didn't check > each one but the numbers tallied. > > Yup - just tried again and got the same pitch-hold problem. I checked > everything for this controller in new-config, making sure that all the > nodes were ok, and it all looked fine. > > LeeE
I thought I'd give it another go, with debug on the pitch-hold controller and waddya know - this time the pitch hold worked and the alt hold failed. Ok - so I set debugging on all three of the pitch related controllers and on the next test it was back to the pitch hold problem again but with no heading hold either. Anyway, there was no output from the pitch hold controller although I could see the climb rate and altitude controllers come in as they were engaged. I paused the sim once I was above the target altitude, inserted some blank lines into the debug o/p, so I could find the point again, and reset the a/p. After doing this I could then see debug o/p from the pitch controller. Do you want to see the debug o/p? 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
