FBW A32NX Speed Managed Mode Wont Engage

I have a recurring problem using both the Development & Experimental version that although I have programmed the MCDU and everything looks OK, frequently I cannot engage Speed Managed Mode. When I try to engage it the dashes and dot flash on and then speed resets to selected mode 100. Up until the recent merge of the experimental version into the development version I was using the experimental version and as this problem would appear then disappear then reappear again with various updates I always put it down to bugs in experimental version.

Recently I switched to the development version and it was fine for a few days but after an update a couple of days ago the problem is back What I don’t understand is occasionally it works and as no-one else seems to be reporting this issue, it might be something I am missing during the programming of the MCDU.

Do you have FD engaged on pilot and co-pilot sides of the glare-shield?

Alternatively, do you have a mapping for the SPD button, to a physical button that might be set to pull the button out?

1 Like

Have you calibrated your throttles in the “iPad” settings (aka EFB)? The DEV and EXPERIMENTAL versions both require throttle calibration now. Might be an issue if your throttles aren’t accurately calibrated in the A32NX mod?

Experimental mode is experimental. And FBW are testing out a new AP. Recommend you only use Stable or Development for now.

Concur you have to have the flight director on before the speed and heading commands will accept to “dot” mode.

Hello, did you manage to map managed/selected speed button please ? If yes to what please ? Thanks !!

I didn’t no, but ghost mappings can be a pain.

Can i take it that there is no such command?

Thank you so much for this it was a button or to be precise it was the mode select rotary on the Bravo Throttle that was guilty party . If it was on IAS then I cannot engage Speed in Managed Mode. Also noticed when Bravo throttle mode select rotary is on HDG then I can’t engage Heading in Managed Mode either.

This explains exactly why sometimes it would work fine and then in the middle of a flight stop working.

This has bugged me for weeks but I never raised it because I was using the experimental version so its great to have have it finally answered

3 Likes

The new AP and FlyByWire controls have now been taken from the experimental version and merged into the current Development version.

I would be nice if the sim had selectable key binding commands for every action item in the flight deck. I would love to be able to press a button / flip a switch on my controllers to engage managed speed/heading/altitude modes. I played around with the SLOT commands but I can only get speed to move into managed mode and it stays there…

The SDK isn’t complete yet. Give it a few years and we will have that.

1 Like

I have the same problem with both managed speed and heading on the 32NX stable version, although in my case its not the throttle as I am only using an Attack joystick. Shame as I can only fly manually now, or fly the Neo which works perfectly.

Are you using Legacy mode or Lock mode for the UI interaction? Are you sure you are pushing the knob in?

Thank you for the reply I am using “Legacy” I tried changing this to “Lock” and it makes matters worse ( unable to push the knobs at all ) It works fine with the Neo ( crossed the Atlantic yesterday evening) but I then loose all the nice FlyByWire enhancements. Its not a problem really as I always manage to find a way around the problems by controlling the aircraft manually, but I don’t understand why its happening. Spose I will stay with the Neo. Thank you .

To “push” a button using Lock mode requires a non-intuitive method. You have to hold down the LMB and then click the RMB. It’s actually a lot easier to use once you get the hang of it.

If I were you I would try the development version instead. The Stable version often gets made incompatible when updates happen.

Thank you again. I will give that a try.

Ahh, I have almost resolved my problem ( although I don’t know how ) The “heading” now allows me to engage managed mode, and I can apply managed to altitude once I have reached around 150 knots. That’s good enough for me. Thank you for your help.