FSUIPC 6.1 no longer functioning in PMDG NGXu

[tgroth]

Hello, 

    Purchased  new Jetline computer and completed my set up of  fsuipc for the PMDG 737 in P3Dv5.2. All controls worked flawlessly for a week. Today my yoke, rudder pedals, and Jetmax 737 TQ are not functiong with in the PMDG virtual cockpit. I use the following programs; Prepar3D_v5_Professional_5.2.22.27615, GSX Level 2 version 2.9.4 , ActiveSky P3D For Prepar3D v5 build 7877,Active Sky Cloud Art , and PMDG 737 NGXu. FSUIPC is registered. Simply cannot live with out my FSUIPC any help greatly appreciated.

FSUIPC6.1.log FSUIPC6.ini FSUIPC6.JoyScan.csv

[John Dowson]

There is a strange error relating to your JetMAX 737 TQ, but it was still acquired for use:

Quote

      875 Product= <not readable at this time: maybe device disconnected?>
      875    Vendor=1FD1, Product=0600 (Version 1.2)
      875    GUIDs returned for product: VID_1FD1&PID_0600:
      875       GUID= {96151C00-1F85-11EC-8003-444553540000}
      875       Details: Btns=9, POVs=(0, 0, 0, 0), Cal=x00000000, Max=R744,U710,V768,X0,Y0,Z705
 

Your controllers are also ON in P3D (and you are using RawInput):

Quote

906 Controllers are set to ON, using RawInput within P3D

If you don't have any assignments in P3D, best to turn of controllers there, and also use the default DirectInput.

You should also switch to using JoyLetters, so please set the AutoAssignLetters ini parameter to Yes.

Your  profile section should also be changed from:

Quote

[Profile.737NGXu]
1=PMDG 737-800NGXu PMDG House Blended Winglets (N738BW | 2019)
2=PMDG 737-79PNGXu SSW Southwest Airlines Tennessee One (N922WN) || 2020
3=PMDG 737-700NGXu BW Southwest Airlines (N200WN | 2019 | Heart)
4=Lockheed Martin F-35A Lightning II
5=PMDG 737-700NGXu BW Southwest Airlines (N205WN | 2017 | Heart)
6=PMDG 737-700NGXu BW Southwest Airlines (N210WN | 2019 | Heart)
7=PMDG 737-700NGXu BW Southwest Airlines (N238WN | 2010 | Canyon Blue)
8=PMDG 737-700NGXu BW Southwest Airlines (N7734H | 2013 | Canyon Blue)
9=PMDG 737-700NGXu SSW Southwest Airlines (N284WN | 2019 | Canyon Blue)
 

to

Quote

[Profile.737NGXu]
1=PMDG 737-800NGXu
2=PMDG 737-79PNGXu
3=PMDG 737-700NGXu
4=Lockheed Martin F-35A Lightning II

This will then match all the different versions of the 737, so that you don't have to add them again if you change liveries.

Please make the above changes. Also, disable all logging except for Buttons & Keys and Events. Then try again - load an aircraft and press one if your assigned buttons on each device, then exit and show me your updated  FSUIPC6.ini and FSUIPC6.log files.

John

[John Dowson]

Also, check your USB power management settings - make sure they are not set to power off....

[tgroth]

John,

 Updated  FSUIPC6.ini and FSUIPC6.log files you requested after changes made.  The control inputs such as buttons, flaps, yoke or rudder pedals continue not to function.

FSUIPC6.ini FSUIPC6.log

[John Dowson]

55 minutes ago, tgroth said:

Updated  FSUIPC6.ini and FSUIPC6.log files you requested after changes made.

Ok - you didn't update your profile section, but that is not that important.

The log you posted shows:

1. When you pressed button 0 on your yoke, this sent the PARKING_BRAKES control, as assigned:

Quote

   213922 Button changed: bRef=0, Joy=2 (C), Btn=0, Pressed
   213922 [Buttons.PMDG 737-700NGXu BW Southwest Airlines (N200WN | 2019 | Heart)] 13=RC,0,C65752,0
   213922 Repeating flag set: bRef=0, Joy=2, Btn=0 (RepeatDelayCtr=1)
   213922 FS Control Sent: Ctrl=65752, Param=0 PARKING_BRAKES
   213922 *** EVENT: Cntrl= 65752 (0x000100d8), Param= 0 (0x00000000) PARKING_BRAKES
 

However, note that you have set this assignment to repeat - you almost certainly don't want this on Parking Brake control.

Button 4 on your yoke is also sending the assigned control:

Quote

   255453 Button changed: bRef=0, Joy=2 (C), Btn=4, Pressed
   255453 [Buttons.PMDG 737-700NGXu BW Southwest Airlines (N200WN | 2019 | Heart)] 8=RC,4,C65971,0
   255453 Repeating flag set: bRef=0, Joy=2, Btn=4 (RepeatDelayCtr=1)
   255453 FS Control Sent: Ctrl=65971, Param=0 THROTTLE2_DECR
   255453 *** EVENT: Cntrl= 65971 (0x000101b3), Param= 0 (0x00000000) THROTTLE2_DECR

So it looks like the button assignments on your yoke are working. Are the yoke axis working?

