Several missing controls

[Raceguy]

Hello

My setup: Windows 10  P3Dv4.5.13.32097  FSUIPCv6.1.9 Registered (just upgraded from v5)

I have a complex P-51 cockpit with 14 devices connected to my PC.  Those include TPR pedals, MSFFB joystick, 3 Saitek panels and 9 Desktop Aviator USB devices with 2 of them controlling buttons and axis.   

A few days ago the rudder, aileron and elevator trim controls stopped working. They are pots connected to the DTA boards. They had worked great for 5 years and were setup and calibrated with FSUIPCv5.

I opened FSUIPCv5 to correct the issue and found that those 3 axes are no longer recognized by FSUIPC in the axis assignment tab. The trim controls are seen in FSUIPC joystick calibration so I calibrated but they still do not appear in the axis assignment even after several pushes of the rescan button. Checking all other axis in FSUIPC I found the throttle, flaps, carb controls and other axis can be seen and work fine.

Thinking the board had failed I opened the Windows Joystick Calibration app and all of the buttons and axis on the boards were recognized and worked.  I use SPAD.neXt for my Saitek panels so I checked the axis there and they were recognized. I then turned to P3D and checked the axis there and all worked except the 3 trim units.

I had been using FSUIPCv5 (registered) so yesterday I upgraded to FSUIPCv6 (registered) and still the 3 trim controls are missing. I went through the calibration again which worked but they are still not seen on the axis assignment tab.

I would appreciate any help to get these 3 items back in service.

Thank you

Ed

FSUIPC6.ini FSUIPC6.log FSUIPC6.JoyScan.csv

[John Dowson]

Before I look at this in detail, could you clean your FSYUPC6.ini fil please. You have multiple sections for these when there should be only one: [General], [WideServer], [GPSout], [GPSout2], [AutoSave].

Also, I suggest that you clean-up your profiles to use substrings, so change

Quote

[Profile.P-51 MIL]
1=A2A North American P-51D MIL Moonbeam McSwine TW
2=A2A North American P-51D MIL Twilight Tear
3=A2A North American P-51D MIL Old Crow Late
4=A2A North American P-51D MIL Cripes A Mighty 3rd
5=A2A North American P-51D MIL American Beauty
6=A2A North American P-51D MIL Excalibur
7=A2A North American P-51D MIL Sweet and Lovely
8=A2A North American P-51D MIL Big Beautiful Doll
9=A2A North American P-51D MIL Gunfighter
10=A2A North American P-51D MIL Crazy Horse
11=A2A North American P-51D MIL PETIE 2nd
12=A2A North American P-51D MIL Glamorous Glen III
13=A2A North American P-51D MIL Miss Helen

to

Quote

[Profile.P-51 MIL]
1=A2A North American P-51D MIL

and

Quote

[Profile.P-51 CIV]
1=A2A North American P-51D CIV Excalibur
2=A2A North American P-51D CIV USAF Thunderbirds
3=A2A North American P-51D CIV American Beauty
4=A2A North American P-51D CIV Big Beautiful Doll
5=A2A North American P-51D CIV Moonbeam McSwine A2A
 

to

Quote

[Profile.P-51 CIV]
1=A2A North American P-51D CIV

and similar for your other profiles

For the profile you were using (P-51 MIL), you also have the same axis control assigned to multiple axes, e.g.
2=BZ,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
19=JR,256,D,3,0,0,0    -{ DIRECT: Rudder }-

5=SY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
6=SR,256,D,2,0,0,0    -{ DIRECT: Elevator }-

Its generally not a goof idea to assign multiple axes to the same axis control as they can interfere, especially when on the same controller.

35 minutes ago, Raceguy said:

A few days ago the rudder, aileron and elevator trim controls stopped working.

Do you mean these assignments:

Quote

[Axes.P-51 MIL]
RangeRepeatRate=10
0=BX,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
1=BY,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
2=BZ,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
4=SX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
5=SY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
6=SR,256,D,2,0,0,0    -{ DIRECT: Elevator }-
7=DZ,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
8=DR,256,D,21,0,0,0    -{ DIRECT: ElevatorTrim }-
9=DU,256,D,28,0,0,0    -{ DIRECT: Rudder Trim }-
10=DV,256,D,27,0,0,0    -{ DIRECT: Aileron Trim }-
 

 

