Do those sensitivity settings work just as well for the default Neo’s?
No… If you want the default A320neo or the A32NX development version, you need to use this sensitivity curve:
Hello, I am struggling with this for a couple hours now… I did firmware update and calibration several times (i calibrated also the reverse position) and I STILL cannot get it to work.
I am unable to use reverse thrust. Now the only possibility for me is to fix the reverse locks in up position, so that I can use the full throttle space.
By the way, in vanilla, stable and dev build it works perfectly. Any ide how to get it to work on Custom FBW version?
EDIT:
I got it to work and even better than in the FBW github tutorial. It works PERFECTLY. Here is my config file:
[Throttle]
Log = true
Enabled = true
ReverseOnAxis = true
ReverseIdle = true
DetentDeadZone = 1.2
DetentReverseIdle = -0.90
DetentReverseFull = -1.00
DetentIdle = -0.42
DetentClimb = 0
DetentFlexMct = 0.53
DetentTakeOffGoAround = 1.00
When you use the Custom FBW version, you should have a throttle config.ini file. In your throttleconfig file, you should have these values. Note that the Reverse on Axis is set to true. By default this is set to false, which is why you won’t be able to do reverse thrust if you don’t edit this file first. This should give you a good baseline to start:
[Throttle]
Log = true
Enabled = true
ReverseOnAxis = true
ReverseIdle = true
DetentDeadZone = 2.5
DetentReverseIdle = -0.90
DetentReverseFull = -1.00
DetentIdle = -0.42
DetentClimb = 0.06
DetentFlexMct = 0.53
DetentTakeOffGoAround = 1.00
If you’re using the Custom FBW with Custom AP build that you can get here A32NX cFBW cAP, You should be able to configure your throttle configuration using the EFB FlyPad.
You may want to check out these settings: It works perfectly!
[Throttle]
Log = true
Enabled = true
ReverseOnAxis = true
ReverseIdle = true
DetentDeadZone = 1.2
DetentReverseIdle = -0.90
DetentReverseFull = -1.00
DetentIdle = -0.42
DetentClimb = 0
DetentFlexMct = 0.53
DetentTakeOffGoAround = 1.00
1 Like
I have been using the TCA Quadrant with great success after replacing the Throttleconfiguration.ini with this one:
You will find Throttleconfiguration in the work folder:
(this is obviously not in the Community folder)
Ohh yeah, this is the new one from the installer. I’ve been using the Custom AP and Custom FBW version, where I set up the throttle directly through the EFB flypad, and not using the config ini file anymore.
I tried everything to get the throttle to not iddle on reverse on my TCA quadrant but nothing seems to work… and i am flying on the custom A32NX. not sure what else to do at this point.
got it to work! i had to completely delete my flybywire mode and rebuild the ini file.
This settings work perfect for me!!! Thank you
My throttle quadrant wasn’t working right even after reinstalling A320NX and reconfiguring my ThrottleConfig.ini file, then I read your post and thought to check my sensitivity settings. Sure enough, my L-Axis X and L-Axis Y were no longer linear. Don’t know how that happened, but I changed them back and my throttles are working great again. I had to hit the reset button and jiggle the dead zone a little to get the curves to snap back to linear.
Sadly, you’ll all probably have to do it all again, as it was broken by yesterdays update…
I have had my TQ and Sidestick for a few months now, and up until then everything worked as expected, however, the TQ has become totally unusable as 75% of the time it disconnects, which causes both engines to shut down. Even when I am not flying, 95% of the time I get an error saying incompatible device! I have updated the firmware, software, and have the latest drivers. I have also checked and replaced the cable 3 times, as well as using a different USB socket, but this has done absolutely zero.
I have written to Thrustmaster and I am waiting for their reply.
1 Like
I’ve found the following to work with the new way the FBW is setup via the flypad, just a case of sticking it in the ThrottleConfiguration.ini
[Throttle]
Log = true
Enabled = true
ReverseOnAxis = true
ReverseIdle = true
DetentDeadZone = 1.2
DetentReverseIdle = -0.90
DetentReverseFull = -1.00
DetentIdle = -0.42
DetentClimb = 0
DetentFlexMct = 0.53
DetentTakeOffGoAround = 1.00
[throttle_common]
reverse_on_axis = true
[throttle_axis_1]
reverse_low = -0.560000
reverse_high = -1.000000
reverse_idle_low = -0.550000
reverse_idle_high = -0.550000
idle_low = -0.470000
idle_high = -0.520000
climb_low = -0.020000
climb_high = 0.011000
flex_mct_low = 0.470000
flex_mct_high = 0.520000
toga_low = 1.000000
toga_high = 1.000000
[throttle_axis_2]
reverse_low = -0.560000
reverse_high = -1.000000
reverse_idle_low = -0.550000
reverse_idle_high = -0.550000
idle_low = -0.470000
idle_high = -0.520000
climb_low = -0.020000
climb_high = 0.011000
flex_mct_low = 0.470000
flex_mct_high = 0.520000
toga_low = 1.000000
toga_high = 1.000000Please tell me where to look for the file now ThrottleConfiguration.ini.
There’s a thread for this problem here:
ty twinedsquid5151 worked a treat,ive been struggling with the flypad calibration setting, but now copying and pasteing your settings it worked a treat
Are you connecting your TQ to a USB hub by any chance? I’m asking because the TQ is drawing a lot of power from the USB port. So if you’re connecting it to a USB hub along with other hardware and the USB hub is only connected to a single USB port in your PC. The power may be insufficient for the TQ as the power is split between the other hardware connected to your hub. This can cause regular disconnection as the TQ requires a constant stable power being delivered through the USB connection.
This rarely happens if you connect the TQ directly into your PC without going through a USB hub, or if you have to use a USB hub, make sure it’s an Active and powered USB hub using an external power supply.
Are you using the new experimental or Development version?