Jump to content
The simFlight Network Forums

ATR 72 Throttle Calibration?


AndyCYXU

Recommended Posts

Anyone got this working? I tried using THROTTLE1_AXIS_SET_EX1 but it's all messed up in the sim once calibrating in the aircraft. Mainly the throttle will not go down to IDLE but sits somewhere around F1 - 40 % range :(

 

Other then THROTTLE1_AXIS_SET_EX1 don't seem to be recognized by the aircraft, btw it works good in Fenix but not in the ATR

I would rather not use MSFS joystick assignment but will if there is no other way.

 

Thanks

Link to comment
Share on other sites

I calibrated it in old windows calibration tool and it helped a bit still not perfect acting like it cannot read the pot on one side, but it works fine as POT is read very clearly in PMDG, so not a bad POT

 

open to more ideas if anyone had similar problem, i am using jetmax throttle so not much use out of usual tutorials out there

 

Link to comment
Share on other sites

ok so it seems to be FSUPIC problem I figured out i can choose IGNORE AXES, but it does not seem to work if I shut down FSUIPC completely then it can manage the throttle for this aircraft from within MSFS but as soon as I turn FSUPIC on they are all messed up as if the IGNORE AXES does not seem to work very well

Do not really need to shut down FSUPIC just use the disconnect feature

I use a profile for this ser up as there are few buttons I'd like to use

I make that easy !

HOW CAN I STILL USE FSUIPC FOR MY OTHER PROGRAMS BUT HAVE IT NOT MESS WITH MY THROTTLE AT ALL.

Because as soon as I start FSUIPC it messes up the whole throttle even though I have it to ignore every axle of it.

wish I had an issue with 30 seconds splash screen 

Link to comment
Share on other sites

Good morning
for a hotas warthog, when the hotas throttle is on idle, the throttles on the atr are on reverse to counter this, i.e. when the throttle is on idle and also on the atr, this is what I did.
2=CZ,256,F,67110,0,0,0,*1,+8192 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
3=CR,256,F,67103,0,0,0,*1,+8192 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-

and for the reverse I have them configured on a button
0=RC,6,K113,8 -{Key press: F2}-
1=RC,7,K112,8 -{Key press: F1}-

  • Like 1
Link to comment
Share on other sites

ok thanks for that, I will try to play with these numbers although I am not sure their meaning but I will read up on them see what i can find out, these are mine when the throttle is configured

3=AV,256,F,67110,0,0,0    -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
4=AS,256,F,67103,0,0,0    -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-

and this is my throttle range of motion, there is no reverse so when I am in ATR my throttle on idle (-16xxx) "ATR reads it as 0" in the ATR aircraft it show as if throttle was at around 40%..

Throttle1=-16300,-512,-225,16383/32
Throttle2=-16384,-512,512,16135/32

so what do you think should i add there ??  although that is me just blindly putting some #s in w/o any understanding :D

Quote

3=AV,256,F,67110,0,0,0,*1,+16383    -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-

 

I managed to get the Reversers just like you with button assignments different key perhaps but same idea this works OK

 

ALSO  to mention I removed the FSUIPC.key files so I basically run the FSUIPC as in unregistered and that allowed me to actually use both MSFS and FSUIPC for other stuff, where FSUIPC was not messing with my throttle axis, NOT an ideal solution, but will do for now, hopefully will get it worked out.

Link to comment
Share on other sites

Good evening

for information on *1,+8192 see FSUIPC7 for Advanced Users page 41 here Additional parameters to scale input axis values

for this
3=AV,256,F,67110,0,0,0 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
4=AS,256,F,67103,0,0,0 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-
to try
3=AV,256,F,67110,0,0,0,*1,+8192 -{ TO SIM: THROTTLE2_AXIS_SET_EX1 }-
4=AS,256,F,67103,0,0,0,*1,+8192 -{ TO SIM: THROTTLE1_AXIS_SET_EX1 }-

,*1,+8192 must be added manually
if not working correctly instead of *1,+8192 try *0.9,+8192 or 0.8 or 0.7 until working correctly

Link to comment
Share on other sites

