Jump to content

Thrust Levers-No Joy


OgMan

Recommended Posts

Greetings:

I have been struggling for two full days to work out a thrust lever dilemma. In use the CH Throttle Quadrant and I read the Vol. 7 Thrust Lever Setup manual and have tried a few times to set the levers with FSX parameters and also with FSUIPC using both of the suggested methods.

With the TQ in FSX mode, the Airbus thrust levers move but unless I have the TQ controls pushed up to 60% thrust or more they kick into reverse.

With the FSUIPC solution, I downloaded the 2 lua files and put them in my FSX Modules folder but they do not show up as choices in the FSUIPC dropdown menu (all I have are Axis_Throttle_1 and _2.

I think I have disabled FSUIPC control of the TQ by deleting the assignment in the axis tab as that is the only method of which I am aware.

I am running out of ideas and a little frustrated so I thought that by posting here, even as vague as the problem is, I could see if anyone else has been struggling and swearing as much as I...Misery does love company but a brilliant suggestion to help solve the problem would be even better.

Link to comment
Share on other sites

Misery does love company but a brilliant suggestion to help solve the problem would be even better.

Luv this part you wrote - well written

I had a ton of problems also - hope they are over what I found was when I pushed the throttle to assign it it said axis 5 - I didnt pay attention to what it assigned - after looking at the documentation again it should say axis Z , not sure if this is your problem just throwing it out there - I never use fsuipc as you need a master degree to use that program

Link to comment
Share on other sites

That axis problem is not the same as mine sad to say.

A question for the Aerosoft staff though...

I was doing a search for possible fixes today and came across a thread by Mathijas from April 28,2011 providing a fix for Airbus X throttle problems as well as one from Shaun Fletcher from January 12, 2013 (aerosoft.zendesk.com/entries/22924406-A) . Might that information be relevant to the A318/A319? (I apologize that I do not have the topic ID for the first referenced fix).

Link to comment
Share on other sites

Hmm that sounds familiar but checking my airbus 320/321 files - I dont have anything file wise to fix this as I save any needed patches - have to keep thinking - did you set your sensitivity and null settings to the recommended settings in the manual ?

Not sure about this but - I had many problems with the airbus throttles with my saitek throttles so I did a fresh install of P3D and no fsiupc and it works perfectly - I did not load fsiupc - I know that sounds crazy but its working for me - i usually load fsiupc right after my sim installs - I may be on to something - for now I am not installing it as I think only pmdg needs it

Link to comment
Share on other sites

Oh another thing never put a controller into a usb hub can cause lots of problems - been there done that

Your ailerons elevator and throttle axis should be sensitivity all the way to the right and null all the way to the left on the slider settings only using fsx menu system - I would get fsiupc uninstalled completely to rule that out

Link to comment
Share on other sites

Yes, sensitivities are full and null zone is minimal.

As far as the USB hub- just before all this drama the flight controls were recognized by windows7 and FSX but did not respond to any inputs. I plugged the hub into a different port and they once again were responsive, however, when I checked them in the Windows Devices it shows 3 unspecified HD-compliant game controllers in the devices section (which checking their properties confirms they are the yoke, TQ and pedals) and in an Unspecified section 2 entries for CH Control Manager Root Device and the three individual entries for Yoke, TQ, and Pedals. So the controls are showing up twice-which was not the case a few days ago.

I have been using the hub for quite awhile and am not sure I would even have enough USB ports to plug in the controllers individually...but if you think it could make a difference I will try and move some stuff around.

Link to comment
Share on other sites

Yes, sensitivities are full and null zone is minimal.

As far as the USB hub- just before all this drama the flight controls were recognized by windows7 and FSX but did not respond to any inputs. I plugged the hub into a different port and they once again were responsive, however, when I checked them in the Windows Devices it shows 3 unspecified HD-compliant game controllers in the devices section (which checking their properties confirms they are the yoke, TQ and pedals) and in an Unspecified section 2 entries for CH Control Manager Root Device and the three individual entries for Yoke, TQ, and Pedals. So the controls are showing up twice-which was not the case a few days ago.

I have been using the hub for quite awhile and am not sure I would even have enough USB ports to plug in the controllers individually...but if you think it could make a difference I will try and move some stuff around.

Had a feeling you were using a hub might be the problem just trying to eliminate some things - you can put something else in the hub but not a throttle it will cause problems and hopefully it works out for you

Link to comment
Share on other sites

  • Aerosoft

That axis problem is not the same as mine sad to say.

A question for the Aerosoft staff though...

I was doing a search for possible fixes today and came across a thread by Mathijas from April 28,2011 providing a fix for Airbus X throttle problems as well as one from Shaun Fletcher from January 12, 2013 (aerosoft.zendesk.com/entries/22924406-A) . Might that information be relevant to the A318/A319? (I apologize that I do not have the topic ID for the first referenced fix).

Yes it is the same code used.

Link to comment
Share on other sites

Here is my input on the same problem. I have CH Quadrant, CH Pedals and a Microsoft Side winder joystick. All these were connected to a 4 Port USB hub together with the keyboard. I also use FSUIPC and calibrate all controls through it with the exception of the throttles. This used to work fine with the Aerosoft A320. However when I installed the A318 A319 it was a nightmare. When I thought that all was fine and calibrated it soon turned up most of the times that I loose all controls. So back to square one, first I changed the throttles to a Saitek V1 but no joy. Then when I thought that all was fine lost controls of the pedals, after that it was the turn of the throttles. I did not put a post in the forum as nobody was experiencing this and concluded that the problem was within my set up. Patiently and after days of trial and error I have found where I think my problem was, I removed the keyboard usb from the same hub shared by the throttles and placed it directly to the PC .

I am saying this because for the past three days I have been enjoying flying the new A 319 with all controls in place and it is really a joy and keep hoping that my problems are solved.

These are the steps that I take for calibrating the Throttles:

In the FSX Settings-Controls tick the enable controller.

Go to Advanced and put the Sensitivity Engine 1 and 2 Axis to extreme right and to extreme left for Null Zone again for both engines.

Go to Calibration and calibrate.

Go to Control Axes and put assignments for Engine 1 throttle axis to Z axis and Engine 2 throttle axis to Y axis (on the CH Quadrant)

In the FSUIPC go to Axis Assignment, tick Send to FS as normal axis and choose Axis Throttle 1 Set, then go to Joystick calibration and ensure that this shows Axis not processed. Repeat for throttle 2 choosing Axis Throttle 2 Set.

Restart as otherwise the settings won't come effective.

Note. Ensure that in the configurator you choose 2 in the Throttles axis count

So far this setup is working fine and Hope this will be of help.

Leslie

Link to comment
Share on other sites

Og is this issue resolved ?

I have not had the opportunity to try different settings. I should be able to within the next couple of days and I will report back.

Thank you.

Link to comment
Share on other sites

Making some progress. I removed the controllers from the hub and they are operational (although I still have the situation that I have always had when I start FSX the controls are not recognized. I have to unplug them and replug...which was simpler to do with the hub but now requires 3 unplugs and replugs) meaning I can obtain takeoff thrust but I am not yet able to throttle back to Lever Climb.

I think this may be a calibration issue and I will be working on that today.

Link to comment
Share on other sites

Making some progress. I removed the controllers from the hub and they are operational (although I still have the situation that I have always had when I start FSX the controls are not recognized. I have to unplug them and replug...which was simpler to do with the hub but now requires 3 unplugs and replugs) meaning I can obtain takeoff thrust but I am not yet able to throttle back to Lever Climb.

I think this may be a calibration issue and I will be working on that today.

"when I start FSX the controls are not recognized. I have to unplug them and replug."

That may be some new motherboard bio updates - or a new usb driver from you motherboard manufacturer look into that - may not be your sim - sounds like a windows issue - look there - at least your getting somewhere

Link to comment
Share on other sites

  • Aerosoft

"when I start FSX the controls are not recognized. I have to unplug them and replug."

That may be some new motherboard bio updates - or a new usb driver from you motherboard manufacturer look into that - may not be your sim - sounds like a windows issue - look there - at least your getting somewhere

Or cheap USB hub...

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use