2.  I don't see any other Button changed messages logged.  Did you try any buttons on your other devices? If so, FSUIPC is not seeing these. 
If you go into the buttons assignment dialog, does this recognse the buttons on those devices? How about the axis assignment dialog?
Maybe you can show me your FSUIPC6.JoyScan.csv file.

17 hours ago, tgroth said:

All controls worked flawlessly for a week. Today my yoke, rudder pedals, and Jetmax 737 TQ are not functiong

What changed during this period?

I see that you have also assigned your axis with 'Direct to FSUIPC Calibration'. Lots of folks have issues assigning this way with PMDG aircraft due to priority levels - it is usually better to assign to the FS control instead.

You could also try switching your devices USB ports (and maybe change from USB3 to USB2 id that is relevant and possible).

It may also be worth trying to initially configure with a stock aircraft as well, just to check if you can assign your devices in a nin add-on a/c.

John

P.S. Also try rebooting first, if not done already!

[John Dowson]

Oh - and  I see that you have installed FSUIPC6 in your Documents folder:

Quote

   Reading options from "C:\Users\Timothy\Documents\Prepar3D v5 Add-ons\FSUIPC6\FSUIPC6.ini"

I have seen this cause some strange issues, although I don't fully understand why and don't think it is related to your issues. But better if you can re-install into a different, non windows-protected, such as C:\FSUIPC6 (no need to re-register). You will need to copy across your files (FSUIPC6.ini, FSUIPC6.key, any luas, macros or dlls, etc) from the old folder to the new one after re-installation.

John

[tgroth]

Hi John,

         

1. When you pressed button 0 on your yoke, this sent the PARKING_BRAKES control, as assigned:

  Its actually assigned to turn off autopilot. This is yet another new anomaly.

 2 So it looks like the button assignments on your yoke are working. Are the yoke axis working?

 Non of the yoke buttons are working as originally set up, The only axis that is functioning is the rudder pedals and that is intermittent at best

 3 I don't see any other Button changed messages logged.  Did you try any buttons on your other devices? If so, FSUIPC is not seeing these.

 Yes the auto throttle cut off switch is on the Jetmax TQ just as in the actual 737, It no longer works. 

4 What changed during this period?

  MS Windows 10 updates and the addition of some FlyTampa scenery, The computer is used exclusively for flight simulation and only P3Dv5,2 is installed

5 It may also be worth trying to initially configure with a stock aircraft as well, just to check if you can assign your devices in a nin add-on a/c.

   My throttle, yoke and rudder pedals where working with the default F 35

6 P.S. Also try rebooting first, if not done already!

   Yes done on multiple occasions

7 Oh - and  I see that you have installed FSUIPC6 in your Documents folder:

  I did not change the installation destination that is where I found it, yes kinda odd.

John as a user of Multiple variants of FSUIPC I can say this process of setting this new computer up has been exhausting for FSUIPC is not the only program that has been an issue. ChasePlane took a Jetline representative  to remote in and after 45 minutes determined it was a keyboard issue. That worked for 3 days and the same issue resurfaced. After disconnecting my flight peripherals and adding them back one by one I isolated the issue to the Jetmax TQ-specifically to the fuel cut off lever. No more issues with ChasePlane and I got a new shinny keyboard. I have 3 FlyTampa scenerys  installed and Boston causes a CTD everytime I use it. the other two work with out issue.  George from FlyTampa has been able to provide little insight. I have had this computer for 5 weeks and yet have I flown a virtual revenue flight in my 737. Thank you soooo much for your input it is greatly appreciated sir. Enough ranting back to work on fixing this issue 

 

 

 

 

   

[John Dowson]

16 hours ago, tgroth said:

1. When you pressed button 0 on your yoke, this sent the PARKING_BRAKES control, as assigned:

  Its actually assigned to turn off autopilot. This is yet another new anomaly.

There are no assignments to any button to turn off the autopilot - unless you are doing this assigned to a keypress. If that is the case, then please let me know which assignment?

Could it be that your device ids have changed? Looking at your ini axis assignments, you have aileron and elevator axis assigned to device A, which is your throttle, and throttle to device C, which is your Yoke (B is rudder), so try switching those devices by changing your [Joynames] section to:

Quote

[JoyNames]
AutoAssignLetters=Yes
0=JetMAX 737 Throttle
0.GUID={96151C00-1F85-11EC-8003-444553540000}
1=Pro Flight Cessna Rudder Pedals
1.GUID={5F850FB0-1F85-11EC-8001-444553540000}
2=Pro Flight Cessna Yoke
2.GUID={5F94C720-1F85-11EC-8002-444553540000}
C=JetMAX 737 Throttle
C.GUID={96151C00-1F85-11EC-8003-444553540000}
B=Pro Flight Cessna Rudder Pedals
B.GUID={5F850FB0-1F85-11EC-8001-444553540000}
A=Pro Flight Cessna Yoke
A.GUID={5F94C720-1F85-11EC-8002-444553540000}
 

Let me know how it goes with that change, and any issues please show me your updated .log and .ini files.
Note that this will invalidate any assignments recently made to thos devices, so you may wish to remove or update them manually (by changing the joy letters used in the assignments).

John

Edited October 21, 2021 by John Dowson
Further info added