36 minutes ago, Raceguy said:

I opened FSUIPCv5 to correct the issue and found that those 3 axes are no longer recognized by FSUIPC in the axis assignment tab. The trim controls are seen in FSUIPC joystick calibration so I calibrated but they still do not appear in the axis assignment even after several pushes of the rescan button.

So you don't see anything when you move those axes (DR, DU, DV)? If you see another axis instead, just hit the Ignore button and try again.

Otherwise, please clean your ini as suggested and show me the updated ini and an FSUIPC6.log file, this time with LINDA disabled (temporarily), logging for Axes controls enabled, load your aircraft and move one of the unrecognised axes through its full range, then exit.

John

[Raceguy]

Hello John

As suggested I have removed the duplicate controls from the axis list and reduced the list of liveries for all 5 planes from the profile.

[Profile.P-51 MIL]

1=A2A North American P-51D MIL

I checked the 3 trim controls again and can report the same results.  The Rudder and Aileron trims show value changes in the calibration tab but the Elevator trim does not.  In the axis assignment tab all 3 fail to register any movement.

I have attached an updated ini and an FSUIPC6.log file with LINDA disabled temporarily and logging for Axes controls enabled.  I load my aircraft and moved the elevator control, which was one of the unrecognized axes, through its full range then exited the program.

Thank you
Ed

I tried to attached the files and got a message for each one that they exceeded max size of 20KB yet these files are smaller that the ones I posted yesterday.

I have uploaded them in the following post.

 

[Raceguy]

OK, they went through this time.

FSUIPC6.ini FSUIPC6.log

[John Dowson]

You posted a continuation log - please always post a full log file for support, i.e. never use the New Log function if generating a log for support purposes.

16 hours ago, Raceguy said:

I checked the 3 trim controls again and can report the same results.  The Rudder and Aileron trims show value changes in the calibration tab but the Elevator trim does not.  In the axis assignment tab all 3 fail to register any movement.

I really don't understand how the rudder and aileron trim can be seen in the calibration tab but not in the assignments tab. It is strange also that SPAD,next recognises the trim axes but not P3D or FSUIPC.

Are the other axes on this device (DTA Rotary Encoder) recognised, i.e. PropPitch and Throttle:

Quote

[Axes.P-51 MIL]
...

5=DZ,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
...
15=DT,256,D,4,0,0,0    -{ DIRECT: Throttle }-

?

Are you using any specific drivers or software with this device, or are you using the default windows drivers?

Can you download and try the HiDScanner program (available from the Download Links -> Useful Additional Programs section of this forum), run that and see if that recognises the rotaries you have assigned to the trim controls.

Also try connecting it to a different USB hub, to see if that helps - and check you have power management disabled on all your hubs - windows has a tendency to reset this on updates.

Finally, you could try disconnecting the device, uninstalling any specific drivers (if installed), cleaning the registry entries for the device, reboot and then reconnect to see if that helps.

On 10/10/2022 at 5:44 PM, Raceguy said:

A few days ago the rudder, aileron and elevator trim controls stopped working. They are pots connected to the DTA boards. They had worked great for 5 years and were setup and calibrated with FSUIPCv5.

Something must have changed to cause this, and I suspect either a registry issue or maybe a hardware fault somewhere...

John

[Raceguy]

Hi John

Thank you for your help and patience in working with this issue.  I am not a PC expert but have enjoyed learning a lot as I built and use my pit. I have posted another FSUIPC log file as requested without using the New Log function. I hope it has the information you need.

You had asked if the other axes (i.e. PropPitch and Throttle) on the DTA device are recognized and they are.  All axes are seen in W10 joystick calibration, SPAD.neXt. P3D sees all axes except trim.  FSUIPC sees, calibrates and assigns all axes except for the trim controls.  On the calibration tab FSUIPC sees the rudder and aileron trims and shows value changes but the elevator trim does not react. On the axis assignment tab all 3 fail to register any movement.

