TUSBA problems
-
I have a TUSBA R2 that I am having trouble with. I am reaching out to the manufacturer, RealSimulator, but thought I would also seek some assistance in the BMS controller forum. I have read through the posts here but have not found a solution. If there is a TUSBA user out there that can help – I’d really appreciate it.
In the standard Thrustmaster HOTAS configuration, where the throttle connects to the joystick and the joystick connects to the USB port – everything works. All axes and buttons function properly. I have installed a brand-new x/y cursor switch for the radar cursor and a hall-effect sensor has replaced the original potentiometer. So, I should be getting good signals. Every switch is correctly mapped in the BMS configuration section and the x/y radar cursor is dead center perfect.
I do not use any of the Foxy macro programming - all buttons are used as in the real jet.
The two main reasons I want to use the TUSBA are: greater fidelity/accuracy with the throttle axis and to convert the throttle’s connection to USB. This will work better for me in the simpit environment.
I’ve installed the TUSBA and configured it with the RS HID Tool as instructed from RealSimulator’s video and manual. As far as I can tell it’s done correctly.
I then configured all the buttons and axes in the BMS configuration section. I have also disabled the throttle axes in the Thrust Master CCP program.
Connecting the throttle to the TUSBA - TUSBA breaks the radar cursor control and throttle.
-
Throttle indicator in BMS config only goes about 70% up the blue bar in the BMS configuration section. The throttle, full forward, does not go beyond that 70% blue bar with the TUSBA. I cannot get into afterburner, the PPH gauge doesn’t get above 15,000. With the standard Thrust Master connection (no TUSBA) I can get 60,000+ pph in afterburner.
-
The second issue is that the x/y cursor is no longer centered and moves on its own, TUSBA has somehow messed this up because it worked perfectly in the default setup .
As soon as I get airborne in Falcon BMS the radar goes active. The radar cursor starts moving on its own to upper right corner, this bumps the range up to the next level then repeats the travel to the upper right corner again bumping the range up to where it reaches the top (5, 10, 20, 40, 80, 160) and max’s out at 160 nm. At this point the cursor is at the very top of the MFD and repeatedly travels from center to the right side of the screen along with the vertical bars.
I have tried setting dead zones in BMS and in the RS HID tool – it doesn’t make a difference. And, dead zones should not be needed anyway – since the cursor works fine in the standard configuration.
Any thoughts I what I should try?
-
-
Have you installed RealSimulator Device Tool?
I think you should check your TQS each button and axis by the tool.
Tusba requires some modification and adjustment by the tool.
Please refer RealSimulator Device tool manual when you check your TQS.There is tip, your TQS throttle with hall sensor moves little distance in the tool, so do not worry about that.
That’s normal. -
@jcook I am using TUSBA for a long time, and If I remember well, you should do the calibration first, thru windows control panel/devices.
-
I agree with koskar12, you can also check if the running mouse is due to the microstick or TUSBA by checking the controller advanced option in the “in game” setup. If the x and y axes are not showing any displacement then it must be calibration of the TUSBA. The RS-DEV-TOOL should show a displacement for the cursor.
-
I have a faint memory of this same issue. I believe I tried a different USB port and it seemed to work .
-
as @koskar12 Says,
Mine is an R1, but should work the same.Place to start is with windows. See if its correctly connected to windows, then you can look at the additional middleware, and BMS.
Try not use a USB hub, and connect directly to your MB or USB riser PCI.
Its plug n play, so should show up as a controller in windows. If it does then from the settings tab on the properties window you can calibrate the axis, (control panel, Devices & Printers, ) If you can’t get all the buttons moving and showing up on this as they should, then you have a hardware or device driver issue.
-
@jcook I had the same issue. None of the Manufacturers recommendations worked for me. Tried everything but even manual entries would not force the Tusba to go to 100%. Could never get it to go above 70%. I ended up disconnecting it and putting g it in the drawer. I then went and flashed the firmware on the Cougar.
My Cougar then worked properly so didn’t need to go back to the Tusba R2. Since I have the Warthog stick, I just put the Cougar stick under my desk and fly with the Cougar Throttle and Warthog stick. -
Thank you all for the input.
bstar07 - yes, as I mentioned in my post I setup the TUSBA with the RS HID tool following the manual and their setup video.
Koskar12 - I think initially I did open the Windows tool and tested the axes and buttons, don’t remember doing any ‘configuration’ though. Everything seemed to work fine there. Last time I went into the Windows config, I didn’t see a tab for checking the axes and buttons as I had seen before. So that’s strange.
Alfred - the ‘running mouse’ did not show up anywhere except in the MDF when flying. Everywhere else it was stationary and centered.
MudDog - Congratulations. I tried another USB, switching ports while the PC was running. This got things working (see below).
Fish44 - I’m plugged directly into a USB 2 port on the back of my PC. Haven’t tried a USB 3 port yet.
Here is what I did:
While my PC was on I unplugged the TUSBA and then plugged it into a different USB 2 port. I then entered BMS and tested the throttle axis and it now goes to the full bar height! So that is progress. Next I tested the Flight Control and Avionics pages in the advanced setup – all the settings were still there – so that is progress also.Next I took a flight and I had better control over my throttle, and x/y cursor. So now things are working, I still need to do some experimenting and adjustments. The X/Y cursor needs some adjustment, maybe inverting it – I’ll have to fly it a bit and make some incremental changes. But, the cursor sliding all over the MFD no longer happens.
I did notice a strange thing when moving the throttle from MIL power into the Afterburner section, an input button appeared. See the photos below.
In the first picture I am at MIL power (just under afterburner) – it shows: INPUT Button 78 (No Function Assigned)
In the second picture I have entered the Afterburner – it shows INPUT Button 79 (TQS: SPEED BRAKE Switch – Close)
I don’t the there should be any button assigned to the throttle movement – whether the button has an INPUT defined or not.
I think this maybe the range settings in the RS HID Tool, where the MIN, IDLE, MIL, AFT, MAX ranges are set.
This last picture is an example picture from the manual to show what I mean. It doesn’t represent my settings.
How can I get rid of the SPD BRAKE Switch - Close input when going into afterburner? -
@jcook Pls see the below picture. Its all in Greek Windows, but I have highlighted the selections that I had made. I think in English the term should be: micro Adjustment. Then just follow the instructions. If you see under settings only the Test button, then I would unplugTusba and re-plug again. If you have already done all the above, I am afraid that I cannot help more my friend.
Concerning the issue with the SPD BRAKE sw, I have the same switches enable. but it does not affect the SPD BRK function in my setup. Pls check if in your setup SPD BRK is enabled in more inputs. In my setup SPD BRK is 73, 74, 75.
If this is not helpfull, I would consider to go back to RS_HID_DEV_TOOL, and redo the Pairing function. -
Have you changed key file such as BMS - BasicDX WH TUSBA.key?
It looks like your direct X button numbers on throttle shift are conflict.
You have to modify throttle shift direct X button numbers to fit your environment.
That’s explained in Tusba manual and BMS one.
for example.SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 “========== THROTTLE SHIFTED ==========” <-- Original one
Comms Off (Center) (Win DX289 = BMS DX288)
SimDoNothing 288 -1 -2 0 0x0 -1
Comms VHF (Down) (Win DX290 = BMS DX289)
SimTransmitCom2 289 -1 -2 0 0x0 -1
Comms UHF (Up) (Win DX291 = BMS DX290)
SimTransmitCom1 290 -1 -2 0 0x0 -1
Comms IFF In (Right) (Win DX292 = BMS DX291)
SimCommsSwitchRight 291 -1 -2 0 0x0 -1
SimDoNothing -1 0 0XFFFFFFFF 0 0 0 -2 “========== THROTTLE SHIFTED ==========” <-- Modified one to fit my computer environment.
Comms Off (Center) (Win DX289 = BMS DX288)
SimDoNothing 320 -1 -2 0 0x0 -1 Original one SimDoNothing 288 but mine is 320.
Comms VHF (Down) (Win DX290 = BMS DX289)
SimTransmitCom2 321 -1 -2 0 0x0 -1
Comms UHF (Up) (Win DX291 = BMS DX290)
SimTransmitCom1 322 -1 -2 0 0x0 -1
Comms IFF In (Right) (Win DX292 = BMS DX291)
SimCommsSwitchRight 323 -1 -2 0 0x0 -1
-
@jcook
The analog (throttle) and digital (button) circuits are completely separate.
You should not see any change of button inputs to the game while moving the throttle unless you have some damaged wiring which is shorting when you move the throttle. Like i said before check the hardware first. -
@jcook said in TUSBA problems:
How can I get rid of the SPD BRAKE Switch - Close input when going into afterburner?
To ensure you do not have DX buttons 14, 15 & 16 bound to your throttle axis, you should have your Idle, Mil & Aft buttons display a darker grey inner box, to achieve this you right click on each of these buttons as in my picture.
Any green, as in your picture, means that part of the throttle range has a DX button bound to it, if the other two buttons are light grey then they are also bound - you cannot right click Min or Max.