Jump to content
The simFlight Network Forums
Sign in to follow this  
MRIZ

FSUIPC and Saitek Throttle mixture lever

Recommended Posts

*** Moved to Support Forum - Please post all support requests here ***

Hi.

I have bought a registered copy of FSUIPC  to make customized confs of my Saitek stuff.

I have tried to configure the Mixture lever (the last on the right: the red capped one) but when I move this lever nothing happens.

It seems that FSUIPC doesn't see this particular lever. It works, instead, with the other two.

The thottle I am using is the one directly connected to the Yoke via a PS2 port.

Any suggestions?

Thank you very much to anyone will help me.

Max

Share this post


Link to post
Share on other sites

Hi Max,

if you can't see it as an axis, but you can see the other two levers, then I suspect its either faulty or you have a dodgy connection somewhere. Can you see all 3 rocker switch buttons (6 buttons)?

Can you check what axis the device is reported as having in your fsuipc log file, you should find something like this:

    16813 Product= Saitek Pro Flight Yoke
    16813    Manufacturer= Saitek
    16813    Vendor=06A3, Product=0BAC (Version 3.4)
    16813    GUIDs returned for product: VID_06A3&PID_0BAC:
    16813       GUID= {327F7D90-F534-11E7-8005-444553540000}
    16813       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255

Cheers,

John

Share this post


Link to post
Share on other sites

Hi, John.

Thanks a lot for your assistance.

Yes, I can see all the 3 rocker switch buttons.

Where can I find out the fsuipc log file? I mean the path to the folder where this file is.

As soon as I find it out, I'll have a look at it and publish the part regarding the Saitek Pro Flight Yoke so, if you want, you can comment it.

Thank you again.

Ciao,

Max

Share this post


Link to post
Share on other sites

Its in the Modules folder - if you go to the FSUIPC 'Logging' tab there's an 'Open Folder' button which will take you there. You may have to configure explorer to see system files/known extensions.

 

Share this post


Link to post
Share on other sites

Hi, John.

Here is what I have found out.

1) the first lever (from the left to the right) of the throttle is recognized as  Z axis (Joy#0);

2) the second lever (from the left to the right) of the throttle is recognized as  U axis (Joy#0);

3) the third lever is not seen at all (when I move it, nothing happens in FSUIPC Axis Assignment tab);