Regarding drivers I am using the default windows drivers for the DTA devices.

I downloaded and ran HiDScanner and its log is attached.  There are 2 DTA rotary encoder boards listed in the report.  Line 739 lists the information for the board that has 6 connections for the throttle, prop pitch, flaps and the 3 trim controls in question. Line 906 shows the second DTA rotary encoder board with only 5 rotary encoders connected and all work OK.

I connected the DTA board to a different hub and got the same results.

 

Power management for all USB’s has been checked and it is off for all devices.

I have not tried disconnecting the device, uninstalling any specific drivers (if installed), cleaning the registry entries for the device, reboot and then reconnect as I am not sure how to do this.

Take care

Ed

FSUIPC6.ini HidScanner.log

FSUIPC6.log

[John Dowson]

Hi Ed,

I will look at those files in detail and get back to you. However, I first want to understand some changes compared to your previous files. The latest ini you posted does not have anything assigned to elevator trim. whereas previously you had this assigned:

Latest ini:

Quote

[Axes.P-51 MIL]
RangeRepeatRate=10
0=BX,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
1=BY,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
2=BZ,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=SX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
4=SY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
5=DZ,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
6=DU,256,D,28,0,0,0    -{ DIRECT: Rudder Trim }-
7=DV,256,D,27,0,0,0    -{ DIRECT: Aileron Trim }-
8=DS,256
9=DS,B,16255,16383,M1:57,0    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
10=DS,B,14460,15389,M1:57,1    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
11=DS,B,10420,13241,M1:57,2    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
12=DS,B,256,1475,M1:57,3    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
13=DS,B,-12697,-12440,M1:57,4    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
14=DS,B,-16352,-15807,M1:57,5    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
15=DT,256,D,4,0,0,0    -{ DIRECT: Throttle }-
 

Previous ini:

Quote

[Axes.P-51 MIL]
RangeRepeatRate=10
0=BX,256,D,8,0,0,0    -{ DIRECT: RightBrake }-
1=BY,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
2=BZ,256,D,3,0,0,0    -{ DIRECT: Rudder }-
3=BR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
4=SX,256,D,1,0,0,0    -{ DIRECT: Aileron }-
5=SY,256,D,2,0,0,0    -{ DIRECT: Elevator }-
6=SR,256,D,2,0,0,0    -{ DIRECT: Elevator }-
7=DZ,256,D,5,0,0,0    -{ DIRECT: PropPitch }-
8=DR,256,D,21,0,0,0    -{ DIRECT: ElevatorTrim }-
9=DU,256,D,28,0,0,0    -{ DIRECT: Rudder Trim }-
10=DV,256,D,27,0,0,0    -{ DIRECT: Aileron Trim }-
11=DS,256
12=DS,B,16255,16383,M1:57,0    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
13=DS,B,14460,15389,M1:57,1    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
14=DS,B,10420,13241,M1:57,2    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
15=DS,B,256,1475,M1:57,3    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
16=DS,B,-12697,-12440,M1:57,4    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
17=DS,B,-16352,-15807,M1:57,5    -{ Entering=Macro 1A2A_P51_M: L:LandFlapsPos set }-
18=DT,256,D,4,0,0,0    -{ DIRECT: Throttle }-
19=JR,256,D,3,0,0,0    -{ DIRECT: Rudder }-
 

Have you manually removed this assignment?

22 hours ago, Raceguy said:

I have not tried disconnecting the device, uninstalling any specific drivers (if installed), cleaning the registry entries for the device, reboot and then reconnect as I am not sure how to do this.

I will investigate further first, but it may be a good idea to disconnect the two DTA Rotary Encoder devices, reboot, clean the registry (back-up first), reboot and then reconnect.
But first I would like more information from the HidScanner program - you need to keep it running to log changes of the trim rotaries...or not, as the case may be. I know this utility can do this but not sure how at the moment - I will get back to you....

John

 

Later: sorry, I was mistaken - the utility does not log axes/button changes, only device connections

Edited October 14, 2022 by John Dowson
Later added

