thanks lee for the reply, particular about the "thinking it through" part; and am already thinking about a problem I've encountered, although I'm still trying to get the hang of the autopilot.
VNAV. - (don't know how to explain the problem well) I've managed to get the Altitude hold, Vertical Speed, glidescope and Pitch to work well individually, eg the Altitude Hold has a spike filter on the <input> which removes the "lurches" and violent movements. However switching between the VNAV modes causes the "elevator" which all the PID's are individually driving to "Jump" to a new position. eg switching from -1000 fps vertical speed descent to a climb to altitude hold above. This "immediate elevator jump" can be clearly seen on the yoke and the HUD elevator indicator and causes the aircraft to bounce around. I'm not sure how to tackle this problem, or indeed what the real problem is. One thought would be to make ALL the vnav PID's/calculations feed a single output such as "target-climb-rate-fps", and then this would be filtlered to manipulate the elevator. That would mean making some convertion eg from the glideslope to "target-climb-rate-fps". Another would to have some sort of "crossfade" as the PID's swap from one to another. Are there any existing solutions to this problem. Any advice greatly appreciated. regards pete > > A word of advice though: you can end up with very complex autopilot > configurations (the last one I did was 1256 lines long), with lots > of new property tree nodes being referenced, so it pays to think it > all through first and get yourself organised so that you can keep > track of everything - don't just start adding new nodes etc. > willy-nilly. I suggest adding a new parent node beneath /autopilot > e.g. /autopilot/FCS and then add all your custom stuff beneath that > node instead of just adding lots of new nodes beneath /autopilot. > > As your autopilot becomes more complex it pays to set up new > sub-parent nodes to group together each type of thing you're > working with e.g. > > /autopilot/FCS/settings > /autopilot/FCS/targets > /autopilot/FCS/controls > > LeeE > > > ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
