[NO BUG] Pitch Axis "Goes To Sleep" ?

[Emmy]

Perhaps I'm not understanding the FBW system yet, but when I fly straight and level for more than about a minute, pitch becomes unresponsive until I give a pretty good yank to wake it back up. Most unfortunate in close formation...

 

No A/P modes are engaged.

 

TM Warthog Stick and Throttle with Curves at 0 and a dead zone of 1.

[NineLine]

Just straight and level, nothing fancy going on? Could you include a short track that shows the issue?

 

Edit: Just flew straight and level myself, and only ever saw this breaking out of autopilot.

Edited May 31, 2018 by NineLine

[Emmy]

I'll effort that miracle...

 

But yeah, just straight and level with no A/P engaged. Roll remains responsive but Pitch seems to develop its own "Dead Zone"

[Emmy]

So I think I understand what's going on now...

 

Took off from Nellis direct Mormon Mesa

Hand flew until I was bout 20 DME from the VOR with no resistance or hesitation in pitch or roll.

Engaged the BALT A/P until 15 DME

Disco'd the A/P BUT the jet wanted to keep flying as if it were on A/P

THEN it needed a sizeable pull to be back under fine control via joystick.

 

Something in the A/P system is not letting go of the FBW (?)

 

Track Attached...

Pitch Goes To Sleep.trk

[Wags]

Paddle switch to disengage A/P.

[Emmy]

Even if you deselect a mode? No : next to anything?

If that's the case, then my bad and disregard.

[Emmy]

Ok, this is my "Embarrassed Face"

 

You do indeed have to pull the Paddle to fully disco' the A/P even with no active mode.

 

Disregard...

[Wizard1393]

I'm confused by this AP. I've had BALT and RALT to work a few times, don't know how, but most of the time, it won't kick in. It starts the AP, showing the A/P notice in the HSI, but it does not engage any kind of alt hold and is not marked with the colon on the UFC. Am I missing something? I also get a warning/attention message in the HSI saying "AUTO PILOT".

Are there certain criteria to have BALT working? Also, If the attitude selector switch is set to STBY as in using the Standby Attitude Indicator, I get a master caution saying "INS ATT". Liddle help here plz? :)

 

EDIT: Also, once when I had BALT working and engaged at about a 1000ft, I switched to RALT and the plane violently pitched down causing a blackout and when I came to, I was in a ~20 deg dive and 100 feet to go to the ground.

Edited May 31, 2018 by chrisofsweden

[Jack McCoy]

I'm confused by this AP. I've had BALT and RALT to work a few times, don't know how, but most of the time, it won't kick in. It starts the AP, showing the A/P notice in the HSI, but it does not engage any kind of alt hold and is not marked with the colon on the UFC. Am I missing something? I also get a warning/attention message in the HSI saying "AUTO PILOT".

Are there certain criteria to have BALT working? Also, If the attitude selector switch is set to STBY as in using the Standby Attitude Indicator, I get a master caution saying "INS ATT". Liddle help here plz? :)

 

EDIT: Also, once when I had BALT working and engaged at about a 1000ft, I switched to RALT and the plane violently pitched down causing a blackout and when I came to, I was in a ~20 deg dive and 100 feet to go to the ground.

 

A flight partner and I both experienced the same problem: I found out that the AP baro and radar altitude modes won't engage (or rather disengage immediately) when the pitch (and maybe roll) joystick input is not absolutely zero (0). I fixed that by putting a deadzone of 4 on my Warthog's pitch axis. This value may of course vary with the quality or construction of your stick.

[Wizard1393]

A flight partner and I both experienced the same problem: I found out that the AP baro and radar altitude modes won't engage (or rather disengage immediately) when the pitch (and maybe roll) joystick input is not absolutely zero (0). I fixed that by putting a deadzone of 4 on my Warthog's pitch axis. This value may of course vary with the quality or construction of your stick.

 

Ok! So thats what it is then probably thanks! I've got a warthog too and never ever had to use any deadzones on it. Can anyone from ED or other knowledgable person comment on whether the AP BALT/RALT should require absolute zero stick input?

[Wags]

A flight partner and I both experienced the same problem: I found out that the AP baro and radar altitude modes won't engage (or rather disengage immediately) when the pitch (and maybe roll) joystick input is not absolutely zero (0). I fixed that by putting a deadzone of 4 on my Warthog's pitch axis. This value may of course vary with the quality or construction of your stick.

 

You need to be within roll and pitch parameters for the AP to engage.