[John Dowson]

Sorry, one more question:

21 hours ago, Raceguy said:

On the axis assignment tab all 3 fail to register any movement.

But what do you see registered in the axis assignment tab when you do this? Do you see the correct JoyLetter and axis letter registered and not the in/out numbers changing? Or do you see a different joy letter or axis letter registered? If that is the case, click Ignore Axis and try again. I would like to know if the device and axis letters are recognised or not in the axes assignment tab.

Thanks,

John

[Raceguy]

Hi John

Regarding the missing ElevatorTrim in the latest INI, I did not remove this line or press Clear in FSUIPC. 

When I said “On the axis assignment tab all 3 fail to register any movement” I meant there is no recognition of the controller at all.  The JoyLetter and axis letter do not show any information even after clicking on RESCAN and moving the controls several times.  The in/out numbers do not change and under Type of action required the area remains grayed out as if no controller was moved.

You mention it may be a good idea to disconnect the two DTA Rotary Encoder devices, reboot, clean the registry (back-up first), reboot and then reconnect.  Two questions to help me understand this action. 

One, if W10 and SPAD.neXt can see all components of these devices, but FSUIPC cannot, how will this correct the issue?  Could there be issues in the registries that are affecting FSUIPC and not W10 and SPAD?

Two, how do I find these devices in the registry?  I have edited the registry in the past but have no idea how or where to find these devices.  I’ll give it a try if you would please let me know how.

Thank you again for your time and patience!

Take care

Ed

[John Dowson]

1 minute ago, Raceguy said:

Regarding the missing ElevatorTrim in the latest INI, I did not remove this line or press Clear in FSUIPC. 

Hmm...even stranger....

5 minutes ago, Raceguy said:

When I said “On the axis assignment tab all 3 fail to register any movement” I meant there is no recognition of the controller at all.  The JoyLetter and axis letter do not show any information even after clicking on RESCAN and moving the controls several times.  The in/out numbers do not change and under Type of action required the area remains grayed out as if no controller was moved.

But what is registered, if anything? If nothing is registered, why click the Rescan button? If anything IS registered, what? And if another axes IS registered, have you tried clicking the Ignore Axis button and trying again? And repeat until the axis is recognised...or not, as the case may be...please try this until the axis is recognised or you see no joystick letter or axis letter recognised. That would confirm that the axis/axes are not being seen. It is difficult for me to know this without you doing this and reporting back. 

And you say there 'is no recognition of the controller at all' - but I thought the other axes assigned to that controller were functioning ok: 'You had asked if the other axes (i.e. PropPitch and Throttle) on the DTA device are recognized and they are' .
So, if hey are recognised and working, so is the device.

Sorry to be so pedantic but your issue is very strange and you need to be very clear otherwise it gets confusing....
Maybe you could take a short video of what you see, which may help clarify things... 

9 minutes ago, Raceguy said:

One, if W10 and SPAD.neXt can see all components of these devices, but FSUIPC cannot, how will this correct the issue?  Could there be issues in the registries that are affecting FSUIPC and not W10 and SPAD?

Possibly - there are various APIs to access HID devices. You say that these are also not recognised by P3D. and FSUIPC recognises the device, and was previously ok (for 5 years) but there are now problems with specific axes/pots on the device (the ones assigned to trim), not the device itself (other axes are working, no?), so the problem is not that straightforward as device recognition. Or at least this is what it seams...

26 minutes ago, Raceguy said:

Two, how do I find these devices in the registry?  I have edited the registry in the past but have no idea how or where to find these devices.  I’ll give it a try if you would please let me know how.

I will let you know how to do this if/when necessary - for now, please just clarify the above.

Cheers,

John

[Raceguy]

Hi John

I apologize, I have not been clear so let me try again.

The DTA board and all of its 32 buttons and 6 axes are seen by W10 and SPAD.neXt. I load my plane and in FSUIPC select the correct profile. When I select the axis assignment tab the throttle, prop pitch and flaps appear in the Type of action required and the in/out values change as I move the specific control.  However, the elevator, rudder and aileron trim do not appear in the Type of action required and the in/out values do not change as I move the specific control. I do click on Rescan after each control test.