3) all the all the 3 rocker switch buttons are seen by FSUIPC regularly as buttons from 14 to 19 (always Joy#0).

This is what is contained in the FSUIPC log file:

********* FSUIPC5, Version 5.15 (27th November 2018) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FECBDE0000
Windows 7 Professional 64 Bit with SP 1.0 reported as Build 7601 (OS 6.1)
Prepar3D.exe version = 4.4.16.27077
Reading options from "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="massimo rizzo"
User Addr="mrizfsx@gmail.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 13/03/2019 17:47:05
        0 FLT path = "C:\Users\Max_I7_6800K\Documents\Prepar3D v4 Files\"
        0 Using DialogMode
       15 FS path = "C:\Program Files\Lockheed Martin\Prepar3D v4\"
      156 ---------------------- Joystick Device Scan -----------------------
      156 Product= Saitek Pro Flight Rudder Pedals
      156    Manufacturer= Saitek
      156    Vendor=06A3, Product=0763 (Version 1.1)
      858    GUIDs returned for product: VID_06A3&PID_0763:
      858       GUID= {F2A8C2E0-34E9-11E7-8001-444553540000}
      858       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      873 Product= Saitek Pro Flight Yoke
      873    Manufacturer= Saitek
      873    Vendor=06A3, Product=0BAC (Version 3.4)
      873    GUIDs returned for product: VID_06A3&PID_0BAC:
      873       GUID= {1BDB3520-D27B-11E6-8002-444553540000}
      873       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      873 -------------------------------------------------------------------
      873 Device acquired for use:
      873    Joystick ID = 2 (Registry okay)
      873    2=Mad Catz Pro Flight Rudder Pedals
      873    2.GUID={F2A8C2E0-34E9-11E7-8001-444553540000}
      873 Device acquired for use:
      873    Joystick ID = 0 (Registry okay)
      873    0=Pro Flight Yoke
      873    0.GUID={1BDB3520-D27B-11E6-8002-444553540000}
      873 -------------------------------------------------------------------
      889 LogOptions=00000000 00000001
      904 -------------------------------------------------------------------
      904 VRI port 1 "com0" failed to open
      904 SimConnect_Open succeeded: waiting to check version okay
      904 Opened separate AI Traffic client okay
      904 ### PDKmodeHelper callback registered!
    52166 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.4.16.27077 (SimConnect: 4.4.0.0)
    52166 Initialising SimConnect data requests now
    52166 FSUIPC Menu entry added
    52182 ... Using Prepar3D with Academic License
    52307 C:\Users\Max_I7_6800K\Documents\Prepar3D v4 Files\Maule Maine.fxml
    52307 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Maule_M7_260C\Maule_M7_260C.air
   170399 C:\Program Files\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Carenado CT206H_Stationair\CT206H.air
   170836 ### The user object is 'CT206H Stationair GASVW'
   170836 ### Mode is NORMAL
   172147 ### Mode: PAUSE on
   256122 Loading Complete ...
   256793 ### Mode is NORMAL
   258540 User Aircraft ID 2 supplied, now being used
   258540 Aircraft loaded: running normally now ...
   258758 System time = 13/03/2019 17:51:24, Simulator time = 14:02:37 (18:02Z)
   258758 Aircraft="CT206H Stationair GASVW"
   264764 -------------------- Starting everything now ----------------------
   264811 LUA.0: beginning "C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\ipcReady.lua"
   264983 LUA.1: [START] *********************** STARTING LINDA ***********************
   264998 LUA.1: LINDA:: [START] Loading System Configuration files
   265014 LUA.1: LINDA:: *********************************************************************
   265014 LUA.1: LINDA:: [START] WARNING - All LUA logging switched off !!!
   265014 LUA.1: LINDA:: [START] Go to Setup LINDA to switch on (if required)
   265014 LUA.1: LINDA:: *********************************************************************
   265061 LUA.1: LINDA:: [START] System Configuration files loaded
   265919 Advanced Weather Interface Enabled

 

 

Thanks a lot for your hep.

 

Max

Share this post


Link to post
Share on other sites

Hi Max,

the third lever should be the U axis, and the axis is given in the details for that device.

As I said, I think you have a hardware or connection problem if the axis can't be seen. Anything device/axis thats seen by windows should be available in FSUIPC.  Maybe try temporarily enabling controls in your sim to see if the sim can see it (but I doubt it!).

I also see you are using LINDA - try without this to see if that makes a difference (e.g. rename your ipcReady.lua to ipcReady.disabled), but again I doubt this will do anything either but quick and worth a try.

Is this a new device? Have you ever been able to use/assign to this axis?

Are you also using a VRInsight device? This error indicates that its either not connected or on the wrong com port: VRI port 1 "com0" failed to open

Maybe you could also post your joyscan.csv file, also located in the Modules folder.

Cheers,

John

 

Share this post


Link to post
Share on other sites

Hi, John.

No, I have never configured this axis.

Windows does nothing when I move this axis, unlike when I move the other two.

But when I move the central lever, the Windows Property advanced panel shows the movement of the third cursor also.

I do not have VRInsight device.

Here is the content of joyscan.csv file:

 

Good?, flags, VID, PID, Name, INIid, REGid, RegEntry, INIguid, REGguid, HIDguid, ValsOK?, ReadsOk?

,,, HIDscanning completed

N, x00, x06A3, x0763, , -1, -1, 0, {NULL}, {NULL}, {F2A8C2E0-34E9-11E7-8001-444553540000}, Y, N
N, x00, x06A3, x0BAC, , -1, -1, 0, {NULL}, {NULL}, {1BDB3520-D27B-11E6-8002-444553540000}, Y, N

,,, REGscanning completed

N, x00, x06A3, x0763, Mad Catz Pro Flight Rudder Pedals, -1, 2, 0, {NULL}, {F2A8C2E0-34E9-11E7-8001-444553540000}, {F2A8C2E0-34E9-11E7-8001-444553540000}, Y, Y
N, x00, x06A3, x0BAC, Pro Flight Yoke, -1, 0, 0, {NULL}, {1BDB3520-D27B-11E6-8002-444553540000}, {1BDB3520-D27B-11E6-8002-444553540000}, Y, Y

,,, User settings imported

N, x00, x06A3, x0763, Mad Catz Pro Flight Rudder Pedals, 2, 2, 0, {F2A8C2E0-34E9-11E7-8001-444553540000}, {F2A8C2E0-34E9-11E7-8001-444553540000}, {F2A8C2E0-34E9-11E7-8001-444553540000}, Y, Y
N, x00, x06A3, x0BAC, Pro Flight Yoke, 0, 0, 0, {1BDB3520-D27B-11E6-8002-444553540000}, {1BDB3520-D27B-11E6-8002-444553540000}, {1BDB3520-D27B-11E6-8002-444553540000}, Y, Y

,,, Values matched and decided

Y, x1E, x06A3, x0763, Mad Catz Pro Flight Rudder Pedals, 2, 2, 0, {F2A8C2E0-34E9-11E7-8001-444553540000}, {F2A8C2E0-34E9-11E7-8001-444553540000}, {F2A8C2E0-34E9-11E7-8001-444553540000}, Y, Y
Y, x1E, x06A3, x0BAC, Pro Flight Yoke, 0, 0, 0, {1BDB3520-D27B-11E6-8002-444553540000}, {1BDB3520-D27B-11E6-8002-444553540000}, {1BDB3520-D27B-11E6-8002-444553540000}, Y, Y
 

Max

 

 

Share this post


Link to post
Share on other sites

Hi Max,

from what you say, it certainly sounds like you have faulty hardware or a faulty connection.

You also say: 

Quote

But when I move the central lever, the Windows Property advanced panel shows the movement of the third cursor also.

By 'cursor' do you mean 'lever'? Still, I suspect that your hardware is faulty.

FSUIPC receives the axis values from Windows, so I'm afraid if Windows is not seeing that lever, then there's nothing that can be done in FSUIPC to resolve this problem. FSUIPC will only recognise the first axis movement/value it receives. Having two axis values for one lever movement sounds very suspicious - either a hardware problem or a driver issue would be the culprit.

Btw, have you installed any Saitek driver software? If so, please remove this and re-test. If not, I think you have a hardware (or Windows) problem.

Cheers,

John

P.S. Don't forget to try without LINDA, and also please post your ini file.

Share this post


Link to post
Share on other sites

John, 

thank you very much for your help.

I will try removing any Saitek driver and without Linda running.

I will tell you as soon as I'll test it.

 

Thanks again!

Max

 

Share this post


Link to post
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
Sign in to follow this  

×

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.