TQS Cursor double pot drifting: known fixes for this?
-
Sorry, yes. Separately on each axis move the axis to each of its limits and note the red numbers at each max and min position, these should be input in the max and min fields in the calibration applet, then average between the red numbers to get the centre, again input this in the centre field of the calibration applet.
Thanks. Did you do this for the Z Axis as well or just the microstick?
-
Thanks. Did you do this for the Z Axis as well or just the microstick?
Only the microstick, my Z axis reports 98.5% and 0.05% or 64574 and 32 so, no need and Z rotation is on a HAL sensor so, again, no need.
-
Only the microstick, my Z axis reports 98.5% and 0.05% or 64574 and 32 so, no need and Z rotation is on a HAL sensor so, again, no need.
Thanks
-
I’m still experience stick drift. For me I am using a leobonard board and a delta sim microstick. Any thoughts?
-
I’m still experience stick drift. For me I am using a leobonard board and a delta sim microstick. Any thoughts?
Have you tried adjusting\increasing your dead zones etc in game, under controllers > advanced > avionics.
Not being familiar with LeoBodnar boards and not knowing what, if any control software it might have, I can’t suggest anything further other than increasing the dead zones in game, there maybe some adjustments under windows game controllers applet, but again, I’m not familiar with it as my TUSBA etc is supplied with it’s own dedicated HID software that allows calibration and dead zone adjustment, my TQS has the original microstick, the only internal change I made was the throttle pot, upgraded to a HAL sensor, the TUSBA converts the TQS into a standalone USB device providing 12 bit resolution for much better accuracy. This is why the red raw values in DiViewer are used for calibration as the black values represent a windows standard which I believe are problematic for calibrating through the original gameport connector or it’s a precedence issue that windows generally wins, my memory is hazy on this but the solution for me and many others was TUSBA.
In the event you might be interested, here’s the link to Realsimulators TUSBA https://realsimulator.com/tusba/ I can’t recommend their products highly enough for getting a second life and better overall control of your original Cougar setup.
Sorry I can’t be of much more help but please, keep us updated and let us know if changing your deadzones helped, there may well be people in the future looking for a solution.
-
Have you tried adjusting\increasing your dead zones etc in game, under controllers > advanced > avionics.
Not being familiar with LeoBodnar boards and not knowing what, if any control software it might have, I can’t suggest anything further other than increasing the dead zones in game, there maybe some adjustments under windows game controllers applet, but again, I’m not familiar with it as my TUSBA etc is supplied with it’s own dedicated HID software that allows calibration and dead zone adjustment, my TQS has the original microstick, the only internal change I made was the throttle pot, upgraded to a HAL sensor, the TUSBA converts the TQS into a standalone USB device providing 12 bit resolution for much better accuracy. This is why the red raw values in DiViewer are used for calibration as the black values represent a windows standard which I believe are problematic for calibrating through the original gameport connector or it’s a precedence issue that windows generally wins, my memory is hazy on this but the solution for me and many others was TUSBA.
In the event you might be interested, here’s the link to Realsimulators TUSBA https://realsimulator.com/tusba/ I can’t recommend their products highly enough for getting a second life and better overall control of your original Cougar setup.
Sorry I can’t be of much more help but please, keep us updated and let us know if changing your deadzones helped, there may well be people in the future looking for a solution.
I will but trying to figure it out.
-
I will but trying to figure it out.
Maybe this will help?
Also, DiView is the calibration software that LeoBodnar boards provide as per this link http://www.leobodnar.com/shop/index.php?main_page=page&id=12 so, you’ve got everything you need.
-
I converted a Cougar TQS with a Bodnar (this one - http://www.leobodnar.com/shop/index.php?main_page=product_info&cPath=94&products_id=204) and found out in doing so that the TQS micro-stick is not a joystick. It is a quadrature device similar to a mouse - hence “mouse stick”.
What this means electrically is that it outputs signal based on it’s position within an angularly related quadrant - it’s a Lissajous, and not X-Y like a joystick. This makes interfacing it via a Bodnar joystick input difficult…but not impossible. It’s not that difficult on a Mac, but only because of a really slick utility called ControllerMate. What I ended up having to do was to interpret what quadrant the Cursor Controller is in, map that output to keyboard Arrow keys, and set BMS to use Arrow keys for Cursor Control.
Having done this, I now have a dead solid Cursor Control with ZERO drift on this particular TQS, which I use with my Mac version of FAF, about exclusively. In fact, if you want to kill Cursor drift problems on the Cougar TQS this is THE way to do it, and you should be able to also do it using Foxy or TARGET for a complete Cougar, but I haven’t tried that - you can’t do this with Foxy or TARGET for just the TQS alone because all of the Cougar “smarts” are in the stick base.
-
My X axis on the micro stick drifts slightly and setting the dead zone to high stops it from drifting
-
I was thinking about this some more. I have the wiring diagram for the TQS can anyone provide the labeling for the micro-cursor? I guessed at part of it so I am wonder if that is the issue?