On the calibration tab the rudder and aileron trim values do change as I turn the knob but the elevator trim does not react.

This is why I noted that I feel the DTA device is working properly since W10 and SPAD.neXt can see every controller connected and all but the 3 trim controls are seen by FSUIPC.

I kept clicking the Rescan button hoping that another scan would find the control I was moving.

This 70 year old guy is frustrated since this pit has been working for 5 years and I didn’t change any settings. 

I don’t know how to make a video except with my iPhone and those file become huge very quickly.  I have used TeamViewer to share my desktop with a few friends.  Would you want to log in and see first hand what is happening?

I hope the information above better explained what I am seeing. 

Again, thank you for your patience and help with this issue.

Take care

Ed

[John Dowson]

Hi Ed,

I'm sorry but it is still not clear to me...could you re-read what I have said in my previous post and answer the specific questions and try what I have advised, i.e. you again say:

13 hours ago, Raceguy said:

However, the elevator, rudder and aileron trim do not appear in the Type of action required and the in/out values do not change as I move the specific control. I do click on Rescan after each control test.

Here you say 'elevator, rudder and aileron trim do not appear in the Type of action required' but what does show, if anything, in the joystick id/letter and axis letter boxes? Does anything register there, and if so, and it is not the correct axis, have you trued clicking the Ignore Axis button (not the Rescan button) and then trying again?

14 hours ago, Raceguy said:

I kept clicking the Rescan button hoping that another scan would find the control I was moving.

Again, if a different axis is showing, click the Ignore Axis button and try again, not the Rescan button. Please do this and tell me what joystick id and axis letter you see, and it is not the expected one click the Ignore Axis button and try again.

14 hours ago, Raceguy said:

On the calibration tab the rudder and aileron trim values do change as I turn the knob but the elevator trim does not react.

This indicates that the rudder trim and aileron trim ARE assigned, and you should see these (eventually) in the axis assignment tab. You will not see the Elevator trim as the latest ini you posted shows no assignments for this. You need to get this axis recognised again in the axis assignment panel  (again, click Ignore Axis until you see this, NOT Rescan) and re-assign this.

So, please take another look using the Ignore Axis button and not the Rescan button, and tell me what letters you see in the joystick and axis boxes.

John

[Raceguy]

Hi John

I apologize again for not making the information clear. I’ve been married 40+ years and may have been told that before.

In the following I am looking at ONLY the DTA board that has connections for throttle, prop pitch, flaps, elevator trim, rudder trim and aileron trim.

Steps taken:

Started Flight PC and ran W10 joystick calibration. All 6 axes and all buttons are recognized.

Start P3D to default plane

Load A2A P-51

Start SPAD.neXt just to test DTA board.  All axes and buttons are recognized. Checked each axis and button and confirmed there are NO setups in SPAD.neXt for this board.

Open P3D controls tab and noted that “Joystick controllers are currently DISABLED” as suggested by FSUIPC. Checked each controller listed for any axis and there are none listed.

In P3D using the virtual cockpit view I move each of the 6 axis connected to this board.  The throttle, prop pitch, flaps, rudder trim and aileron trim all move.  The elevator trim does not.

I open FSUIPC, select the P-51 MIL profile and select the Axis assignment tab.

I move the throttle, prop pitch and flaps, clicking rescan after each one.  All 3 show the correct Joy# and Axis# as well as the in/out changing as I move the device. Also the correct function is listed for each one under the Type of Action area.

I then move my controls for the elevator trim, rudder trim and aileron trim and NOTHING on the page reacts.  There is No Joy# and Axis#, NO value appears in the in/out section and NO function is listed for each one under the Type of Action area. All of the sections remain BLANK. FSUIPC, for these 3 connections on the Axis assignment tab, does not see anything.

I then select the Joystick calibration tab.  I move to the section that shows the elevator trim and I move my control.  There are NO values shown in the in/out section.  I click reset and still NO values.

