TM Warthog APDIS inverted?

[Boris]

I've been using the Warthog in its default configuration for the A-10C, but recently I've been playing around with target to program the buttons for other modules.

 

I've come across a weird behavior with the APDIS (autopilot engage / disengage button) on the throttle base.

 

The button registers as pushed constantly and pushing the button ceases the action. This means, that if I want to assign a "hold" function to the button, such as for jettisoning stores, the button is constantly pressed and only "unpressed" when I physically push the button.

 

This surely can't be normal behaviour, can it?

[txmtb]

Just checked mine, it's button 26 and shows as off, then on when pressed. Maybe something is screwy with the target config.

[DeepDrummer]

I've been using the Warthog in its default configuration for the A-10C, but recently I've been playing around with target to program the buttons for other modules.

 

I've come across a weird behavior with the APDIS (autopilot engage / disengage button) on the throttle base.

 

The button registers as pushed constantly and pushing the button ceases the action. This means, that if I want to assign a "hold" function to the button, such as for jettisoning stores, the button is constantly pressed and only "unpressed" when I physically push the button.

 

This surely can't be normal behaviour, can it?

 

Remember there are two buttons in one at that location. It messed me up for a minute.

What happens in the lower half ( I forget the name, on office machine here) could affect your outcome if you push hard..

[DeepDrummer]

Because it is a two position button, there would be continuity at the top and bottom with middle being open, I would guess. Press halfway will be the release point.

 

OMG. I just realized that I avoided the lower half probably because I looked at it A$$ backwards.

I used the paddle S4 to shift just the top button to use it effectively.

It's like a 3 position toggle switch spring loaded to the down position with two stages from there.

 

Target can apply a function to the ON, OFF, OFF to ON, On TO Off.

The switch is probably behaving normally. I'll have to fire up my other machine to test.

 

Yes. I knew I had troubles exactly like that.

I just ran and checked my sheets.

My BF 109 + Spitfire is finished (not using the lower PENG or whatever the lower half is called) and both seem to work perfectly.

My P-51 has only ONE bone of contention.

I set the rockets/bombs switch to the bottom of the APDIS on the P-51 and it does not switch but activates APDIS instead of it's lower half.

Thank you sir. Here's hoping I just needed to look at it differently.

We'll switch things around and figure it out later today.

The bottom line is, I would not fault the switch.

[DeepDrummer]

Just checked mine, it's button 26 and shows as off, then on when pressed. Maybe something is screwy with the target config.

 

It's the "hold"

Since that button is 3 position with the first position ON then the "Hold" in the statement is keeping it on until it releases from moving off the held position. Hold should be used on 2 position spring loaded switches that are normally open to be easily done although there are probably workarounds.

 

Using the "pulse" instead of the "hold" is the way to go here and in most cases or better use the bottom section of the same button which functions like a normal 2 position spring loaded to off switch.

In the Target GUI click the side of the button to see the lower half. drag and work with that to make it simple or use a different switch.

 

"Hold" continues the action until release

"Pulse" sends the command once and stops sending the command and so "pulse" will jettison stores yet not keep the Button in a "hold" and so.

Hold is for gun triggers, zoom in slow zoom out slow and things that require you to hold a two position button (not 3) on until you are finished performing an action that requires it. Spring loaded to the off position is the best place to use "hold" and only if required.

For irrecoverable things like jettisoning stores or opening canopies, I have been assigning some to a second layer activated by the S4 lever so I don't inadvertently do things I don't want in flight.

 

So yes, the script with the "hold" is causing it. I believe.

 

That switch is weird but normal.

 

Another real easy solution is to simply use the bottom half of that switch instead. That way, there is no "pulse" or "hold" on start up and one could then use it as a "hold" and it should work fine since it releases when released.

 

 

Use "hold" sparingly.

I NEVER use Press and Release

Edited July 24, 2017 by DeepDrummer