Jump to content

Cougar throttle / TUSBA issue


markturner1960

Recommended Posts

Hi, I have just installed my newly modified cougar throttle ( fitted a hall sensor upgrade) and connected using the TUSBA R2.

 

I calibrated within real simulator HID tool, however, the throttle axis is not correct, it shows idle as max and is at 100% when in idle position. I thought this could be easily fixed by inverting the axis, however, it wont let me check the INV box next to the axis.

 

Can someone tell me correct procedure to correct this and calibrate the throttle axis and detent positions please?

 

As I have replaced the hall sensor, may this be something to do with the position of the sensor?

 

Thanks

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor. Tir5. PC2 ( Helo) Scan 3XS Intel 9900 K, 32 GB Ram, 2080Ti, 50 inch Phillips monitor

 F/A-18C: Rhino FFB base TianHang F16 grip, Winwing MP 1, F-18 throttle, TO & Combat panels, MFG crosswind & DFB Aces  seat :cool:                       

Viper: WinWing MFSSB base with F-16 grip, Winwing F-16 throttle, plus Vipergear ICP. MFG crosswind rudders. 

Helo ( Apache) set up: Virpil collective with AH64D grip, Cyclic : Virpil CM3 base & TM F18 grip, MFG crosswind rudders, Total controls AH64 MFD's,  TEDAC Unit. 

 

Link to comment
Share on other sites

EDIT - Not resolved

 

I am told by Malc from BMS who installed the viper gear hall sensor upgrade, that some of these come with a wire reversed, which is why max and min are reversed. He said this can be solved by inverting the axis in software. I have done this in the real simulator HID tool software for the TUSBA, however, in DCS, in the viper, although the axis is the right way around now, afterburn kicks in at idle.

 

Is there any users out there with cougars and the TUSBA, who are sufficiently knowledgeable to help with this? I feel it may be something to do with where the various detents are set in the TIUSBA software, I have done this but am not sure if it is correct.

 

Thank you


Edited by markturner1960

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor. Tir5. PC2 ( Helo) Scan 3XS Intel 9900 K, 32 GB Ram, 2080Ti, 50 inch Phillips monitor

 F/A-18C: Rhino FFB base TianHang F16 grip, Winwing MP 1, F-18 throttle, TO & Combat panels, MFG crosswind & DFB Aces  seat :cool:                       

Viper: WinWing MFSSB base with F-16 grip, Winwing F-16 throttle, plus Vipergear ICP. MFG crosswind rudders. 

Helo ( Apache) set up: Virpil collective with AH64D grip, Cyclic : Virpil CM3 base & TM F18 grip, MFG crosswind rudders, Total controls AH64 MFD's,  TEDAC Unit. 

 

Link to comment
Share on other sites

Ok, resolved... my issue was the TUSBA adds additional axis, which you don’t need. Get rid of these and everything works as it should. The reversed axis is misleading, it’s just the way the TUSBA reports it.

System specs: PC1 :Scan 3XS Ryzen 5900X, 64GB Corsair veng DDR4 3600, EVGA GTX 3090 Win 10, Quest Pro, Samsung Odyssey G9 Neo monitor. Tir5. PC2 ( Helo) Scan 3XS Intel 9900 K, 32 GB Ram, 2080Ti, 50 inch Phillips monitor

 F/A-18C: Rhino FFB base TianHang F16 grip, Winwing MP 1, F-18 throttle, TO & Combat panels, MFG crosswind & DFB Aces  seat :cool:                       

Viper: WinWing MFSSB base with F-16 grip, Winwing F-16 throttle, plus Vipergear ICP. MFG crosswind rudders. 

Helo ( Apache) set up: Virpil collective with AH64D grip, Cyclic : Virpil CM3 base & TM F18 grip, MFG crosswind rudders, Total controls AH64 MFD's,  TEDAC Unit. 

 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...