I am having a really strange problem on my recent NGX flights where the A/P CMD  A will not turn on.  I have the FMS setup correctly, FD for pilot is primary, FD for FO is secondary (confirmed by green light).  The A/T is on.  

 

After takeoff in stable climb when I turn on the A/P CMD it just flickers yellow and remains on.  

 

Yesterdays flight was the SAM 2M SID out of EGKK and I ended up hand flying the departure up to about 10,000ft before I could get the A/P to come on and stay on.  As far as I know I was in a stable climb and withing 5 degrees of the first waypoint which was about 5 miles down field on runway heading.

 

Even selecting HDG select and speed it would not come on.  Honestly not sure what changed to finally get the a/p working.

 

Any ideas ?

The 737 autopilot cannot be engaged if pressure is being placed on the control column. Make sure the controls are neutral and the aircraft is trimmed out before trying to engage CMD.

 

 

Any ideas ?

 

Are you in trim before activation?  Have you checked your failures to see if you've broken your shear pin?

I think maybe its because I have pressure on the Yoke.  I only have usage based failures on so that probably rules out the shear pin.  Anyway I will double check again.   thanks,

Happened again.   I cannot get CMD to engage.  I have no pressure on the yoke, stable flight, trimmed properly, direct to active waypoint and I double checked all failure and they are off.  Reset them just to be sure.  Running out of ideas here, maybe I just need to reinstall it?

 

 

direct to active waypoint

 

That's not a requirement for autopilot engagement.

 

 

 

Running out of ideas here, maybe I just need to reinstall it?

 

...and there it is!  The overused simmer answer: well if it doesn't work, let's just reinstall it!

 

I doubt that'll fix it, honestly.

 

Try this:

1. Take off.
2. Trim it up.
3. Unplug your hardware.
4. Engage CMD A.

Works?  Hardware issue.

Doesn't work?  Keep troubleshooting here.

What is the hardware?

 

Sometimes unplugging everything helps, especially if it a Saitek. Unplug throttle, peddles, yoke, and recalibrate.

 

 

Sometime when programming with the Saitek profile editor you get conflicting commands that clash with the PMDGs.

Hardware is CH Products Yoke, Throttle & Pedals, plus the VRInsight MCP II panel.  OK will give it a try and see what happens.

Hello Mark,  My CHProducts Yoke is programmed into FSUICP  Button 1 assigned to keyboard A, autopilot works every time.  If yours is not, give it a try. Richard Welsh. PS, FS Controls will have to be amended accordingly. RW.

Here are my results.

 

Loaded up NGX, took off, stabilized climb (approx 1500 ft/min, 240 knots).  

Turned on CMD A - nothing.

Clicked CMD A on the VRInsight - nothing.

Disconnected one at a time all hardware, tried to click on CMD.  nothing.

 

Shut down FSX and plugged everything back in, restarted computer.

 

Tried again....nothing.

 

Just for fun loaded up the PMDG 777.  Tried same thing...worked perfectly first time with all hardware plugged in.  both mouse and VRInsight could turn on the A/P.

 

 

Hmmm, so....reinstalling the NGX (not FSX and not Windows, just the NGX) looks like it mgith be worth a try unless anyone else has any good ideas.

Do you have to have realistic AP engagement turned on in the options? If it is, it will require you in order to engage CMD A, to be on a heading of the first programmed fix, with a margin of about 10 degrees.

Yes. Before reinstalling, just try by desactivating the realistic A/P engagement in the FMC aircraft setup options. Or you can display the flight controls position on the second EICAS and be sure all controls are centered before pushing the button.

 

 

Stephane LI-THIAO-TE

Envoyé de mon iPad à l'aide de Tapatalk

Yep, I agree with the above: turn off the realistic A/P engagement option.