Re: Replacing microstick double pot - latest intelligence please

Hi,
Does anyone know the 6 pins conector brand that the Cougar microstick have on the pcb?
I know it is a 6 pin male conector, but do not know its pitch and if it is jst, fpc or other type of conector.
I want to try build the pcb to be used with a RKJXV1224005 microstick, but i need the conector specs in order to make it “plugable”. Not sure if it is the right word or expression. 😄

Thanks in advance!

@mjones https://forum.falcon-bms.com/topic/27236/radar-cursor-axes-change-when-changing-usb-input-on-pc

I have mine set to 30,20,30,20, and not had issues in any modes TGP/FCR VR and 2D. Here’s a video of how that looks during alignment…

Just a clarification on the update driver from control panel.
u must select the Browse my computer for drivers and point to the folder where the drivers are
which is
C:\Program Files (x86)\HOTAS\drivers

U must do this for
Thrustmaster HOTAS Cougar (IN)
AND
Thrustmaster HOTAS Cougar (OUT)

@Puckertoe All I did was do the washer and axel pad things and it worked great. https://cougar.flyfoxy.com/mods.php#smooth
I did not do the rest on that list. I also put friction tape on the barrel not electrical tape. The friction tape makes smoother movement when making small corrections.

@sabre185 said in Cougar Startup:

Mine looks like this,
034d76dc-2bbe-4473-ba9e-3df9e73abdaa-image.png

Mine too.

My Cougar works under Win11!and Throttle!

@Atlas I have the FCC3 mode in my Pit and a new Cougar that I converted (Throttle) to a Hall Sensor
@Badger @JollyFE That’s exactly what I was looking for and couldn’t find, I had the instructions too???
Thank you

Now I have to install another Hall sensor with a larger angle (180 deg) I only have 90, that’s not enough…

Thanks to everyone who responded and helped

Ran BMS 3.73 today, rudder pedals working perfectly. The crimped wires are not a factor. I have heard the expression, “If it isn’t broke, don’t fix it”, Yes, I was using the sim when he chewed the cable under my desktop. I was so focused on the game I didn’t notice what was happening until I lost rudder control. Initially thought it was a BMS 3.73 bug as I am no longer using the Cougar CCP with the new Launcher. Interesting, the cat does not like an AC electrical cord. I was worried about that as well, thanks!

@Icarus I spent the holiday break fixing bugs and filling gaps, that should allow everyone to become an AL user…

@Gavlar50 Perfect, happy for you! Just be aware that as I understand your setup you shouldn’t change any key or axis in falcon or that will mess your setup. Always use the alternate launcher to avoid any issue 🙂
Enjoy this crazy sim!

@Magic49th

Hi Magic,
I found the solution, what I did was change the sequence in the DeviceSorting.txt file Let’s say your answer pointed me in the right direction
THANKS

@jcook said in Trim question:

For the nose up, down, left, right trim hat-switch on the joystick, is there a way to adjust the amount of trim being applied when the button is moved?

Nope.

Hi gents,

I’ve experienced weird issue with keymapping using Launcher running under Linux
For some strange reason I cannot map few buttons on TM Cougar TQS+RS TUSBA2.
Problem is key/button mapping dialog ignores input from COMM up/left/right, DF override forward and SpeedBrake switch forward.
While it’s perfectly happy with COMM down, DF aft/centre and SB aft/centre, Cursor enable and Man uncage.
What makes it weird main Launcher window on mapping tab correctly reports all of the stubborn buttons just fine 😕
Any suggestions?

'till I’ll solve this issue, I’ll stick with oldschool way (man editing keyfile by hand seems to be the fastest way to do the job for me).

@Dukera Thanks for the reply. Sounds like some freq. interference on the USB circuit.

@Virus to be honest, although the force sensor is far superior in many ways, right now I am happy with the setup, as it is much easier to install. When I first upgraded the Cougar, it took me some time to build a rig that could withstand the forces I applied to the stick and I broke the first attempts. I am also considering at one point, for reasons I cannot expand on right now, to switch to a centre stick setup so a force sensor is a no-go.

The throttle is still fully functional and the throttle axis response is quite decent for a 20+ years old machine, but it is time to move on to something with AB and idle detents and a control panel.

Fly safe
-Skipper

@gusva 👍

I use the Cougar Throttle which is connected via TUSBA R2. Unfortunately, in the ALTERNATIVE LAUNCHER I can not map the function of the comms switch. The switch is recognized in the keymapping (DX2,DX3,DX4,DX5) but only the function “TQS: COMMS Switch down - VHF” is correctly assigned with DX2. UHF, IFF OUT and IFF IN are always assigned to DX1.

Does anyone have an idea?

Problem solved: I forgot to disable the COMMS OFF button in the Realsimulatur HID Device Tool under the TUSBA R2 section. This disables the comms switch center position DX1 button.

Why only “TQS: COMMS Switch down - VHF” is correctly assigned with DX2 even if DX1 is not disabled remains a mystery…