Raw axis value overriden

[ysav]

I have defined axis assignments using raw axis values. All axes are also sent direct to FSUIPC. The ultimate source is actually fed by EPIC so the IN value is always comprised between 0 and 255. Calibration works just fine. However, when I later return to the FSUIPC configuration window and select the joystick calibration tab, the IN and OUT values are much greater than what I initially calibrated. E.g. the throttle1 calibration will show an IN value of 17800 and OUT value of 16384 whereas after the initial calibration, at the same throttle lever position, it showed an IN value of 97 and an OUT value of 2081. However, if I navigate to the axis assignment tab and immediately back to the joystick calibration tab, then the proper in and out values are shown again.

How can I avoid this ? After exiting setup, all is generally fine. From time to time however, I have seen the elevator flicker; when pushing the sidestick forward, it would flicker to the neutral position and back.

I am currently having problems with magenta's FCU when the single throttle is mapped to 4 throttles and I am questioning if it is related to the above problem. When engaging auto thrust, the left engine's N1 value sticks to whatever it was at before auto thrust was engaged. FCU obviously struggles to achieve the intended performance.

Currently using V4.40.

Thanks for your help.

Yves Savard

[Pete Dowson]

I have defined axis assignments using raw axis values. All axes are also sent direct to FSUIPC. The ultimate source is actually fed by EPIC so the IN value is always comprised between 0 and 255.

Why use RAW? Really that facility, whilst intended for uses with EPIC, is actually suited to SOFTWARE axes, i.e. those axes controlled by the programming of the EPIC rather than merely the A to D converters for axes connected there. And then you wouldn't be sending the values "for calibration" as they would be for use as they are, real numbers for things like Headings, Altitudes, etc.

Calibration works just fine. However, when I later return to the FSUIPC configuration window and select the joystick calibration tab, the IN and OUT values are much greater than what I initially calibrated. E.g. the throttle1 calibration will show an IN value of 17800 and OUT value of 16384 whereas after the initial calibration, at the same throttle lever position, it showed an IN value of 97 and an OUT value of 2081.

By "same throttle position" do you mean exactly the same, or you mean roughly by feel or look? When you move the throttle, is the IN value moving in the high range, or is this 17800 value you see just the initial one, there when you open the Tab?

How can I avoid this ? After exiting setup, all is generally fine. From time to time however, I have seen the elevator flicker; when pushing the sidestick forward, it would flicker to the neutral position and back.

That doesn't sound like the same thing at all - the neutral position would be a value which calibrates to zero, so not an extreme, larger, value but something near your 128 (for the 0-255 range).

I am currently having problems with magenta's FCU when the single throttle is mapped to 4 throttles and I am questioning if it is related to the above problem. When engaging auto thrust, the left engine's N1 value sticks to whatever it was at before auto thrust was engaged.

Sorry, I have no idea about that. Do you get no problem when you don't have it mapped to 4 throttles?

My first inclination would be to change from RAW mode and use the normal input mode which is quite correct for analogue axes and suits them better. RAW mode is supported for passing usable numbers, not intended to be calibrated. However, I'd like to get to the bottom of this problem even if that would be the best thing (and quickest thing) to do.

Obviously i need more information. Can you use the Logging facilities in FSUIPC, please? The Axis logging check box should be set. You will get HUGE logs, and I don't want to wade through them, so I'd need you to try to narrow them down to the area getting a problem. If you have to send me anything, ZIP it, please, and send to petedowson@btconnect.com.

Oh, and please first update to the latest interim version, from the Updates announcement above, just in case something I've changed in the last two months affects it.

Regards

Pete

[Pete Dowson]

I have defined axis assignments using raw axis values. All axes are also sent direct to FSUIPC.

...

E.g. the throttle1 calibration will show an IN value of 17800 and OUT value of 16384

Okay, I have reproduced this in the current interim update as well. So there is not need for you to send me any logging, after all, at least for this problem.

But I believe it is only affecting the calibration screen, not the RAW axis scanning or its operation. So if you do have some other problem, like that elevator centering, you'd need to try using the logging to isolate that. It does sound more likely to be either an odd incorrect value coming from the EPIC, or, more likely perhaps, an alternative elevator assignment interfering with its values.

I will work on fixing the way the RAW input are affecting the calibration IN values, though I must admit, as I said earlier, it was never really intended for RAW values to be "calibrated". In fact in may be an oversight arising from that fact.***

I would advise you to try using the normal inputs for analogue values (as opposed to software-generated specific values).

*** LATER:

For information, I've identified the cause of the wrong calibration "IN" values. It does only apply to the calibration, and to FSUIPC4 only. It is actually a function of FSX. In order to continue scanning FSX-assigned axes whilst in FSX's "dialog mode" (which has to be used for FSUIPC to present its options), FSUIPC has to make a call to FSX to make it happen (after all, for such axes FSUIPC is dependent upon FSX supplying the values, and this doesn't normally happen when it is "stopped", as in dialog mode). The call it does to achieve this is a facility of SimConnect.

It seems that, even if no axes (no joysticks in fact) are enabled in FSX itself, this call does a scan of attached joysticks and puts the calibration mode back to normal, thereby disabling "raw" mode. In turn this creates entirely the wrong range of values in FSUIPC4.

I've fixed it, ready for the next FSUIPC4 update, by restoring RAW mode on entry to and exit from the options dialogues.

However, unless there are really good reasons for staying in "RAW" mode, I repeat my advice, to try always using the normal inputs for analogue values (as opposed to software-generated specific values). I'm sure it would be less problematic.

Regards

Pete

[Pete Dowson]

I've fixed it, ready for the next FSUIPC4 update, by restoring RAW mode on entry to and exit from the options dialogues.

Okay, version 4.425 is now available with this fix. Please see the Updates announcement above.

Regards

Pete

[ysav]

Now using v4.425

Why use RAW? Really that facility, whilst intended for uses with EPIC, is actually suited to SOFTWARE axes, i.e. those axes controlled by the programming of the EPIC rather than merely the A to D converters for axes connected there. And then you wouldn't be sending the values "for calibration" as they would be for use as they are, real numbers for things like Headings, Altitudes, etc.

Wanted to use FSUIPC’s calibration as a one stop shop for calibration. Otherwise, I’ll need to first calibrate these axes in window’s game controller calibration. I found your tool more convenient. I’ve now set these as per your recommendation, without using the raw value (elev, aileron and throttle). As for other discrete axes values, I have had them defined in epicinfo.cfg from day 1. All ok on this side.

Do you get no problem when you don't have it mapped to 4 throttles?

My FCU issue arises only – and still arises - when mapping to 4 throttles.

Thank you so much for fixing the Raw issue so fast. I do plan to use it soon - for software assigned values.

Thank you !

Yves Savard