Jump to content
The simFlight Network Forums

Only one of Saitek throttle quadrant and trim wheel recognized at the same time in FSUIPC


Recommended Posts

First only the trim wheel (Saitek Cesna pro) was seen by FSUIPC  5.14 and not the throttle quadrant (none of the three axis, and none of the buttons of the quadrant neither). I changed the USB connections to the PC, and now only the throttle quadrant is recognized (all three axis and the buttons), the trim wheel not anymore...

All other axis (thrustmaster warthog throttle + joystick) are properly scanned and successfully assigned

Basically I see the same as described in this post only-1-of-2-throttle-quads-recognized (except I have 1 trim wheel + 1 throttle quadrant instead of 2 throttle quadrants)

Both trim and throttle modules are seen by P3DV4 in  the control options and are properly functioning when assigned.

So at the moment I have the throttle assigned in FSUIPC and the trim in the control options of P3DV4, but that's not very satisfactory since the trim wheel settings will be the same for all airplanes.

Thanks for help.

Vvince

 

 

 

Edited by vvince
free space for upload
Link to comment
Share on other sites

55 minutes ago, vvince said:

First only the trim wheel (Saitek Cesna pro) was seen by FSUIPC  5.14 and not the throttle quadrant (none of the three axis, and none of the buttons of the quadrant neither). I changed the USB connections to the PC, and now only the throttle quadrant is recognized (all three axis and the buttons), the trim wheel not anymore...

You supplied useful files, but not the FSUIPC5.INI file, in which you define the ID numbers. The problem, as shown in the Log is that the same ID is being used by both devices:

      265 Device acquired for use:
      265    Joystick ID = 3 (Registry fixed)
      265    3=Saitek Pro Flight Cessna Trim Wheel
      265    3.GUID={ED1EE8B0-A133-11E8-8001-444553540000}
      265 Device acquired for use:
      265    Joystick ID = 3 (Registry okay)
      265    3=F16 MFD 2
      265    3.GUID={B6D35820-5B64-11E6-800A-444553540000}

Best show the INI file next time. Meanwhile try changing it to define a free ID for one or the other, such as 5.  Naybe use 5 for the trim wheel as you aren't assigning to that at present. Be sure to changet both the 3= and 3.GUID= lines.

I hope you are using Joy Letters so that assignments you make are retained should the IDs change.

Pete

 

Link to comment
Share on other sites

Thanks a lot Pete,

the problem is solved. I edited the .ini file, and manually assigned Joy names (so I left AutoAssignLetters=No).

But two things are still bothering me : before doing manual naming, I tried  AutoAssignLetters=Yes (which did not work : the wheel was still unseen). And now I have some A, B, C, E names with << MISSING JOYSTICK >> entries, not assigned anymore. If I delete these entries they keep coming back and I could not find out what should be edited where to free these names again.

A second thing : in the operation of renaming the controllers, all the axis and key binding have been lost, although they are still present in the .ini file. Is there a way to edit the .ini file such that the renamed controller get their assignment back in FSUIPC (without re assigning everyuthing manually of course).

Thanks again, cheers

 

Vvince

 

PS : by the way, the upload limit is a bit low : 20kB... I had to delete the former uploads to be able to upload the 16kB FSUIPC.ini

 

 

 

 

 

FSUIPC5.ini

Link to comment
Share on other sites

9 hours ago, vvince said:

But two things are still bothering me : before doing manual naming, I tried  AutoAssignLetters=Yes (which did not work : the wheel was still unseen).

It's the assignment of the ID numbers which should make it "seen" (i.e. not clash). AutoAssign merely assigns A, B, C, D ... etc to whatever devices are uniquely seen. Otherwise it is the same as manualy choosing letters. (The latter is obviously better in the sense that you can then assign meaningful letters, like J, T, W, R. but it is an easy option to let FSUIPC do it for users not so good at editing files).

10 hours ago, vvince said:

And now I have some A, B, C, E names with << MISSING JOYSTICK >> entries, not assigned anymore. If I delete these entries they keep coming back and I could not find out what should be edited where to free these names again.

There must be assignments to those. Deleting the entries in [JoyName] cannot change those. You'd need to delete the assignment lines to those letters in the Axis and Button sections, or, better, cange the letters to the ones you want assigned.

Once you've started using letters, whilst they will be automatically used to change the previous numeric ID assignments in those sections, undoing them is not automatic. It cannot be, because as "missing joysticks" FSUIPC doesn't know which other letter to use. I suppose it could just delete all such lines, but then folks wouldn't have the better option and changing the letters (see your point 2, which is exactly this).

