markturner1960 Posted May 12, 2020 Posted May 12, 2020 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.
markturner1960 Posted May 13, 2020 Author Posted May 13, 2020 (edited) 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 May 13, 2020 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.
Spins321 Posted May 17, 2020 Posted May 17, 2020 Hello, I have the TUSBA with an unmodified F-16 Cougar TQS. Unfortunately, I can't really help. I'm also trying to figure out the best way to model idle detent and also getting the comm switch to work with SRS.
markturner1960 Posted May 18, 2020 Author Posted May 18, 2020 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.
Grits26 Posted May 20, 2020 Posted May 20, 2020 (edited) Thanks for your posting this. I have a TUSBA and Vipergear Throttle Hall sensor on the way, this will definitely help using this as reference! Edited May 28, 2020 by Grits26
Magoo5150 Posted May 27, 2020 Posted May 27, 2020 Oh sweet, the throttle C-MUK is back in stock! I just ordered one too... man the shipping is more than the C-MUK itself.
Recommended Posts