4 minutes ago, knich said:

Thanks....problem is AP was canceling during CRZ.  Pitch and speed were fine.  It would cancel, I would rengage, it would work for a few miles and then cancel again.  Does it every flight. 

I have been using FBW since early days of MSFS 20.  This is the first time it has done this.  Didn't have this problem even when FBW removed the plane from marketplace.  I install the plane via FBW installer.

I'm experiencing a similar behavior, not only with the current stable, but with the previous one too. The A/P is definitely wonky for me. 

2 minutes ago, Drumcode said:

I'm experiencing a similar behavior, not only with the current stable, but with the previous one too. The A/P is definitely wonky for me. 

Yep...had this with 7.1 too.  

 

Pay attention to the speed restrictions on the way points in your flight plan .. you have some way points that are loaded with a speed restriction dropping your speed dangerously close to the A prot range and if this happens while you are climbing at high altitude or already at high altitude cruise the AP will disconnect as it should. Happened to me yesterday climbing through FL350 for 370 going from CYYZ to KBOS. Identified the issue (Way point JOSSY in the  flight plan had a speed attached at 220) , corrected by leveling off, gathering speed and switched to manual speed control  mach .78.. got out of  A prot and switched the AP back on. Waited until i was clear of the erroneous way point and carried along my merry way by switching back to managed speed mode since the next way point had no speed restriction attached.

Im not saying you may not have a valid issue. But usually this is a case of the person not able to identify whats going on, Whats the cause and how to address. When the AP disconnects on me the first place i look is at my speeds. Because in my personal experience the only way the airbus has disconnected the AP on me is if i had yanked the controller rapidly, Pressed Z or the AP button or encroached on the limits of the aircraft's performance envelope by not being vigilant enough or followed proper procedure.

Edited November 10, 20214 yr by Maxis

@knich @Drumcode

Reasons why AP will disconnect are:
- sidestick input > 50% (behind calibration)
- rudder input > 40% (behind calibration)
- any protection active (high speed protection, high angle of attack protection)
- Pitch is > 25°
- Pitch is < -13°
- Bank angle is > 45°
- on ground and go around is initiated
- ROLL OUT mode is disengaged on ground (in case of Autoland)

There are no other reasons why AP will disconnect. It‘s always one of the above.

Did you maybe use TOD calculator in the EFB with NumPad keys?

We found out recently that the TOD calculator in the EFB does not disable all events and if you press Enter key or 0 it will change the rudder. When you reach 40% of possible travel AP will disconnect. I‘ve seen at least 2 people having disconnects due to that issue. There is work on a solution to that problem. As a workaround you can press NumPad 5 or slightly move your rudder axis for a short moment.

4 hours ago, AGuther said:

@knich @Drumcode

Reasons why AP will disconnect are:
- sidestick input > 50% (behind calibration)
- rudder input > 40% (behind calibration)
- any protection active (high speed protection, high angle of attack protection)
- Pitch is > 25°
- Pitch is < -13°
- Bank angle is > 45°
- on ground and go around is initiated
- ROLL OUT mode is disengaged on ground (in case of Autoland)

There are no other reasons why AP will disconnect. It‘s always one of the above.

Did you maybe use TOD calculator in the EFB with NumPad keys?

We found out recently that the TOD calculator in the EFB does not disable all events and if you press Enter key or 0 it will change the rudder. When you reach 40% of possible travel AP will disconnect. I‘ve seen at least 2 people having disconnects due to that issue. There is work on a solution to that problem. As a workaround you can press NumPad 5 or slightly move your rudder axis for a short moment.

Did anything drastically change in the FMS flight plan? It's like a night and day for me in terms of behavior between 7.1 and 7.2? I had absolutely no disconnects with 7.1 from the take off to final. I do run a brand new alpha and bravo which are properly calibrated and no, did not use the TOD calculator at all. I have yet to have a flight without any disconnects tbh since I switched. 

As I have your attention, are there any plans to not request the change of destination from ATC on waypoint deletion from the FMS?

I think this mod hates my system. I tried the 0.7.1 version and using esc key stopped working. Had problems with other planes as well. The only mods I had were this mod and the AS CRJ. Maybe one day I can try this one out. 

@RobJC
Do you have a custom keyboard profile?

Edited November 12, 20214 yr by AGuther

@Drumcode
Here are the release notes from 0.7.1 to 0.7.2:

https://docs.flybywiresim.com/release-notes/v072/

Nothing drastically changed in that sense.

Edited November 12, 20214 yr by AGuther

Thanks all for helping to resolve this issue.

I have posted a video of the problem.  As you will see, the AP cancels in CRZ and it happens virtually every time I try to scroll view.  Although not captured here, it also just randomly cancels at CRZ.

As fyi, I walked thru the FBW setup guide and so all my detents are supposedly set according to the guide. 

I appreciate any help as it is very frustrating and has not happened until recently.  

 

 

At the beginning of the video, it looks like the AP disconnects when you move the view back to the right.

Are you using a hat switch to move the view around? Perhaps one of the hat switch directions has a binding to the AP. To check, go into Options, Controls and bring up your controller profile. On the left, click the mouse in Search by Input, then move the hat switch in one direction. See what pops up on the right. Repeat for each hat switch direction, clearing the search by input field each time.

If you are not using a controller to move the view around, try the same thing with whatever you are using to move the view.

...jim

It really looks like a binding problem as JimBrown suggests. The plane is shaking like after a hard rudder input, which would cause AP disconnect. I guess, u are using the mouse to control views?

Matthias

2 hours ago, JimBrown said:

At the beginning of the video, it looks like the AP disconnects when you move the view back to the right.

Are you using a hat switch to move the view around? Perhaps one of the hat switch directions has a binding to the AP. To check, go into Options, Controls and bring up your controller profile. On the left, click the mouse in Search by Input, then move the hat switch in one direction. See what pops up on the right. Repeat for each hat switch direction, clearing the search by input field each time.

If you are not using a controller to move the view around, try the same thing with whatever you are using to move the view.

...jim

Yes..I am using hat switch.  I will check it out.  Thanks.

7 minutes ago, ankh21 said:

It really looks like a binding problem as JimBrown suggests. The plane is shaking like after a hard rudder input, which would cause AP disconnect. I guess, u are using the mouse to control views?

Matthias

No mouse for views.  I am using TCA sidekick hat switch. 

3 hours ago, JimBrown said:

At the beginning of the video, it looks like the AP disconnects when you move the view back to the right.

Are you using a hat switch to move the view around? Perhaps one of the hat switch directions has a binding to the AP. To check, go into Options, Controls and bring up your controller profile. On the left, click the mouse in Search by Input, then move the hat switch in one direction. See what pops up on the right. Repeat for each hat switch direction, clearing the search by input field each time.

If you are not using a controller to move the view around, try the same thing with whatever you are using to move the view.

...jim

Checked..they all match the views I programmed.  No AP binding.

Any other suggestions?

Sorry, no further idea. Is really looks like something is shaking the rudder. When you first reset view you can clearly see, that the airplane is shaking like a dogs tail. And again you can see it in the second top down outside view. And this hard rudder input disconnects the autopilot. So check EVERY assigned controller if there are doubles for rudder or other control surfaces. Beside that I have no idea. 

Matthias