After a full week of testing, forum reading, and many hours of frustration, I just figured out what was causing my T7 throttle levers to snap-back to idle, regardless of the physical throttle lever action of my Saitek Cessna Yoke & TQ.

 

As Pete suggested over in his forum, I now have all my T7 axis set to 'Send to FS as Normal Axis' and no Calibration section in my "PMDG 777 profile", in my fsuipc.ini file.  If you need to reverse an axis (without a calibration section), put a ", *-1" at the end of the axis assignment row in the fsuipc.ini file.  I have the 'Enable Controllers' box UNCHECKED in the FSX Menu Controllers GUI and there are no axis assigned to any of my devices in the bottom of the in the FSX standard.xml 'controllers' file.

 

The real remaining problem - why I was still having the Throttles snapping-back to idle, was the continued use of a Lua ThrottleManager object in my fsuipc.ini file.  It has been used for a long time with all my other aircraft axis, including the NGX, to reverse the throttle axis logic, using the same physical levers as reversers.  This lua 'ThrottleManger' module was not activated by an axis, but a Button declared in my FSUIPC.ini file.  It is triggered by a switch at the bottom of the physical lever travel on my Saitek axis.

 

I commented-out this Lua 'ThrottleManger' module (my only Lua module) in the 'Auto' section of the ini file, by adding a semi-colon at the beginning of the line.

[Auto]
;1=Lua ThrottleManager

Then in the 'Button' section of my T7 profile, I also commented-out (semi-colon at after the equals sign) the two buttons assigned to activate this module, to reverse the throttle levers.

[Buttons.PMDG 777]
...
21=;PY,20,CL1:T,1 ;      LUAToggle ThrottleManager
22=;PY,21,CL1:T,2 ;      LUAToggle ThrottleManager
...

These are now my PMDG T7 FSUPIC.ini axis assignments with AT on during taxi, and the FMC Throttles option set to over-ride 'Only in Arm/Hold' mode.  No "Calibration.PMDG 777" section exists in this profile.

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Combat Rudder Pedals
0.GUID={AF33D730-F67D-11E0-8001-444553540000}
1=Saitek Pro Flight Cessna Yoke
1.GUID={9D140D20-7B85-11E2-8001-444553540000}
2=Saitek Pro Flight Throttle Quadrant
2.GUID={20921B30-B542-11E0-8005-444553540000}
Y=1
T=2
R=0

[Axes.PMDG 777]
; Axis assigned as 'Send to FS as Normal Axis'
0=RX,256,F,66387,0,0,0,*-1 ;	Rudder
1=RY,256,F,66388,0,0,0 ;	Left Toe Brake
2=RR,256,F,65764,0,0,0 ;	Right Toe Brake
3=YX,256,F,65763,0,0,0 ;	Ailerons
4=YY,256,F,65762,0,0,0 ;	Elevator
5=YZ,256,F,66382,0,0,0,*-1 ;	Spoilers
6=YU,256,F,66420,0,0,0 ;	Axis Throttle 1 Set
7=YV,256,F,66423,0,0,0 ;	Axis Throttle 2 Set
8=TZ,256,F,66534,0,0,0,*-1 ;	Flaps





Just reading....  as described on  page 41 of the FSUIPC for Advanced Users doc, it appears we can use Lua modules on a 'per profile' basis, instead of all aircraft, by creating a "Auto.ProfileName" section for each profiled aircraft.

 

Hope this helps someone else...

Thanks for the detailed post Al.  I'm looking forward to getting my throttle to work properly.

Strange. My Saitek Yoke and TQ just "worked" (calibrated through FSUIPC). Don't know anything about a Lua ThrottleManager

An updated axes section as I had some of the Saitek Rudder Pedals axes mixed up.

 

