Re: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-14 Thread James Turner
On Friday, June 14, 2002, at 04:19 am, Jim Wilson wrote: Armed vs. Active modes: Active modes are the only ones that affect control surfaces. Armed modes select an impending active mode that may or may not get triggered, depending on if the condition for that mode is satisfied. Note

RE: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-14 Thread Jon Berndt
AXIS 3) Yaw damper: I am anxious that this be a totally separate system from the autopilot, it's a very independent system apart from the fact it drives control surfaces and the switch is usually on the MCP :-) If we ever go as far as systems modeling at the block level, that's especially

Re: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-14 Thread Jim Wilson
James Turner [EMAIL PROTECTED] said: c. Heading Select (HDG-SEL) uses ailerons to turn toward heading bug (or setting from FMC). Switches to active Heading Hold when target reached. Changing heading bug after Heading Hold is active requires initiating HDG-SEL again (won't

Re: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-13 Thread Jim Wilson
James Turner [EMAIL PROTECTED] said: On Tuesday, June 11, 2002, at 02:34 am, Jim Wilson wrote: Not a problem...give me a day or two to get things together. Probably there won't be as much changed as there will be added, but some of the settings need to be exposed in the

Re: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-11 Thread Jim Wilson
James Turner [EMAIL PROTECTED] said: yeah, this is basically what I was expecting, The current auto-pilot code is a bit hard-coded to use the radio stack for NAV modes, for example, we need a general course deviation or heading deviation (once we decide which) input, and then a NAV/GPS

Re: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-11 Thread James Turner
On Tuesday, June 11, 2002, at 02:27 pm, Jim Wilson wrote: If I'm not mistaken (and I easily could be) the FMC would usually just feed the autopilot heading and speed data when using non-radio-stack NAV modes. The FMC monitors the course and the AP only needs to follow the commands

Re: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-11 Thread John Wojnaroski
Well, this is where it gets interesting :-) We really need to define the auto-throttle property nodes, so that the FMC/MCDU can set (some of ) those. Or, on the 757/767, this is done via a physical panel, apparently (if I understand Thomas' comments). (the 777 uses a THRUST LIM page). And

Re: [Flightgear-devel] Autopilot planning [was RE: progress]

2002-06-11 Thread Tony Peden
On Tue, 2002-06-11 at 08:15, James Turner wrote: On Tuesday, June 11, 2002, at 02:27 pm, Jim Wilson wrote: If I'm not mistaken (and I easily could be) the FMC would usually just feed the autopilot heading and speed data when using non-radio-stack NAV modes. The FMC monitors the