Yoke Aileron (x-axis) not recognized in FSUIPC6

[Andre Korver]

Been flying with P3D / PMDG B777 / TCA Boeing yoke and system worked flawlessly for a long time. Suddenly the aileron axis (x-axis) stopped responding.

In the FSUIPC window the values of the X-axis are fluctuating up and down.

In the calibration tab the x-axis values won't change when turning the yoke. Set/Reset won't work.

FSUIPC6 ini.txt FSUIPC6 log.txt

[John Dowson]

You only have the aileron axis assigned in one profile:

Quote

[Profile.B777KLM]
1=PMDG 777-300ER KLM (PH-BVK | 2013 | Yellowstone National Park)

[Axes.B777KLM]
RangeRepeatRate=10
0=0X,256,D,1,0,0,0    -{ DIRECT: Aileron }-
1=0Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-
 

Your log shows that you were using this aircraft:

Quote

   206469 Aircraft="PMDG 777-300ER Singapore Airlines (9V-SWV | 2013)"

which is in this profile:

Quote

[Profile.PMDG B777]
1=PMDG 777-300ER Singapore Airlines (9V-SWV | 2013)
2=PMDG 777-300ER Cathay Pacific Airways (B-KPK | 2009)

[Axes.PMDG B777]
RangeRepeatRate=10
0=0Y,256,D,2,0,0,0    -{ DIRECT: Elevator }-

i.e. you have no assignments to the aileron om the profile for that aircraft.

I do not understand why you have different profiles for the same aircraft, different liveries. You should use one profile, and change the aircraft name in that profile to catch all variants, e.g.

Quote

[Profile.PMDG B777]
1=PMDG 777-300ER

And make sure you have the aileron assigned and calibrated in that profile.

John

[Andre Korver]

Hello John,

Thanks for swift reply.

From this side no idea how I got to several profiles as, up to my knowledge, I only used one B777. Regardless of the livery.

To clear it all up I saw no other option to re-install FSUIPC. The result is that now no yoke axis (Y nor X) are detected in FSUIPC.

Using the yoke without FSUIPC, In P3D) I get the well known TCA issue of 'from 0 to 16300 in just a touch. Your program solved this issue, up to recently without me having changed anything as far as I know.

FSUIPC6.log

[John Dowson]

3 hours ago, Andre Korver said:

To clear it all up I saw no other option to re-install FSUIPC.

Why? That does nothing at all....the ini file (containing your assignments) will still be the same - or did you delete this? If you delete this, you will have to re-assign and re-calibrate.

Try the attached ini - just save it to your FSUIPC installation folder:

FSUIPC6 ini

Any issues, please re-attach both your .log and .ini files.

[Andre Korver]

I may have been too rigorous in deleting. I've restored the ini file up to no avail. Also the ini file sent by you (thanks for that) didn't work.

Now, with a slight touch to the throttle the yoke swings full left and the throttle goes full forward. (no idea why the throttle suddenly got involved.)

Calibrating is the issue. In the calibration tab I can't seem to get the sim / yoke communicate with FSUIPC.

 

[John Dowson]

Can you please ALWAYS attach your FSUIPC6.log and FSUIPC6.ini files - there is no point in reporting issues with assignments if you do not provide these files, and every time please as they are changed/updated each time you run FSUIPC.

You also have controllers active in P3D. If assigning in FSUIPC, it is better to disable controllers in P3D. As a minimum, you need to check that any axis assigned in FSUIPC is NOT assigned in P3D. And be aware that P3D can sometimes automatically re-assign an axis if controllers are not disabled. You have no assignments to your throttle in FSUIPC, so this MUST be assigned elsewhere, probably in P3D

You say you have been flying a long time and this is a new issue. What has changed? Why do you only have two axis (aileron and elevator) assigned in FSUIPC? Are the rest assigned in P3D? If so, why are you even using FSUIPC - if everything else is assigned in P3D, why not just assign the aileron and elevator there, as you do not seem to be using anything else in FSUIPC?

I suggest you try assigning in FSUIPC with controllers disabled in P3D. 

3 hours ago, Andre Korver said:

Calibrating is the issue. In the calibration tab I can't seem to get the sim / yoke communicate with FSUIPC.

For PMDG aircraft, you should not calibrate if the axis is assigned in P3D or elsewhere, and should only be calibrated if assigned in FSUIPC with 'Direct to FSUIPC Calibration'. Sometimes even this can give issues, and if so you should assign using 'send to FS as normal axis; and not calibrate.
 

[Andre Korver]

Good morning John,

Thanks again for reply and apologies for late reply.

The main reason I use FSUIPC is that using the yoke directly assigned to P3D has it's issues. (A lot of people seem to have this, the aileron goes from 0 to full in just a touch) FSUIPC managed to solve that issue. The only thing that changed over time was the addition of a new livery. (CX)

BTW I can't seem to send the log and ini files along due to a size restriction.

 

[John Dowson]

1 hour ago, Andre Korver said:

BTW I can't seem to send the log and ini files along due to a size restriction.

Compress/zip them if too large. When you attach them, can you please explain what the issue is, and also remember to check any/all assignments in P3D (or disable controllers).

1 hour ago, Andre Korver said:

the aileron goes from 0 to full in just a touch

If an axis goes from 0 to full, then this is usually because it has been registered as a digital on/off axis. See the following FAQ entry on how to resolve this (written for saitek devices but applies generally - just use the correct VID/PID numbers for your device): 

 

[Andre Korver]

Good morning John,

 

Thanks again for your patience.

At the moment:

The Yoke Axis have not been directly assigned in P3D.

In FSUIPC: In the tab 'Axis assignment' (profile specific box is ticked)

Joy# 0 Axis# X (aileron); In - Out values are 0. This changes when I move the yoke.

Joy# 0 Axis# Y (elevator); In - Out values are 0. This changes when I move the yoke. 

In the tab 'Axis calibration' 

The values at both Aileron and Elevator remain unchanged when moving the yoke.

Even when zipped the .log and .ini files are bigger than the 1.55kB I can send along. Any other way to send these?

[John Dowson]

On 12/10/2023 at 8:38 AM, Andre Korver said:

Even when zipped the .log and .ini files are bigger than the 1.55kB I can send along. Any other way to send these?

Post them individually. Your limit will increase the more you post. If too large, you can also send them to me in a message - click my user icon then message.

If you are assigning with 'Send direct to FSUIPC calibration', I do not understand why you cannot see the axis values change in the calibration panels.

PMDG aircraft do sometimes have issues with FSUIPC calibration. If assigning with 'Send direct to FSUIPC calibration' causes issues, try assigning with 'Send to FS as normal axis' and remove the calibration.

I don't understand why this was previously working and has suddenly stopped. What has changed? You also said that this was for the x-axis/aileron, but now you also say that this applies to the y-axis/elevator as well. Has it changed again?