Yet another warthog slew upgrade

[WurzelGummage]

1 hour ago, edmuss said:

Possibly a broken solder joint or wire inside, only way to tell is disassembly.

Cool, thanks, I'll pop it apart and take a look.

 

Edit: I have taken it apart, can't see any obvious issue 

 

[WurzelGummage]

Further edit...

Dismantled, reassembled, now working fine. No idea why, but let's hope it lasts. 

[edmuss]

It's might be a break in the wire between the plug and the daughter board, in one position it breaks connection, flexed another way it makes connection.

A multimeter on continuity connected to both ends whilst wiggling the wires would help identify if it happens again.

[heloguy]

Quick shout out to say thanks.  I have two WH throttles, each with the mod, and one a year older than the other.  The oldest one is going on 6 years old, and they are both going strong.  Wouldn't have a WH throttle without this.  Thanks!

[darkman222]

@Deltaalphalima1For the Force sensor TDC slew upgrade for WW F16EX Throttle your website says that youre awaiting more stock for July 2024. Did I already miss it, and its sold out again, or are you still waiting for it to be produced?

[Deltaalphalima1]

19 hours ago, darkman222 said:

@Deltaalphalima1For the Force sensor TDC slew upgrade for WW F16EX Throttle your website says that youre awaiting more stock for July 2024. Did I already miss it, and its sold out again, or are you still waiting for it to be produced?

Our WW F16EX force sensor is new this month (July) but we have already sold all of the first batch! We are currently making the next batch which should be ready in around two weeks time.

[darkman222]

@Deltaalphalima1 The F16EX force sensor works like a charm. Nice piece of hardware. One thing I am wondering is if there is any way to disable the axis while the sensor is depressed?

I was looking for that in the winwing software which does not offer that option. As there seems to be a firmware for the analog thumbstick I thought, maybe there is something similar for the F16EX force sensor.

Disabling the axis while depressing the TDC helps in the F16 because depressing slews the Aim9 seeker. But moving the axis the same time also enables the radar again and auto locking the bandit which is no good for stealthiness.

[Deltaalphalima1]

21 hours ago, darkman222 said:

@Deltaalphalima1 The F16EX force sensor works like a charm. Nice piece of hardware. One thing I am wondering is if there is any way to disable the axis while the sensor is depressed?

I was looking for that in the winwing software which does not offer that option. As there seems to be a firmware for the analog thumbstick I thought, maybe there is something similar for the F16EX force sensor.

Disabling the axis while depressing the TDC helps in the F16 because depressing slews the Aim9 seeker. But moving the axis the same time also enables the radar again and auto locking the bandit which is no good for stealthiness.

That's great to hear! I don't know of any easy way to disable the axes on keypress. Surely it is possible, but it might need a custom script in simapppro, or extra joystick software.

I'm not to familiar with all that - but I will look into it and see if I can work something out.

[Deltaalphalima1]

On 9/16/2024 at 12:41 PM, darkman222 said:

@Deltaalphalima1 The F16EX force sensor works like a charm. Nice piece of hardware. One thing I am wondering is if there is any way to disable the axis while the sensor is depressed?

I was looking for that in the winwing software which does not offer that option. As there seems to be a firmware for the analog thumbstick I thought, maybe there is something similar for the F16EX force sensor.

Disabling the axis while depressing the TDC helps in the F16 because depressing slews the Aim9 seeker. But moving the axis the same time also enables the radar again and auto locking the bandit which is no good for stealthiness.

I haven’t been able to get simapppro to do it, but I have got it working using a plugin for joystick gremlin. I think that is probably the best way to achieve what you're looking for.

The plugin should work with any joystick and axis/button combination, in case anyone else needs it. It centres and stops an axis from moving when a button is held down. It does one axis at a time, so for the slew you will need to add two instances of the plugin to joystick gremlin, one for X and one for Y.

I have attached the plugin and some instructions on how to set up joystick gremlin and vjoy. It is a bit rushed and based on an old project I did, so let me know if you need any more help configuring it.

stop_axis.py vJoy and setup (stop_axis).zip

[darkman222]

@Deltaalphalima1 Thank you so much. This is the exact thing I am looking for since months if not years now. Although I was hoping for something that didnt need an extra program to be run in the background, yeah, probably unless ED builds something into the "F16 special" menu, thats the best way to do it.

Works just perfect that way. Thanks again!

 

**************************

EDIT 1:

It almost worked. The autostart drops this error:

 

I can click okay, and start joystick gremlin manually after that and it works fine.

*******************************

EDIT 2:

Its a known autostart issue of Joystick gremlin.

Workaround:

Create a *.VBS file like joystick_gremlin.vbs

 

Put that code into the file:

Set oShell = CreateObject ("Wscript.Shell")
Dim strArgs
strArgs = "cmd /c cd ""C:\Program Files (x86)\H2ik\Joystick Gremlin\"" & joystick_gremlin.exe"
oShell.Run strArgs, 0, false

 

