Hi after takeoff I turn on the autopilot. After a short time it turns off by himself and I can’t turn it on again. Not via my stick or the button in the plane. If I push it it always sounds like turning it off. Never seen this before. Developer version updated today.
same problem, i noticed that AP disconnects when using the ipad on board
yep, actually saw this yesterday so it was an issue before the latest update. I was only able to get it to stay on after flying for like 15 minutes.
*EDIT I had the same issue just now, but after cycling managed nav mode, it seems to be working.
I’m quite sure it’s not an issue of the Autopilot but maybe - sorry to say - how you fly the plane.
If you get into low speed or in high alpha situation the plane will now switch into alpha protection mode and eventually disconnect the AP and also apply TOGA thrust being called A.FLOOR then.
Here an example from a Level-D sim and keep in mind that the V_alpha_protection and V_alpha_max speeds can already come up in steep curves and/or high load situations.
If not cautious enough this can also happen to real pilots:
F-HEPE (bea.aero)
4 Likes
Thanks for the info. Third fly worked so I will keep your information in mind.
1 Like
You probably were typing something in the FlyPad and that character is bound to the Toggle Autopilot command. If you’re using hadware like a sidestick or a throttle quadrant, it’s best to unbind the keyboard keys so they don’t get conflicted when you’re typing something in the flypad.
Otherwise, if you need the binding, make sure you rebind your keyboard into keys that doesn’t confict when you’re trying to type.
You can also open the window separately with right alt+click on the ipad. You can type on that mode without activating keyboard bindings and just close it when you’re done.
On the FlyPad I am certain that I have only typed in numbers 0 to 9, no ALPHA characters or SHIFT, ALT, or CTRL keys.
Then I did 2 flights with FlyPad open but not using it and had no problems.
well, if I need to type in airport ICAO code on the dashboard, it’s alpha characters.
Sure, but I simply used FlyPad to evaluate the speed of descent in the performance window, then entered the FL and distance, only numbers.
still… maybe one of those numbers are bound to the autopilot button? Or maybe it’s bound to a primary flight control where pressing them is equal to moving the stick and it disengage the AP. even numeric characters that’s using numpad is usually bound to the primary flight controls.
Has anyone being able to engage the AP in the DEV model ?
Lately every time i press the AP switch,nothing happens.
And when i set the lever on CLB i get an orange-red indication in screen which says ASYM
What did i miss?
The model is updated every day almost
Yes today without any problems. Try to delete everything and Reinstall the plane completely. Often works for me if it got some problems.
Hello,
I have FBW A32NX 0.6.3 (last stable) on World Update 6 update.
I can reach desired altitude 30000ft with AP on with correct heading.
But, once I reach desired altitude, AP turned off itself.
I have tried to turn on again, but, instead holding the altitude, my plane dive with crazy vertical speed.
I have tried to turn off and on auto thrust too, but it didn’t help.
The only way to save plane from diving itself is let AP off and climb manually to desired altitude (manual until landing). If I try to turn on AP again, it will dive again.
Is this bug or I made mistake flying with this plane?
I usually fly with Icon A5, C152, and C172.
Isn’t this a double post to the new thread you just opened?
check your assist options. Make sure you turn them all off by setting them as Hard/True to Life.
yes, I double posted to another similar thread, sorry.
1 Like
I have set assist to Hard. Updated to FBW A32NX 0.7.0.
It seems fix my altitude AP problem.