December 8, 201114 yr Morning to alli write this post because i want describe you an A/P's problem, problem caused, probably, by me.Well, the situation is the follow:"CMD A" button is on and active as F/D and A/T are active too.Flight level 100, SPD active, LNAC active too.Now, for one any reason, i decide to take the cloche and dive the aircraft (the truth is that my son, 2 years, look at me, little smile, and grabs the stick in 3 seconds )Ok, after this the alarm A/P starts to ring and then i switch it off. So, i wish to rearm the "CMDA" button but it's impossible! A little flash of the lights but always the button goes off.Well, but the "CMD B" button is avaible.Armed it, the autopilot returns to work well. But another dive caused by my son... another one alarm by A/P, switched off. So, i tried to arm CMD B but same as CMD A. Little lights then switch to off. NO CMDA in avaible, NO CMDB is avaible.With no success i've tried to push "Z" button, the "DISEGAGE" bar on MCP and "DISENGAGE BUTTON" on 3d cloche.What do i wrong?Thanks in advance. Emanuele
December 8, 201114 yr Hi Crostino,I'm very interested to see this post because I have recently posted with EXACTLY the same problem:1) Unscheduled (to put it politely) nosedive 2) A/P disconnect horn3) CMD A failure with the same momentary on/off blink of the arm light4) CMD B operationalI think the consensus here is that there's a problem caused by our control stick that causes the initial dive. This translates to sudden movement on the yoke which breaks CMD A. Your CMD B failure will probably have been caused by the same.I hope there's a fix, although I've only experienced this once :)Sincerely, Louis Vallance | P3D v4.5 (no shaders) | i9-9900K | 32GB | RTX 2080
December 8, 201114 yr I'm pretty sure I've seen a documentary where this behaviour caused a crash.I.e. It's meant to be that way. Pushing the stick too much while the AP is on should disconnect it. If I recall correctly, throwing the AP disconnect and re-engaging it might help afterwards.Check the manuals, pretty sure you'll find something in there about it. Sam Allen
December 8, 201114 yr It is to do with some mechanical system being broken if too much force is applied to the control column during AP use, or something...It is in the manuals somewhere...Andrew Andrew Entwistle
December 8, 201114 yr You've likely sheared off the rivets connecting your yoke to the AP. If that's the case you're stuck flying manually until you're on the ground. AT will still work, so you've still got one paddle at least.EDIT: It takes a great deal of force to do this in real life. Without accurate force feedback the same thing can inadvertently happen in the sim with a large deflection on your yoke. Kenneth Weir My Saitek yoke mod i7 2600k @ 4.7 8GB Gskill CAS7 2x GTX580 SLI Surround + GT520 Accessory Win7x64
December 8, 201114 yr As told in previous posts, you broke both AP shear pins disconnecting the autopilot actuators from the controls. This means that your A AP first, and B after, are both broken. They must be fixed on ground. Regards Andrea Daviero
Create an account or sign in to comment