Jump to content
The simFlight Network Forums
Daniel Baker

A330 Aerosoft Professional Reverse Thrust

Recommended Posts

  •  
  • Daniel Baker
  • members
  • member_new.png.99b82ab860293ea8af00702fe
  • 0
  • 27 posts

Hi,

 

I'm having issues getting the reverse thrust to engage properly on the Aerosoft A330 Professional.

 

Using Aerosoft A330 Professional version 1.0.0.8

P3D 4.5 HF2

Windows 10.0.17763 Home

Saitek Flight Yoke & Throttle + 2nd Saitek Throttle Quadrant, CH Rudders

 

I've tried setting up the throttle both suggested ways;

1) Using standard P3D assignments

2) Using FSUIPC assignments and using F2 for reverse

 

In each case the throttles work fine, but reverse thrust is hesitant to engage, and when it finally does, will not stay locked (ie; holding F2 engages reverse, but it wobbles back and forth within the reverse thrust range - like something is pulling it back to idle)


I've asked in Aerosoft forum for help, and they are convinced that that nothing is wrong with their programming and that the most likely candidate is FSUIPC.  Even though I've removed my FSUIPC.ini file and let it rebuild (so no assignments), and enabled the controllers through P3D, I am told it is likely FSUIPC that is the most likely candidate (sorry, I think that's what they're telling me, even though I don't understand how that could be...)  I may have misunderstood (here's the thread)

 

One thing: the Saitek drivers do not have a calibration option as such, only the attached.

 

I've attached my FSUIPC.ini file.  Please let me know if I can supply anything else...

 

Appreciate any help,

 

Daniel

FSUIPC5.ini

Share this post


Link to post
Share on other sites

Hi,

first please update to latest FSUIPC5154, as you are using an old not supported version (5151).

FSUIPC does only do things you ask for. If you run it with a fresh INI file it doesn't interfere. When you have used only standard P3D assignments and you had the same problem then there is of course already nothing to blame FSUIPC.

When using FSUIPC for axis then Saitek software should not run at all !

When running with FSUIPC5154 and short session with activating the reverser, please activate Axis logging and copy and paste the FSUIPC5.log file content unaltered as it is. Session has to be fully closed to do so.

Thomas

Share this post


Link to post
Share on other sites
8 hours ago, Daniel Baker said:

In each case the throttles work fine, but reverse thrust is hesitant to engage, and when it finally does, will not stay locked (ie; holding F2 engages reverse, but it wobbles back and forth within the reverse thrust range - like something is pulling it back to idle)

That sounds like your throttle lever is jittering, sending different values to the Sim all the time. If you calibrated in the Sim, try setting a null zone. Same if you use FSUIPC. 

And don't assign axes in both FSUIPC and P3D. If you use FSUIPC for assignments ensure controllers are actually disabled in P3D. Otherwise you will get conflicts.

I think also that the Aerosoft A320 is a bit like the PMDG Boeings and has its own way of doing things with axis inputs. If you assign in FSUIPC don't assign "direct to calibration", but to the FS controls "Axis throttle ...". It might not like you calibrating in FSUIPC either.

8 hours ago, Daniel Baker said:

I've asked in Aerosoft forum for help, and they are convinced that that nothing is wrong with their programming and that the most likely candidate is FSUIPC.  Even though I've removed my FSUIPC.ini file and let it rebuild (so no assignments), and enabled the controllers through P3D, I am told it is likely FSUIPC that is the most likely candidate

Well, that's patent nonsense. But we are used to it -- FSUIPC always gets the blame, it's their easy way of not bothering to help properly.

Pete

 

Share this post


Link to post
Share on other sites

Hello gentlemen,

Thanks for your help!

5 hours ago, Thomas Richter said:

first please update to latest FSUIPC5154, as you are using an old not supported version (5151).

Done!  Thanks for pointing this out.

 

5 hours ago, Thomas Richter said:

When running with FSUIPC5154 and short session with activating the reverser, please activate Axis logging and copy and paste the FSUIPC5.log file content unaltered as it is. Session has to be fully closed to do so.

Attached.

 

5 hours ago, Pete Dowson said:

And don't assign axes in both FSUIPC and P3D. If you use FSUIPC for assignments ensure controllers are actually disabled in P3D. Otherwise you will get conflicts.

Yes, I should have been more clear about that, sorry: I made sure I had either a) FSUIPC bindings, or b) P3D bindings - never both at the same time.  When I went to enable controllers and assign bindings in P3D, I first removed the FSUIPC.ini file from the modules directory in order to let it build a new clean one.

 

5 hours ago, Pete Dowson said:

That sounds like your throttle lever is jittering, sending different values to the Sim all the time. If you calibrated in the Sim, try setting a null zone. Same if you use FSUIPC. 

That's precisely what I was thinking (they are old, and Saitek was kind of cheaply made) so I tries to calibrate.  

