December 31, 201114 yr I was cruising at 38,000 ( LNAV & VNAV) and I accidentally disengaged the autopilot. Tried to re-engage CMD A,but the light just flashes on and off quickly. I am however able to engage CMD B, but hitting CMB B actually was engaging CWS ( as this was annunciated on the PFD) remembered reading somewhere something about toggling the flight director switches on & off and then making sure that the pilot's f/d switch was turned on first, but doing this does not help. Anyone have any idea as to why CMD A would not re-engage?Thanks Mark Mardjani i7 2600K, ASUS P8P67 Deluxe, Nvidia 560Ti, 8GiG RAM, WIN 7 / 64, All PMDG, FSX+ACCEL, GEX, UTX, AS2012, Ult. Traffic 2, Aerosoft Manhattan X, FSDT, Imagine Sim, EZDOK, Track IR
December 31, 201114 yr I was cruising at 38,000 ( LNAV & VNAV) and I accidentally disengaged the autopilot. Tried to re-engage CMD A,but the light just flashes on and off quickly. I am however able to engage CMD B, but hitting CMB B actually was engaging CWS ( as this was annunciated on the PFD) remembered reading somewhere something about toggling the flight director switches on & off and then making sure that the pilot's f/d switch was turned on first, but doing this does not help. Anyone have any idea as to why CMD A would not re-engage?Thanksthe only thing i can think of is the aircraft trimmed for flight usually is the case for the cmda not being able to be selected. like are you moving the control columne at all make sure its centred I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
December 31, 201114 yr Author Peter / Derian,Thanks for the suggestions. I trimmed before takeoff, but may have overtrimmed afterwards perhaps?. I'll check that- see if I can re-create the problem. Also, didn't show any failures. Mark Mardjani i7 2600K, ASUS P8P67 Deluxe, Nvidia 560Ti, 8GiG RAM, WIN 7 / 64, All PMDG, FSX+ACCEL, GEX, UTX, AS2012, Ult. Traffic 2, Aerosoft Manhattan X, FSDT, Imagine Sim, EZDOK, Track IR
December 31, 201114 yr You could have also broken CMD A. If you yank on the yoke while A/P is engaged, it can damage that autoflight system, making only CMD B usable. Tyler St. Peter Specs- i7-950 OC@ 3.4Ghz, Asus P6TSE, ATI HD5770, 750W PSU, Water cooled, Hitachi 1TB HDD
December 31, 201114 yr Peter / Derian,Thanks for the suggestions. I trimmed before takeoff, but may have overtrimmed afterwards perhaps?. I'll check that- see if I can re-create the problem. Also, didn't show any failures.You make have trimmed for takeoff indeed but then after your starting to accelerate though/past VR speed, if you have a VR speed of say 156 and trimmed at 6.14 units; but then start to move to 250 knots and if still keeping 6.14 units your going to have a high climb rate from the trim alone and therefore need to start to trim down as the aircraft speeds up.Or you can turn off realistic AP engagement. -Raven HarrisIntel i7 980X @ 4.43GHz | ASUS Rampage III | Corsair 6GB DDR3 2000MHz | 3 EVGA GTX280 | Corsair 1200 Watt | Intel 510 SSD (RAID 0)PMDG - 747-400/8iF | MD11/F | BAe J41 | 737NG 6/7/8/9 Hope ER/BBJ|777LR/FFlight1- Cessna Mustang
January 1, 201214 yr Author Thanks for all the suugestions everyone. I haven't had a chance yet to try to reproduce this, but I appreciate all the support. Mark Mardjani i7 2600K, ASUS P8P67 Deluxe, Nvidia 560Ti, 8GiG RAM, WIN 7 / 64, All PMDG, FSX+ACCEL, GEX, UTX, AS2012, Ult. Traffic 2, Aerosoft Manhattan X, FSDT, Imagine Sim, EZDOK, Track IR
January 1, 201214 yr Commercial Member Most likely thing is spurious joystick input that won't let it engage. Unplug your stick/yoke and see if it works - if it does you know that's the issue. Ryan MaziarzFor fastest support, please submit a ticket at http://support.precisionmanuals.com
Create an account or sign in to comment