BAW242

Thanks John, everything is working well now. Appreciate the help!

Thanks John, attaching latest files. Note that I have just recalibrated the X56 controllers using the Logitech guidance here https://support.logi.com/hc/en-gb/articles/360023194074-Recalibrate-controller-axes-RegEdit Because I was having a ghost input issue on the Throttle and one source said to try that. I guess that action may also have had an effect on my device IDs in FSUIPC. I have also been doing some work on the .ini file to bring over assignments from my old build, they were not on the original .ini file yesterday. Thanks David FSUIPC7.ini FSUIPC7.JoyScan.csv FSUIPC7.log

Hi,FSUIPC7.ini per attached I have a new build PC and just did fresh Windows and MSFS install, plugged devices in and created new .ini but there are multiple duplicates. Any idea how to resolve this? And why are some known as numbers and some letters? Thanks David [JoyNames] 0=Saitek Pro Flight X-56 Rhino Stick 0.GUID={DA420C30-BF82-11EF-8002-444553540000} 1=WINWING FCU-32 1.GUID={22FAE130-BF84-11EF-8003-444553540000} 2=Saitek Pro Flight X-56 Rhino Throttle 2.GUID={4E4E61D0-BF85-11EF-8007-444553540000} 3=Saitek Pro Flight X-56 Rhino Stick 3.GUID={36F9A260-BF85-11EF-8005-444553540000} 4=Bravo Throttle Quadrant 4.GUID={6342F1B0-BFA7-11EF-8001-444553540000} 5=TCA YOKE BOEING 5.GUID={6E68F2B0-BFA7-11EF-8002-444553540000} 6=Controller (Afterglow Gamepad for Xbox 360) 6.GUID={8ABFE450-BFA7-11EF-8003-444553540000} A=Saitek Pro Flight X-56 Rhino Stick A.GUID={DA420C30-BF82-11EF-8002-444553540000} B=WINWING FCU-32 B.GUID={22FAE130-BF84-11EF-8003-444553540000} C=Saitek Pro Flight X-56 Rhino Throttle C.GUID={4E4E61D0-BF85-11EF-8007-444553540000} D=Saitek Pro Flight X-56 Rhino Stick D.GUID={36F9A260-BF85-11EF-8005-444553540000} E=Bravo Throttle Quadrant E.GUID={6342F1B0-BFA7-11EF-8001-444553540000} F=TCA YOKE BOEING F.GUID={6E68F2B0-BFA7-11EF-8002-444553540000} G=Controller (Afterglow Gamepad for Xbox 360) G.GUID={8ABFE450-BFA7-11EF-8003-444553540000} FSUIPC7.JoyScan.csv FSUIPC7.log

Hi John - solved! It was the X56 button assigned directly in MSFS to Decrease Throttle to engage Reverse Thrust, something must have been corrupted at the MSFS end as the button seems to have been generating 4 separate inputs into MSFS (it actually froze my system when I went into the assignments and pressed it, I had to unplug the X56 to unfreeze it). So nothing to do with FSUIPC but FSUIPC logs helped me work it out...I am really sorry - my troubleshooting must have been flawed and perhaps when I tested FSUIPC I didn't actually select Reverse Thrust on that landing. I have removed this assignment and re-assigned as aircraft specific in FSUIPC and all is now working again. Thanks for your troubles. David