However, the Saitek drivers don't have a "calibrate" function anywhere that I can find: under setting up USB Game Controllers and selecting my Saitek Flight Yoke + Throttle, or my extra Throttle Quadrant (giving me six levers in total, for 4 throttles + spoilers + flaps) There is only a Test and a Deadzones tab, no Settings tab (with a Calibrate button) like I do with my Logitech Attack 3 (which I use to emulate the Airbus sidestick) and my CH Pro Pedals.

I get around this lack of calibration by using FSUIPC Joystick Calibration, which works for all my other aircraft.  When using the Aerosoft Pro and assigning Axis Throttle 1 Set from "Send to FS as a normal axis" - which works.  However, the minute I try to calibrate through FSUIPC Calibration the Aerosoft Pro the throttle stops responding - which is what you're alluding to when you say "It might not like you calibrating in FSUIPC either", of course.

When I then (again after removing the FSUIPC.ini file, so that no FSUIPC Aerosoft bindings exist) and "enable controllers" in P3Dv4.5, I also set a very heathy null zone.

Either way, I get the exact same behaviour.  I've even set up Deadzones in the Saitek driver screen, moving them past the "jittery" zone (which I can see as a tiny fluctuating zone) but it still doesn't work.  I'm not sure what options I have left to calibrate further?

 

To be clear about all of this: The Saitek does not have a "Reverse Zone", as such: there is a zone below the throttle range that when you slide the throttle into activates a button, which I assign to reverse (throttle decrease options in either FSUIPC or P3D - again, never at the same time)

 

Sorry for the epic-length post.  And again many thanks for your help...

Daniel

FSUIPC5.1.log

Share this post


Link to post
Share on other sites

Hi,

Quote

 I've even set up Deadzones in the Saitek driver screen, moving them past the "jittery" zone (which I can see as a tiny fluctuating zone) but it still doesn't work.  I'm not sure what options I have left to calibrate further?

As I said, make sure you deactivate or better uninstall the Saitek driver as the Saitek driver might send a modified axis value.

Thomas

Share this post


Link to post
Share on other sites
19 minutes ago, Thomas Richter said:

Hi,

As I said, make sure you deactivate or better uninstall the Saitek driver as the Saitek driver might send a modified axis value.

Thomas

To be honest, I've had a hell of a time with Saitek drivers and their way-too-complicated driver process.  

I'm not sure how best to approach this?  How do I deactivate them?

 

Thanks,

Daniel

Share this post


Link to post
Share on other sites
7 hours ago, Daniel Baker said:

To be clear about all of this: The Saitek does not have a "Reverse Zone", as such: there is a zone below the throttle range that when you slide the throttle into activates a button, which I assign to reverse (throttle decrease options in either FSUIPC or P3D - again, never at the same time)

Yes. As far as i know that's how most Saitek users do it.

Looking at the log both Thrttle1 and Throttle2 seem to be rapidly alternating between two values:

   279610 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 0 (0x00000000) THROTTLE1_SET
   279610 ***  AXIS: Cntrl= 65820 (0x0001011c), Param= 701 (0x000002bd) THROTTLE1_SET

   279563 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 0 (0x00000000) THROTTLE2_SET
   279563 ***  AXIS: Cntrl= 65821 (0x0001011d), Param= 701 (0x000002bd) THROTTLE2_SET


Are you assigning in FSUIPC to those controls, or to Axis Throttle1 Set and Axis Throttle2 Set? If not the latter change over.

But first, before loading P3D,  in the [JoyStickCalibration...] section for your A320 in the INI file, change this:

UseAxisControlsForNRZ=No

to

UseAxisControlsForNRZ=Yes

then re-calibrate in FSUIPC with a dead zone at idle (minimum).

However, if the A320 really doesn't like doing a reverse setting even with FSUIPC not doing anything, then I don't think anything in FSUIPC will help.

Pete

 

 

  • Like 1

Share this post


Link to post
Share on other sites

Hi Pete,

 

I'm assigning to Throttle1 Set and Throttle2 Set.

 

I've done as you say and it's suddenly working properly - at least with the aircraft parked and engines off.  I'll have to find some time this week to try it in flight.

Eventually I'm going to have to ditch these cheap Saitek controllers - they're just too old and unsupported now.

 

Many thanks again for your help,

Daniel

Share this post


Link to post
Share on other sites

Hi guys,

 

Looks like I have this working now - many thanks.

I'm not sure, but I think the issue is that the Airbus Pro throttle system/programming is extremely sensitive to noise of any kind whatsoever, and will not easily allow for any kind external recalibration/optimization.  My throttle are a bit old so they're noisy, but that hasn't been an issue because I can use FSUIPC to mitigate that extremely effectively.

Also, Saitek drivers are odd and strangely configured.  I had to edit the registry to recalibrate, using these tools: https://support.logi.com/hc/en-gb/articles/360023194074

 

Between that and the advice from Pete above it all seems to work now.

 

Again, thanks for your help, and I hope this helps someone in the future with similar issues.

Daniel

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy 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.