Winwing / WINCTRL MCDU, CDU, PFP3N, PFP4/7 - Configuration & Troubleshooting - User-To-User Support Thread

User Support Hub Hardware & Peripherals
, , , , , ,
142

Thanks Dave, but no that wasn’t working at all. It would only display “Ticket 0/0” after logging in and nothing was clickable. Could not even open the live chat window, nothing was happening.

I did however get it sorted thanks to the Winctrl discord, so I’ll post this here in case it helps anyone else.

Whatever store you are logged into at the time, either regional or global. Log out.
Select a different store, in my case I logged out of Canada and into Global, then log in again.
This time my ticket was there and I was on my way again.

143

I was informed it is not compatible. I found a solution using a SPAD profile,

144

Yeah, took me a while to figure out how to set it up. Once you have done the calibration, open the sim and create an empty profile for the Minor+PAC then close the sim and go back to SimApp Pro. Now you can go to key bindings for that device and download the WinWing mapping profile, select the profile you made in the sim and click run. All works now…

145

That worked perfectly thank you so much! I now have a fully working Fenix with the Ursa :smiling_face:

And actually you also alerted me to the fact I didn’t have my install paths set up on Simapp pro either as initially I wasn’t even seeing any options to download keybindings.

Does this work for all aircraft or just certain ones like Fenix?

I started going down the spad route but it seems to lag a bit on my PC plus you don’t get the force feedback of Simapp pro and my mcdu doesn’t seem to work without it either.

So if possible I would rather try and stick with Simapp for everything if possible.

147

Chiming in

Developed this issue this week alone. Buttons stop working, screen always working and mirroring. Using Mobi exclusively.

After 10-30 minutes buttons go dead. Simapp and firmware up to date. Power Plan has USB power save OFF. USB direct to Mobo.

Although I can recover without a unplug and plug back in by running simapp. When Simapp launches the MCDU doesnt show then all the sudden connects.

Windows doesnt give me a disconnect or any other warning prior to my buttons going dead. completely lost on what to do because i didnt change any configurations prior to this issue appearing.

148

I have the same issue. I can reproduce it when using multiple WINCTRL devices, including the MCDU. The MCDU buttons stop working after 5–30 minutes, while the display and lights continue to work. The only reliable fix is disconnecting/reconnecting the MCDU USB cable.

I spent a lot of time testing different combinations of software, including MobiFlight, and also tried eliminating SimAppPro entirely and using only MobiFlight. I also tried using HidHide, I selected “Inverse application cloak” then only selected Mobiflight, but the issue still occurred.

I found that I can also recover the MCDU by running the following from an Administrator Terminal:

pnputil /restart-device "USB\VID_4098&PID_BB36\8465C121C7707032D4362012"

I also noticed that Windows exposes the MCDU as a game controller, with two axes corresponding to the MCDU’s light sensors. When the buttons stop working, these axes also stop updating. I was considering writing a watchdog script to monitor the axes and automatically run the pnputil command when they freeze.

I’m using the latest SimAppPro and firmware versions.

I opened a support ticket with WINWING and provided the following:

My MCDU-32 buttons stop working after a while. I’m using MSFS 2024 with the Fenix A320. I’ve used the MCDU for many months without issue, but recently purchased the WINCTRL FCU. Now, when both the MCDU-32 and FCU are connected, the MCDU buttons stop working after a while.

Firmware V1.04, SimAppPro 1.17.3.

The MCDU display and lights continue to work. Only the buttons stop responding. Disconnecting/reconnecting the USB cable fixes the issue, but it reoccurs frequently.

WINWING initially responded:

“Our software team has noticed this issue, and are working on it. Please wait for future firmware update.”

I asked whether it was being treated as a high-priority issue and whether they could provide a rough timeframe.

Their latest response was:

“Our tech team will issue the new firmware update recently.”

So it appears to be a known WINCTRL firmware issue, and a firmware update is apparently being prepared.

149

Looks like a firmware update was released today. If anyone has the opportunity to check it out I’d be interested to know if this is resolved.

150

I just installed the new MCDU-32 firmware V1.06. After upgrading the firmware the MCDU didn’t work at all, it just said “Winctrl” on the screen. I noticed in the Environment Check page in Simapppro that SimLogic was not running, so I clicked the button on that page to start it and it started working again.

I fired up MSFS 2024 + Fenix A320 with both my MCDU & FCU connected and left unattended for 30 minutes, and the buttons are still working afterwards, so that is looking promising.

