Connect a Winwing FMC/MCDU to FlyByWire A32NX in MSFS 2024 with SimAppPro, profile and SimBridge steps, plus blank-screen and input fixes.
To connect a Winwing FMC/MCDU to the FlyByWire A320neo in Microsoft Flight Simulator 2024, use the PC version, connect the unit by USB, install SimAppPro, select its FlyByWire A32NX integration profile, and run any bridge component that profile requires. Do not use the stock A320neo or A320neo V2 profile.
In Airbus terminology, the panel is an MCDU; the flight-management computers behind it are the FMGCs. Winwing and integration profiles will usually list the hardware as an MCDU rather than an FMC.
How do I set up the Winwing MCDU with A32NX?
The reliable method is to match the exact Winwing device, A32NX build and SimAppPro integration rather than assigning every button through MSFS Controls Options.
- Confirm PC compatibility. SimAppPro is a Windows helper application, so this connection method is for MSFS 2024 on PC. Plugging the unit into an Xbox Series X|S or PlayStation 5 does not provide the required aircraft connector.
- Install the correct aircraft. Use the MSFS 2024-compatible FlyByWire A32NX, not the default A320neo or A320neo V2. Follow our A32NX installation and aircraft-selection checks if both Airbus versions appear in the aircraft menu.
- Prepare the Winwing hardware. Connect it with a known data-capable USB cable, preferably directly to the PC while testing. Install SimAppPro, verify that it identifies the exact unit, and apply only firmware intended for that model. Our Winwing USB, firmware and profile setup covers the underlying device configuration.
- Select the FlyByWire profile. In SimAppPro, choose or install the integration specifically labelled for the FlyByWire A32NX and MSFS 2024. Select MCDU 1/captain or MCDU 2/first officer as appropriate. If SimAppPro offers to install a connector package, ensure it uses the active MSFS 2024
Communityfolder rather than an older MSFS 2020 installation. - Run the required connector. Some SimAppPro integrations communicate with A32NX directly; others require FlyByWire SimBridge. Install and run SimBridge through the FlyByWire installer only when the selected profile calls for it. The same external-display principle is explained in our guide to the A32NX remote MCDU connection.
- Load and power the aircraft. Start SimAppPro and any required bridge, launch MSFS 2024, then load the FlyByWire A32NX. Supply electrical power to the aircraft and confirm that the cockpit MCDU is alive before judging the hardware display. Test a page key, line-select key and scratchpad entry.
Which aircraft and platforms will work?
A Winwing unit works only when its integration supports the exact aircraft, simulator and hardware model being used.
| Configuration | Expected result |
|---|---|
| MSFS 2024 PC with FlyByWire A32NX | Works when SimAppPro provides a compatible A32NX profile or connector for the Winwing model. |
| MSFS 2024 PC with stock A320neo or A320neo V2 | The A32NX profile will not work correctly. Use an aircraft-specific integration if Winwing supplies one. |
| MSFS 2024 on Xbox or PS5 | The SimAppPro method is unavailable because the console cannot run the required Windows helper and connector. |
| Boeing-layout Winwing CDU | Do not assume compatibility with the Airbus A32NX. The exact device must appear in the profile's support list. |
Why is the Winwing MCDU screen blank?
A blank Winwing MCDU usually points to aircraft power, the wrong profile, a missing display connector or a blocked local connection.
| Symptom | Likely cause and fix |
|---|---|
| Hardware and cockpit MCDUs are both dark | Power the aircraft first. A cold-and-dark A32NX will not provide an active MCDU display immediately. |
| Cockpit MCDU works, but hardware is blank | Check that the A32NX display integration or required SimBridge process is running. Confirm the captain/first-officer unit selection and allow the local connection through the Windows firewall rather than disabling the firewall. |
| Display works, but buttons do nothing | Reinstall or re-enable the SimAppPro input connector and confirm that the A32NX profile, not a generic Airbus profile, is active. Run MSFS and its helper applications at the same Windows privilege level. |
| Each press registers twice | The same control is probably assigned in both SimAppPro and MSFS. Remove the duplicate MSFS assignment or create a clean device profile. |
| SimAppPro cannot see the unit | Try another data-capable cable and a direct motherboard USB port. Avoid an unpowered hub during diagnosis, then recheck the device and firmware pages. |
| It worked in MSFS 2020 but not MSFS 2024 | The connector may be installed in the wrong Community folder, or the selected profile may support only MSFS 2020. Repoint or reinstall it only if Winwing lists MSFS 2024 compatibility. |
Should I bind every MCDU key in MSFS?
No—generic MSFS control assignments cannot provide the MCDU screen data and may not expose every aircraft-specific key.
Let the dedicated A32NX integration handle the display, line-select keys, scratchpad and function keys. Use an MSFS control profile only for inputs the integration explicitly leaves unmapped, and keep it free of duplicate assignments. Our A32NX profile and conflict checks explain how to isolate ignored or repeated inputs.
What should I check after an A32NX or SimAppPro update?
After an update, verify that the A32NX profile still recognises MSFS 2024 and that its connector remains in the active simulator installation.
- Confirm SimAppPro still detects the exact Winwing model.
- Check that the selected aircraft remains FlyByWire A32NX rather than A320neo V2.
- Reapply the connector only if the integration reports it missing or the
Communitylocation changed. - Restart SimBridge when the profile requires it, especially if its executable was replaced and Windows asks for firewall permission again.
- Do not run several MCDU connectors simultaneously; competing integrations can produce duplicate presses, stale displays or an incorrect MCDU side.