Jump to content
The simFlight Network Forums

Can I use this with the mode switch on my X56?


Recommended Posts

Posted (edited)

Curious, and my reading here didn't see any potential answers. 

I have a Saitek X56, and the Throttle has a mode switch. Does FSUIPC recognize this so I can use the mode switch to program a button with different commands? A quick test seems to show I can't. 

Edited by bahnzo
Posted

I'm not sure about the Saitek X56, but its possible with the mode switch on the saitek yoke.
When you change the mode switch, does FSUIPC see this in the buttons and switches assignment dialog? If so, it should be straightforward to use in FSUIPC.

If not, some folks had to remove/rename a file called SaiD0BAC.PRO (in C:\Windows\System32) to get the mode switch of the yoke recognised. Maybe there is something similar for the X56?

Also, note that FSUIPC only sees the first 32 buttons (0-31), so if the button number of the mode switch is higher than that it won't be recognisd in the assignments panel and you would have to resort to lua to program the button. You can check in the windows game controllers utility to see if your mode switch is recognised there (and what number it has).

Finally, make sure that you have not installed the saitek software or drivers and just use the standard windows drivers.

Posted
15 hours ago, John Dowson said:

I'm not sure about the Saitek X56, but its possible with the mode switch on the saitek yoke.
When you change the mode switch, does FSUIPC see this in the buttons and switches assignment dialog? If so, it should be straightforward to use in FSUIPC.

If not, some folks had to remove/rename a file called SaiD0BAC.PRO (in C:\Windows\System32) to get the mode switch of the yoke recognised. Maybe there is something similar for the X56?

Also, note that FSUIPC only sees the first 32 buttons (0-31), so if the button number of the mode switch is higher than that it won't be recognisd in the assignments panel and you would have to resort to lua to program the button. You can check in the windows game controllers utility to see if your mode switch is recognised there (and what number it has).

Finally, make sure that you have not installed the saitek software or drivers and just use the standard windows drivers.

Hi John, thanks for taking the time. FSIUP does not seem to see the mode switch in the buttons and switches assignments. Changing it between modes doesn't show anything in the "Joy#" boxes at the top. I can assign things to a button, but those assignments stick across all modes. 

I don't have that exact file, but I do have one similar, so I'm guessing it's what you mean. It's called: SaiD053C.pro. It appears to be some sort of base level default profile. 

The button limit might an issue. The default windows game controllers utility doesn't list numbers for the throttle buttons, but there are two 8-way hats on the throttle, so if those are being counted as buttons for each direction, then it's certainly over the limit. If not, then probably not. 

Of course I have the saitek drivers and software installed 🙂 And it works well, but the reason I'd really like to use FSUIPC is I noticed it sends the commands directly to the sim, where when I program the throttle with the software it only sends the keystrokes to the active window. Which isn't always MSFS as I'm sure you understand I have other windows on my other monitor open during flight. So I'm constantly having to click back into the MSFS window to get the buttons to work in the sim. 

I included the log, if you have the time I had a question that might help here. I noticed my throttle is listed as having 0 buttons. And then below I noticed it says "265    WARNING: Joystick ID 1 is duplicated in Registry" which is my throttle. Is this causing a problem somehow?

Do you have any suggestions? Should I try removing the .pro file to start? I'm a little reluctant to remove all my software and drivers as they at least work, if not as well as I'd like. 

FSUIPC7.log

Posted
8 hours ago, bahnzo said:

I noticed my throttle is listed as having 0 buttons. And then below I noticed it says "265    WARNING: Joystick ID 1 is duplicated in Registry" which is my throttle. Is this causing a problem somehow?

No, its only a warning and nothing to worry about.

8 hours ago, bahnzo said:

The button limit might an issue. The default windows game controllers utility doesn't list numbers for the throttle buttons, but there are two 8-way hats on the throttle, so if those are being counted as buttons for each direction, then it's certainly over the limit. If not, then probably not. 

32 (buttons 0-31) is the standard button limit, but POV buttons (usually) have the 8 button ids from 32-39 which you can assign as either an axis (e.g usually PAN_VIEW, butthis is not working in MSFS) or as buttons.

8 hours ago, bahnzo said:

Do you have any suggestions? Should I try removing the .pro file to start? I'm a little reluctant to remove all my software and drivers as they at least work, if not as well as I'd like.

I would certainly try without the saitek software installed first. You can always re-install it later if needed. I would then try without the drivers, and use the default windows drivers (again, you can always re-install later if needed). Finally you could try without that file - i.e. temporarily rename it. You can revert back to the original name if it doesn't help or causes issues.

  • 3 years later...
Posted (edited)

Hi everyone!

@John Dowson I'm trying to configure my Logitech X56 and include the mode selector to adjust (Altitude, HDG and Speed) on the PMDG MSFS B737.

I'm reading the documentation, but as I'm not a programmer I'm very confused.

With this line of code in FSUIPC7.ini I can adjust the Heading bug:

59=PE,29,CPPMDG_B737_MCP_HDG_INC,0 -{Preset Control}-
60=PE,30,CPPMDG_B737_MCP_HDG_DEC,0 -{Preset Control}-

However, I would like to create conditions to use the M1, M2 and M3 mode selector on my Logitech X56.

From what I understand in the documentation, I should do this:

59=CP(+E,134),PE,29,CPPMDG_B737_MCP_HDG_INC,0
60=CP(+E,134),PE,30,CPPMDG_B737_MCP_HDG_DEC,0

But I've tried it that way and it doesn't work!

My idea is to change the altitude by leaving it in M1 mode. in M2 the Heading Bug and M3 the speed.

I made a drawing (work of art) to make it easier to understand. I want usage rights to the image! 🙂

Can someone help me?

 

x56-Joy-config.jpg

Edited by Flávio Oliveira
Posted
On 5/11/2024 at 6:23 PM, Flávio Oliveira said:

From what I understand in the documentation, I should do this:

59=CP(+E,134),PE,29,CPPMDG_B737_MCP_HDG_INC,0
60=CP(+E,134),PE,30,CPPMDG_B737_MCP_HDG_DEC,0

Read the documentation again...should be:

59=CP(+E,134)E,29,CPPMDG_B737_MCP_HDG_INC,0
60=CP(+E,134)E,30,CPPMDG_B737_MCP_HDG_DEC,0

i.e. no ,P after the offset condition.

  • 2 weeks later...
Posted
3 minutes ago, Flávio Oliveira said:

I did as you told me and it didn't work, I'll share my FSUIPC.ini file with you so you can tell me where I'm going wrong.

But now you have assigned to a missing joystick:

Quote

A=X56 H.O.T.A.S. Throttle
B=X56 H.O.T.A.S. Stick
C=Saitek Pro Flight Rudder Pedals
E=<< MISSING JOYSTICK >> << MISSING JOYSTICK >>

...

[Buttons.B737 PMDG]
2=CP(+E,134)E,29,CPPMDG_B737_MCP_HDG_INC,0     -{Preset Control}-
3=CP(+E,134)E,30,CPPMDG_B737_MCP_HDG_DEC,0     -{Preset Control}-
 

The mode switch is on the throttle so you need to change those E's to A's (and remove that missing joystick entry).
You should also use substrings for your aircraft name(s) in the [Profile.xxx] sections. I have made these changes in the attached FSUIPC7.ini file if you could try it.

Any issues, please activate logging for Buttons & Switches and also attach your FSUIPC7.log file together with your FSUIPC7.ini file.

John

FSUIPC7.ini

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.