I then go to the next page that has the aileron and rudder trim and move each control.  The in/out values change and let me calibrate each one.  I then go back to the Axis assignment tab and move the aileron and rudder trim but they still show NO Joy# and Axis# and NO value appears in the in/out section.

You said:  This indicates that the rudder trim and aileron trim ARE assigned, and you should see these (eventually) in the axis assignment tab.

They never appear.

You said:  You will not see the Elevator trim as the latest ini you posted shows no assignments for this. You need to get this axis recognized again in the axis assignment panel  (again, click Ignore Axis until you see this, NOT Rescan) and re-assign this.

How do I get this axis recognized in axis assignment panel? When I move my control for the elevator trim NOTHING appears, not even an incorrect link to another axis. I can’t use the Ignore Axis button because nothing appears.

I have attached pictures of SPAD.next and W10 joystick calibration showing that all buttons and axis are recognized by those programs.  Also there are 3 pics of FSUIPC showing the blank axis assignment tab I see when moving any of the 3 trim controls and the calibration tab for elevator trim and rudder aileron trim. I know the values for rudder and aileron trim are not accurate but I just wanted to show how they are seen by FSUIPC.

Thank you again. 

Take care

Ed

[John Dowson]

Hi Ed,

18 hours ago, Raceguy said:

I then move my controls for the elevator trim, rudder trim and aileron trim and NOTHING on the page reacts.  There is No Joy# and Axis#, NO value appears in the in/out section and NO function is listed for each one under the Type of Action area. All of the sections remain BLANK. FSUIPC, for these 3 connections on the Axis assignment tab, does not see anything.

Ok, thanks - this is want I wanted to confirm.

In FSUIPC, the rudder trim was assigned to axis U, the aileron trim to axis V, and the elevator trim previously assigned to axis S. What are the corresponding axis letters for these axes in windows controllers and Spad.next?

18 hours ago, Raceguy said:

I open FSUIPC, select the P-51 MIL profile and select the Axis assignment tab.

What do you mean by ' select the P-51 MIL profile'? You should not need to do this - profiles are automatically loaded based on the current aircraft name, and if you go to the axis assignment tab you should see the profile already loaded. It is only in the Button and key press assignment tabs where you have the ability to switch between profile and general assignments, as the general assignments for buttons and key presses are used when you have a profile, unless overridden in that profile.

Do you see the same behavior when using another profile,, e.g. when using the aircraft A2A North American P-51D CIV?

Could you also perform a test when you run with a default ini and see if these axes are recognised - just temporarily rename your FSUIPC6.ini file (e.g. to FSUIPC6.ini.unused) and run P3D/FSUIPC, and see if the axes you were using for the trim controls are recognised then.

 Can you also run a test without running Spad.next, just to confirm that is not causing this issue.

John

[John Dowson]

And one more test, with your original FSUIPC6.ini, could you add the following to the [General] section:
    Debug=Please
    LogExtras=x1000

and generate another log file where you  move the axes assigned to the trim controls with the assignments window open, then exit. The log file could be quite large and so may need zipping before attaching.

John

[Raceguy]

Hi John

You said:  In FSUIPC, the rudder trim was assigned to axis U, the aileron trim to axis V, and the elevator trim previously assigned to axis S. What are the corresponding axis letters for these axes in windows controllers and SPAD.neXt?

Two things. One, regarding the axis letters, in the previous full ini file, (before today’s default ini) I agree on the rudder axis U and aileron trim axis U but I see the elevator trim assigned to axis R not S.

Here is what is listed.

=DR,256,D,21,0,0,0   -{ DIRECT: ElevatorTrim }-

=DS,256 with no other information.

I went back to an ini file from January of this year and see the same information for both DS and DR.  Screen shot attached.

Also,seeing several duplicates in the files got me thinking.  Over the years I have had 2 different joysticks and 2 different rudder pedal sets.  Could remnants of these old devices have remained I the ini after new controllers were installed?  When replacing controllers should the old ones be removed manually?

Two, I don’t know how to see the axis letters in W10 and SPAD.  I grabbed a screen shot of what I can see for both which are attached.

You said:  What do you mean by select the P-51 MIL profile'?