152

Got the Moza MB7F FCD yesterday. It isn’t working.

Getting “Waiting for Game Data” on the screen. Moza thinks it’s a SU6 issue and says they’re looking into it. Lesson is buyer beware with these Chinese companies. Moza has at least been somewhat responsive, but how you even ship a product that just doesn’t work at all is mind boggling to me. I’ve been simming, flying and racing, for over a decade and have never had so many issues with peripherals.

EDIT: Took about a week but Moza has fixed the issue and things are working well. Can recommend the MB7F for anyone looking for a WINCTRL alternative.

153

FS 2020 with PMDG. Installed firmware 1.6 and simappro version 1.17.4 and PFP 3N would not show PMDP FMC. Once im in the cockpit i have to power cycle the PFP 3N and after power cycle it shows the FMC but i still get a red error 12. Since Winwing changed to Winctrl its going downhill…

154

Does anyone have the Winctrl Tiller? I just received mine. With the FBW A32NX I use the FCU, EFIS L and MCDU for a long time without any issues. Now with the Tiller connected, it’s the only thing communicating to the sim (MSFS2024) , the MCDU, FCU and EFIS go dark and not responding. As soon as I disconnect the Tiller, they light up and work normal again. I’ve ruled out USB ports, cables and power issues. Last night I loaded a default Airbus 320 (Inibuilds?) and all is working except the MCDU, but reading back in this thread that seems to be “normal” for that plane…

Winctrl support is, what can I say,… working their scripted response. But no, I won’t replace my motherboard (yes I’m serious)

155

Below is a copy/paste from the first post in this thread. Please do this for all WinCtrl devices.

External devices used with MSFS 2020/2024 should ideally be connected through a powered USB hub. Also, make sure your system power plan is set to High Performance.
Lastly, you should disable power saving for MCDU, PFP3N,7,4. Press Windows + R, then copy and paste this command:

explorer shell:::{A8A91A66-3A7D-4424-8D24-04E180695C7A}

press ENTER.

Then, double-click Winwing PFP-3N and in the new window go to the Hardware tab. Select USB Input Device and click Properties.

image
image586×275 11.6 KB

In the new window, go to the Power Management tab and uncheck “Allow the computer to turn off this device to save power”.

image
image576×229 8.42 KB

Click OK and restart PC.

Repeat this for all the devices you use with MSFS 2020 and 2024.

156

Thanks Ten,

I double checked just in case but all of that I already did earlier.

In the meantime I did get a result though. I thought I would check again and disconnected one by one each Winctrl device separately (I have 5 in total) and when I got to the MCDU, , the others came back online. When reconnecting the MCDU, all stayed on including the MCDU! .

After ending and going back to the main menu, subsequently starting a new flight I expected the same workaround was necessary but no, everything worked normal!?

I remember now that at the same time I received the Tiller and fired up SimApp , there was a MCDU firmware update.

Maybe it needed a hard reset of some sort by disconnecting while online but what the heck.

While I suspected the NWS Tiller, it actually was the MCDU knocking the rest out.

Whatever it was, I did a successful flight in the FBW so I’m happy now. Thanks for the suggestions regardless

157

@PH051 Thanks for the detailed update and for sharing what helped.

WinCtrl recommends disconnecting all other devices before every firmware update. Only the keyboard, mouse and the device being updated should be connected. So if you had never disconnected the other devices before and only did it this time, that may be exactly why it worked.

158

Yeah I did have only mouse & keyboard connected during the fw update, That was not the issue in my case. Apparently it needed a disconnect during the sim connection. I know it makes no sense.

159

Hi everyone,

I received my Winctrl 32 RMP and could not get it work. Other Winctrl hardware works (e.g. 32 AGP Metal). I tried every inbuild A32* in MSFS 2020, every inbuild A32* in MSFS 2024, also FlyByWire MSFS 2024 - no luck. Only A330 in MSFS 2024 showed digits on the Winctrl 32 RMP but rotating the knob did not change anything and other buttons actions did not mirror in the in-game aircraft.

I updated SimAppPro, updated Winctrl 32 RMP firmware - nothing helped. Testing in SimAppPro works - I press buttons and it is shown in the Testing tab / control map of SimAppPro .

Would appreciate recommendations.

160

For the FBW A32NX, you need to install SimBridge and make sure it is running in the background. Without SimBridge running, the WinCtrl 32 RMP won’t communicate with the aircraft.

161

Yes! It is running. Still no 32 RMP communication though.