Search the Community
Showing results for tags 'autopilot disconnect'.
Found 3 results
-
Greetings All!, So i decided to do a re-familiarization flight in the J-41 as its been a while. So I go through the tutorial and all is well until I get to takeoff and it says engage the autopilot. After much frustration I know the issue, its my joystick... I have the X52, a great stick! Ok, I have the trim wheel set to the axis wheel on the "e" button (owners will know what i mean) the large wheel on the throttle. Now, I moved it to here instead of the two lighted buttons on the stick for greater control. It works FANTASTIC on hand flown GA aircraft, it allows me to make fine adjustments and hold an altitude easily! The PROBLEM is I think, because the trim is now assigned to a wheel its a manual control now, not a push button adjustment. So my theory is the J-41 can't automatically move that wheel in real life (that would be awesome lol) so it interprets the fact that the wheel isn't moving as pilot input, and disengages itself. Per the AOM for the J41: section G 8.11 Autopilot cut-out The autopilot will disengage if any of the following conditions exist: ... -Manual over-ride by the pilot beyond a point at which a servo clutch becomes disengaged. That's what I'm assuming, because the physical wheel is a analog control, the plane thinks I'm moving it (even though I'm not) and it cuts out. This seems to be confirmed by unmapping the trim controls, and then the ap engages just fine... So, my question, is there a way I can leave the trim mapped to that wheel and still get the autopilot to work in the J-41? Or am I looking at changing my control mapping every time I wish to switch from the J-41 to another aircraft? Thanks
-
Hi all, I was just wondering what the correct procedure for disengaging A/P and A/T on final is? I currently use the disengage bar on the MCP and the A/T switch which I realize is not correct and results in the A/P-A/T alarm annoyingly going off while landing. Can anybody suggest the correct procedure for this, especially if there's one that won't have me take my hands off the controls? Cheers, Matteo
-
I suspect what just happened to me was the autopilot disconnecting for, as per QRH, Flight Envelope Protection but I'm not 100% sure... I'd been happily cruising at FL370/M.85 for an hour or so when the warning horn went off and "Autopilot" came up on the EICAS. A/P, A/T, Vnav and Lnav all remained lit correctly but the A/P clearly wasn't in VNAV as the 777 booted the throttles and started climbing quite sharply to well above FMC and MCP flight levels. I was connected to Vatsim, using AS2012 weather (NOT uploaded to the FMC) and the winds had been swinging around a bit where I was (between Iceland and Scotland over the ocean). I use FSUIPC wind and pressure smoothing so they're never dramatic nasty shifts or gusts. Happening somewhat unexpectedly I can't actually recall what the wind was doing at the moment it occurred so I can't describe the situation precisely and am just trying to fathom a reason for an AP disconnect like that. So could, for example, a wind reversal (as in common is FSX) at a slow rate of change trigger Flight Envelope Protection or am I barking up the wrong tree?