And that file then goes into your autostart folder: For example C:\Users\alex\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup

 

Now autostart works. Thanks again for the script!

Edited September 24, 2024 by darkman222

[jonsky7]

@Deltaalphalima1

Hi Delta,

I was wondering if you knew what the other settings were in the Warthog Calibration tool A10_calibration.txt.

Basically, I have replaced the "Friction lever" pot with a hall effect sensor, but I only get travel from about -11,000 to 11,000.

I changed
MultShifts_T   = 0x06;   // 46 
from 0x07

and that gets me to about 20,000 either side of centre, but 0x05 is too sensitive, and I'm reaching 32,767 with about a 1/3 of the axis to go.

Can you suggest anything please?

[Deltaalphalima1]

14 hours ago, jonsky7 said:

@Deltaalphalima1

Hi Delta,

I was wondering if you knew what the other settings were in the Warthog Calibration tool A10_calibration.txt.

Basically, I have replaced the "Friction lever" pot with a hall effect sensor, but I only get travel from about -11,000 to 11,000.

I changed
MultShifts_T   = 0x06;   // 46 
from 0x07

and that gets me to about 20,000 either side of centre, but 0x05 is too sensitive, and I'm reaching 32,767 with about a 1/3 of the axis to go.

Can you suggest anything please?

To be honest I have never worked out exactly what the other settings do in the file. I did look at replacing the friction lever potentiometer a while ago and ran into the same issue as you, where the original pot has a much smaller output range than most alternatives.

You could try to change the variables:

MultInit_TP    = 0x39;   // 54   0011 1001  +57 DEC
MultInit_TN    = 0xDE;   // 55  1101 1110   (twos compliment, I think) -37 DEC

I’m sure they are related, but not sure what they do.

Mabey try changing first to:

MultInit_TP    = 0x0A;   // 54   00001010 +10 DEC
MultInit_TN    = 0xF6;   // 55  11110110 -10 DEC

And then to:

MultInit_TP    = 0x64;   // 54  01100100 +100 DEC
MultInit_TN    = 0x9C;   // 55  10011100  -100 DEC

And see if those change anything obvious?

Other than that, the easiest way is probably to reduce the output of the hall sensor. Either mechanically limit the travel, or electrically reduce the output somehow, to match what the throttle expects.

[jonsky7]

42 minutes ago, Deltaalphalima1 said:

To be honest I have never worked out exactly what the other settings do in the file. I did look at replacing the friction lever potentiometer a while ago and ran into the same issue as you, where the original pot has a much smaller output range than most alternatives.

You could try to change the variables:

MultInit_TP    = 0x39;   // 54   0011 1001  +57 DEC
MultInit_TN    = 0xDE;   // 55  1101 1110   (twos compliment, I think) -37 DEC

I’m sure they are related, but not sure what they do.

Mabey try changing first to:

MultInit_TP    = 0x0A;   // 54   00001010 +10 DEC
MultInit_TN    = 0xF6;   // 55  11110110 -10 DEC

And then to:

MultInit_TP    = 0x64;   // 54  01100100 +100 DEC
MultInit_TN    = 0x9C;   // 55  10011100  -100 DEC

And see if those change anything obvious?

Other than that, the easiest way is probably to reduce the output of the hall sensor. Either mechanically limit the travel, or electrically reduce the output somehow, to match what the throttle expects.

Thank you, I will give that a try,

Windows USB Calibration seems to do the trick, just thought it would be nice to not have to do that.

[h4ruuu]

Hi… im interested with pinky switch and analog slew modification for TM hotas… are they ready stock? Please reply my question

Edited November 29, 2024 by h4ruuu

[Deltaalphalima1]

11 hours ago, h4ruuu said:

Hi… im interested with pinky switch and analog slew modification for TM hotas… are they ready stock? Please reply my question

Yes both are in stock and ready to ship if you place an order through the website

 

[jackd]

Hi Damien

For maybe 3 years i have your slew mod installed, but never installed the calibrated firmware in my TM warthog Throttle, FW v23.

Delta_Sim_Fast_Slew_v100.tmf however wont install. Any ideas?

 

[Deltaalphalima1]

18 hours ago, jackd said:

Hi Damien

For maybe 3 years i have your slew mod installed, but never installed the calibrated firmware in my TM warthog Throttle, FW v23.

Delta_Sim_Fast_Slew_v100.tmf however wont install. Any ideas?

 

 

It looks like the firware tool is failing at the first step, putting the throttle into the "bulk" driver mode, which it then uses to update the firmware.

A few things to try:

