TQS Microstick requires re-calibration all the time
-
Until recently, I used my recently acquired TM Cougar + TQS with my old Q9550 and ASUS P5Q SE2 motherboard, running Windows 7 x64 and BMS 4.33.3.
Once I had my Cougar and TQS calibrated and configured, the microstick would always just work immediately when I booted up my PC and jumped into BMS.I recently upgraded my old rig with an i7 3770 and Intel DQ77MK motherboard and reinstalled Windows 7 x64 to ensure that I wouldn’t have any issue with lingering drivers and old crappy installs, etc.
Now I’ve noticed that my TQS Microstick isn’t working at all in BMS 4.33.3 (and 4.33.4) until I manually re-calibrate my Cougar and TQS using the HOTAS Cougar Control Panel.
I have to do this every time I boot my PC. And after that, it’s all fine but having to do this every time is extremely annoying.
(though not as annoying as forgetting it and finding myself over the FLOT in an MP flight without any means to control my FCR or TGP.)Any idea what the issue is? I’m sure the Cougar and TQS are fine as I never had this problem until I swapped out the motherboard?
The Cougar is on firmware 3.06. Is there a certain setting I should set?
-
does it drift or does it not work at all?
-
Do you actually have to calibrate or just click the (can’t remember what it’s called) apply/upload/activate button?
-
@Red:
does it drift or does it not work at all?
It doesn’t do anything until I re-calibrate it, like it’s not there/disconnected. But after that, it works beautifully - there is no drift at all.
Do you actually have to calibrate or just click the (can’t remember what it’s called) apply/upload/activate button?
Well I thought I had to calibrate it but after your post I also tried just clicking any of the buttons on the HOTAS Cougar Control Panel in the Startup & Calibration tab and that seems to work too?
I don’t think BMS is the problem at all, but somehow I have to “wake up” the microstick or something? Does that make any sense at all?
-
Just new to BMS from AF but I do believe you have to change your MFD to sensor of interest (DMS down I think) then enable the cursor by pressing the cursor control.
In Cougar calibration you do have to click a button each time you move the pots. I have found that the easiest way for me to calibrate the microstick is to move it in the direction directed and then move it around until you see a center reading in the values shown. In other words if it goes up to 245 and then back down again, center the position on the highest value (245) and click a button but note that someof the axis use the lower center value so click when you see the lowest value. That has worked well for me. Also a bit of dead zone can help prevent a drifting radar cursor.
Also I use USB CH pedals so my microstick uses TM right and left toe brakes in the BMS setup … and since radar range knob doesn’t work in BMS I use that to control my HUD brightness.
Hope that helps.
-
… and since radar range knob doesn’t work in BMS I use that to control my HUD brightness.
Um, you might want to rethink that. The range knob controls the gain on the AG FCR and more importantly, controls the zoom function of the cameras in the TGP. Pretty valuable IMO.
-
say can disconnecting the microstick without disconnecting the cougar from the PC (connection at the miniboard) burn the microstick or the miniboard?
-
solved
-
It doesn’t do anything until I re-calibrate it, like it’s not there/disconnected. But after that, it works beautifully - there is no drift at all.
Well I thought I had to calibrate it but after your post I also tried just clicking any of the buttons on the HOTAS Cougar Control Panel in the Startup & Calibration tab and that seems to work too?
I don’t think BMS is the problem at all, but somehow I have to “wake up” the microstick or something? Does that make any sense at all?
When I was still using my Cougar i had to to the “retrieve / apply” dance after every reboot as well, I even wrote an autohotkey scripts for it to automate the process
What I had to do was fire up the CCP, then click “retrieve values from device”, wait a second, then click “apply” and the microstick would wake up after that.
It’s been a while so I may have gotten the names wrong here, but it was only those two operations that usually fixed the problem for me (also win7 64bit)
cheers, Uwe
