Saitek Throttle Problem

[John Pettit]

Hi Pete,

Currently I have a registered copy of FSUIPC5 (version 5.153) All was working well yesterday on my new flight computer. Today I had the following problem(s) when running Aerosoft A321 Professional on Prepar3Dv4.5 :

After engine start the Autothrottle button illuminated green and would not disengage until restart of P3D. After re-start of P3D when engines had been started (and NO A/Throttle active green) the throttles would not function correctly, i.e. physical movement of Saitek throttles did not produce any Virtual Cockpit movement of throttles or engine RPM increase with normal movement. Oddly, if the throttles were 'pumped' back and forth, the engine rpm would slowly increase. All other axes of Saitek Pro flight controls (spoilers, flaps, rudders, toe-brakes) worked correctly according to FSUIPC assignment, as did the axes on the Thrustmaster 1600M joystick.

I tried changing the aircraft model back to the Aerosoft A320 Professional which I had successfully used yesterday, but the problem persisted.

Here is the FSUIPC5.log file:

********* FSUIPC5, Version 5.153 (12th December 2019) by Pete & John Dowson *********
Running inside Prepar3D v4
Module base=7FFC24BD0000
Windows 10 Home 64 Bit reported as Build 18363, Release ID: 1909 (OS 10.0)
Prepar3D.exe version = 4.5.13.32097
Reading options from "C:\Prepar3D\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="JohnPettit"
User Addr="xxxxxx@xxxxxxxxxx"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 26/02/2020 21:23:15
        0 FLT path = "C:\Users\John\Documents\Prepar3D v4 Files\"
        0 Using DialogMode
       16 FS path = "C:\Prepar3D\"
       94 ---------------------- Joystick Device Scan -----------------------
      156 Product= Saitek Pro Flight Yoke
      156    Manufacturer= Saitek
      156    Vendor=06A3, Product=0BAC (Version 3.4)
      156    GUIDs returned for product: VID_06A3&PID_0BAC:
      156       GUID= {7A5E0AF0-5428-11EA-8004-444553540000}
      156       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      156 Product= T.16000M
      156    Manufacturer= Thrustmaster
      156    Vendor=044F, Product=B10A (Version 5.0)
      156    GUIDs returned for product: VID_044F&PID_B10A:
      156       GUID= {7A65FA30-5428-11EA-8007-444553540000}
      156       Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255
      172 Product= Saitek Pro Flight Rudder Pedals
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0763 (Version 1.0)
      172    GUIDs returned for product: VID_06A3&PID_0763:
      172       GUID= {7A6C14B0-5428-11EA-800D-444553540000}
      172       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      172 Product= Saitek Pro Flight Quadrant
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0C2D (Version 2.0)
      172    GUIDs returned for product: VID_06A3&PID_0C2D:
      172       GUID= {7A6C14B0-5428-11EA-800E-444553540000}
      172       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      172 -------------------------------------------------------------------
      172 Device acquired for use:
      172    Joystick ID = 0 (Registry okay)
      172    0=Saitek Pro Flight Yoke
      172    0.GUID={7A5E0AF0-5428-11EA-8004-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 1 (Registry okay)
      172    1=T.16000M
      172    1.GUID={7A65FA30-5428-11EA-8007-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 2 (Registry okay)
      172    2=Saitek Pro Flight Rudder Pedals
      172    2.GUID={7A6C14B0-5428-11EA-800D-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 3 (Registry okay)
      172    3=Saitek Pro Flight Throttle Quadrant
      172    3.GUID={7A6C14B0-5428-11EA-800E-444553540000}
      172 -------------------------------------------------------------------
      203 LogOptions=00000000 00000001
      203 -------------------------------------------------------------------
      203 SimConnect_Open succeeded: waiting to check version okay
      219 Opened separate AI Traffic client okay
     9875 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.13.32097 (SimConnect: 4.5.0.0)
     9875 Initialising SimConnect data requests now
     9875 FSUIPC Menu entry added
     9875 ... Using Prepar3D with Professional License
     9891 C:\Users\John\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
     9891 C:\Prepar3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    30469 Weather Mode now = Theme
    31922 C:\Users\John\Documents\Aerosoft\Aerosoft A320-A321 Professional\SimObjects\Airplanes\Aerosoft A320 IAE Professional\A320.air
    31922 C:\Users\John\Documents\Prepar3D v4 Files\EGLL, A320,Stand 521, Engs OFF,APU running.fxml
    39438 ### The user object is 'Aerosoft A320 professional BRITISH AIRWAYS G-EUUU'

and here is the FSUIPC.JoyScan.csv file :

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

,,, HIDscanning completed

N, x00, x06A3, x0BAC, , -1, -1, 0, {NULL}, {NULL}, {7A5E0AF0-5428-11EA-8004-444553540000}, Y, N
N, x00, x044F, xB10A, , -1, -1, 0, {NULL}, {NULL}, {7A65FA30-5428-11EA-8007-444553540000}, Y, N
N, x00, x06A3, x0763, , -1, -1, 0, {NULL}, {NULL}, {7A6C14B0-5428-11EA-800D-444553540000}, Y, N
N, x00, x06A3, x0C2D, , -1, -1, 0, {NULL}, {NULL}, {7A6C14B0-5428-11EA-800E-444553540000}, Y, N

,,, REGscanning completed

N, x00, x06A3, x0BAC, Saitek Pro Flight Yoke, -1, 0, 0, {NULL}, {7A5E0AF0-5428-11EA-8004-444553540000}, {7A5E0AF0-5428-11EA-8004-444553540000}, Y, Y
N, x00, x044F, xB10A, T.16000M, -1, 1, 0, {NULL}, {7A65FA30-5428-11EA-8007-444553540000}, {7A65FA30-5428-11EA-8007-444553540000}, Y, Y
N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, -1, 2, 0, {NULL}, {7A6C14B0-5428-11EA-800D-444553540000}, {7A6C14B0-5428-11EA-800D-444553540000}, Y, Y
N, x00, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, -1, 3, 0, {NULL}, {7A6C14B0-5428-11EA-800E-444553540000}, {7A6C14B0-5428-11EA-800E-444553540000}, Y, Y

,,, User settings imported

N, x00, x06A3, x0BAC, Saitek Pro Flight Yoke, 0, 0, 0, {7A5E0AF0-5428-11EA-8004-444553540000}, {7A5E0AF0-5428-11EA-8004-444553540000}, {7A5E0AF0-5428-11EA-8004-444553540000}, Y, Y
N, x00, x044F, xB10A, T.16000M, 1, 1, 0, {7A65FA30-5428-11EA-8007-444553540000}, {7A65FA30-5428-11EA-8007-444553540000}, {7A65FA30-5428-11EA-8007-444553540000}, Y, Y
N, x00, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 2, 2, 0, {7A6C14B0-5428-11EA-800D-444553540000}, {7A6C14B0-5428-11EA-800D-444553540000}, {7A6C14B0-5428-11EA-800D-444553540000}, Y, Y
N, x00, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, 3, 3, 0, {7A6C14B0-5428-11EA-800E-444553540000}, {7A6C14B0-5428-11EA-800E-444553540000}, {7A6C14B0-5428-11EA-800E-444553540000}, Y, Y

,,, Values matched and decided

Y, x1E, x06A3, x0BAC, Saitek Pro Flight Yoke, 0, 0, 0, {7A5E0AF0-5428-11EA-8004-444553540000}, {7A5E0AF0-5428-11EA-8004-444553540000}, {7A5E0AF0-5428-11EA-8004-444553540000}, Y, Y
Y, x1E, x044F, xB10A, T.16000M, 1, 1, 0, {7A65FA30-5428-11EA-8007-444553540000}, {7A65FA30-5428-11EA-8007-444553540000}, {7A65FA30-5428-11EA-8007-444553540000}, Y, Y
Y, x1E, x06A3, x0763, Saitek Pro Flight Rudder Pedals, 2, 2, 0, {7A6C14B0-5428-11EA-800D-444553540000}, {7A6C14B0-5428-11EA-800D-444553540000}, {7A6C14B0-5428-11EA-800D-444553540000}, Y, Y
Y, x1E, x06A3, x0C2D, Saitek Pro Flight Throttle Quadrant, 3, 3, 0, {7A6C14B0-5428-11EA-800E-444553540000}, {7A6C14B0-5428-11EA-800E-444553540000}, {7A6C14B0-5428-11EA-800E-444553540000}, Y, Y

 

If there is any other information you require please let me know. Any and all help much appreciated, as always. I am hoping it's something simple I've missed. I just tried the controls set-up on a Beech Baron BE58 and all axes work 100% on that model as assigned within FSUIPC.

John

NB: I removed my e-mail address from thefiles above for obvious reasons.

 

 

 

[John Dowson]

Could you activate Axis controls logging (from the FSUIPC logging tab) and generate another FSUIPC5.log file showing your problem, and then upload this together with your FSUIPC5.ini file please.

It seems strange that it was working one day and not the next - something must have changed. Do you know what? Can you also check to see if you have controllers disabled in P3D, and if not then check your P3D assignments as well.

Cheers,

John

[John Pettit]

Hi John,

I have done as requested. I confirm that P3Dv4 controls are NOT Enabled (there are no assignments for the throttle axes within P3Dv4). I have not changed anything that I am aware of since the system worked as intended.

I reloaded my Aerosoft A320 Professional in P3Dv4 from a re-booted computer. The engines were running, so I ran the APU and cut both engines. I then loaded a new flight and restarted the engines on pushback. The engines started perfectly. Hardware throttle movement resulted in correct responses in the FSUIPC5 Calibration window, but NOT to the throttle response or engine instrument parameters in the Virtual Cockpit, i.e. no thrust produced.

Here is the FSUIPC5.ini file:

[General]
UpdatedByVersion=5153
History=HQMZG41IO9WUWD9LAUN8P
InitDelayDevicesToo=No
PMDG737offsets=Auto
PMDG747offsets=Auto
PMDG777offsets=Auto
Annotate=Yes
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
RestoreSimcWindows=No
FixMachSpeedBug=No
AutoScanDevices=Yes
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=Yes
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ZapAirRange=1.50
ZapGroundRange=0.25
ZapCylinderAltDiff=0
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
WideLuaGlobals=Yes
AxesWrongRange=No
TCASid=Flight
TCASrange=40,3
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
ThreadAffinityMask=x0
LuaAffinityMask=x0
InitDelay=0
GetNearestAirports=Yes
LogOptionProtect=Yes
TimeForLuaClosing=2
WeatherReadFactor=2
WeatherRewriteSeconds=1
TrafficStallTime=1
InitialStallTime=10
NormalStallTime=1
LuaRerunDelay=66
ComReadLoopTime=20
ControlsListBuild=32097
Console=No
ConsoleWindowTopMost=No
FSVersionUsed="Lockheed Martin® Prepar3D® v4",4.5.13.32097
SimConnectUsed=4.5.0.0
LogAxes=Yes

[Traffic Limiter]
AirportPreference=50
PlannedAirportsPreference=50
GroundPreference=50
NearerPreference=50
TargetFrameRate=0
TrafficLimit=0

[JoyNames]
AutoAssignLetters=No
0=Saitek Pro Flight Yoke
0.GUID={7A5E0AF0-5428-11EA-8004-444553540000}
1=T.16000M
1.GUID={7A65FA30-5428-11EA-8007-444553540000}
2=Saitek Pro Flight Rudder Pedals
2.GUID={7A6C14B0-5428-11EA-800D-444553540000}
3=Saitek Pro Flight Throttle Quadrant
3.GUID={7A6C14B0-5428-11EA-800E-444553540000}

[JoystickCalibration]
RudderBlendLowest=1
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
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
Aileron=-16384,0,512,16383
Elevator=-16256,0,512,16383
Rudder=-15932,0,0,16383
LeftBrake=-16380,16380/16
SlopeLeftBrake=4
RightBrake=-16380,16380/16
SlopeRightBrake=4
Mixture=-16380,16380
Flaps=0,16380/16
Spoilers=-16380,16380/16
Throttle1=-16384,-512,512,16383/32
Throttle2=-16384,-512,512,16255/32

[Axes]
PollInterval=10
RangeRepeatRate=10

[Buttons]
PollInterval=25
ButtonRepeat=20,10

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

[GPSout]
GPSoutEnabled=No

[GPSout2]
GPSoutEnabled=No

[WideServer]
WideFSenabled=Yes

[Sounds]
Path=C:\Prepar3D\Sound\
Device1=Primary Sound Driver
Device2=Speakers (2- High Definition Audio Device)
Device3=Digital Audio (S/PDIF) (2- High Definition Audio Device)
Device4=Headset Earphone (Microsoft LifeChat LX-3000)
Device5=U28E590 (3- NVIDIA High Definition Audio)

[Profile.A320]
1=Aerosoft A319 professional BRITISH AIRWAYS G-DBCF
2=Aerosoft A320 professional BRITISH AIRWAYS G-EUUU
3=Aerosoft A321 professional BRITISH AIRWAYS G-EUXG

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

[Profile.RealAir C172sp Skyhawk]
1=RealAir Cessna Skyhawk 172SP British Airways Flying Club

[Axes.RealAir C172sp Skyhawk]
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=0U,256,D,6,0,0,0    -{ DIRECT: Mixture }-
4=2X,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
5=2Y,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
6=2R,256,D,3,0,0,0    -{ DIRECT: Rudder }-

[Buttons.RealAir C172sp Skyhawk]
0=R0,32,C65735,0     -{PAN_DOWN}-
1=R0,36,C65734,0     -{PAN_UP}-
2=R0,34,C65672,0     -{PAN_RIGHT}-
3=R0,3,C65615,0     -{ELEV_TRIM_UP}-
4=R0,2,C65607,0     -{ELEV_TRIM_DN}-
5=P0,1,C65791,0     -{AUTOPILOT_OFF}-

[Buttons.A320]
0=R1,32,C65735,0     -{PAN_DOWN}-
1=R1,2,C65615,0     -{ELEV_TRIM_UP}-
2=R1,3,C65607,0     -{ELEV_TRIM_DN}-
4=R1,36,C65734,0     -{PAN_UP}-
5=R1,38,C65671,0     -{PAN_LEFT}-
6=R1,34,C65672,0     -{PAN_RIGHT}-
7=P0,1,C65791,0     -{AUTOPILOT_OFF}-
8=P0,15,C66080,0     -{GEAR_DOWN}-
9=P0,14,C66079,0     -{GEAR_UP}-

[JoystickCalibration.A320]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
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
RudderBlendLowest=1
Aileron=-16384,0,512,16383
Elevator=-16256,0,512,16383
Rudder=-15932,0,0,16383
Mixture=-16380,16380
LeftBrake=-16380,16380/16
SlopeLeftBrake=4
RightBrake=-16380,16380/16
SlopeRightBrake=4
Spoilers=-16380,16380/16
Flaps=0,16380/16
Throttle1=-16384,-512,512,16383/32
Throttle2=-16254,-512,512,16255/32

[Profile.Beech Be58 Baron]
1=Beech Baron 58 BAV Flying Club G-BAVB

[Axes.Beech Be58 Baron]
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,9,0,0,0    -{ DIRECT: Throttle1 }-
3=0U,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
4=0V,256,D,17,0,0,0    -{ DIRECT: PropPitch1 }-
5=2R,256,D,3,0,0,0    -{ DIRECT: Rudder }-
6=3X,256,D,18,0,0,0    -{ DIRECT: PropPitch2 }-
7=3Y,256,D,13,0,0,0    -{ DIRECT: Mixture1 }-
8=3Z,256,D,14,0,0,0    -{ DIRECT: Mixture2 }-

[Buttons.Beech Be58 Baron]
0=R0,32,C65735,0     -{PAN_DOWN}-
1=R0,2,C65607,0     -{ELEV_TRIM_DN}-
2=R0,3,C65615,0     -{ELEV_TRIM_UP}-
3=R0,6,C66278,0     -{RUDDER_TRIM_LEFT}-
4=R0,7,C66279,0     -{RUDDER_TRIM_RIGHT}-
5=R0,36,C65734,0     -{PAN_UP}-
6=R0,34,C65672,0     -{PAN_RIGHT}-
7=R1,38,C65671,0     -{PAN_LEFT}-

Here is the FSUIPC.1.log :

********* FSUIPC5, Version 5.153 (12th December 2019) by Pete & John Dowson *********
Running inside Prepar3D v4
Module base=7FFB58CB0000
Windows 10 Home 64 Bit reported as Build 18363, Release ID: 1909 (OS 10.0)
Prepar3D.exe version = 4.5.13.32097
Reading options from "C:\Prepar3D\Modules\FSUIPC5.ini"
Checking the Registrations now ...
User Name="JohnPettit"
User Addr="xxxxxxx@xxxxxxx"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
       16 System time = 27/02/2020 13:51:31
       16 FLT path = "C:\Users\John\Documents\Prepar3D v4 Files\"
       16 Using DialogMode
       32 FS path = "C:\Prepar3D\"
      110 ---------------------- Joystick Device Scan -----------------------
      110 Product= Saitek Pro Flight Yoke
      110    Manufacturer= Saitek
      110    Vendor=06A3, Product=0BAC (Version 3.4)
      157    GUIDs returned for product: VID_06A3&PID_0BAC:
      157       GUID= {7A5E0AF0-5428-11EA-8004-444553540000}
      157       Details: Btns=23, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U255,V255,X1023,Y1023,Z255
      157 Product= T.16000M
      157    Manufacturer= Thrustmaster
      157    Vendor=044F, Product=B10A (Version 5.0)
      157    GUIDs returned for product: VID_044F&PID_B10A:
      157       GUID= {7A65FA30-5428-11EA-8007-444553540000}
      157       Details: Btns=16, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R255,U0,V0,X16383,Y16383,Z255
      157 Product= Saitek Pro Flight Rudder Pedals
      157    Manufacturer= Saitek
      157    Vendor=06A3, Product=0763 (Version 1.0)
      157    GUIDs returned for product: VID_06A3&PID_0763:
      157       GUID= {7A6C14B0-5428-11EA-800D-444553540000}
      157       Details: Btns=0, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R511,U0,V0,X127,Y127,Z0
      172 Product= Saitek Pro Flight Quadrant
      172    Manufacturer= Saitek
      172    Vendor=06A3, Product=0C2D (Version 2.0)
      172    GUIDs returned for product: VID_06A3&PID_0C2D:
      172       GUID= {7A6C14B0-5428-11EA-800E-444553540000}
      172       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R0,U0,V0,X255,Y255,Z255
      172 -------------------------------------------------------------------
      172 Device acquired for use:
      172    Joystick ID = 0 (Registry okay)
      172    0=Saitek Pro Flight Yoke
      172    0.GUID={7A5E0AF0-5428-11EA-8004-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 1 (Registry okay)
      172    1=T.16000M
      172    1.GUID={7A65FA30-5428-11EA-8007-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 2 (Registry okay)
      172    2=Saitek Pro Flight Rudder Pedals
      172    2.GUID={7A6C14B0-5428-11EA-800D-444553540000}
      172 Device acquired for use:
      172    Joystick ID = 3 (Registry okay)
      172    3=Saitek Pro Flight Throttle Quadrant
      172    3.GUID={7A6C14B0-5428-11EA-800E-444553540000}
      172 -------------------------------------------------------------------
      203 LogOptions=00000000 00000001
      203 -------------------------------------------------------------------
      203 SimConnect_Open succeeded: waiting to check version okay
      203 Opened separate AI Traffic client okay
    13110 Running in "Lockheed Martin® Prepar3D® v4", Version: 4.5.13.32097 (SimConnect: 4.5.0.0)
    13110 Initialising SimConnect data requests now
    13110 FSUIPC Menu entry added
    13110 ... Using Prepar3D with Professional License
    13125 C:\Users\John\AppData\Local\Lockheed Martin\Prepar3D v4\Prepar3D_Default.fxml
    13125 C:\Prepar3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    65516 C:\Users\John\Documents\Aerosoft\Aerosoft A320-A321 Professional\SimObjects\Airplanes\Aerosoft A320 IAE Professional\A320.air
    65532 ### The user object is 'Aerosoft A320 professional BRITISH AIRWAYS G-EUUU'
    65532 ### Mode is NORMAL
    66078 ### Mode: PAUSE on
   130360 Aircraft loaded: running normally now ...
   130469 User Aircraft ID 2 supplied, now being used
   131250 System time = 27/02/2020 13:53:42, Simulator time = 13:51:43 (13:51Z)
   131250 Aircraft="Aerosoft A320 professional BRITISH AIRWAYS G-EUUU"
   152063 Loading Complete ...
   152063 ### Mode is NORMAL
   154188 -------------------- Starting everything now ----------------------
   154250 Exception 25 "ILLEGAL_OPERATION", Ref 735, Index param -1 on read AddData for "CG PERCENT LATERAL"
   154250 Exception 25 "ILLEGAL_OPERATION", Ref 736, Index param -1 on read AddData for "AVIONICS MASTER SWITCH"
   154250 ASN active function link set
   154250 Ready for ActiveSky WX radar with additional data
   154282 Exception 25 "ILLEGAL_OPERATION", Ref 762, Index param -1 on read AddData for "BARBER POLE MACH"
   154282 Exception 25 "ILLEGAL_OPERATION", Ref 763, Index param -1 on read AddData for "FUEL SELECTED TRANSFER MODE"
   154313 Exception 25 "ILLEGAL_OPERATION", Ref 764, Index param -1 on read AddData for "HYDRAULIC SYSTEM INTEGRITY"
   154313 Exception 25 "ILLEGAL_OPERATION", Ref 765, Index param -1 on read AddData for "ATTITUDE CAGE"
   154344 Exception 25 "ILLEGAL_OPERATION", Ref 791, Index param -1 on read AddData for "VELOCITY BODY X"
   154344 Exception 25 "ILLEGAL_OPERATION", Ref 792, Index param -1 on read AddData for "VELOCITY BODY Y"
   154375 Exception 25 "ILLEGAL_OPERATION", Ref 793, Index param -1 on read AddData for "ROTATION VELOCITY BODY X"
   154375 Exception 25 "ILLEGAL_OPERATION", Ref 794, Index param -1 on read AddData for "ROTATION VELOCITY BODY Z"
   154407 Exception 25 "ILLEGAL_OPERATION", Ref 820, Index param -1 on read AddData for "NAV SOUND:1"
   154407 Exception 25 "ILLEGAL_OPERATION", Ref 821, Index param -1 on read AddData for "NAV SOUND:2"
   154438 Exception 25 "ILLEGAL_OPERATION", Ref 822, Index param -1 on read AddData for "ADF SOUND"
   154438 Exception 25 "ILLEGAL_OPERATION", Ref 823, Index param -1 on read AddData for "COM ACTIVE FREQUENCY:2"
   154485 Exception 25 "ILLEGAL_OPERATION", Ref 849, Index param -1 on read AddData for "VELOCITY WORLD Y"
   154485 Exception 25 "ILLEGAL_OPERATION", Ref 850, Index param -1 on read AddData for "STRUCT WORLD ROTATION VELOCITY"
   154516 Exception 25 "ILLEGAL_OPERATION", Ref 851, Index param -1 on read AddData for "ACCELERATION WORLD X"
   154516 Exception 25 "ILLEGAL_OPERATION", Ref 852, Index param -1 on read AddData for "ACCELERATION WORLD Y"
   154547 Exception 25 "ILLEGAL_OPERATION", Ref 878, Index param -1 on read AddData for "CABIN SEATBELTS ALERT SWITCH"
   154547 Exception 25 "ILLEGAL_OPERATION", Ref 879, Index param -1 on read AddData for "HYDRAULIC SWITCH:1"
   154578 Exception 25 "ILLEGAL_OPERATION", Ref 880, Index param -1 on read AddData for "HYDRAULIC SWITCH:2"
   154578 Exception 25 "ILLEGAL_OPERATION", Ref 881, Index param -1 on read AddData for "HYDRAULIC SWITCH:3"
   154610 Exception 25 "ILLEGAL_OPERATION", Ref 907, Index param -1 on read AddData for "GENERAL ENG MAX REACHED RPM:4"
   154610 Exception 25 "ILLEGAL_OPERATION", Ref 908, Index param -1 on read AddData for "ATC MODEL"
   154641 Exception 25 "ILLEGAL_OPERATION", Ref 909, Index param -1 on read AddData for "IS LATITUDE LONGITUDE FREEZE ON"
   154641 Exception 25 "ILLEGAL_OPERATION", Ref 910, Index param -1 on read AddData for "ATTITUDE BARS POSITION"
   154672 Exception 25 "ILLEGAL_OPERATION", Ref 936, Index param -1 on read AddData for "RECIP ENG FUEL AVAILABLE:4"
   154672 Exception 25 "ILLEGAL_OPERATION", Ref 937, Index param -1 on read AddData for "RECIP ENG MANIFOLD PRESSURE:3"
   154703 Exception 25 "ILLEGAL_OPERATION", Ref 938, Index param -1 on read AddData for "RECIP ENG COWL FLAP POSITION:3"
   154703 Exception 25 "ILLEGAL_OPERATION", Ref 939, Index param -1 on read AddData for "RECIP ENG ALTERNATE AIR POSITION:3"
   154735 Exception 25 "ILLEGAL_OPERATION", Ref 965, Index param -1 on read AddData for "RECIP ENG RIGHT MAGNETO:2"
   154735 Exception 25 "ILLEGAL_OPERATION", Ref 966, Index param -1 on read AddData for "RECIP MIXTURE RATIO:2"
   154766 Exception 25 "ILLEGAL_OPERATION", Ref 967, Index param -1 on read AddData for "RECIP ENG BRAKE POWER:2"
   154766 Exception 25 "ILLEGAL_OPERATION", Ref 968, Index param -1 on read AddData for "RECIP CARBURETOR TEMPERATURE:2"
   154797 Exception 25 "ILLEGAL_OPERATION", Ref 994, Index param -1 on read AddData for "RECIP ENG EMERGENCY BOOST ACTIVE:1"
   154797 Exception 25 "ILLEGAL_OPERATION", Ref 995, Index param -1 on read AddData for "RECIP ENG EMERGENCY BOOST ELAPSED TIME:1"
   154828 Exception 25 "ILLEGAL_OPERATION", Ref 996, Index param -1 on read AddData for "RECIP ENG WASTEGATE POSITION:1"
   154828 Exception 25 "ILLEGAL_OPERATION", Ref 997, Index param -1 on read AddData for "RECIP ENG TURBINE INLET TEMPERATURE:1"
   154875 Exception 25 "ILLEGAL_OPERATION", Ref 1023, Index param -1 on read AddData for "GENERAL ENG EXHAUST GAS TEMPERATURE:3"
   154875 Exception 25 "ILLEGAL_OPERATION", Ref 1024, Index param -1 on read AddData for "GENERAL ENG GENERATOR SWITCH:3"
   154907 Exception 25 "ILLEGAL_OPERATION", Ref 1025, Index param -1 on read AddData for "GENERAL ENG GENERATOR ACTIVE:3"
   154907 Exception 25 "ILLEGAL_OPERATION", Ref 1026, Index param -1 on read AddData for "GENERAL ENG DAMAGE PERCENT:3"
   154938 Exception 25 "ILLEGAL_OPERATION", Ref 1052, Index param -1 on read AddData for "GENERAL ENG FUEL PUMP SWITCH:1"
   154938 Exception 25 "ILLEGAL_OPERATION", Ref 1053, Index param -1 on read AddData for "GENERAL ENG MASTER ALTERNATOR:1"
   154969 Exception 25 "ILLEGAL_OPERATION", Ref 1054, Index param -1 on read AddData for "TAILHOOK POSITION"
   154969 Exception 25 "ILLEGAL_OPERATION", Ref 1055, Index param -1 on read AddData for "PARTIAL PANEL ADF"
   155000 Exception 25 "ILLEGAL_OPERATION", Ref 1081, Index param -1 on read AddData for "GPS IS APPROACH ACTIVE"
   155000 Exception 25 "ILLEGAL_OPERATION", Ref 1082, Index param -1 on read AddData for "GPS POSITION LAT"
   155032 Exception 25 "ILLEGAL_OPERATION", Ref 1083, Index param -1 on read AddData for "GPS POSITION LON"
   155032 Exception 25 "ILLEGAL_OPERATION", Ref 1084, Index param -1 on read AddData for "GPS POSITION ALT"
   155063 Exception 25 "ILLEGAL_OPERATION", Ref 1110, Index param -1 on read AddData for "GPS APPROACH IS WP RUNWAY"
   155063 Exception 25 "ILLEGAL_OPERATION", Ref 1111, Index param -1 on read AddData for "GPS COURSE TO STEER"
   155094 Exception 25 "ILLEGAL_OPERATION", Ref 1112, Index param -1 on read AddData for "GPS FLIGHT PLAN WP COUNT"
   155094 Exception 25 "ILLEGAL_OPERATION", Ref 1113, Index param -1 on read AddData for "GPS APPROACH WP COUNT"
   155360 Advanced Weather Interface Enabled
   243500 Sim stopped: average frame rate for last 91 secs = 36.7 fps
   243500    Max AI traffic was 0 aircraft
   243500 -------------------------------------------------------------------
[Log closed by user request, and continued in new file]
   282344 System time = 27/02/2020 13:56:13, Simulator time = 13:53:14 (13:53Z)
   282344 *** FSUIPC log file being closed
Minimum frame rate was 30.5 fps, Maximum was 38.9 fps
Average frame rate for running time of 112 secs = 37.8 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 45 Allocs, 43 Freed
********* FSUIPC Log file closed ***********

And here is a second FSUIPC5.log file (initial part):

********* FSUIPC5, Version 5.153 (12th December 2019) by Pete & John Dowson *********
User Name="JohnPettit"
User Addr="xxxxxxx@xxxxxxxx"
FSUIPC5 Key is provided
WIDEFS7 not user registered, or expired
   282344 System time = 27/02/2020 13:56:13, Simulator time = 13:53:14 (13:53Z)
   282344 FLT path = "C:\Users\John\Documents\Prepar3D v4 Files\"
[Continuation log requested by user]
Running inside Prepar3D v4 on Windows 10
Module base=7FFB58CB0000

   282344 LogOptions changed, now 10000000 00000001
   282422 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -14744 (0xffffc668) AXIS_SPOILER_SET
   282422 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
   282422 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
   282453 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -14744 (0xffffc668) AXIS_SPOILER_SET
   282453 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
   282453 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
   282485 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -14744 (0xffffc668) AXIS_SPOILER_SET
   282485 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
   282485 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
   282485 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -13055 (0xffffcd01) RUDDER_SET
   282485 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
   282485 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
   282516 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -14744 (0xffffc668) AXIS_SPOILER_SET
   282516 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
   282516 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
   282516 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
   282516 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
   282516 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -13354 (0xffffcbd6) RUDDER_SET
   282578 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -14744 (0xffffc668) AXIS_SPOILER_SET
   282578 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
   282578 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
   282578 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
   282578 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
   282578 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= -13503 (0xffffcb41) RUDDER_SET

 

then lots of the same, finishing with:

  4413797 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -16055 (0xffffc149) AXIS_SPOILER_SET
  4413797 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
  4413797 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
  4413813 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
  4413813 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
  4413813 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 0 (0x00000000) RUDDER_SET
  4413860 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -16055 (0xffffc149) AXIS_SPOILER_SET
  4413860 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
  4413860 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
  4413875 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
  4413875 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
  4413875 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 0 (0x00000000) RUDDER_SET
  4413907 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -16055 (0xffffc149) AXIS_SPOILER_SET
  4413907 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
  4413907 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
  4413907 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 0 (0x00000000) RUDDER_SET
  4413907 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
  4413907 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
  4413953 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -16055 (0xffffc149) AXIS_SPOILER_SET
  4413953 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
  4413953 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
  4413953 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 0 (0x00000000) RUDDER_SET
  4413953 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
  4413953 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET
  4414016 ***  AXIS: Cntrl= 65694 (0x0001009e), Param= 0 (0x00000000) ELEVATOR_SET
  4414016 ***  AXIS: Cntrl= 65695 (0x0001009f), Param= 0 (0x00000000) AILERON_SET
  4414016 ***  AXIS: Cntrl= 65696 (0x000100a0), Param= 0 (0x00000000) RUDDER_SET
  4414047 ***  AXIS: Cntrl= 66382 (0x0001034e), Param= -16055 (0xffffc149) AXIS_SPOILER_SET
  4414047 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 16 (0x00000010) THROTTLE1_SET
  4414047 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 16 (0x00000010) THROTTLE2_SET

This last file was 23,000+ in size, so I aslimited by file size for sending. I trust there is enough information contained within what has been sent.

If not, I will break it down into smaller chunks, but a quick inspection indicated it was just repeated information.

Best wishes,

John

 

[John Dowson]

You seem to have your throttle1 assigned to your yoke:

        2=0Z,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-

and have your throttle2 assigned to two different axis on your throttle quadrant:

        8=3X,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
        9=3Y,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

Presumably you want both throttle1 and throttle2 on your throttle quadrant, no? Please try this first.

If you are still having issues after you have resolved this, it may be that the A320/1 throttle axis don't play well with FSUIPC calibration due to priority levels. If this is the case, you could try switching the assignments from 'Send direct to FSUIPC Calibration' to 'Send to FS as normal axis', and use the Axis Throttle<n> Set controls instead.

Note that you can ignore the errors reported in the log file - see this post for a (partial) explanation: 

Let me know how it goes.

John

 

[John Dowson]

Also could you also check your A320 configuration - what 'Throttle Axis count' are you using?

This post shows how to set-up the A320 using a single throttle axis: https://www.avsim.com/forums/topic/561341-aerosoft-airbus-professional-throttle-settings-using-fsuipc/ - but presumably you want to use a separate axis for throttle1 and throttle2, no?

John

 

[John Pettit]

Hi John,

In response toyour first e-mail above:I have deleted/removed that second axis assigment to throttle 2. Now have 1 axis on Saitek Pro Yoke quadrant (right end) assigned to Throttle 1 and the left most axis on the Saitek Throttle Quadrant assigned to Throttle 2. This gives adjacent throttle levers. The middle levers on both lever quadrants are redundant in my set-up.

I tried switching assignments as in the second part of your e-mail, but, no change.

Yes, I wish to have both throttles working independently. I checked theconfigurator and it showed only one axis. I edited it to show two axes, but again, no change - still no throttle functioning.

I did try switching the assignments from 'Send direct to FSUIPC Calibration' to 'Send to FS as normal axis', and use the Axis Throttle<n> Set controls instead: again,no change.

???

John

[John Dowson]

I think you should be ok with 'Send direct to FSUIPC Calibration', so please use that and make sure that you have calibrated both throttle axis in FSUIPC.

Once you've done that, can you re-upload your updated ini and log files, with the Axis controls logging activated (and using 2 axis in the configurator.). Please activate each throttle axis independently (throttle1 then throttle2) for the test.

You can attach them to your post, no need to copy/paste them. Don't start a new log, and you can zip the log up if it is large.

Thanks,

John

[John Pettit]

Hi John,

Have done as requested. To be certain you have all relevant information I have included the complete previous log file in zipped format (the things I am learning to do!).

I am beginning to think the problem lies in the interface between FSUIPC5 and Aerosoft A3xx Professional. When I load any other aircraft model the FSUIPC control assignments all work perfectly.

Regards,

John

FSUIPC5.ini FSUIPC5.log FSUIPC5_previous.zip

[John Pettit]

I have just completed a full uninstall and clean re-install of my Aerosoft A318/A321 Professional Bundle following precisely the instructions on Aerosoft Support website 'pinned' instruction set. The problem remains exactly as before -no change. As you can imagine, this is all incredibly frustrating.

I posted the problem on the Aerosoft Support forum, but no reply as yet.

[John Dowson]

You now have throttle1 assigned to two axis on your yoke (throttle):

[Axes.A320]
RangeRepeatRate=10
0=0Z,256,D,22,0,0,0    -{ DIRECT: Spoilers }-
1=0U,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
2=0V,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-

Please remove one of these assignments.

You also have your flaps assigned to 2 axis, but that is not relevant to your problem.

For your log, did you do as requested, i.e move throttle1 fully forward then back, then the same for throttle2? Your log shows movements on many other axis. Could you repeat please and just use the throttles for the test. The initial throttle1 movement shows it only going as high as 7606 (less than half the full range) before it reduces, and then throttle2 the same, although later I can see higher values for both throttles, which is confusing...

What maximum/minimum values are you seeing for each throttle in the calibration screen?

...later: just rechecked your log, and it tells me that the aircraft you used was the Aircraft="Beech Baron 58 BAV Flying Club G-BAVB"? I thought your problem was with the Aerosoft A320/A321? I am confused....could you remove that duplicate throttle1 assignment and provide the log of the suggested test with the correct aircraft please?

John

P.S. May also be a good idea to set

    AutoAssignLetters=Yes

in your [JoyNames] section. This will prevent problems if/when you  change your USB connections (which can give your devices different numbers).

Edited February 29, 2020 by John Dowson
Further info added

[John Pettit]

HiJ ohn,

Apologies for causing you much grief. Here are the files attached as requested, with full axis movement of those assigned to throttle 1 and throttle 2. Full calibration was checked bforehand - full movement, no erratic responses. All axes checked for duplication and none found (I had spotted the previous duplication and removed it). At each stage I exited Prepar3D and rebooted the computer. Once it had all been checkd I then did the axis check as requested after a reboot and restart of P3D.

For the Yoke Quadrant throttle the maximum value of 16,383 and a minimum of -16,384 was observed.

For the Throttle Quadrant throttle the maximum value of 16,384 and a minimum of -16,254 was observed.

Prior to all this I had removed all axis assigments within Prepar3D and only used FSUIPC5.

After all this there was no thrust response to throttle lever movement

Hopefully this information will now be of use.

With many thanks,

John

 

 

FSUIPC5.log FSUIPC5.ini

[John Pettit]

Hi John,

Some additional information: this morning I started up P3Dv4 from cold and checked the .ini file. This did not show any changes to the GUIDs which still had numeric assignments. I then accessed FSUIPC Options again and re-checked. The Alpha assigments now appeared for all hardware except the T.16000M joystick which still has numeric GUID of 1. The numeric assigments were still listed. I have attached the latest .ini file.

Can I change this by manually editing the .ini file? Should I do so?

In addition I assigned buttons 23 and 7 (the buttons at the rear most travel of the two throttle axes) to the function 'Throttle x Decr Small' to act as thrust reversers. This worked correctly, with reverse thrust being applied to the A320, but which also correctly cancelled the reverse thrust when throttles were moved into forward thrust position.

One thought did occur - might it be worth trying to completely uninstall, then re-install FSUIPC5?

FSUIPC5.ini

[John Dowson]

That last ini looks fine - it has assigned a letter to each of your device (which is now used in your assignments) and contains the joy id numbers as well, which is needed for the mapping to the letters. Not really much point re-installing FSUIPC - its only the dll that gets installed (as well as you documents).

For the test, you moved each throttle independently as asked, no? If so, your logs show throttle1 and throttle2 controls being sent at the same time. You say that you removed all axis assignments in P3D, but these have a tendency to be re-assigned. Can you check again please -  and its better to disable controllers completely if not assigning in P3D, or at least for these tests. Still, not seeing any reasonable values for your throttle movements in FSUIPC though, which is strange. I'll check to see what additional logging we can add to track this down and get back to you.

John

 

[John Pettit]

Hi John,

I confirm each throttle was moved independently. In P3D I did disable all controllers by ensuring box was unticked.

As an observation, when I had assigned the switches to activate reverse thrust the throttle 1 reverse worked as correctly when selected on its own. If I selected throttle 2 to activate reverse thrust on its own, it indicated REV but nothing more. Iit only worked correctly if throttle 1 was also actvated at the same time.

When I go to Axis Calibration in FSUIPC5 I get full independent movement of each thrust lever axis. I will do the test again after a restart to be doubly sure.

John

[John Pettit]

Re the above:

Test repeated - throttle 2 had dropped its assignment, so was re-assigned. A full calibration of each throttle was then done. Full range was indicated and set.

Engines then were both started. Once started each engine throttle was advanced about 1 inch independently to check thrust response. No respones noted. This was repeated observing Virtual Cockpit thrust lever movement. No movement noted.

Here again are the relevant ini and log files.

In great appreciation,

John

FSUIPC5.ini FSUIPC5.zip

[Pete Dowson]

3 minutes ago, John Pettit said:

Here again are the relevant ini and log files.

John asked me to see if I could help, so forgive me if I've missed something.

Unfortunately the Log supplied is a "continuation" log -- you pressed the New Log button for some reason. Without the early part of the log, showing what has been detected and assigned and which aircraft is loaded it is difficult to know what to make of the part you have supplied.

So, were you using the A320 in the Profile called "A320". Is that the only aircraft with which you have problems?

If it was the A320 I'm rather worried and confused by your assignments:

1=AV,256,D,9,0,0,0    -{ DIRECT: Throttle1 }-
8=DX,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
9=DY,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

You have Throttle 1 assign on your Saitek Yoke, and TWO axes assigned to Throttle 2 on your Saitek quadrant. So I'm not at all surprised by what you see happening.

Have you tested your throttles in any other aircraft? I see you have two throttles assigned for the Baron, but oddly both to the Yoke along with the elevator, ailerons and the left prop pitch.

The Aerosoft A320 is, I understand, a fairly sophisticated model, and it may be doing rather different things with some of the axes, like the PMDG Boeings, which read axis values at a higher level so you would need to assign to the regular "Axis Throttle" controls, not "Direct to FSUIPC calibration" as you have done. With PMDG aircraft you really can't calibrate in FSUIPC either because two different values might then be sent on to the sim's engine. The A320 may well be the same.

However, before going down that route, try changing this line in the [JoystickCalibration.A320] section of the INI:

UseAxisControlsForNRZ=No

Change the No to Yes.

Pete

 

 

[John Dowson]

2 hours ago, John Pettit said:

throttle 2 had dropped its assignment, so was re-assigned.

In FSUIPC? Why do you think this? FSUIPC cannot 'drop assignments'. You now again have multiple assignments to your throttle2:

8=DX,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
9=DY,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

Also, did you disable controllers completely in P3D, as advised (in Controls -> Other -> 'enable Controllers' checkbox not checked)?

2 hours ago, John Pettit said:

Once started each engine throttle was advanced about 1 inch independently to check thrust response

As advised, please advance each throttle independently through its FULL range.

The log file attached is also a 'continuation log', i.e. you started a new log file. Please do not do this - I need to see the full log.

...later...and just saw Pete's response...try the change in UseAxisControlsForNRZ after you have finally generated the initial request log file please, i.e.
   - full log file (no continuation)
   - controllers disabled in P3D
   - each throttle axis assigned only once in FSUIPC
   - each throttle moved independently through its full range

Thanks,

John

[John Pettit]

John and Pete,

Regarding the dropped assignment - I don't know what else to call it.

I have just rebooted my computer and started P3D. I loaded the Aerosoft A320 Pro at EGLL stand 521. The following is a step by step description of what I did and what I found:

1. Opened P3D Options>Controls>Other and checked Controllers Enabled box NOT ticked.

2. Opened FSUIPCv5 via ADDONS menu tab.

3. Opened 'Axis Assignments' to Profile A320.

4. Checked both throttle assignments independently with full throttle movement - both OK

5. Shut down P3D

 

Will now go and change UseAxisControlsForNRZ in the ini file. I am assuming you want another test after I have made this change?

We shall not be beaten!

John

 

FSUIPC5.log FSUIPC5.ini

[John Dowson]

But your ini still shows duplicate throttle assignments for throttle2:

8=DX,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-
9=DY,256,D,10,0,0,0    -{ DIRECT: Throttle2 }-

And you also now have an additional custom control defined:
10=DZ,256,F,23,0,0,0    -{ TO SIM: Custom control: <23> }-

Not sure what that one does...

6 minutes ago, John Pettit said:

Will now go and change UseAxisControlsForNRZ in the ini file. I am assuming you want another test after I have made this change?

Yes, after we get a log file produced with only one axis assigned to throttle1 and throttle2! Just delete one of those entries shown above (8 or 9) directly in your ini file (with P3D not loaded). This will remove that axis assignment.

Really your log file is confusing as it is only/mainly showing parameter values of 0 and 16 to your THROTTLEn_SET controls. You could also try changing the throttle assignments for the A320 profile to 'Send to FS as normal axis' (rather than 'Send direct to FSUIPC calibration') and use the Axis Throttle<n> Set controls to see if you are getting throttle axis values through using that.

John

 

[John Pettit]

Well! I think we've solved it!

After doing the test above I entered the ini file, found the appropriate line under UseAxisControlsForNRZ and changed the response to Yes.

I restarted P3D and loade the A320 as before. Checked the throttle assigments were still OK, they were. I then operated each throttle independently and each throttle worked as required.

One small anomaly, though. The reverse actuation on Throttle 2 switch onlyoperates in tandem with Throttle 2 switch. This is actually not a problem as I wouldn't use reverse on single engine operation.

I shall now go flying and report back (briefly!).

An enormous thank-you toyou both - your support has been immense as has your patience. Believe me when I say it's hugely appreciated.

Best wishes,

John

[John Dowson]

Glad its now working for you!

John

[John Pettit]

And to confirm - flight from EGLL to EGPD in Aerosoft A320 Pro: all worked just as programmed.

Again, many, many thanks!