1. Make sure you have all the warthog drivers installed (the drivers are required for the update to work, dowload and install "Package drivers - Hotas Warthog - 2018_TMHW_1 + Firmware" https://support.thrustmaster.com/en/product/hotaswarthog-en/#drivers
2. Idealy make sure your throttle is plugged into a USB 2.0 port, directly into your motherboard, not through a USB hub
3. Try running the firmware update tool as administrator

[jackd]

Hi Damien. thnks

My throttle works fine, USB 2.0, admin tried, still NADA.

The latest drivers are 2025_TH_4.exe, in regards of my AVA base for the basic Viperstick.

2018_TMHW_1.exe, is that only TM warthog throttle related?

fw check in TARGET ( idont use it normally) v23:

-----------------------

ADDED: I ran 2018_TMHW_1.exe, that partly fixed it, but i got a new error message:

But it seems it worked in the TARGET check, FW 100  LoL, your slew button works a lot better ! Had to reset the Joy IDs, but all OK now.

BTW thanks:

Edited June 24 by jackd

[Deltaalphalima1]

20 hours ago, jackd said:

Hi Damien. thnks

My throttle works fine, USB 2.0, admin tried, still NADA.

The latest drivers are 2025_TH_4.exe, in regards of my AVA base for the basic Viperstick.

2018_TMHW_1.exe, is that only TM warthog throttle related?

fw check in TARGET ( idont use it normally) v23:

 

-----------------------

ADDED: I ran 2018_TMHW_1.exe, that partly fixed it, but i got a new error message:

 

But it seems it worked in the TARGET check, FW 100  LoL, your slew button works a lot better ! Had to reset the Joy IDs, but all OK now.

BTW thanks:

 

 

I think 2018_TMHW_1.exe is for the throttle and the original stick base, and 2025_TH_4.exe is just the new AVA base.

Ideally it should have no errors during the firmware update, so i'm not sure what's going on there, but if TARGET is showing V100 and your thorttle is working then you should be good to go!

[jackd]

PS my X-axis works fine with your mounted button and FW 100, but the Y-axis keeps oscillating ... any ideas to fix this?

[Deltaalphalima1]

20 hours ago, jackd said:

PS my X-axis works fine with your mounted button and FW 100, but the Y-axis keeps oscillating ... any ideas to fix this?

That is probably a calibration issue after the update, it shouldn't really change anything, but sometimes it seems to.

Can you try the calibration procedure and see if that fixes it?:

1: Clear any existing Windows calibration in the game controller menu by going to  
Set up USB game controller >> Throttle HOTAS Warthog >> Settings >> Reset to Default >> Apply >>OK
(If Apply is greyed out then the calibration is already cleared, and you can move on to the next step.)
 
2: Check if you have any other joystick programs that could interfere with the calibration - such as TARGET or JoystickGremlin.
You may need to disable them while you run the calibration.
 
3: Download the latest version for the calibration tool from my website (Thumbstick_Sensor_Calibration_Tool)
Make sure you have extracted the zip file after downloading. The "A10_calibration.txt" file must be in the same folder "Throttle Warthog Calibration (V1.07).exe" is run from.
 
4: Run the calibration tool and carefully follow the on-screen instructions. It should run through all the way through with no error messages.
Be very careful to move the throttles to the OFF, IDLE and MAX positions when asked.
OFF is the fully back position over the detent lifts, IDLE is the next stop up or the minimum flight setting, and MAX is the fully forward position over any afterburner detents.

If you have any custom detents or afterburner lifts installed, you might need to remove them temporarily for the calibration.

When running the calibration tool, it’s only necessary to push the sensor until it just reaches the edge of its travel, don't push it with force further than that.

 

 

[jackd]

That worked, Thanks

[darkstarRAF]

TM Warthog slew replacement suddenly stopped working. Pressing it works fine (button 1 response normal) but X/Y is in dead center and so far nothing helps, driver update, recalibration with v1.07, firmware upgrade to 100 - didn't help. Any ideas?

Edited Sunday at 10:01 PM by darkstarRAF

[darkstarRAF]

Tried to reseat it, also tried to switch connectors - didn't help. It was working fine few days ago and the only thing that changed is USB port throttle plugged in now (I was moving PC around). Tried different ports - no luck

[Deltaalphalima1]

10 hours ago, darkstarRAF said:

Tried to reseat it, also tried to switch connectors - didn't help. It was working fine few days ago and the only thing that changed is USB port throttle plugged in now (I was moving PC around). Tried different ports - no luck

If it stopped working when you were moving things around, it could well be a problem with the wire/connector that might have shifted.

The best way is to disconnect both ends of the sensor cable and swap them around, so the end that was connected to the slew sensor is now connected to the throttle and vice versa, that will make sure all the connections have been re-seated in case there is any dirt or corrosion causing a problem - and then try running the calibration again after reseating the cable.

If the calibration was run when the sensor wasn't working, it can get stuck with a 'zero' calibration, which can to be fixed by running the tool again when it is working properly. If it's still not working do you have the original sensor you could test with?