unfortunately none of this seem to be working for me at all, I am pretty sure that I am doing it right, but it seems to have no effect on the axis travel in ATR or in its calibration EFB. I tried different values even all kinds of combinations restarting FSUIPC to no effect at all.

 

Link to comment
Share on other sites

Since it is hard to explain in writing this is what happens:

If I run unregistered copy of FSUIPC I can then set it up fine via MSFS and run FSUIPC for other programs that use it, but cannot run registered FSUIPC as it starts to mess with my axis right away even if they are set on ignore in fsuipc.

I added the log and ini files if it might help any.

at the beginning I say "Calibrator reads -1600", it actually reads -16000, well 16xxx just mis spoke here

FSUIPC7.log FSUIPC7.ini

Link to comment
Share on other sites

Good morning
I don't want to talk nonsense, but it seems to me that you don't have throttle axes set in the fsuipc.ini file at least not as I had mentioned
3=FWD,256,D,10,0,0,0 -{ DIRECT: Throttle2 }-
4=AS,256,D,9,0,0,0 -{ DIRECT: Throttle1 }-

[Axis]
PollInterval=10
RangeRepeatRate=10
0=AR,256,D,23,0,0,0 -{ DIRECT: Flaps }-
1=AU,256,D,22,0,0,0 -{ DIRECT: Spoilers }-
2=AU,B,-8128,-6554,66066,0,66067,0 -{ DIRECT: SpoilersEntering=SPOILERS_ARM_ON, Leaving=SPOILERS_ARM_OFF }-
3=FWD,256,D,10,0,0,0 -{ DIRECT: Throttle2 }-
4=AS,256,D,9,0,0,0 -{ DIRECT: Throttle1 }-
the axes should not be set on the EFB but in fsuipc, let's say that's what I did otherwise john will have to look at this for more help

Link to comment
Share on other sites

I will try one more time, thank you for the time making this video..

1. I do have registered FSUIPC, of course I do :)

2. I do not have a profiles folder ? not sure why, I do have profiles, if you look at my FSUIPC.ini they are listed at the bottom of it, why I do not have profile folder beats me.

image.thumb.png.7b4b4e8614b3cf31761b5db14931f555.png

You are correct in this particular one I do not have the *1,+8192 written there it is just one of many and in the end I just left it at that, but I did do it with this option added.

3, I will try again I will delete the calibration that ATR made in its directory and only use FSUIPC, I though you were suppose to use it like that, that is what I have done in fenix for example, first i calibrate everything in FSUIPC, then I got it calibrated in Fenix's FMC, but maybe this ATR's calibration EFB is broken or something. (probably is)

Thank you for making the video, I give it a shot again. :)

 

 

Link to comment
Share on other sites

Good evening
in your fsuipc.ini in general at the line UseProfiles=Yes you must change the Yes to files and the profile folder will create this look at the beginning of my video, look carefully at the steps I do in the video, at some point I create a new ATR profile. the profiles you have in your fsuipc.ini file are automatically created. I prefer to create a separate file for each aircraft, maybe also make a video with all the steps you do on fsuipc.
and i don't understand why you did this.

ALSO to mention I removed the FSUIPC.key files so I basically run the FSUIPC as in unregistered and that allowed me to actually use both MSFS and FSUIPC for other stuff, where FSUIPC was not messing with my throttle axis, NOT an ideal solution, but will do for now, hopefully will get it worked out.

Link to comment
Share on other sites

6 hours ago, target11 said:

and i don't understand why you did this.

ALSO to mention I removed the FSUIPC.key files so I basically run the FSUIPC as in unregistered and that allowed me to actually use both MSFS and FSUIPC for other stuff, where FSUIPC was not messing with my throttle axis, NOT an ideal solution, but will do for now, hopefully will get it worked out.

After fighting with FSUPIUC  I was able to configure the axis using MSFS controls menus. However as soon I started FSUIPC even though I had the axes set as ignore they were not actually ignored and FSUIPC was messing everything up. So by "deleting" FSUIPC.key file I was able to use unregistered like version of FSUIPC which did not mess with my hardware yet was sending required info to other software that still depends on it, like Self Loading Cargo for example.

 

 

ANYWAYS I finally got it working so thank you very much for your help.