10 hours ago, vvince said:

A second thing : in the operation of renaming the controllers, all the axis and key binding have been lost, although they are still present in the .ini file. Is there a way to edit the .ini file such that the renamed controller get their assignment back in FSUIPC (without re assigning everything manually of course).

This is the problem I've just explained above. you would either need to change them to the correct letter, or easier, change the letters to the A, B, C etc, as appropriate, in the Joynames section. Which you choose to do would depend on how much work changing the assignments represents.

10 hours ago, vvince said:

PS : by the way, the upload limit is a bit low : 20kB... I had to delete the former uploads to be able to upload the 16kB FSUIPC.ini

Best always to ZIP files as, being pure text, the Zip up pretty small.
However, it makes it easier for both of us, with text files, simply to click on the <> button just above,
and paste the whole text into the box presented. This produces a result like this (for this paragraph in this case):

Best always to ZIP files as, being pure text, the Zip up pretty small.
However, it makes it easier for both of us, with text files, simply to click on the <> button just above,
and paste the whole text into the box presented. This produces a result like this (for this paragraph in this case):

Scroll bars are provided for overwide text and long texts.

Pete

 

Link to comment
Share on other sites

Hi Pete,

Thanks, but I still do not get it :

49 minutes ago, Pete Dowson said:

There must be assignments to those. Deleting the entries in [JoyName] cannot change those. You'd need to delete the assignment lines to those letters in the Axis and Button sections, or, better, cange the letters to the ones you want assigned.

I do not see any assignment lines referring to A, B, C or E in the [Axes] or [Buttons ] sections, so I do not know what to delete.


[JoyNames]
AutoAssignLetters=No

Q=Saitek Pro Flight Quadrant
Q.GUID={ED58DE70-A175-11E8-8001-444553540000}
J=Joystick - HOTAS Warthog
J.GUID={B6D1D180-5B64-11E6-8008-444553540000}
R=Flight Control Rudder
R.GUID={8D1028B0-1FA9-11E7-8001-444553540000}
N=F16 MFD 2
N.GUID={B6D35820-5B64-11E6-800A-444553540000}
T=Throttle - HOTAS Warthog
T.GUID={B6D1D180-5B64-11E6-8007-444553540000}
M=F16 MFD 1
M.GUID={B6D35820-5B64-11E6-800B-444553540000}
W=Saitek Pro Flight Cessna Trim Wheel
W.GUID={ED1EE8B0-A133-11E8-8001-444553540000}
0=Saitek Pro Flight Quadrant
0.GUID={ED58DE70-A175-11E8-8001-444553540000}
1=Joystick - HOTAS Warthog
1.GUID={B6D1D180-5B64-11E6-8008-444553540000}
2=Flight Control Rudder
2.GUID={8D1028B0-1FA9-11E7-8001-444553540000}
5=Saitek Pro Flight Cessna Trim Wheel
5.GUID={ED1EE8B0-A133-11E8-8001-444553540000}
4=Throttle - HOTAS Warthog
4.GUID={B6D1D180-5B64-11E6-8007-444553540000}
3=F16 MFD 2
3.GUID={B6D35820-5B64-11E6-800A-444553540000}
6=F16 MFD 1
6.GUID={B6D35820-5B64-11E6-800B-444553540000}
B=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
C=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
E=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>
A=<< MISSING JOYSTICK >>


[Axes]
PollInterval=10
RangeRepeatRate=10
0=BX,256,D,1,0,0,0	-{ DIRECT: Aileron }-
1=BY,256,D,2,0,0,0	-{ DIRECT: Elevator }-
2=CX,256,D,7,0,0,0	-{ DIRECT: LeftBrake }-
3=CY,256,D,8,0,0,0	-{ DIRECT: RightBrake }-
4=CR,256,D,3,0,0,0	-{ DIRECT: Rudder }-
5=EY,256,F,66994,0,0,0	-{ TO SIM: AXIS_ZOOM }-
6=EZ,256,D,10,0,0,0	-{ DIRECT: Throttle2 }-
7=ER,256,D,9,0,0,0	-{ DIRECT: Throttle1 }-
8=ES,256,D,21,0,0,0	-{ DIRECT: ElevatorTrim }-

