Another Throttle Problem

[Dougal 2]

I finally got out the plastic and bought this tonight, I first had the throttle issues already discussed.

At first, I had no throttle movement at all. After following the instructions in the other 'solved' thread, the throttles now move indipentantly.

However, when TOGA is applied, the thrust only reaches 'climb', and is stated as such on the ND as 'LVR CLB'.

Is this something I'm doing wrong, or is there still a throttle issue?

I have English FSX with registered FSUIPC

This is what I currently have:

[Common]

Logging=0

NullZone=0

[FlightControls]

Enable=1

[FADEC]

//AxesCount=1

//InvertAxes=1

//Event1=AXIS_THROTTLE_SET

AxesCount=2

Event1=AXIS_THROTTLE1_SET

Event2=AXIS_THROTTLE2_SET

[KyleD 1027]

Hi Phil,

When you put your thrust levers in the TOGA detent, the EICAS in the upper right should say "TOGA", and on the PFD, in column 1 row 2 you should see "LVR CLB", which is advising you to reduce the levers to the climb detent- that is completely normal. There are no ND indications for thrust, so you may have got your terms mixed. If anything, please include a screenshot for further help and understanding.

[Kostap 19]

Kyle,

that is normal when one has reached acceleration altitude - but I got this on setting takeoff thrust - it said MAN TOGA and below THR CLB at the same time while still on the ground. I think though that this might happen if you have not done the FMC setup (PERF especially). With a properly configured INIT and PERF this thing did not happen.

So Phil, check if that solves your issue - it did for me.

Kosta

[Dougal 2]

Yes, I'm getting this on the ground, but as advised, it's PROBABLY because because I'm sill a complete **** with this FMC ;-)

If I understand you correctly then, if I just firewall the throttles (manually) before PROPERLY setting up the FMC, I can then expect to see 'LVR CLB' in top left of ND?

Thanks

[Dougal 2]

Just seen I've got another problem... The throttles on the A320 are now working perfectly, BUT not on the 321 model!

I have them both in the same FSUIPC profile as below:

[Profile.Airbus Ext]

1=Airbus A320

2=Airbus A321

[Axes.Airbus Ext]

0=0X,256,D,7,0,0,0

1=0Y,256,D,8,0,0,0

2=0Z,256,D,3,36,0,0

3=1X,256,D,1,0,0,0

4=1Y,256,D,2,0,0,0

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

6=1U,256,F,66423,0,0,0

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

[JoystickCalibration.Airbus Ext]

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,16320

Elevator=-16384,0,0,16383

Rudder=-16253,512,512,16383

LeftBrake=-15232,16384/24

SlopeLeftBrake=15

RightBrake=15360,16384/24

Spoilers=-16383,16384/16

[Joshua Che. 1601]

Just seen I've got another problem... The throttles on the A320 are now working perfectly, BUT not on the 321 model!

I have them both in the same FSUIPC profile as below:

[Profile.Airbus Ext]

1=Airbus A320

2=Airbus A321

[Axes.Airbus Ext]

0=0X,256,D,7,0,0,0

1=0Y,256,D,8,0,0,0

2=0Z,256,D,3,36,0,0

3=1X,256,D,1,0,0,0

4=1Y,256,D,2,0,0,0

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

6=1U,256,F,66423,0,0,0

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

[JoystickCalibration.Airbus Ext]

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,16320

Elevator=-16384,0,0,16383

Rudder=-16253,512,512,16383

LeftBrake=-15232,16384/24

SlopeLeftBrake=15

RightBrake=15360,16384/24

Spoilers=-16383,16384/16

Hi,

Have you done this?

Now go into the \Flightsimulator X\ mainfolder, find the \Modules\ folder and find the FSUIPC4.ini file and open it with notepad.

Find this line:

ShortAircraftNameOk=

and ensure it reads:

ShortAircraftNameOk=Yes

[Dougal 2]

I have indeed yes. It's the first thing I do when installing FSUIPC as I have VERY many aircraft and profiles.

[Dougal 2]