1. First of all I changed as you suggested UseProfiles=Yes -->  UseProfiles=Files and now I have folders just like you, also changed/added these two ShortAircraftNameOk=No UseAirLocForProfiles=Yes which helps as now every single 737/Airbus/ATR is right away assigned the specific profile and I don't have to set it for every single livery which was vary cumbersome. 

2. I deleted the ATR72 config file so it doesn't mess stuff more just in case. NEEDS TO STAY DELETED USING IT WILL SCREW THINGS UP AGAIN !!!

3. What actually fixed it was this setting I found buried in this manual. 

image.png.d56438ac64793683c19794b08e9cc1d3.png

UseAxisControlsForNRZ=Yes

I noticed that the ATR EFT was only reading 16384-0 also my FSUIPC calibration was reading -16384 to 16384 in IN reading but OUT said 16384 to 0 ... after reading I saw that is what was happening, changing this option helped.

Right after that my throttle was behaving just like yours on your video then I added *1, +8192 to the definition and it works good. I was going to then use the ATR's EFB to config the detents/notches but no, messed it up all over had to delete the calibration file in ATR directory and cannot use this thing with FSUIPC.

I do notice that it slightly limited the travel range there of the throttle when I go to the top but that's fine I can live with that. All in all moves as it should.

 

I will leave it here just in case someone ever runs into this problem too.

Thank you Target11 now I go try to get the flaps configured LMAO

PS I still don't understand why FSUIPC was screwing with my throttles after I specifically say "ignore axis" to the point I have to put it in "unregistered" mode as explained above, maybe not using the profiles in a way I will use them now might have something to do with it, not sure but I got it working good now so I leave it at that.

 

 

 

 

Link to comment
Share on other sites

Sorry I am a bit late to this one... Looks like you have solved your issue thanks to @target11 so I won' t read this in detail, but there are a few points you should be aware of:

1. The change UseProfiles=Yes -->  UseProfiles=Files  just makes FSUIPC use separate files for profiles. Without this. you can still use profiles (unless you set this option to No) - there is no change in the profile functionality. The Profile folder is only created once this option is set to Files.

2. 

7 hours ago, AndyCYXU said:

I still don't understand why FSUIPC was screwing with my throttles after I specifically say "ignore axis" to the point I have to put it in "unregistered" mode as explained above, maybe not using the profiles in a way I will use them now might have something to do with it, not sure but I got it working good now so I leave it at that.

The Ignore axis button is just used in the assignments panel, it has no affect when the axis panel isn't open. If you don't have a profile  for an aircraft, the general [Axis] section will be used. Also, be aware that if you, for example, create a profile-specific [Axes.xxx] section for an aircraft, but not a profile specific [JoystickCalibration.xxx] section, then the general [JoystickCalibration] section will be used. So, if you want to assign an axes for a specific aircraft in MSFS rather than in FSUIPC, not only do you nee to create an empty profile-specific Axes section, but you should also create a profile-specific calibration section and remove/reset the calibration for each axes assigned elsewhere. If you don't do this, FSUIPC will still calibrate the axes assigned elswhere.

3. 

7 hours ago, AndyCYXU said:

UseAxisControlsForNRZ=Yes

I noticed that the ATR EFT was only reading 16384-0 also my FSUIPC calibration was reading -16384 to 16384 in IN reading but OUT said 16384 to 0 ... after reading I saw that is what was happening, changing this option helped.

I am surprised that you need to set this option. I haven't looked at the ATR yet (I will do later), but you shouldn't really need to change this option if assigned to the correct axes control and with the No Reverse Zone option checked/unchecked as appropriate for yout throttle and aircraft. I will take a look at this in the ATR later.

John

  • Like 1
Link to comment
Share on other sites

12 hours ago, John Dowson said:

I am surprised that you need to set this option. I haven't looked at the ATR yet (I will do later), but you shouldn't really need to change this option if assigned to the correct axes control and with the No Reverse Zone option checked/unchecked as appropriate for yout throttle and aircraft. I will take a look at this in the ATR later.

yes do look at it later if you can, but only after doing this UseAxisControlsForNRZ=Yes were my throttles behaving properly in ATR, in both cases (with ot without this option) I had to tick the "no reverse", but without it they moved like on the video I posted. ATR would not move throttles when POT read below 0 value, and 0 value was near the top of green line on the throttle quadrant (approx 50% or so).