[Buttons]
PollInterval=25
ButtonRepeat=20,10
1=RB,32,C65607,0 	-{ELEV_TRIM_DN}-
2=RB,36,C65615,0 	-{ELEV_TRIM_UP}-
3=RB,34,C66277,0 	-{AILERON_TRIM_RIGHT}-
4=RB,38,C66276,0 	-{AILERON_TRIM_LEFT}-
5=PE,22,C65758,0 	-{FLAPS_INCR}-
6=PE,21,C65759,0 	-{FLAPS_DECR}-
7=PE,20,C65570,0 	-{GEAR_TOGGLE}-
8=PE,7,C66064,0 	-{SPOILERS_ON}-
9=PE,6,C66065,0 	-{SPOILERS_OFF}-
10=PB,2,C3,0 	-{Custom control: <3>}-
11=PB,4,C66541,0 	-{TOGGLE_TAILWHEEL_LOCK}-
12=RE,32,C65734,0 	-{PAN_UP}-
13=RE,36,C65735,0 	-{PAN_DOWN}-
14=RE,34,C65672,0 	-{PAN_RIGHT}-
15=RE,38,C65671,0 	-{PAN_LEFT}-
16=PE,10,C65759,0 	-{FLAPS_DECR}-
17=PE,25,C66391,0 	-{TOGGLE_TAIL_HOOK_HANDLE}-
18=PE,11,C65758,0 	-{FLAPS_INCR}-
19=PT,11,C65758,0 	-{FLAPS_INCR}-
20=PT,10,C65759,0 	-{FLAPS_DECR}-

 

Also similarly, for my second point, I do not see neither reference to a Joystick name in the airplane profiles. Here is an example with the VRS FA18 (the one with the most buttons assigned...)

The buttons first:


[Profile.VRS_FA!8]
1=VFA-143 "Pukin' Dogs" Line

[Buttons.VRS_FA!8]
0=P6,15,K49,8 	-{Key press: 1}-
1=P6,16,K50,8 	-{Key press: 2}-
2=P6,17,K51,8 	-{Key press: 3}-
3=P6,18,K52,8 	-{Key press: 4}-
4=P6,0,K54,8 	-{Key press: 6}-
5=P6,1,K55,8 	-{Key press: 7}-
6=P6,2,K56,8 	-{Key press: 8}-
7=P6,3,K56,8 	-{Key press: 8}-
8=P6,4,K48,8 	-{Key press: 0}-
9=P6,5,K49,10 	-{Key press: ctl+1}-
10=P6,6,K50,10 	-{Key press: ctl+2}-
11=P6,7,K51,10 	-{Key press: ctl+3}-
12=P6,8,K52,10 	-{Key press: ctl+4}-
13=P6,9,K53,10 	-{Key press: ctl+5}-
14=P6,10,K54,10 	-{Key press: ctl+6}-
15=P6,11,K55,10 	-{Key press: ctl+7}-
16=P6,12,K56,10 	-{Key press: ctl+8}-
17=P6,13,K57,10 	-{Key press: ctl+9}-
18=P6,14,K48,10 	-{Key press: ctl+0}-
19=P1,10,K38,10 	-{Key press: ctl+Up}-
20=P1,12,K40,10 	-{Key press: ctl+Down}-
21=P1,13,K37,10 	-{Key press: ctl+Left}-
22=P1,11,K39,10 	-{Key press: ctl+Right}-
23=P1,16,K49,11 	-{Key press: ctl+shft+1}-
24=P1,17,K50,11 	-{Key press: ctl+shft+2}-
25=P1,14,K51,11 	-{Key press: ctl+shft+3}-
26=P1,15,K52,11 	-{Key press: ctl+shft+4}-
28=P1,2,K46,9 	-{Key press: shft+Del}-
30=P1,3,K46,8 	-{Key press: Del}-
31=P1,6,K13,8 	-{Key press: Rtn}-
32=P1,8,K46,9 	-{Key press: shft+Del}-
35=P1,4,K90,11 	-{Key press: ctl+shft+Z}-
36=R4,32,K38,9 	-{Key press: shft+Up}-
37=R4,36,K40,9 	-{Key press: shft+Down}-
38=R4,34,K39,9 	-{Key press: shft+Right}-
39=R4,38,K37,9 	-{Key press: shft+Left}-
40=P4,0,K13,8 	-{Key press: Rtn}-
41=R4,3,K67,8 	-{Key press: C}-
42=R4,5,K70,8 	-{Key press: F}-
45=P4,14,K85,10 	-{Key press: ctl+U}-
46=P4,10,K82,10 	-{Key press: ctl+R}-
47=P6,19,K53,8 	-{Key press: 5}-
48=P3,15,K49,8 	-{Key press: 1}-
49=P3,16,K50,8 	-{Key press: 2}-
50=P3,17,K51,8 	-{Key press: 3}-
51=P3,18,K52,8 	-{Key press: 4}-
52=P3,19,K53,8 	-{Key press: 5}-
53=P3,0,K54,8 	-{Key press: 6}-
54=P3,1,K55,8 	-{Key press: 7}-
55=P3,2,K56,8 	-{Key press: 8}-
56=P3,3,K57,8 	-{Key press: 9}-
57=P3,4,K48,8 	-{Key press: 0}-
58=P3,5,K49,10 	-{Key press: ctl+1}-
59=P3,6,K50,10 	-{Key press: ctl+2}-
60=P3,7,K51,10 	-{Key press: ctl+3}-
61=P3,8,K52,10 	-{Key press: ctl+4}-
62=P3,9,K53,10 	-{Key press: ctl+5}-
63=P3,10,K54,10 	-{Key press: ctl+6}-
64=P3,11,K55,10 	-{Key press: ctl+7}-
65=P3,12,K56,10 	-{Key press: ctl+8}-
66=P3,13,K57,10 	-{Key press: ctl+9}-
67=P3,14,K48,10 	-{Key press: ctl+0}-
68=P4,1,K69,8 	-{Key press: E}-