Without doubt, this IS a great looking addon that also has great potential, but I wish all this had been sorted prior to release:-(

[WillClark 0]

Dougal, have you tried to remove the

[FADEC]

//AxesCount=1

removing forward slashes here // InvertAxes=1

//Event1=AXIS_THROTTLE_SET

Should look like the below…

[FADEC]

//AxesCount=1

InvertAxes=1

//Event1=AXIS_THROTTLE_SET

[WillClark 0]

Can anyone tell me why I can not hit enter to start a new paragraph...? Its like the enter key doesn't work in here....

[Dougal 2]

Hi Will

Any changes I make there, stop the throttles working on the 320, so i'm then left with nothing;-)

[Dougal 2]

Grrrr...... this is SOOOOO frustrating

I don't think an addon of this caliber and in this price range should have these problems.

[Leslie 2]

I am getting the same problems with the throttle like Douglas. I have tried what with FSUIPC4.ini and Fadec as suggested but no success. I have removed the CH Quadrant and using the keyboard but both PFD and Engine Warning Display show Climb and pressing F3 or F4 the throttle remains around 25.7 on both engines. Any suggestions.

Leslie

[Dougal 2]

I am getting the same problems with the throttle like Douglas. I have tried what with FSUIPC4.ini and Fadec as suggested but no success. I have removed the CH Quadrant and using the keyboard but both PFD and Engine Warning Display show Climb and pressing F3 or F4 the throttle remains around 25.7 on both engines. Any suggestions.

Leslie

Looks like we've had it for now Leslie. Seems like the support guys have either had enough head scratching, or they've gone home for the day;-) Pity they don't operate like Flight1. I'm sure you know what I mean;-)

[Joshua Che. 1601]

I am getting the same problems with the throttle like Douglas. I have tried what with FSUIPC4.ini and Fadec as suggested but no success. I have removed the CH Quadrant and using the keyboard but both PFD and Engine Warning Display show Climb and pressing F3 or F4 the throttle remains around 25.7 on both engines. Any suggestions.

Leslie

Hi,

We do not support keyboard throttling even if its via FSUIPC.

[Joshua Che. 1601]

Looks like we've had it for now Leslie. Seems like the support guys have either had enough head scratching, or they've gone home for the day;-) Pity they don't operate like Flight1. I'm sure you know what I mean;-)

Hi,

sames goes if you are using keyboard for throttling. If you are not though, reset the calibration of your FSUIPC and re calibrate.

[WillClark 0]

I am sure they tried resetting... I know how you feel. I am running Win 8 and saitek Cessna series controls. Took me almost 3 hours to get them to work.

I cleared everything in FSUIPC and followed the direction in making the changes. Nothing worked for me until I made changes to FADEC.... Sorry I couldn't help. I hope you all get that sorted out....

[Kostap 19]

Dougal,

I checked my FSUIPC setup and it works fine for A320 as well as A321. But different to your setup I did not use Profiles but the suggested approach of using the short names [xxx.Airbus A32]. You may have an issue with FSUIPC here - I do not think that this is an AirbusX related problem.

Cheers

Kosta

[Dougal 2]

Thanks Kosta. Even so, They're more than a little lacking in the 'help' department. I thought this was a 'support forum', but sadly alas, it seems it's actually a 'user to user' forum.

[Joshua Che. 1601]

Thanks Kosta. Even so, They're more than a little lacking in the 'help' department. I thought this was a 'support forum', but sadly alas, it seems it's actually a 'user to user' forum.

Frankly,

We dont support FSUIPC at all. But due to overwhelming number of users we provide limited support on FSUIPC. Bear in mind that I myself don't use FSUIPC so sorry if I cant help you much.

[Dougal 2]

I don't really think there's a need for sarcasm. You know full well I wasn't referring to FSUIPC, which is not, in my opinion where the problem lay. If you're not willing help to get my AEROSOFT product working, then so be it.

[Jarkko 39]

Hello,

If only possible, can you please post 4 screenshots of the problem while it's happening:

1) PFD so we can see what modes are active

2) E/WD to see what the engines are doing

3) FSUIPC axis tab with throttle axis moved.

4) FSUIPC calibration tab with throttle info showing

These would help alot!

Thanks!

[Dougal 2]

I see a 'T.O. INHIBIT' is showing. Is that be the cause of only reaching 86% N1? Why would it be present if it can be over ridden by F4 though?

I don't see anything here though that could possibly cause the 320 to be okay, but have locked throttles on the 321 :-(

[Patrick1246 353]

http://forum.aerosoft.com/index.php?/topic/59749-to-inhibit-showing-at-take-off/

[Dougal 2]

http://forum.aerosof...ng-at-take-off/

That's funny.... I just came back to say I'd found that post, only to miss your by 1 minute;-)

I can JUST manage without the 321 model for now, but with a max N1 of 86%, it's hard getting out of some places for sure.