What I have been doing is open FSUIPC to the first panel Options and Settings.  I then click on Buttons and Switches and put a check mark in the Profile Specific box to make sure the proper profile is loaded.  I just tried skipping the Buttons and Switches page and went right to axis assignment and the P-51 MIL profile loaded.  I just tried the same steps for the CIV and the CIV profile loaded fine.  Hmm, didn’t know I could skip the profile select action.

You said:  Could you also perform a test when you run with a default ini and see if these axes are recognized - just temporarily rename your FSUIPC6.ini file (e.g. to FSUIPC6.ini.unused) and run P3D/FSUIPC, and see if the axes you were using for the trim controls are recognized then

I renamed the ini as ini.unused, started P3D then opened FSUIPC.  On the axis assignment tab I moved the throttle, prop pitch and flaps and saw a value in the in/out cells for each control. I then moved the controls for the 3 trim axis and no values appeared in the in/out cells.  I then tried the calibration page and could calibrate the throttle, prop pitch and flaps but the 3 trim controls registered nothing in the in/out cells.

You said:  Can you also run a test without running SPAD.neXt, just to confirm that is not causing this issue.

The test above using a new ini files was performed without SPAD.neXt running.  It does not start automatically so I start it manually after I have loaded any A2A plane.

I created another log file with the Debug text and it’s attached.

Thank you for all of your help!

Take care

Ed

FSUIPC6 E Gilbert.zip

[John Dowson]

14 hours ago, Raceguy said:

Two things. One, regarding the axis letters, in the previous full ini file, (before today’s default ini) I agree on the rudder axis U and aileron trim axis U but I see the elevator trim assigned to axis R not S.

Here is what is listed.

=DR,256,D,21,0,0,0   -{ DIRECT: ElevatorTrim }-

That is in your P-51 CIV profile, not in your P-51 MIL profile, which your latest ini shows no assignment, although your previous ini did:
    8=DS,256,D,21,0,0,0    -{ DIRECT: ElevatorTrim }-

15 hours ago, Raceguy said:

=DS,256 with no other information.

That is ok - you have additional assignments to flaps macros via a set of ranges (right-hand side of axes assignments panel) for that axis.

15 hours ago, Raceguy said:

What I have been doing is open FSUIPC to the first panel Options and Settings.  I then click on Buttons and Switches and put a check mark in the Profile Specific box to make sure the proper profile is loaded.  I just tried skipping the Buttons and Switches page and went right to axis assignment and the P-51 MIL profile loaded.  I just tried the same steps for the CIV and the CIV profile loaded fine.  Hmm, didn’t know I could skip the profile select action.

Yes, you don't need to do this. Profiles are automatically loaded based on the aircraft name, its just that in the button and key assignment panels, you can assign a button/key in either the general section or in the profile, so you can check/uncheck the profile-specific box in those assignment panels. For axes it will automatically be checked and not possible to uncheck, and calibration will depend if you have profile-specific calibration or not.

 

15 hours ago, Raceguy said:

You said:  Could you also perform a test when you run with a default ini and see if these axes are recognized - just temporarily rename your FSUIPC6.ini file (e.g. to FSUIPC6.ini.unused) and run P3D/FSUIPC, and see if the axes you were using for the trim controls are recognized then

I renamed the ini as ini.unused, started P3D then opened FSUIPC.  On the axis assignment tab I moved the throttle, prop pitch and flaps and saw a value in the in/out cells for each control. I then moved the controls for the 3 trim axis and no values appeared in the in/out cells.  I then tried the calibration page and could calibrate the throttle, prop pitch and flaps but the 3 trim controls registered nothing in the in/out cells.

Ok, thanks - that confirms there is nothing strange in your ini preventing the trim axes being seen.

15 hours ago, Raceguy said:

I created another log file with the Debug text and it’s attached.

Thanks - I will take a look and get back to you. However, you now seem to be using LINDA as well....your previous logs do not show LINDA being used  - why have you suddenly added this into the mix?

 

[Raceguy]

Hi John