and the axis


[Axes.VRS_FA!8]
RangeRepeatRate=10
0=1X,256,D,1,0,0,0	-{ DIRECT: Aileron }-
1=1Y,256,D,2,0,0,0	-{ DIRECT: Elevator }-
2=2X,256,D,7,0,0,0	-{ DIRECT: LeftBrake }-
3=2Y,256,D,8,0,0,0	-{ DIRECT: RightBrake }-
4=2R,256,D,3,0,0,0	-{ DIRECT: Rudder }-
5=4X,256
6=4X,BR,-16384,-6586,1071,39	-{ Entering=key press/hold: Right }-
7=4X,BR,6336,16383,1071,37	-{ Entering=key press/hold: Left }-
8=4Y,256
9=4Y,BR,-16384,-6265,1070,40	-{ Entering=key press & release: Down }-
10=4Y,BR,6368,16383,1070,38	-{ Entering=key press & release: Up }-
11=4Z,256,D,10,0,0,0	-{ DIRECT: Throttle2 }-
12=4R,256,D,9,0,0,0	-{ DIRECT: Throttle1 }-
13=4S,256
14=4S,BR,5952,16383,1071,65574	-{ Entering=key press/hold: Up }-
15=4S,BR,-16384,-6971,1070,65576	-{ Entering=key press & release: Down }-

 

What should I edit in order to have these bindings assigned to the device T and J (throttle and joystick Thrustmaster).

Obviously there are some things I am missing.

 

Thanks,

Vvince

Link to comment
Share on other sites

2 hours ago, vvince said:

I do not see any assignment lines referring to A, B, C or E in the [Axes] or [Buttons ] sections, so I do not know what to delete.

You have B, C and E referenced in the [Axes] section:

0=BX,256,D,1,0,0,0	-{ DIRECT: Aileron }-
1=BY,256,D,2,0,0,0	-{ DIRECT: Elevator }-
2=CX,256,D,7,0,0,0	-{ DIRECT: LeftBrake }-
3=CY,256,D,8,0,0,0	-{ DIRECT: RightBrake }-
4=CR,256,D,3,0,0,0	-{ DIRECT: Rudder }-
5=EY,256,F,66994,0,0,0	-{ TO SIM: AXIS_ZOOM }-
6=EZ,256,D,10,0,0,0	-{ DIRECT: Throttle2 }-
7=ER,256,D,9,0,0,0	-{ DIRECT: Throttle1 }-
8=ES,256,D,21,0,0,0	-{ DIRECT: ElevatorTrim }-

Similarly the [Buttons] section has references to B and E (plus two good ones to T).

 

2 hours ago, vvince said:

Also similarly, for my second point, I do not see neither reference to a Joystick name in the airplane profiles. Here is an example with the VRS FA18 (the one with the most buttons assigned...)

The sections for Profiles are not revised UNTIL they are actually read, which will be when you load an aircraft with that profile.

Pete

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.