Saitek Throttle Quadrant and Reverse Thrust Issue

[markdosborne88]

Good Morning,

I've had my Saitek throttle quadrant set up for reverse thrust using FSUIPC for years without any problems.  Yesterday on my landing roll I pulled the throttle lever to reverse and the reversers would not not engage on the PMDG 777-300ER.  Today I've clean loaded the PMDG 737, 747, and 777 and the reverse thrust is still not working on any aircraft.  I have attempted to re-assign the reverse thrust as per the manual and I'm still getting no reverse thrust engagement.  My setup:

Buttons + Switches tab

Joy# 2    20 Btn#

Select for FS control ticked

Control sent when button pressed:

"Throttle Decr"

Parameter 0

Control to repeat while held ticket

Control sent when button released:

"Throttle Cut"

Parameter 0

 

This setup has worked for me for the past few years.  I have tried both profile specific and non profile specific and multiple different PMDG aircraft with nil result.  I have attempted to use other buttons to assign reverse thrust with nil result.  I have spoilers and flaps set with the other two levers which are working fine, as are my other assigned buttons on the quadrant.  The yoke, buttons on the yoke and rudder pedals are all working as normal.  I have recently assigned profile specific TOGA, auto throttle disarm and autopilot disconnect for the three aircraft mentioned, but the reverse thrust has worked fine since assigning the new buttons.  I have since deleted the new assignments while troubleshooting but still getting no auto throttle engagement.  Pressing "F2" will engage the auto throttle as normal on each aircraft.

I am using version 5.121b of FSUIPC with P3Dv4.5 and no crashes have been noted,

FSUIPC5.log:

********* FSUIPC5, Version 5.121b (2nd October 2017) by Pete Dowson *********
Running inside Prepar3D v4
Module base=7FF88EEB0000
Windows 10 Home 64 Bit reported as Build 17134, Release ID: 1803 (OS 10.0)
Prepar3D.exe version = 4.5.12.30293
Checking the Registrations now ...
User Name="Mark Osborne"
User Addr="markdosborne88@hotmail.com"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 29/08/2019 11:21:15
        0 FLT path = "C:\Users\Mark\Documents\Prepar3D v4 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 4.5.12.30293
        0             api.dll: 4.5.12.30293
        0        controls.dll: 4.5.12.30293
        0      fs-traffic.dll: 4.5.12.30293
        0             G3D.dll: 4.5.12.30293
        0        language.dll: 4.5.12.30293
        0            sim1.dll: 4.5.12.30293
        0        visualfx.dll: 4.5.12.30293
        0         weather.dll: 4.5.12.30293
        0          window.dll: 4.5.12.30293
        0 ----------------------------------
       15 FS path = "C:\Locheed Martin\P3Dv4\"
       93 ---------------------- Joystick Device Scan -----------------------
       93 Product= Saitek Pro Flight Yoke
       93    Manufacturer= Saitek
       93    Vendor=06A3, Product=0BAC (Version 3.4)
      109    GUIDs returned for product: VID_06A3&PID_0BAC:
      109       GUID= {BA86C510-C148-11E7-800D-444553540000}
      109       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      109 Product= Saitek Pro Flight Rudder Pedals
      109    Manufacturer= Saitek
      109    Vendor=06A3, Product=0763 (Version 1.1)
      109    GUIDs returned for product: VID_06A3&PID_0763:
      109       GUID= {BA8676F0-C148-11E7-800A-444553540000}
      109       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      109 Product= Logitech Attack 3
      125    Manufacturer= Logitech
      125    Vendor=046D, Product=C214 (Version 2.5)
      125    GUIDs returned for product: VID_046D&PID_C214:
      125       GUID= {BA8601C0-C148-11E7-8003-444553540000}
      125       Details: Btns=11, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      125 -------------------------------------------------------------------
      125 Device acquired for use:
      125    Joystick ID = 2 (Registry okay)
      125    2=Saitek Pro Flight Yoke
      125    2.GUID={BA86C510-C148-11E7-800D-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 1 (Registry okay)
      125    1=Saitek Pro Flight Rudder Pedals
      125    1.GUID={BA8676F0-C148-11E7-800A-444553540000}
      125 Device acquired for use:
      125    Joystick ID = 0 (Registry okay)
      125    0=Logitech Attack 3
      125    0.GUID={BA8601C0-C148-11E7-8003-444553540000}
      125 -------------------------------------------------------------------
      140 LogOptions=00000000 00000001
      140 SimConnect_Open succeeded: waiting to check version okay
      140 Opened separate AI Traffic client okay
    40812 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.12.30293 (SimConnect: 4.5.0.0)
    40812 Initialising SimConnect data requests now
    40812 FSUIPC Menu entry added
    40812 ... Using Prepar3D with Professional License
    40828 C:\Users\Mark\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    46296 C:\Locheed Martin\P3Dv4\.air
    70203 C:\Locheed Martin\P3Dv4\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
    70203 PMDG 737 offsets enabled
   115578 Aircraft loaded: running normally now ...
   115578 User Aircraft ID 2 supplied, now being used
   116015 System time = 29/08/2019 11:23:11, Simulator time = 11:22:22 (23:22Z)
   116015 Aircraft="Boeing 737-838(WL) Qantas 'New Livery' VH-VZL"
   129609 Starting everything now ...
   129687 ASN active function link set
   129687 Ready for ActiveSky WX radar with additional data
   130937 Advanced Weather Interface Enabled
   536937 Sim stopped: average frame rate for last 413 secs = 27.7 fps
   536937    Max AI traffic was 45 aircraft (Deleted 0)
   845828 Sim stopped: average frame rate for last 246 secs = 29.4 fps
   845828    Max AI traffic was 46 aircraft (Deleted 0)
   914515 Sim stopped: average frame rate for last 44 secs = 29.4 fps
   914515    Max AI traffic was 46 aircraft (Deleted 0)
  1235578 Sim stopped: average frame rate for last 188 secs = 29.2 fps
  1235578    Max AI traffic was 46 aircraft (Deleted 0)
  1921234 Sim stopped: average frame rate for last 458 secs = 29.4 fps
  1921234    Max AI traffic was 48 aircraft (Deleted 0)
  2571781 Sim stopped: average frame rate for last 39 secs = 28.9 fps
  2571781    Max AI traffic was 48 aircraft (Deleted 0)
  2918671 Sim stopped: average frame rate for last 328 secs = 29.4 fps
  2918671    Max AI traffic was 48 aircraft (Deleted 0)

FSUIPC5.JoyScan:

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

,,, HIDscanning completed

N, x00, x06A3, x0BAC, , -1, -1, 0, {NULL}, {NULL}, {BA86C510-C148-11E7-800D-444553540000}, Y, N
N, x00, x06A3, x0763, , -1, -1, 0, {NULL}, {NULL}, {BA8676F0-C148-11E7-800A-444553540000}, Y, N
N, x00, x046D, xC214, , -1, -1, 0, {NULL}, {NULL}, {BA8601C0-C148-11E7-8003-444553540000}, Y, N

,,, REGscanning completed

N, x00, x06A3, x0BAC, Saitek Pro Flight Yoke, -1, 2, 0, {NULL}, {BA86C510-C148-11E7-800D-444553540000}, {BA86C510-C148-11E7-800D-444553540000}, Y, Y
N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, -1, 1, 0, {NULL}, {BA8676F0-C148-11E7-800A-444553540000}, {BA8676F0-C148-11E7-800A-444553540000}, Y, Y
N, x00, x046D, xC214, Logitech Attack 3, -1, 0, 0, {NULL}, {BA8601C0-C148-11E7-8003-444553540000}, {BA8601C0-C148-11E7-8003-444553540000}, Y, Y

,,, User settings imported

N, x00, x06A3, x0BAC, Saitek Pro Flight Yoke, 2, 2, 0, {BA86C510-C148-11E7-800D-444553540000}, {BA86C510-C148-11E7-800D-444553540000}, {BA86C510-C148-11E7-800D-444553540000}, Y, Y
N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 1, 1, 0, {BA8676F0-C148-11E7-800A-444553540000}, {BA8676F0-C148-11E7-800A-444553540000}, {BA8676F0-C148-11E7-800A-444553540000}, Y, Y
N, x00, x046D, xC214, Logitech Attack 3, 0, 0, 0, {BA8601C0-C148-11E7-8003-444553540000}, {BA8601C0-C148-11E7-8003-444553540000}, {BA8601C0-C148-11E7-8003-444553540000}, Y, Y

,,, Values matched and decided

Y, x1E, x06A3, x0BAC, Saitek Pro Flight Yoke, 2, 2, 0, {BA86C510-C148-11E7-800D-444553540000}, {BA86C510-C148-11E7-800D-444553540000}, {BA86C510-C148-11E7-800D-444553540000}, Y, Y
Y, x1E, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 1, 1, 0, {BA8676F0-C148-11E7-800A-444553540000}, {BA8676F0-C148-11E7-800A-444553540000}, {BA8676F0-C148-11E7-800A-444553540000}, Y, Y
Y, x1E, x046D, xC214, Logitech Attack 3, 0, 0, 0, {BA8601C0-C148-11E7-8003-444553540000}, {BA8601C0-C148-11E7-8003-444553540000}, {BA8601C0-C148-11E7-8003-444553540000}, Y, Y

My version of FSUIPC is paid and registered and the aircraft I fly regularly are the PMDG 737, 747 and 777.  I have located the .ini file and if you require it I can send it through.  If you need any more information I can attempt to provide it.

Best regards,

Mark

[Thomas Richter]

Hi,

first thing to do is to update to latest FSUIPC5.152 as you run a very old, no longer supported, version.

The download link is Install FSUIPC5.152

Then run again and close the session. Please send all three files, FSUIPC5.ini. FSUIPC.log and FSUIPC5.JoyScan (best zipped).

Quote

********* FSUIPC5, Version 5.121b (2nd October 2017) by Pete Dowson *********

Thomas

[markdosborne88]

Thanks for the quick response.  Apologies for the out of date program.  The files are attached below.

Best regards,

Mark

FSUIPC5.zipFSUIPC5.JoyScan.zipFSUIPC5 (2).zip

[Thomas Richter]

Hi,

when looking at your INI file you i,e, for all aircrafts two controller assigned with the same functions. That is already something that will give trouble as bosth controller are connected. Also you should use:

[JoyNames]
AutoAssignLetters=Yes

Quote

[JoyNames]
AutoAssignLetters=No
0=Logitech Attack 3
0.GUID={BA8601C0-C148-11E7-8003-444553540000}
1=Saitek Pro Flight Rudder Pedals
1.GUID={BA8676F0-C148-11E7-800A-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={BA86C510-C148-11E7-800D-444553540000}

[Axes]
PollInterval=10
RangeRepeatRate=10
0=0X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=0Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
2=0Z,256,D,4,0,0,0    -{ DIRECT: Throttle }-
3=1X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
4=1Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
5=1R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
6=2X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
7=2Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
8=2Z,256,D,4,0,0,0    -{ DIRECT: Throttle }-
9=2U,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
10=2V,256,D,23,0,0,0    -{ DIRECT: Flaps }-

In addition you use profiles, again for the A2A Cessna 182 double assignments.

For PMDG 777 you created a profile but there are no Assignments for axes or buttons.

I would first clean that out and start proper with the assignments with one controller for axes and not having two assigned as the one that is not in use might sometimes overwrite the other. Also make sure you have Controller disabled in P3D in Options->Controls->Other

As for PMDG you have to send the axes direct to FS and not to FSUIPC for Calibration, that is a know problem with PMDG and a very common mistake.

Thomas

[Pete Dowson]

58 minutes ago, Thomas Richter said:

for all aircrafts two controller assigned with the same functions. That is already something that will give trouble as bosth controller are connected

Just a bit of clarification about that. If the controls are calibrated in FSUIPC then it will arbitrate between the two inputs, using the value with the most deflection from "normal".  They won't conflict. This is the arrangement used for dual controls, caprain and first officer.

But, Yes, for PMDG it isn't good to use "Direct to Calibration". The way their aircraft work simply doesn't like it, and you can get conflicting actions.

Pete

 

[markdosborne88]

Thanks Thomas and Pete for the quick replies.  Seems as though I had a few conflicts so I started from scratch by backing up and moving the contents of the modules folder and then starting with a fresh install.  Apart from attempting to set the throttle using "Send to FS as normal axis" which I was unsuccessful, the only button I attempted to set up was the reverse thrust using the steps in my original post which still is not engaging the reverse thrust.  I've attached the three files again for your browsing.  Controllers have been disables in P3D and pressing F2 engages the reverse thrust.

I have searched online for a PMDG specific throttle setup guide but have been unsuccessful.  If you could point me in the direction of one that you approve of that would be great too.

 Best regards,FSUIPC5.JoyScan.zip
MarkFSUIPC5 (2).zip 

FSUIPC5.zip

[Thomas Richter]

Hi,

42 minutes ago, markdosborne88 said:

the only button I attempted to set up was the reverse thrust using the steps in my original post which still is not engaging the reverse thrust.

in your original post you have the problem that the reverser don't work for the PMDG 777.

Quote

From original post:

Yesterday on my landing roll I pulled the throttle lever to reverse and the reversers would not not engage on the PMDG 777-300ER. 

But in your current INI file you sent there is nothing set for PMDG 777, only for PMDG 737?

If you look at the SDK .h file from PMDG for their different types you will find for example

PMDG_777
#define THIRD_PARTY_EVENT_ID_MIN    0x00011000            // equals to 69632

#define EVT_CONTROL_STAND_REV_THRUST1_LEVER                (THIRD_PARTY_EVENT_ID_MIN + 499)
#define EVT_CONTROL_STAND_REV_THRUST2_LEVER                (THIRD_PARTY_EVENT_ID_MIN + 503)

But for example you use for the PMDG 737 standard FS control but for PMDG (and other add-on AC) you have clearly to use their controls from their SDK, a well known problem.

[Buttons.PMDG B737-800W]
0=R2,20,C65602,0     -{THROTTLE_DECR}-
1=U2,20,C65604,0     -{THROTTLE_CUT}-

Try the correct PMDG controls instead for the related PMDG profiles.

Thomas

[markdosborne88]

Thanks Thomas,

I initially found the issue in the 777, and then went on to write that the problem was present in all three of the PMDG aircraft.

Anyway after the re-install of FSUIPC (the latest version) and after my last post, I opened P3D and I was able to set the reverse thrust for each aircraft.  Perhaps starting fresh after having conflicts has resolved the issue.

Thanks you both for your time.

Best regards,
Mark