29 replies to this topic

[philldant]

I had to reconfigure my profile after getting a second quadrant. I must have done something different this time but can't seem to fix it. In the past when I had the auto throttle engaged I could move my throttle handles to match the N1 levels as set by th A/T. now if I move them the N1 drops as much as I move the throttles. In other words if the A/T is holding at 80% N1 with my levers at the top, if I try to pull back the throttles to match the 80% the N! drops as I move meaning the only time they would be equal is at idle. Ideas???

Thanks

[Pete Dowson]

philldant, on 21 February 2012 - 08:32 PM, said:

I had to reconfigure my profile after getting a second quadrant. I must have done something different this time but can't seem to fix it. In the past when I had the auto throttle engaged I could move my throttle handles to match the N1 levels as set by th A/T. now if I move them the N1 drops as much as I move the throttles. In other words if the A/T is holding at 80% N1 with my levers at the top, if I try to pull back the throttles to match the 80% the N! drops as I move meaning the only time they would be equal is at idle. Ideas???

With default aircraft the throttles should be ignored when the A/T is engaged. What aircraft are you using? It will make a difference. Some use the same controls as your throttles to operate autothrottle, so you'd be interfering.

I assume posting here you imply you are using FSUIPC3 (FS9 or learlier?) or FSUIPC4 (FSX or P3D?), for calibration, or even assignment. But you give precious little information so I really don't know how to advise further.

Regards
Pete

[philldant]

Pete Dowson, on 22 February 2012 - 12:20 AM, said:

With default aircraft the throttles should be ignored when the A/T is engaged. What aircraft are you using? It will make a difference. Some use the same controls as your throttles to operate autothrottle, so you'd be interfering.

I assume posting here you imply you are using FSUIPC3 (FS9 or learlier?) or FSUIPC4 (FSX or P3D?), for calibration, or even assignment. But you give precious little information so I really don't know how to advise further.

Regards
Pete

Sorry Pete, I am using the latest fsuipc with fsx and pmdg. I had everything configured for the 737ngx and the last time I logged in the profile was not working. Probably something I did but don't know what. Anyway I setup the profile again and that is wen I experienced the issue reported. I have the fsx controls disabled and use fsuipc to calibrate the Saitek Yoke, rudders and two quadrants. Sorry to be a pain...

[Pete Dowson]

philldant, on 22 February 2012 - 02:49 AM, said:

I am using the latest fsuipc with fsx and pmdg. I had everything configured for the 737ngx and the last time I logged in the profile was not working. Probably something I did but don't know what. Anyway I setup the profile again and that is wen I experienced the issue reported. I have the fsx controls disabled and use fsuipc to calibrate the Saitek Yoke, rudders and two quadrants. Sorry to be a pain.

