Would sincerely like to chat in depth about throttle operation, particularly calibration and Idle Detent/Reverser issues. At wit’s end. Had it solved many months ago but previous solution doesn’t work anymore.
Sincerely willing to even pay for assistance at this point.
Thank you.
Ok what I did to get this working was create an empty Spad.Next profile and try various online snippets and eventually I found an uploaded profile that solved all the problems. I then copied and pasted the throttle 1 & 2 configs into my own profile and everything has been working since.
If you go into the Spad.Next online snippets and search for complete device profiles for Bravo with Fenix in search box not too many show up
The profile that worked for me was
id 10630 uploaded 26/02/2024 author schlegld (5 stars)
If that doesn’t work try the Spad.Next discord channel for help. I raised an issue I had recently with them and I got very good support .
I will check this snippet out for sure. My concern is that the idle detent position flipping instantly into reverse is somehow internal to MSFS and Fenix.
For some reason, without calibration idle is fine, but other detents are slightly off. But as soon as I calibrate, suddenly idle detent doesn’t work and goes straight to reverse thrust without any changes to SPAD.
As soon as I enabled the throttle axis in MSFS, the problem disappeared. I don’t want to have to switch in MSFS when I change planes if I can at all avoid it, given how good SPAD is with everything else.
I appreciate the reply though and will keep digging! I’ll get back to you with results from the snippet you posted.
I have been in contact with Fenix support and discovered the core issue.
The Calibration XML file for the Fenix itself may not record a zero value being transmitted by the controller as zero. The fix (as it stands at the time of this post) is to navigate to the Calibration XML file at C:\ProgramData\Fenix\FenixSim A320\calibration.xml
Then edit the first 3 lines of each calibration setting (representing Max Rev/Idle Rev/Idle detents reading from top down) to exactly 0. Save the XML then start the Fenix again.
At this point the throttle will no longer jump below the Idle detent when the physical Bravo throttle axis is at the idle position.
I have advised the Fenix team of my dissatisfaction with this system logic and settings and am hoping they will work to resolve this issue in a future build.