I use this option ONLY in ATR profile specific INI not in general one. Then I had to use this *1, +8192 and it working fine however "(and that is why I am coming back to it) best way to explain it is...

imagine physicals distance travel of my throttle axis from beginning to end is 10cm, now with this *1, +8192 the last 2cm are not recognized by ATR, everything is recognized from 0-8cm, but by the time i reach the 8th cm of travel I am already at full throttle in ATR and the last 2cm are just me moving it but even the EFB says 16384 is reached by the 8th cm, without this the entire 10cm of travel is registered and EFB reads it right from -16384 to +16384, but using the EFB to calibrate (like I do in FBW or Fenix) messes it up, I think its the way the dev programed the axes there... anyways, in the end I got it worked out, it is not very accurate however and fine adjustments are not working very good.

Certainly nothing wrong with my throttle POT as it work flawlessly in all other aircraft

Lastly YES i did end up using Per Profile even for Calibration and using this option UseProfiles=Files makes everything more clear and orderly as well so I like it very much.

ADDED I wanted to add AGAIN :) that NOT using FSUIPC, throttle calibration via MSFS and ATR's EFB work with no issues what so ever with my throttle and ATR, but as I said i need to use FSUIPC for other programs and even for other hardware that I have, so maybe if you can see what could cause such strange behavior of FSUPIC and ATR would be great and could improve.

Thanks

Link to comment
Share on other sites

21 hours ago, John Dowson said:

So, if you want to assign an axes for a specific aircraft in MSFS rather than in FSUIPC, not only do you nee to create an empty profile-specific Axes section, but you should also create a profile-specific calibration section and remove/reset the calibration for each axes assigned elsewhere. If you don't do this, FSUIPC will still calibrate the axes assigned elsewhere.

I will try that with the other ATR42 as to not mess up the one i did so far ATR72, but it might be a way to go then.

SOLVED

Tried it tonight with 42 and it worked very well made the changes to 72 also both work good and FSUIPC is not messing with the axis and can still use FSUIPC for other hardware. Seems to work better when calibrated via MSFS and ATR's EFB so I will leave it at that,, tried to remove the NRZ option but it comes bask.. but whatever doesn't matter big thing was the "per profile" axis calibration then all was good. Only now I have to change in MSFS profile for my throttle when using ATR but that is fine.

 

image.thumb.png.9d9e5248c3da19aac41469dc6cb09855.png

Link to comment
Share on other sites

16 hours ago, AndyCYXU said:

tried to remove the NRZ option but it comes bask..

If editing the calibration options, either do this when FSUIPC7 is not running, or have the axes assignments panel open on the calibration tab and click the "Reload all settings" button after saving your changes.

I didn't realise the ATRs were a payware add-on...I don't have this add-on so unfortunately cannot provide any further assistance in how to configure the throttles in FSUIPC7 for these aircraft.

John

  • Like 1
Link to comment
Share on other sites

Good morning
however, setting the axes on fsuipc is very easy and user friendly, I'm far from an expert, but setting the axes with the ATR efb is anything but user friendly and setting the axes with msfs and the efb is an achievement

but if you have a notch throttle like the Thrustmaster Airbus Throttle or other I understand the principle of configuring with msfs2020 and the efb of the atr

 

Link to comment
Share on other sites

The OP seemed to have issues setting this up in FSUIPC and so is using MSFS. He has a JetMAX 737 Throttle - not knowing this throttle (or having the aircraft) it is difficult for me to advise on what the issue was, but if he is happy with configuring the throttle in MSFS then I am not going to spend any time looking into this.

However, I see the ATR bundle is on sale (for just over 12euros), so I'll probably buy this and take a look later in the week, and see how to configure with the throttles I have (Honeycomb Bravo and a Saitek X-55).

Thanks for your help with this.

John

Link to comment
Share on other sites

8 hours ago, target11 said:

Good morning
however, setting the axes on fsuipc is very easy and user friendly, I'm far from an expert, but setting the axes with the ATR efb is anything but user friendly and setting the axes with msfs and the efb is an achievement

