Dual Saitek TQs unable to assign functions to 2nd unit

[Roger C]

I have installed a Saitek Yoke and 2 Saitek TQ units.  I disabled controllers in FSX and began assigning axes in FSUIPC.  Assignment for Yoke axes was no problem.  I assigned axes as well on the TQ-1 for Speedbrake  and Throttle 1 (not using the middle lever on that unit).  I want to assign functions for Throttle 2, Landing Gear and Flaps to the three levers on TQ-2 however FSUIPC does not recognize the movement of any of those levers as axes or as buttons.

Saitek states that the TQ-2 is recognized by FSX as buttons not axes and setting them up through FSX as such does yield success.  I am unable to repeat that effort when I try instead to assign their functions in FSUIPC.

[Thomas Richter]

Hi,

best is to supply some info of what is used, FSUIPC4.log file and FSUIPC4.ini file and FSUIPC4.JoyScan.csv file.

Make sure you use in FSUIPC4.ini file

[JoyNames]
AutoAssignLetters=Yes

Thomas

[Roger C]

Attached are the files as requested.

 

Thank you for any assistance.

FSUIPC4.ini

FSUIPC4.JoyScan.csv

FSUIPC4.log

[Thomas Richter]

Hi,

first you need to update to latest version, 4.969 is far out of date and unsupported.

Install_FSUIPC4971.zip

Thomas

[Roger C]

OK...I have installed the 49771 update.  Once again, the first TQ is recognized and I can program the axes and buttons, however, the 2nd TQ is not recognized by FSUIPC (I cannot program axes or buttons for it).

Attached are the relevant files.

 

Thanks

FSUIPC4.ini

FSUIPC4.JoyScan.csv

FSUIPC4.log

[Pete Dowson]

4 hours ago, Roger C said:

OK...I have installed the 49771 update.  Once again, the first TQ is recognized and I can program the axes and buttons, however, the 2nd TQ is not recognized by FSUIPC (I cannot program axes or buttons for it).

The problem is that your T-Rudder clashes:

      922 Device acquired for use:
      922    Joystick ID = 1 (Registry okay)
      922    1=Flight Throttle Quadrant
      922    1.GUID={38F6A6D0-BB3C-11E7-800A-444553540000}
      922 Device acquired for use:
      922    Joystick ID = 1 (Registry fixed)
      922    1=T-Rudder
      922    1.GUID={FE144CF0-B4D0-11E7-8001-444553540000}

You defined the T-Rudder as Joystick 1 whilst that was actually assigned, in the Registry, to the Quadrant.

Your INI file contains several other oddities, as if it's an old one which has gone through a lot of problems and weird changes.  You haven't got much assigned or calibrated yet, so you might be much better off just deleting it and starting again. but if you want to persist then some further changes will be needed.

In this section for instance:

[JoyNames]
AutoAssignLetters=Yes

1=T-Rudder
1.GUID={FE144CF0-B4D0-11E7-8001-444553540000}
0=Flight Yoke System
0.GUID={38F6A6D0-BB3C-11E7-8008-444553540000}
A=Flight Yoke System
A.GUID={38F6A6D0-BB3C-11E7-8008-444553540000}
B=T-Rudder
B.GUID={FE144CF0-B4D0-11E7-8001-444553540000}
C=USB Multimedia Keyboard
C.GUID={2FFA85B0-0242-11E1-8001-444553540000}

I'm not sure where you got the USB keyboard listed from -- maybe an old INI file? it isn't recognised as a Joystick type device in the CSV file or the LOG.  Delete both C= lines.

Then add lines for your other quadrant:

1=Flight Throttle Quadrant
1.GUID={38F6A6D0-BB3C-11E7-800A-444553540000}
C=Flight Throttle Quadrant
C.GUID={38F6A6D0-BB3C-11E7-800A-444553540000}

You also need to delete these lines which refer to a rudder which isn't connected

9=2X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
10=2Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
11=2Z,256,D,3,0,0,0    -{ DIRECT: Rudder }-

You have some very strange assignmentrs to the T-Rudder:

4=BX,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
5=BY,256,F,66387,0,0,0    -{ TO SIM: AXIS_LEFT_BRAKE_SET }-
6=BZ,256,D,3,0,0,0    -{ DIRECT: Rudder }-
7=BR,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
8=BU,256,D,23,0,0,0    -{ DIRECT: Flaps }-

Two different ways for Left and Right brakes? Strange? And 2nd Throttle and Flaps assigned to the rudder? Surely not? Maybe that dates to some time when B was a quadrant? Best delete those two and re-assign.

Pete

 

Pete

 

[Roger C]

Pete:

 

First of all, thank you for taking the time to review and support my problem (and everyone else's for that matter).  If there was a Nobel Prize for Flight Sim support you would surely be so awarded.

I went ahead and deleted the INI file and reassigned all the axes and buttons.  Indeed, the second TQ is now recognized and functional.

 

I do have two additional questions:

1-The flaps are set up as an axis, however, they are operating in reverse of how I would like the lever action to operate.  I cannot locate a way to reverse the function on the assignment or calibration pages

 

2-The Saitek Yoke provides for three modes of button assignments (the yoke buttons can be assigned to 3 functions each) but FSUIPC shows the same function that I programmed for buttons in Mode 1 even when switched to Mode 2 or 3.  Is there a way to enable this multi-function capability?

[Pete Dowson]

1 hour ago, Roger C said:

1-The flaps are set up as an axis, however, they are operating in reverse of how I would like the lever action to operate.  I cannot locate a way to reverse the function on the assignment or calibration pages

There's a REV checkbox in the calibration. You need to check that before ANY attempt to calibrate.

1 hour ago, Roger C said:

2-The Saitek Yoke provides for three modes of button assignments (the yoke buttons can be assigned to 3 functions each) but FSUIPC shows the same function that I programmed for buttons in Mode 1 even when switched to Mode 2 or 3.  Is there a way to enable this multi-function capability?

I don't think the Mode switch is seen by FSUIPC. I think it is used by Saitek's own software. You may be able to use it with a Lua plug-in program, but it isn't easy.

Pete

 

[Donovan]

Hi Roger,

I don't use any Saitek drivers, but solely use FSUIPC4.  The Yoke MODE switch, in the following example is B22 (left position="Mode 1"), B23 (center position="Mode 2"), and B24 (right position="Mode 3").  Using The conditional button checking features, I have three modes enabled.  This is just a snippet example from the .ini file.  You have to manually edit the .ini file to set up the  conditional programming.  See FSUIPC4 for Advanced Users section "Compound Button Conditions," page 24 and Appendix 1 - "Doing more with your joystick," starting page 50 for the documentation.

14=CP(+B,22)B,6,K73,9 ;GNS 530W ZOOMOUT, MODE1  -{Key press: shft+I}-
15=CP(+B,22)B,7,K68,9 ;GNS 530W ZOOMIN, MODE1  -{Key press: shft+D}-
16=CR(+B,23)B,6,C66276,0 ;LEFT_ALIERON_TRIM, MODE2  -{AILERON_TRIM_LEFT}-
17=CR(+B,23)B,7,C66277,0 ;RIGHT_ALIERON_TRIM, MODE2  -{AILERON_TRIM_RIGHT}-
18=CR(+B,24)B,6,C66278,0 ;LEFT_RUDDER_TRIM, MODE3  -{RUDDER_TRIM_LEFT}-
19=CR(+B,24)B,7,C66279,0 ;RIGHT_RUDDER_TRIM, MODE3  -{RUDDER_TRIM_RIGHT}-

As I don't use any of the Saitek Drivers, I cannot comment on whether or not that affects FSUIPC "seeing" the button position.

Best,

Don

 

[Pete Dowson]

16 hours ago, Donovan said:

The Yoke MODE switch, in the following example is B22 (left position="Mode 1"), B23 (center position="Mode 2"), and B24 (right position="Mode 3").

Ah, so the Mode switch IS set to send button presses.  I didn't realise that. Good to know - thanks!

Pete