Raceguy

Hi John I have reactivated FSUIPC6 in P3D and all 3 trims are working!! I have set them for the correct action and calibrated and it looks like I'm back in business. I'll keep working on the sim and let you know if the issues return. I can't thank you enough for all of the time and patience you have put into getting this resolved. Take care Ed

The pots I use have a plastic stop inside that can break if the end of the axis is hit too hard. Because of this I was watching the W10 joystick window so I could see when I was approaching the end of the 10 turns. Because of this I didn't notice the device number and axis letter in the assignments. Just now I cleared the FSUIPC7 ini and log files and ran the program again this time focused on the assignment screen. I used the same control order of rudder, then aileron and finished with elevator trim, min, max, min through 10 turns. There was a very slight hesitation, a fraction of a second, when I first turned each pot but all 3 registered the device number and axis letter and the in/out ranges showed the values from one end to the other. This is the first time I have seen any movement for the elevator trim. I have attached an updated log file. I hope this helps. Ed FSUIPC7 Gilbert log file second run.zip

Hi John I didn’t think to look on the system tray to start FSUIPC7, sorry. Just ran FSUIPC7 setting logging at x1000. Opened the assignment panel to axis and rotated all 3 trim pots. I started with the rudder, then aileron and finished with elevator trim. Each pot was turned from min to max and back to min before moving on to the next pot. (these pots are 10 turn units.) I then closed FSUIPC7. I have attached the log file. Thank you again for your help and patience. Take care Ed FSUIPC7 Gilbert log file.zip

John, sorry but I'm stuck again. I ran the 7.exe as admin, which is how I run all programs, and it created a log, ini and joyscan file but can't see how to get to the logging and assignment tabs to perform the test. I looked for a v7 folder with the manual like I have for v6 but don't see one. I ran the exe again thinking that may start the program and it said FSUIPC7 was already running. Sorry to be a pain. Ed

Got it, thanks Ed

Just to be sure, when you say same test do mean all of this or just send you the log v7 will create? registry making a backup with ALL selected disconnected the 2 DTA devices. double clicked on the remove encoders file and rebooted. reconnect 2 encoders calibrated the 3 trim rotaries in Windows Calibration. move each of the 3 axes through their full range (from min to max and back) with the assignments panel open. And let me know the order in which you tried them

Thanks for the files and explanation John. I'll run the program and get you the results. Also thanks for the comment about my pit. Wife said I could retire early but I had to find something to keep me busy. This started in 2015 and initially took 2 1/2 years but I've added several updates since then. Take care Ed

Will running the v7 .exe remove v6 or do I need to do something else to v6 to stop it's action? From yesterdays post you said FSUIPC7 can be run without MSFS. Is that true for P3D? I just want to provide you the best information. Thanks Ed

Hi John Just to check this file says version 7 and I'm running P3D and FSUIPC6. Is it compatible? Thanks Ed

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

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

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

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

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

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

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

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

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

OK, they went through this time. FSUIPC6.ini FSUIPC6.log

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.

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

That's fantastic! Thank you very much! Take care Ed

Hi Pete Thanks for the reply. The 2D panels in the A2A planes open off to the left side of the screen which is also blocked by my frame. Using information I found in the SDK I opened Panel.cfg with Notepad++ and changed the window positions so they open more central and in the same place each time. Well, my wife has said many times that I can take something simple and make it complicated. I appreciate your looking into the change but if that is a change you don't want to make I understand. Thanks again for a great program! Take care Ed

Hello Thank you for a GREAT program. I could not have setup my pit without it! I have been running FSUIPC for many years and I'm now using FSIUPC5 with P3Dv4 in my home cockpit with great success. The picture below shows my pit from a slightly higher viewpoint than my actual view. When FSUIPC opens it appears in the middle of my screen and is blocked by the top of my windshield frame. That may not sound like a big deal but when you reach my age scrunching down to see the window, especially when setting up new planes or just making changes, it is uncomfortable. I have to grab the popup and drag it to the bottom of the screen for viewing each time. Ideally I would like it to open at the bottom of the screen in the center. I have moved some 2D popup's in FSX and P3D to a preferred location but I can't find a way to relocate FSUIPC5. Is this something that I can change to save my old back? Thank you again for this program Ed Raceguy