but if you have a notch throttle like the Thrustmaster Airbus Throttle or other I understand the principle of configuring with msfs2020 and the efb of the atr

 

OPTION 1

Strangely enough with ATR I was able to set up my Throttle via MSFS and EFB without any issues provided my FSUIPC was disabled. Later I learnt how to configure FSUIPC so I can have it enabled and keep configuration via MSFS and ATR's EFB. Which I find the throttle behavior little bit better in this particular aircraft, and ONLY in this particular aircraft. Configuration of notches is better.

---------------------

OPTION2

Per your suggestions I was able to configure it with FSUIPC by the use of  UseAxisControlsForNRZ=Yes and *1, +8192, however notch was not very well working overall throttle wasn't working very good in my case and the behavior was a lot more erratic even at idle I actually had to use *1, +8300 if I recall and even then not working very well. So i went ahead with the Option 1.

-------------------

In PMDG for example I prefer  use of FSUIPC as it provides better calibration for the throttle. When configured via MSFS (I tried it last night) it was very jittery and shaky etc.) when configured via FSUIPC it was very nice and smooth. Which is the reason I was trying to get this configured like that for ATR, but it just does not work in ATR as nice as it does for other aircraft, must have something to do with the way they coded axis which is in part explained in FSUIPC manual where I found the info about the use of UseAxisControlsForNRZ=Yes for these types of aircraft... 

Link to comment
Share on other sites

6 hours ago, John Dowson said:

The OP seemed to have issues setting this up in FSUIPC and so is using MSFS. He has a JetMAX 737 Throttle - not knowing this throttle (or having the aircraft) it is difficult for me to advise on what the issue was, but if he is happy with configuring the throttle in MSFS then I am not going to spend any time looking into this.

However, I see the ATR bundle is on sale (for just over 12euros), so I'll probably buy this and take a look later in the week, and see how to configure with the throttles I have (Honeycomb Bravo and a Saitek X-55).

Thanks for your help with this.

John

if you do play MSFS I would highly recommend ATR for 13 euro it is a steal and it seems to be very well made aircraft for this money,

I would be interested to hear if you were able to configure throttle just using the FSUIPC, idk if my throttle somehow send different input info or what.. why i had this problem yet target11 was able to get it done just using this addition *1, +8192, yet for me it got sorted out after adding this to the aircraft ini file UseAxisControlsForNRZ=Yes Gatwick Flight Simulation Group

That's what my throttle looks like btw :) not a common mass production like Honeycomb Bravo, but then again a POT is a POT i suppose.

Anyhow got it working and learnt a lot about fsuipc though it. 

 

Link to comment
Share on other sites

On 5/1/2023 at 7:56 AM, target11 said:

I made a direct link on a video that explains what I do

if you don't have a registered version of fsuipc it may not work

https://drive.google.com/uc?export=download&id=1t077R2Nuqk38BNf0jGv61xYyshY_Mn-s

once i got ATR profile in FSUIPC and was able to disable FSUIPC from controling my throttle axis by using profile specific calibration and clearing its calibration from FSUIPC, my throttle was behaving exactly like yours on the video, traveling form one extreme to the other, but once i got it configured in EFB, it was traveling from IDLE to MAX. I had unchecked the (Has reverses) option in EFB and used 2 axles, and as i explained in the other post I find it work better then using FSUIPC, still I am using FSUIPC for flaps and other buttons for example to activate reversers etc.. but throttle axis is done via MSFS and ATR's EFB,

anyway if it work good for you via FSUIPC that's great just for me it for some reason not working well so had to come up with this here.

can't wait to go fly finally geez all these hours spent on that gosh at least i leant something i suppose :) 

Thanks again for your help !

Link to comment
Share on other sites

Good evening
yes I understood the principle, you configure axes 1 and 2 on msfs2020, and the notches on the efb, so in this configuration you don't need fsuipc, and moreover you can configure the return axes on the same principle, so you do not need to reconfigure the axes on fsuipc, otherwise you will have a conflict or will not obtain the desired result, after if you use fsuipc for the buttons without configuring the axes there should be no problems . on the other hand if you have no notches and you want to configure the axes on idle a maximum like me then using fsuipc will be less complicated.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.