I have always used LINDA for Saitek panels and for access to its P-51 profile.  When I ran the log yesterday I forgot to name the LINDA files as unused. Do you want me to create another log with LINDA disabled? 

Thank you

Ed

 

[John Dowson]

26 minutes ago, Raceguy said:

Do you want me to create another log with LINDA disabled? 

Yes, please disable LINDA when generating logs for me.

Lets try cleaning the registry before the next test. First, take a backup of your current registry. Tun the windows Registry Editor application and take a registry backup (File -> Export...), remembering to select the All checkbox.

Next, disconnect your two DTA Rotary Encoder devices, and then download and run (i.e. double-click it in windows explorer) the attached file:  removeDTARotaryEncoders.reg

Then reboot and re-connect your devices. Then start FSUIPC7 and see if the trim rotaries are recognised, i.e. the axis assignment box sees them or not (you don't need MSFS running to do this, or anything else) - you won't see the trim assignments, but this is not important at the moment, just want to see if the those axes are recognised.

You can also attach the updated FSUIPC6.ini and FSUIPC6.log files after doing this and I will check them again.

John

 

[Raceguy]

Hi John

I'm working on this but don't know how to run FSUIPC6 without starting P3Dv4.5.  I've looked in the manual under "Programs: facilities to load and run additional programs" but I don't understand the process.

Would you please let me know how to run this?

Thank you

Ed

[John Dowson]

31 minutes ago, Raceguy said:

I'm working on this but don't know how to run FSUIPC6 without starting P3Dv4.5.  I've looked in the manual under "Programs: facilities to load and run additional programs" but I don't understand the process.

Would you please let me know how to run this?

No, sorry - you have to run P3D to use FSUIPC5/6. I mainly get support requests for FSUIPC7/MSFS these days and had switched to FSUIPC7 support mode - sorry about that.

John

[John Dowson]

oh - can you also calibrate the trim rotaries in windows calibration, after you have removed the reg entries and reconnected - this will ensure FSUIPC is getting the full value range.

 

[Raceguy]

Hi John

I opened the registry making a backup with ALL selected

I then disconnected the 2 DTA devices.

I then double clicked on the remove encoders file and rebooted. 

The 2 encoders were then reconnected.

I calibrated the 3 trim rotaries in Windows Calibration.  There are 6 axes on this board and all registered and calibrated fine.

I created a new FSUIPC6 by naming FSUIPC6.ini as FSUIPC6.ini.unused and renamed the 2 LINDA files with the .unused extension then started P3D. I added the Debug lines, saved the ini and closed P3D.

I restarted P3D and selected axis control on the logging page.

On the axis assignment page I moved all 3 trim axis and FSUIPC6 did not display any in/out values.

So, still no trim control action.

I really appreciate you sticking with me on this issue.

Thank you and take care

Ed

FSUIPC ini and log Gilbert.zip

[John Dowson]

Hi Ed,

I didn't think the registry cleaning would do much but it was worth a try.

It is difficult to see what is happening in that log file - I am going to provide a special build for you with additional logging as well as restricting the current logging to the device which has this issue (with joyId 2 and letter D in your original ini). Once I have supplied this build, please perform the same test - and let me know the order in which you are trying the trim controls, and make sure that you just move each control through its full range just the once, i.e. from min axis value to max and then back to min.

However, although I don't understand what has occurred at the moment, I can't see how this can be an issue with FSUIPC5 or FSUIPC6. As this was previously working, do you have any idea what could have changed? Were there any windows updates just before it stopped working?

John

 

[Raceguy]

Hi John

I look forward to trying the special build. 

Regarding Windows updates I have had them turned off for almost 2 years due to video driver problems.  My flight PC was a custom build in 2017 by Jetline Systems here in Florida and is only used for flight related programs. I have 3 video cards running 6 monitors.  The main card, a 1070, is fine but for the other 2 cards the latest drivers were rejected by Windows 10 due to their age since the cards have been discontinued.  I contacted Jetline and was told to reload to the previous working driver build to get those cards back online. At that point I blocked Windows updates.   I have been waiting for video card prices to drop so I can replace the 2 smaller cards.

Take care

Ed