Also, I had to remove all traces of any 'Lau Throttle Manager' entries, even those only associated with other aircraft profiles [Auto.ProfileName] functions for now.  I think the Lua ThrottleManager object gets loaded regardless if it's used in an active profile, and then it conflicts with the PMDG modules (Throttles) when they're loaded loaded at the start of a FS session.  I had to perform a complete fresh restart of FSX each time I wanted to test the affects of the Lua ThrottleManager anywhere in the ini file.  Pressing the 're-read FSUIPC axis' button had no affect on the conflict between the Lua module and the PMDG subsystems (Throttles).

[Axes.PMDG 777]
0=RX,256,F,66387,0,0,0,*-1 ;	Left Toe Brake
1=RY,256,F,66388,0,0,0,*-1 ;	Right Toe Brake
2=RR,256,F,65764,0,0,0 ;	Rudder
3=YX,256,F,65763,0,0,0 ;	Ailerons
4=YY,256,F,65762,0,0,0 ;	Elevator
5=YZ,256,F,66382,0,0,0,*-1 ;	Spoilers
6=YU,256,F,66420,0,0,0 ; 	Axis Throttle 1 Set
7=YV,256,F,66423,0,0,0 ;	Axis Throttle 2 Set
8=TZ,256,F,66534,0,0,0,*-1 ;	Flaps

I tried your settings as per your first post and the throttle axis does not perform well.  I deleted all my control axis settings in FSX, is that what you've done?

I tried your settings as per your first post and the throttle axis does not perform well.  I deleted all my control axis settings in FSX, is that what you've done?

 

It's not as easy as that as I'm used to manually editing my fsuipc.ini file by hand.  It might be easier if you attach your ini file to a post here and let me take a look at it.

 

Also, you need to make sure you have the FSX menu > Controls > 'Controllers Enabled' box UNCHECKED which disables all FSX's built-in axis and calibration functionality.

I used to have reversers working via FSUIPC.  I disabled my Saitek controller in FSX and I still cannot get the reversers to function with the *-1 added.  I tried to set the controls as "Send to FS as Normal Axis" but have since changed back to "Send Direct to FSUIPC Calibration"

 

What a mess, for some reason I have to set reverse axis in FSUIPC otherwise the Spoiler and Flaps deploy when the levers are at the top of the Saitek Quadrant. 

 

This is my current setup.

 

[JoyNames]

AutoAssignLetters=No

0=Saitek Pro Flight Cessna Yoke

0.GUID={0D579E00-55AB-11E1-8001-444553540000}

1=Thrustmaster HOTAS Cougar

1.GUID={E9BA2630-0950-11E1-8001-444553540000}

 

[Axes]

0=0X,256,F,65695,0,0,0  //Aileron

1=0Y,256,F,65694,0,0,0  //Elevator

2=0Z,256,D,4,0,0,0,*-1  //Throttle, Single lever.

3=0U,256,D,22,0,0,0  //Spoiler

4=0V,256,D,23,0,0,0  //Flaps

5=1Z,256,F,65696,0,0,0

6=1R,256,F,65764,0,0,0

7=1V,256,F,66388,0,0,0

8=1T,256,F,66387,0,0,0

 

[JoystickCalibration]

AllowSuppressForPFCquad=Yes

ExcludeThrottleSet=No

ExcludeMixtureSet=Yes

ExcludePropPitchSet=Yes

SepRevsJetsOnly=No

ApplyHeloTrim=No

UseAxisControlsForNRZ=No

FlapsSetControl=0

FlapDetents=No

ReverserControl=66292

Reverser1Control=66422

Reverser2Control=66425

Reverser3Control=66428

Reverser4Control=66431

MaxThrottleForReverser=256

AileronTrimControl=66731

RudderTrimControl=66732

CowlFlaps1Control=66162

CowlFlaps2Control=66163

CowlFlaps3Control=66164

CowlFlaps4Control=66165

SteeringTillerControl=0

MaxSteerSpeed=60

Spoilers=16256,16380/16

Flaps=0,16380/16

FlapStarts=-16384,1,16384