Hi John, I installed v7.4.8 and upgraded Fenix to their latest version, still getting same issue. I have cut the relevant section from the reduced log file below, the time from disconnecting A/P ay 600' to the time that I turned off the strobe and XPDR when exiting the runway. The Warning sounded from about half way through landing roll, 60-80kts during decel until I cancelled it using the mouse/virtual cockpit button. During that time I would have pressed a button on my X56 for Reverse Idle, it is programmed in MSFS as Throttle Decrease and not in FSUIPC. As you mention above, I have programmed the equivalent button on the Honeycomb using FSUIPC. I wonder if this Throttle Decrease command could be the culprit somehow. I will do more testing, eg. no reverse thrust, or removing the assignment in MSFS and adding it as an aircraft specific in FSUIPC. David 12426547 Button changed: bRef=0, Joy=0 (A), Btn=2, Pressed 12426547 [Buttons.Fenix A320 - Aer Lingus 'Old' EI-DEP (2005)] 24=PA,2,CPFNX320_Misc_Sidestick_AP_Disconnect_Captain_Button_Press,0 12426688 Button changed: bRef=0, Joy=0 (A), Btn=2, Released 12426688 [Buttons.Fenix A320 - Aer Lingus 'Old' EI-DEP (2005)] 25=UA,2,CPFNX320_Misc_Sidestick_AP_Disconnect_Captain_Button_Release,0 12478031 EV_KEYDOWN received: 0x6A (j) 12478031 KEYDOWN: VK=106, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0 12478031 .. KeyDown received from FS but not programmed 12478141 EV_KEYUP received: 0x6A (j) 12478141 KEYUP: VK=106, Waiting=0, Shifts=0, lparam=0 (0x0) 12478141 .. KeyUp received from FS but not programmed 12478594 EV_KEYDOWN received: 0x6A (j) 12478594 KEYDOWN: VK=106, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0 12478594 .. KeyDown received from FS but not programmed 12478703 EV_KEYUP received: 0x6A (j) 12478703 KEYUP: VK=106, Waiting=0, Shifts=0, lparam=0 (0x0) 12478703 .. KeyUp received from FS but not programmed 12501953 EV_KEYDOWN received: 0x6E (n) 12501953 KEYDOWN: VK=110, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0 12501953 .. KeyDown received from FS but not programmed 12502000 EV_KEYUP received: 0x6E (n) 12502000 KEYUP: VK=110, Waiting=0, Shifts=0, lparam=0 (0x0) 12502000 .. KeyUp received from FS but not programmed 12505500 EV_KEYDOWN received: 0x60 (`) 12505500 KEYDOWN: VK=96, Waiting=0, Repeat=N, lParam=0 (0x0), Shifts=0 12505500 .. KeyDown received from FS but not programmed 12505578 EV_KEYUP received: 0x60 (`) 12505578 KEYUP: VK=96, Waiting=0, Shifts=0, lparam=0 (0x0) 12505578 .. KeyUp received from FS but not programmed 12531328 Button changed: bRef=0, Joy=1 (B), Btn=18, Pressed 12531328 [Buttons.Fenix A320 - Aer Lingus 'Old' EI-DEP (2005)] 7=PB,18,CPFNX320_LIGHT_STROBE_OFF,0 12531469 Button changed: bRef=0, Joy=1 (B), Btn=18, Released 12531750 Button changed: bRef=0, Joy=1 (B), Btn=16, Pressed 12531750 [Buttons.Fenix A320 - Aer Lingus 'Old' EI-DEP (2005)] 9=PB,16,CPFNX320_Transponder_Mode_Knob_STBY,0

Thanks again John I’ll run another test at the weekend. Most of my axes are assigned directly in MSFS and they’ve always worked fine. I haven’t noticed any issue with the TO CONFIG button, it’s been assigned for a long time and works fine as designed during taxi out and is never touched again after that, but I’ll “fix” that too and see if helps.

No joy with this John, attaching latest .ini and log file from test filght today. It does look like a flap issue of some kind as altering the flap affects the warning. Today I landed Flap Full, spoilers extended normally, idle reverse selected, manual braking, then as exiting runway around 25 kts the warning started to sound. I then retracted flap to zero and the warning stopped momentarily then started again. Setting Flap 2 again stopped it (not 1+F interestingly). FSUIPC7.ini FSUIPC7log.zip

Thanks John I’ll give that a go. It could make sense that some kind of flap issue could be triggering the TO config warning and I have been messing about with flap axis on the new Honeycomb.

Thanks - .ini attached and re. the log, I have attached all the ones I can see as the up to date log seems to be my last flight (PMDG) so I am assuming not useful. D FSUIPC7.1.log FSUIPC7.1_prev.log FSUIPC7.ini FSUIPC7.log

Hi, looking for any guidance on how to troubleshoot this recent problem which appears to be linked to FSUIPC in some way. Several weeks ago I started getting TO config warnings after landing in the Fenix, I can't be certain what action is causing it (eg. selecting reverse thrust or stowing flaps) as the timing slightly varies each time - sometimes on the runway during decel and sometimes when vacating and cleaning up. After a process of elimination it seems to be FSUIPC linked as when I close down FSUIPC I don't have the issue. The problem seems to have started when I installed a new Honeycomb Throttle but this device is only used on my PMDG B737, I even disconnect the Honeycomb and still ge this issue (I use an X56 throttle for Fenix). Another strange aspect is that the warning starts when N1 is idle, at no point is N1 increasing and I thought it should only activate when advancing the throttle which I am not, and the ECAM shows this. Any ideas gratefully appreciated. David

Thanks John, and will do David

Can I just check is it normal on the A32NX FBW that the log is showing constant fast stream of axes and other entries per below? FPS performance of this aircraft is quite a bit below others including Fenix and I am wondering if this constant stream of apparent inputs is an error. Thanks David

Can I ask a question as a relevant novice - I have successfully mapped lots of controls for Fenix, PMDG and A310 using Presets and the mobiflight events.txt file but I can’t work out how to map multi position switches like A320/A310 Landing and Taxi lights. I can only have them mapped to discrete positions (On/Off, Take-Off/Off) when I want the HOTAS switch to mimic the mouse (eg first taxi light click goes from Off to taxi, next click Taxi to Take off). I used to do this in P3D by using the logger to spot the 5 digit ROTORBRAKE code that the mouse was doing then program that in. But it doesn’t seem to log anything in the Fenix or A310 when I use the mouse on these VC switches. any tips? thanks David

Brilliant thanks John David

John there are few new Events missing off the file like ECAM buttons, I can see them recently added on the Mobiflight website. will you do an updated Events file, or could you explain to a novice how to add them manually? eg 1 (>L:S_ECAM_FCTL) for pressing the FCTL button i did read the manual but couldn’t work it out! Thanks David