Unable to engage autopilot

[Schrute, Paper Sales]

I’ve followed the instructions ironmike has given in other threads to the T, but I cannot get the autopilot to engage.

Steps I’ve taken, with no autopilot engaging:

     

• Tomcat steady trimmed at 0 fpm on the VSI. Other times, well within the +-200 fpm limit.
• AP engage.
• Alt hold.
• AP ref light lit.
• NWS/AP ref button pushed.
• AP ref light stays lit

 

Conditions I’ve used, with no autopilot engaging:

• Speed above and below 400 knots.

• VSI well within +-200 fpm. The video I’ve posted shows the tomcat perfectly trimmed.

• Cold start with full alignment and air start.

• Completely deleted and removed all mods and verified the integrity via steam.

• Completely deleted the tomcat module, and all associated files, and redownloaded through steam.

• Tested on both A and B models.

• Tested SP and MP.

• Used both keyboard and keybind for the NWS/AP ref button. Even remapped both.

 

Video for reference. Please note, the F-14VUX mod was deleted. But I used it here so you can more easily see everything.

Discord: https://discord.com/channels/269535523922509826/420225846196961280/870318918613475328

Imgur: https://imgur.com/sutwrnF

[Callsign JoNay]

That's weird man. The new AP is definitely more specific, but I use it multiple times on the daily.

[captain_dalan]

22 hours ago, Schrute, Paper Sales said:

I’ve followed the instructions ironmike has given in other threads to the T, but I cannot get the autopilot to engage.

Steps I’ve taken, with no autopilot engaging:

     

 

• AP engage.
• Alt hold.

 

 

Shouldn't this be inverted? First alt hold (or whatever you wish to select), then AP engage? I always do it in this order. Direction hold, alt hold THEN AP engage. 

[Schrute, Paper Sales]

22 minutes ago, captain_dalan said:

Shouldn't this be inverted? First alt hold (or whatever you wish to select), then AP engage? I always do it in this order. Direction hold, alt hold THEN AP engage. 

No, ironmike spelled it out specifically. Still, even doing it that way doesnt work.

[Golo]

2 hours ago, Schrute, Paper Sales said:

No, ironmike spelled it out specifically. Still, even doing it that way doesnt work.

Just tested it in A, works fine on my end. If you try again drop track file here, I will check it.

[Schrute, Paper Sales]

A little rough, but should get the point across.

autopilotnoworkytrack1.trk

[Golo]

1 hour ago, Schrute, Paper Sales said:

A little rough, but should get the point across.

Ive checked it. You are set correctly for it to work. In track Ive waited until you set your switches and VS, than waited for 1-2 tries of your attempts to engage. Than all I did was just take control and pressed my AP Ref. button, did not work right away I had to reset to 0 fpm VS, because there was a pitch up when I took control for whatever reason. Other that that it worked just fine.

My one guess is there is something wrong with your AP Ref. button binding. My second one, are you trimmed to 0fmp or are you wrestling with the stick to keep it level? You should be trimmed.

[Schrute, Paper Sales]

I just threw that track together, but both times the stick was trimmed. And in the video, perfectly for about a minute or two. And I've remapped the ref button. Just doesn't want to work for me.

[Schrute, Paper Sales]

Following the advice of this thread, I was able to narrow the problem down.

 

With my Thrustmaster T1600M plugged in, the AP will not engage. Without it, works everytime. Tested where it was the sole peripheral, other then mouse and keyboard. Pitch and roll are the only axis bound. Tried deadzones of 0-5, none worked. My own windows game controller utility shows no unwanted movement. It's the only issue I have with this controller, and this is the only module which has exhibited any problems with it.

[Schrute, Paper Sales]

Unbinding and rebinding the axis for both pitch and roll seems to have done the trick. Seems to be working okay now.

[gswindle]

1. Controls:

 You must increase the dead zone in the axis

tune, both the horizonal and vertical.

I have a dead zone equals three. 

I had originally set it zero and there's a little bit too much play in my stick And the autopilot article hold would not function.

I changed it to a three and it works fine.

 

Let me know if that works for you.

 

Good luck

T Swindle 

[gulredrel]

Had the same problem as the original poster.

Rebinding and setting deadzone with my T.16000 did the trick. Was able to engage AP after doing that again.