FlapEnds=-16128,16384,16384

Throttle=-16256,-16256

 

I've had nothing but headaches after installing the 777, haven't even finished 1 short circuit flight with it yet.  

 

Thanks for looking at my setup, appreciate any feedback you can give me.

 

Rob

Ok, I haven't tried this without a aircraft-specific profile [Axes.SomeProfileName].  Second, you don't comment stuff in the fsuipc.ini file with // like you do in the fsx.cfg file for example, you use a semi-colon ; in ini files (anything after the semi-colon won't be read/parsed - look at the comments in my examples above.  Third, you should delete the entire [JoystickCalibration] section including the header itself - everything, so all you have in your example would be the [JoyNames] and [Axes] sections.  Forth, if you are not actually using the couger to control something in the 777, don't have it listed as any axes.  Fifth, the ,*-1 is not about providing 'reversers' functionality such as during landing.  It's used to reverse the travel of a physical axes so it operates as expected when pushed away from you or pulled down towards you.  Normally you would reverse a lever travel in the [JoystickCalibration] section, which is where the FSUIPC GUI would put it, but, since we're removing the entire [JoystickCalibration] section, we're using the ,*-1 trick at the end of an axis line instead.  You will need to add this to the Spoiler and Flaps levers to make it work as expected.  I also added it to my Saitek Rudder toe brakes to reverse their travel as well.

 

So, if you don't really need the Couger, I might reconstruct your [Axes] section like this - be SURE you FSX menu 'Enable Controllers' checkbox is UNCHECKED.  Non of this will work if you're still processing any device FSX menu controls GUI's.

[Axes]
0=0X,256,F,65763,0,0,0 ;         Ailerons
1=0Y,256,F,65762,0,0,0 ;         Elevator
2=0Z,256,F,65765,0,0,0 ;         Axis Throttle Set
3=0U,256,F,66382,0,0,0,*-1 ;     Spoilers
4=0V,256,F,66534,0,0,0,*-1 ;     Flaps

This is my FSUIPC.ini file (without all the other aircraft-specific profile sections), only the "PDMG 777" section.  Some notes include...  This is using 'Send to FS as Nomal Axes'.   DO NOT have any default Axes, Buttons, or JoystickCalibration sections without aircraft-specific profile names defining profiles for multiple aircraft.  Do NOT use any Lua Throttle programs, even possibly in other aircraft sections.  ShortAircraftNameOK and UseProifiles must both be 'yes' for aircraft profiles like this to work.  My hardware is listed in the [JoyNames] section and converted to a letter for each device / Y = Yoke, T = Throttle, R = Rudder.  This is using the latest FSUIPC v4.920 and WideFS/client is enabled.

[General]
UpdatedByVersion=4920
History=FD4DDBOJ2WAC2TP193WHT
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=Yes
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Yes
UseProfiles=Yes
EnableMouseLook=No
AxesWrongRange=No
TCASid=Flight
TCASrange=0
FixedTCASoptions=Yes
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
AdvDisplayHotKey=192,10
Console=No
OOMcheck=Yes
InitDelayDevicesToo=No
UseMidMouseBtn=Yes
UseSystemTime=Yes
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0

[Programs]
;RunIf1=READY,CLOSE,C:\OpusFSX\FSXSERVER.EXE

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Combat Rudder Pedals
0.GUID={AF33D730-F67D-11E0-8001-444553540000}
1=Saitek Pro Flight Cessna Yoke
1.GUID={9D140D20-7B85-11E2-8001-444553540000}
2=Saitek Pro Flight Throttle Quadrant
2.GUID={20921B30-B542-11E0-8005-444553540000}
Y=1
T=2
R=0

