Hello guys, I was trying for the first time the A320NX by FlyByWire. I watched a lot of videos and wrote down every step to make this plane fly.
Today everything was fine, except overspeed. I tried to reduce speed by setting it manually and pulling the button, but nothing. Not even spoilers worked. True problems started at top of descent: I set desired altitude and vertical speed, pulled the buttons but… it started climbing!
As you can see, I set speed, altitude and vertical speed, but the autopilot just ignored them
Which version are you using? Do not use the marketplace version. Delete everything and re install it via the fbw installer. Best the developer version.
You set vs mode. But if the autopilot would lower the nose you will gain speed which will lead you to an overspeed condition, so the protection system will pitch up to get rid of the speed
Thank you for your replies. Yes, it was on, but I tried manual speed and it did not work.
About full power, I am sure I set CLIMB after take off, but maybe I pressed F3 by mistake when changing through “screens” (I use m&k). You might be right, because 89% for both engines seems to be too much
As others have said, check thrust setting After the initial thrust reduction, keep the levers in CLB detent and don’t touch them again until the “RETARD” call for landing. Let the Airbus manage your thrust. You would only need to push the speed knob to have the airplane manage the speed or pull the knob and dial in the speed you want.
There may be something going on with your setup before takeoff. The A/THR button should automatically engage when you apply thrust during takeoff. If you have to activate it manually like it appears in your photo, something earlier in the flight may be the issue, or, it was manually turned off. Under normal operations, you do not need to disable A/THR. You would just use managed or selected speed and let the thrust system do its magic.
Since you don’t have it engaged in the photo, and you are using a static thrust setting, you are going to over speed. It appears an inactive thrust system is contributing to the issue. Looking at your FMA above the PFD, you do not have a thrust mode active.
I have sometimes problem with managed speed mode on landings. It happened to me today when landing at Reno Tahoe KRNO, and most recent at Halifax CYHZ and St Louis Lambert KSTL, though all settings are very the same as other landings (no problem with managed speed). Aircraft passed Decel point, approach mode activated, ILS intercepted, but the speed on approach is way over 280 kts, impossible to deploy Flap 1, using air brake also not help. Distance to runway less than 15 miles. Got crazy!
I noticed that when Decel points are way to close to runways and STAR are missing on route, I always have this problem!
Looking at the last screen shot you posted…Your still flying way to fast to maneuver the A320. Your flying at 350 knts, it doesnt matter what your throttle is set for, if you flying at 350 knts the autopilot will not let you do things like ascend or descend. Before you try to climb or descend, lower your airspeed to 280 knts, then try again, it should then work, once you have reached your desired altitude and are flying straight and level you can return you speed to the 350 knts again. Until you need to maneuver again, then you’ll have to slow down to repeat…
Ok. I would ensure then that you have things setup correctly before you take the runway for departure. In order for the 320 to properly control thrust and hence speed, you need the Auto Thrust system working. What version of FBW are you using ?
Another thought, are you setting up the MCDU with the required information on the INIT A, INIT B, and PERF pages? Does your FMA and FCU look like this on takeoff? If not, that is your issue with A/THR
FMA is always key to know what the A320 is doing. If you don’t have anything in the first row, that would be the indication. If you did reduce thrust before thrust reduction you would still have an indication in the FMA. You would still have the last FMA column showing A/THR in blue or “armed”.
I’m on the experimental version but haven’t experienced this behavior so I’m thinking it’s a setup issue.
Have you properly setup the throttle detents in the settings part of the flypad ?
I gave mine huge deadzones to be sure not to change detent by mistake