So, you must have the throttles assigned in FSUIPC, as well as calibrated? (You don't have to assign in FSUIPC in order to calibrate).

There are lots of threads about difficulties with throttle assignments to suit the PMDG 737NGX. Most seem to lie around having the assignments made to the THROTLESn SET controls instead of the normal FSX controls AXIS THROTTLEn SET controls. If you are wanting reverse zones on the axes there's no choice -- the AXIS_ controls don't offer reverse. Most folks seem to make it all work by setting the No Reverse Zone option on the 4 throttles page, and the "UseAxisControlsForNRZ=Yes" option in the INI. Then either put the reversers on the buttons which get pressed when pulling the throttle levers right back, or assigning separate reverser levers.

Regards
Pete

[cjibbotson]

I had the same issue a few months ago with the NGX not ignoring any movement of the Saitek throttle quadrant levers when Autothrottle was engaged.  With Petes kind help I still couldnt get it to work correctly as I would have liked.  Tried so many different options, having throttle assigned to axis in FSX or controllers disabled in FSX and assigned via FSUIPC.  The ONLY way I could prevent the thrust changing in the NGX was to make sure the throttles were NOT calibrated in FSUIPC, not ideal but meant I could move the physical control lever to match the N1 display in the sim without any sudden change of power.

Chris Ibbotson

[Pete Dowson]

cjibbotson, on 27 February 2012 - 01:14 PM, said:

I had the same issue a few months ago with the NGX not ignoring any movement of the Saitek throttle quadrant levers when Autothrottle was engaged.  With Petes kind help I still couldnt get it to work correctly as I would have liked.  Tried so many different options, having throttle assigned to axis in FSX or controllers disabled in FSX and assigned via FSUIPC.  The ONLY way I could prevent the thrust changing in the NGX was to make sure the throttles were NOT calibrated in FSUIPC, not ideal but meant I could move the physical control lever to match the N1 display in the sim without any sudden change of power.

Everyone else seemed to solve that as I described, by using the "UseAxisControlsForNRZ=Yes" option in the INI file and checking the "No Reverse Zone" option in FSUIPC's calibration page. That simply forces FSUIPC to use the exact same controls as FSX.

There is no reverse zone available in the regular FSX axis controls, which is why FSUIPC normally calibrates using the THROTTLESn_SET controls, which do have a reverse zone. There's no other way to get a reverse zone on an axis. Of course if you have enough throttle levers you can assign separate reversers, which gets over the problem -- otherwise reverse would have to be handled by button assignment.

Regards
Pete

[cjibbotson]

I never assign a reverse zone to the throttles as I use the button assignment which is activated on the Saitek Quad when you move the throttle to idle then push it down to engage the button.  Ticking the NRZ and checking the ini file too failed to help, every time I tried to set calibration in FSUIPC the Autothrottle wouldn't work correctly.  The thrust would change when you moved the lever and often disconnect.  I would have liked 2 axis assigned for throttle 1 and 2 but this required the axis to have their calibration sync'd.

[Pete Dowson]

cjibbotson, on 27 February 2012 - 02:38 PM, said:

I never assign a reverse zone to the throttles as I use the button assignment which is activated on the Saitek Quad when you move the throttle to idle then push it down to engage the button.  Ticking the NRZ and checking the ini file too failed to help, every time I tried to set calibration in FSUIPC the Autothrottle wouldn't work correctly.  The thrust would change when you moved the lever and often disconnect.

Something was certainly set wrong, then, because if that INI file parameter is correct and the NRZ option selected, FSUIPC is sending the same controls, exactly, as assigning in FS itself would. I know a lot of NGX users are using FSUIPC fully without any problems at all.

Quote

I would have liked 2 axis assigned for throttle 1 and 2 but this required the axis to have their calibration sync'd.

Er, why does using two separate throttles need calibration syncing? I never have my two throttles synced. It is quite realistic for the actual positions to be slightly different.  And if for some reason you do want them lined up perfectly you can do that easily enough using FSUIPC's sync pos facilities.

Regards
Pete

[cjibbotson]

I checked and doubled checked all the settings when we previously went through this, removed all assignments in FSX, uninstalled FSUIPC, reinstalled it and setup all axis and buttons again, setting two axis on the throttle quadrant to Throttle 1 and Throttle 2 and they would work fine in any aircraft, moving one lever increases the props or thrust on that particular engine.  I appreciate there can be a bit of difference in the calibration but in the NGX I'm seeing between 5-10% of a difference when the levers are set physically side by side.  I've tried differrent levers and I also have two quadrants so tried 2 levers assigned on the 2nd quadrant, also tried 1 lever on one and 1 on the other but the same issue happens.  They've been unplugged and replugged, used different USB slots etc etc but the result is the exact same, perhaps faulty Saitek units I'm not sure, they are well outside their warranty though they matched % a lot closer in other aircraft.  You have a function built into your module to allievate this sync issue which I have tried many times in the past.  It created 2 major issues, the range of one of the throttles (throttle 2 I think) was reduced so moving the lever all the way to idle resulted in the throttle in the NGX only moving back to about 50-40% but the main problem was as previously mentioned, moving the throttle lever would cause the autothrottle to be overwriten and the thrust would change when it shouldnt, it would then disconnect the AT.  The OP has the same issue as myself and no variant in configuring the controls would work, either assigned only in FSX or assigned in FSUIPC *IF* I enabled any form of throttle calibration in your module.  I'll try it quickly again now as I've just downloaded 4.8 but if it doesnt work I'm just going to have to continue with using a single throttle axis

[Pete Dowson]

cjibbotson, on 27 February 2012 - 11:31 PM, said:

I checked and doubled checked all the settings when we previously went through this, removed all assignments in FSX, uninstalled FSUIPC, reinstalled it and setup all axis and buttons again, setting two axis on the throttle quadrant to Throttle 1 and Throttle 2 and they would work fine in any aircraft, moving one lever increases the props or thrust on that particular engine.  I appreciate there can be a bit of difference in the calibration but in the NGX I'm seeing between 5-10% of a difference when the levers are set physically side by side.

The sync pos facilities in FSUIPC calibration could deal with such discrepancies easy enough. You can choose a number of positions to make the equate and FSUIPC will interpolate between. It effectively creates a specific curved calibration grapg instead of using the plain linear method.

Quote

You have a function built into your module to allievate this sync issue which I have tried many times in the past.  It created 2 major issues, the range of one of the throttles (throttle 2 I think) was reduced so moving the lever all the way to idle resulted in the throttle in the NGX only moving back to about 50-40%

That doesn't sound anything like the sync pos facility. With the latter you simply create many positions which are to give equal input numbers and it fills in the parts between accordingly. You can certainly create enough positions to give very smooth reaults over the whole range. I  don't know what you were using to make such a mess, but it wouldn't have been that.

Quote

... but the main problem was as previously mentioned, moving the throttle lever would cause the autothrottle to be overwriten and the thrust would change when it shouldnt, it would then disconnect the AT.

If using the same throttle controls as FSX assignment uses causes an autothrottle problem ,then there's certainly a bug or design deficiency in the aircraft modelling.

Quote

The OP has the same issue as myself and no variant in configuring the controls would work, either assigned only in FSX or assigned in FSUIPC *IF* I enabled any form of throttle calibration in your module.  I'll try it quickly again now as I've just downloaded 4.8 but if it doesnt work I'm just going to have to continue with using a single throttle axis

You've confused me now. How does using a single throttle axis solve anything, apart perhaps from your sunc?

Pete

[dts]

I have just set up my saitek throttle quad, flying the PMDG NGX i had the problem where unless i fully opened the throttle after hitting toga then i would get an in balance in the engines on takeoff.

I have calibrated 2 seperate axis for each engine, with no reverse zone and also adjusted the ini file with  "UseAxisControlsForNRZ=Yes" and now have no issue with the throttles.  I also have a seperate axis for reverser set up.

This problem has been bugging me litterally since the NGX came out,  this post has sorted this problem out.

[Pete Dowson]

dts, on 28 February 2012 - 12:01 AM, said:

I have calibrated 2 seperate axis for each engine, with no reverse zone and also adjusted the ini file with  "UseAxisControlsForNRZ=Yes" and now have no issue with the throttles.  I also have a seperate axis for reverser set up.

Yes, this is a good solution and many others use it

Quote

This problem has been bugging me litterally since the NGX came out,  this post has sorted this problem out.

Good.

Regards
Pete

[cjibbotson]

Pete Dowson, on 27 February 2012 - 11:42 PM, said:

The sync pos facilities in FSUIPC calibration could deal with such discrepancies easy enough. You can choose a number of positions to make the equate and FSUIPC will interpolate between. It effectively creates a specific curved calibration grapg instead of using the plain linear method.

That doesn't sound anything like the sync pos facility. With the latter you simply create many positions which are to give equal input numbers and it fills in the parts between accordingly. You can certainly create enough positions to give very smooth reaults over the whole range. I  don't know what you were using to make such a mess, but it wouldn't have been that.


Apologies Pete my posts are made from work and I don't have access to FSX but what you describe above is what I'm using to sync the engines, I had in the past set perhaps a minimum of 5 positions from idle to full throttle, advancing both axis to the same position and pressing the sync button.  I am not using any other utility for the controls, either to assign them or control any form of calibration.  The autothrottle issue ONLY rears its ugly head once I set calibration for the throttles, either on page one of the calibration page if a single throttle axis is used or on the other page which has multi engine calibration.

If using the same throttle controls as FSX assignment uses causes an autothrottle problem ,then there's certainly a bug or design deficiency in the aircraft modelling.

As my original posts mentioned a few months ago it didn't matter if I assigned by throttle axis via FSX or via FSUIPC the problem came up if any of the throttles were calibrated within FSUIPC.  Perhaps there is a bug with PMDG as I think they do say not to use any form of calibration.  There is also an issue which causes their main PMDG_737NGX.dll to crash, many users, including myself could only resolve this crash if they set all their controls via FSUIPC and disabled the controllers in FSX.

You've confused me now. How does using a single throttle axis solve anything, apart perhaps from your sunc?

If I have a single axis then they don't need sync'd so I dont use FSUIPC's calibration, as soon as I turn on calibration for one, two axis etc the AT fails to work as it should.



I'm not at home until tomorrow evening but have in the past followed your advice and DTS's comments above "I have calibrated 2 separate axis, one for each engine, with no reverse zone and also adjusted the ini file with 'UseAxisControlsForNRZ=Yes' and it still didnt work.  I'll treble check it tomorrow and if the problem persists I will just have to live with it.

Pete

[cjibbotson]

Sorry my last post didn't post properly with your quotes highlighted separately so hope you can work out my replies

Chris Ibbotson

[Pete Dowson]

cjibbotson, on 28 February 2012 - 12:13 PM, said:

... what you describe above is what I'm using to sync the engines, I had in the past set perhaps a minimum of 5 positions from idle to full throttle, advancing both axis to the same position and pressing the sync button.

In that case I don't understand how you got this result: "the range of one of the throttles (throttle 2 I think) was reduced so moving the lever all the way to idle resulted in the throttle in the NGX only moving back to about 50-40%". That makes no sense when all the sync pos does is match positions, equating different input values for the two axes to the same output values, then calibrating between.

If that simple mechanism is going wrong I need to know, so you shouldn't really keep it a secret. Please show me the resulting calibration sections from the INI, and if possible do a bit of logging -- log Axis events whilst moving the levers, together, slowly from full back to full forward.

Quote

The autothrottle issue ONLY rears its ugly head once I set calibration for the throttles, either on page one of the calibration page if a single throttle axis is used or on the other page which has multi engine calibration.

Odd that no one else gets such a problem. And especially with the page 1 single throttle, which doesn't change the FS control used at all even if you don't change thje INI setting. That's just a straight-forward adjustment ofg the axis values as they pass through FSUIPC.

Quote

As my original posts mentioned a few months ago it didn't matter if I assigned by throttle axis via FSX or via FSUIPC the problem came up if any of the throttles were calibrated within FSUIPC.

I understood you said that all along. Not sure why you are repeating it here. I simply do not understand why your setyup uniquely has an autothrottle cutout problem with FSUIPC using standard FSX controls when no one else seems to.

Quote

Perhaps there is a bug with PMDG as I think they do say not to use any form of calibration.

But all calibration is doing is massaging the axis values en route. It isn't changing anything else.

Regards
Pete

[cjibbotson]

Hi Pete,  I apologise for repeating things, I guess I'm just a little frustrated that your good advice, in my case, doesn't appear to be working.  The issue I described with throttle 2 not going back to idle was something I experienced a few months ago quite a few times despite recalibrating and trying the sync options.  I'll backup my modules folder and reinstall a fresh copy of FSUIPC, will set just the 2 throttle axis and test it in the NGX.  Do I need to enable logging in FSUIPC?  I'll get back to you later as I appreciate it not making sense when it works for others who have experienced the same thing but got your fix to work.  Ps your work on the G3D.dll was a God send and I've not had a CTD with that dll since so thanks Pete

Chris Ibbotson

[Pete Dowson]

cjibbotson, on 29 February 2012 - 09:51 PM, said:

I'll backup my modules folder and reinstall a fresh copy of FSUIPC

All your settings are in the INI file. Reinstalling FSUIPC won't do anything, unless you take the opportunity to update. If you want to start afresh with settings, just rename the INI file.

Quote

Do I need to enable logging in FSUIPC?

Well we can do some logging but just logging everything without knowing precisely what we are doing will just generate heaps of data with no way of analysing it. I need to know more about what the problem really is first, and that includes showing the INI file section with the sync pos settings which you said didn't work and stopped one axis going to idle (as I asked earlier).

Regards
Pete

[cjibbotson]

Ok here's a few ini files in various states of setup

1. axis set up for aileron, elevator, rudder, spoiler, flaps and throttle1 and throttle 2 (all assigned via FSUIPC with FSX controllers disabled - throttles left uncalibrated - result is NGX autothrottle system works as it should, in cruise with MCP Speed moving the Saitek throttles just shows a blue arc on the N1 but the throttles remain set

[General]
UpdatedByVersion=4800
History=3VQ6IHTWU1066YCW6PI3O
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=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=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=No
UseProfiles=Yes
EnableMouseLook=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
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
Console=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0
[JoyNames]
AutoAssignLetters=No
0=Logitech Formula Force EX USB
0.GUID={F421FC40-1933-11E1-8002-444553540000}
1=Saitek Pro Flight Throttle Quadrant
1.GUID={3E7194E0-5430-11E1-8002-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={3E926350-5430-11E1-8003-444553540000}
[Buttons]
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=D:\Microsoft Flight Simulator X\Sound\
Device1=Primary Sound Driver
Device2=Speakers (SoundMAX Integrated Digital HD Audio)
Device3=Digital Output (SoundMAX Integrated Digital HD Audio)
Device4=Speakers (Apowersoft_AudioDevice)
Device5=SPDIF Interface (SoundMAX Integrated Digital HD Audio)
[Axes]
0=0S,256,D,3,0,0,0
1=1X,256,D,22,0,0,0
2=1Y,256,D,9,0,0,0
3=1Z,256,D,10,0,0,0
4=2X,256,D,1,0,0,0
5=2Y,256,D,2,0,0,0
6=2U,256,D,23,0,0,0
[JoystickCalibration]
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,0,16383
Elevator=-16384,0,0,16320
Rudder=-16380,-512,512,16380/16
Spoilers=-16256,16253/16
Flaps=-16384,16383/16

2. As above - throttles 1 and 2 on 4 throttle page now calibrated - result is NGX autothrottle system fails, in cruise with MCP Speed moving the Saitek throttles just shows a white arc on the N1 and throttles increase or reduce according to the movement of the levers then return to their autothrottle percent, if I move a single lever the AT disconnects, this is even when setting NEVER in PMDGs options for Autothrottle Manual Override.  Ive also ticked in FSUIPC the No Reverse Zone though  I think I manually had to change UseAxisControlsForNRZ= to Yes

[General]
UpdatedByVersion=4800
History=3VQ6IHTWU1066YCW6PI3O
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=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=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=No
UseProfiles=Yes
EnableMouseLook=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
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
Console=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0
[JoyNames]
AutoAssignLetters=No
0=Logitech Formula Force EX USB
0.GUID={F421FC40-1933-11E1-8002-444553540000}
1=Saitek Pro Flight Throttle Quadrant
1.GUID={3E7194E0-5430-11E1-8002-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={3E926350-5430-11E1-8003-444553540000}
[Buttons]
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=D:\Microsoft Flight Simulator X\Sound\
Device1=Primary Sound Driver
Device2=Speakers (SoundMAX Integrated Digital HD Audio)
Device3=Digital Output (SoundMAX Integrated Digital HD Audio)
Device4=Speakers (Apowersoft_AudioDevice)
Device5=SPDIF Interface (SoundMAX Integrated Digital HD Audio)
[Axes]
0=0S,256,D,3,0,0,0
1=1X,256,D,22,0,0,0
2=1Y,256,D,9,0,0,0
3=1Z,256,D,10,0,0,0
4=2X,256,D,1,0,0,0
5=2Y,256,D,2,0,0,0
6=2U,256,D,23,0,0,0
[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=Yes
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,0,16383
Elevator=-16384,0,0,16320
Rudder=-16380,-512,512,16380/16
Spoilers=-16256,16253/16
Flaps=-16384,16383/16
Throttle1=-16384,-512,512,16383/32
Throttle2=-16384,-512,512,16128/32

3. Finally with throttles 1 and 2 calibrated and sync'd with about 5 positions, moving both levers at the same time a fraction of their full range, letting go of them and pressing the Sync button.  I think I manually had to change UseAxisControlsForNRZ= to Yes.  The Autothrottle now works almost as it should but throttle2 will only return to 50% when I move the Saitek lever to idle, its like that axis still thinks theres a reverse zone!!
I hope this info helps Pete

Chris Ibbotson

[General]
UpdatedByVersion=4800
History=1JG795HMVPKSWO2MWF8TA
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=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=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=No
UseProfiles=Yes
EnableMouseLook=No
AxesWrongRange=No
TCASid=Flight
TCASrange=40
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
Console=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0
[JoyNames]
AutoAssignLetters=No
0=Logitech Formula Force EX USB
0.GUID={F421FC40-1933-11E1-8002-444553540000}
1=Saitek Pro Flight Throttle Quadrant
1.GUID={3E7194E0-5430-11E1-8002-444553540000}
2=Saitek Pro Flight Yoke
2.GUID={3E926350-5430-11E1-8003-444553540000}
[Buttons]
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=D:\Microsoft Flight Simulator X\Sound\
Device1=Primary Sound Driver
Device2=Speakers (SoundMAX Integrated Digital HD Audio)
Device3=Digital Output (SoundMAX Integrated Digital HD Audio)
Device4=Speakers (Apowersoft_AudioDevice)
Device5=SPDIF Interface (SoundMAX Integrated Digital HD Audio)
[Axes]
0=0S,256,D,3,0,0,0
1=1X,256,D,22,0,0,0
2=1Y,256,D,9,0,0,0
3=1Z,256,D,10,0,0,0
4=2X,256,D,1,0,0,0
5=2Y,256,D,2,0,0,0
6=2U,256,D,23,0,0,0
[JoystickCalibration]
AllowSuppressForPFCquad=Yes
ExcludeThrottleSet=Yes
ExcludeMixtureSet=Yes
ExcludePropPitchSet=Yes
SepRevsJetsOnly=No
ApplyHeloTrim=No
UseAxisControlsForNRZ=Yes
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,0,16383
Elevator=-16384,0,0,16320
Rudder=-16380,-512,512,16380/16
Spoilers=-16256,16253/16
Flaps=-16384,16383/16
Throttle1=-16384,-512,512,16383/32
Throttle2=-16384,-512,512,16128/32
SyncSlopeThrottle2=26/26,37/32,53/48,68/65,92/91,109/110,127/128

[cjibbotson]

Meant to add Pete when No Reverse Zone is ticked I get the following

Throttle 1
(Idle) In -16253 Out -16252 (Max) In 16383  Out 16384

Throttle 2
(Idle) In -16384 Out -4096****** (Max) In 16256 Out 16224

I think the -4096 is the culprit to throttle 2 only returning to 50% on manual thrust despite the lever being returned to idle

[Pete Dowson]

cjibbotson, on 29 February 2012 - 11:57 PM, said:

I think I manually had to change UseAxisControlsForNRZ= to Yes

I don't think it is there normally, so you would have had to add it.

Instead of assigning the throttles "direct to FSUIPC calibration", please assign them to the FS controls, "axis throttle1 set" and "axis throttle2 set". The 'direct to calibration' method bypasses FS and I think the PMDG needs to see them. I hadn't realised you were doing that.

Quote

Meant to add Pete when No Reverse Zone is ticked I get the following
Throttle 1
(Idle) In -16253 Out -16252 (Max) In 16383 Out 16384
Throttle 2
(Idle) In -16384 Out -4096****** (Max) In 16256 Out 16224

Is that with the "sync pos" method of calibration, because you only mentioned 40-50% business in that context I think?

I'll check the numbers here in any case.

Regards
Pete