[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No

[GPSout]
GPSoutEnabled=No
Port=COM0
Speed=4800
Interval=2000
PosTo6Decimal=No
Sentences=

[GPSout2]
GPSoutEnabled=No
Port=<none set>
Speed=4800
Interval=2000
PosTo6Decimal=No
Sentences=

[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002
BroadcastMode=Yes
ProtocolPreferred=UDP

[ClientNames]
1=MAINCOMP

[Sounds]
Path=D:\FSX\Sound\
Device1=Primary Sound Driver
Device2=Speakers (Creative SB X-Fi)
Device3=SPDIF Out (Creative SB X-Fi)
Device4=Headset Earphone (Plantronics Headset)

[Window.Radar Contact]
Docked=0, 952, 2112, 1187

[Profile.PMDG 777]
1=PMDG 777

[Axes.PMDG 777]
0=RX,256,F,66387,0,0,0,*-1 ;	Left Toe Brake
1=RY,256,F,66388,0,0,0,*-1 ;	Right Toe Brake
2=RR,256,F,65764,0,0,0 ; 	Rudder
3=YX,256,F,65763,0,0,0 ; 	Ailerons
4=YY,256,F,65762,0,0,0 ; 	Elevator
5=YZ,256,F,66382,0,0,0,*-1 ;	Spoilers
6=YU,256,F,66420,0,0,0 ; 	Axis Throttle 1 Set
7=YV,256,F,66423,0,0,0 ; 	Axis Throttle 2 Set
8=TZ,256,F,66534,0,0,0,*-1 ;	Flaps

[Buttons.PMDG 777]
ButtonRepeat=20,10
0=;  ********   YOKE Buttons  **********
1=PY,0,K82,9 ;          Soft_AT_DISC Shft-R
2=PY,1,K65,11 ;         Soft_AP_DISC Ctrl-Shft-A
3=RY,2,C65607,0 ;       ELEV_TRIM_DN
4=RY,3,C65615,0 ;       ELEV_TRIM_UP
5=RY,11,C66278,0 ;      RUDDER_TRIM_LEFT
6=RY,12,C66279,0 ;      RUDDER_TRIM_RIGHT
7=;  ********   THRTL QUAD    **********
8=PY,13,K71,11 ;        GEAR_TOGGLE Ctrl-Shft-G
9=PY,14,K79,8 ;         NAV_STROBES_TOGGLE O
10=PY,15,K76,10 ;       LANDING_LIGHTS_TOGGLE Ctrl-L
11=PY,16,K71,9 ;        RUNWAY_LIGHTS_TOGGLE Shft-G
12=PY,17,K82,11 ;       TOGGLE_TAXI_LIGHTS Ctrl-Shft-R
13=PY,18,K76,11 ;       ANTI COLLISION LIGHTS Ctrl-Shft-L
14=PT,0,C65789,0 ;      SIM_RATE_INCR
15=PT,1,C65790,0 ;      SIM_RATE_DECR
16=PT,2,C65752,0 ;      PARKING_BRAKES
17=PT,3,K74,10 ;        Ctrl-J - TOGGLE_JETWAY
18=PT,4,C1009,0 ;	TRAFFIC_DENSITY_TOGGLE
19=PT,5,C66199,0 ;      TOGGLE_AIRCRAFT_LABELS
20=;  ********   THRTL LEVERS  **********
21=RY,20,C65966,0 ;	THROTTLE1_DECR
22=UY,20,C65967,0 ;	THROTTLE1_CUT
23=RY,21,C65971,0 ;	THROTTLE2_DECR
24=UY,21,C65972,0 ;	THROTTLE2_CUT
25=;  ********   YOKE Hat Switch  **********
26=RY,32,C65734,0 ;     PAN_UP
27=UY,32,C66416,-1 ;    PAN_VIEW -1
28=RY,33,C65856,0 ;     PAN_RIGHT_UP
29=UY,33,C66416,-1 ;    PAN_VIEW -1
30=RY,34,C65672,0 ;     PAN_RIGHT
31=UY,34,C66416,-1 ;    PAN_VIEW -1
32=RY,35,C65857,0 ;     PAN_RIGHT_DOWN
33=UY,35,C66416,-1 ;    PAN_VIEW -1
34=RY,36,C65735,0 ;     PAN_DOWN
35=UY,36,C66416,-1 ;    PAN_VIEW -1
36=RY,37,C65855,0 ;     PAN_LEFT_DOWN
37=UY,37,C66416,-1 ;    PAN_VIEW -1
38=RY,38,C65671,0 ;     PAN_LEFT
39=UY,38,C66416,-1 ;    PAN_VIEW -1
40=RY,39,C65854,0 ;     PAN_LEFT_UP
41=UY,39,C66416,-1 ;    PAN_VIEW -1

I added the *-1 as per your explanation, I understand what that means now, the axis work better now.  I removed the [JoystickCalibration] section and will read up on FSUIPC tonight and try to figure out how to reapply the reverser axis to my aircraft.  

 

Lastly, I use the HOTAS Cougar when I fly Airbus type AC and will leave it in for now.  I had a setup for applying reversers which worked even on the Aerosoft Airbus X which many people had an issue with, maybe that will work.

 

Thanks again for your help Al, looking forward to reporting back with positive results.

No problem, Robert.  I hope it works out for you.  Also, I just corrected the lever designations in the last three rows (Z, U, and V) in the Axes section I re-wrote for you above.

I just thought I'd add my 2 cents in here.  I use the Saitek Yoke (with TQ) and 2nd TQ.  I have it running correctly.  The throttles are set through FSUIPC in the following manner:

 

1 Load Aircraft to be configured

2 Open FSUIPC

3 Select Axis Assignment

4 Select Type of Action Required

Send Direct to FSUIPC Calibration

5 Cycle Levers through idle to full throttle - should get the following numbers: -16384, idle to  16383 (approx), full throttle

6 Select action from drop down menu - # 1 Throttle or #2 Throttle

 

Go to Joystick Calibration

 

Joystick Calibration

1 Cycle each throttle lever through range.

 

DO NOT CLICK ON SET OR CALIBRATE JOYSTICK FURTHER.

 

2 Check ExcludeTHROTTLEn_SET (lower right corner)

 

3 Click on OK.

 

That's the throttles set, now for the reverse thrust which is controlled by a switch on the Saitek TQ by pulling the levers through idle detent, activating a switch/button.

 

1 Go to  Buttons and Switches

2 Check

Profile Specific and Select for FS control

3 Push throttle lever down past detent

4 Select Throttle Decr from right side menu

5 Parameter = 0

6 Check

Control to repeat while held

7 Select Throttle 1 (or 2) Cut under

Control sent when button released.

 

That's all there is to it. throttles and reversers set for the T7 or NGX depending on which aircraft you have open.

 

Rob

Forgot to mention, uncheck all Throttle and Throttle Decrease settings in FSX under Saitek Yoke and Saitek TQ

 

Rob

If you're still having problems and you have manually changed the FSUIPC Ini file, delete the file and start over.  You don't need to do anything in the Ini file

 

Rob

Al and Rob,

 

Thanks a bunch, I will give it a go tomorrow.  It will be nice to get a short flight in, I really appreciate your help.

 

Rob

Thanks for the fix but totally disappointing that cant use the LUA throttlemanager with the 777, being able to land and not be hitting silly f2, or the likes, and having proper control of reversers was more realistic.

 

PMDG need to sort it, out, or come up with their own solution that works and hardcoded into the sim.

I don't think it is a PMDG problem/issue.  All TQ's can be configured through FSUIPC.  If you have the Go Flight TQ, you don't use the Go Flight software to set the TQ.  You use FSUIPC and can set the axis to include reverse thrust when you calibrate them through FSUIPC.  If memory serves me correctly, the additional step in that case is to check SET which will automatically set up a reverse section on the lever.  It sets up a Reverse, Idle, and Max for the thrust lever.

 

Rob