Set up the Winwing FCU in MSFS 2024 with SimAppPro, the right aircraft profile, clean bindings and fixes for blank displays or dead controls.
To set up the Winwing FCU in Microsoft Flight Simulator 2024 on PC, connect it by USB, install and run SimAppPro, update the device firmware if prompted, activate the profile for your exact Airbus add-on, and remove duplicate MSFS bindings. Keep SimAppPro running so the displays and annunciators receive aircraft data.
This is primarily a Windows PC setup because the FCU depends on companion software for aircraft data. Connecting it directly to an Xbox Series X|S or PlayStation 5 will not provide the full SimAppPro integration used for displays, lights and aircraft-specific commands.
Winwing FCU setup steps for MSFS 2024
The reliable setup sequence is to establish the hardware connection first, activate the correct aircraft integration, and only then deal with in-simulator bindings.
- Install SimAppPro. Use the software package intended for the FCU and restart Windows if its installer requests it. Run the application at normal user level rather than launching either it or MSFS as administrator.
- Connect the FCU directly. For the first setup, use a motherboard USB port and a known data-capable cable rather than an unpowered hub. Confirm that SimAppPro recognises the device.
- Check the firmware. Apply an update when SimAppPro identifies a required or compatible firmware release. Keep the USB connection stable and never disconnect the panel during an update.
- Select MSFS 2024 and the exact aircraft. If SimAppPro separates MSFS 2020 and 2024, choose the 2024 target. Activate the preset for the specific Airbus model or add-on you intend to fly; visually similar A320 variants can use different internal events.
- Remove competing assignments. In MSFS Controls Options, inspect the FCU if it appears as a controller. Create a clean custom profile and retain only assignments required by the active SimAppPro preset.
- Load a powered aircraft and test. Leave SimAppPro open, start MSFS 2024 and load the supported aircraft in a ready-to-fly state. Turn the speed, heading and altitude knobs, then test their push and pull actions against the virtual FCU.
The FCU has encoders and switches rather than conventional flight-control axes, so it normally does not need joystick-style centre or range calibration. For firmware, device detection and profile principles shared with other panels, see our broader Winwing hardware setup workflow.
Should the FCU be bound in MSFS or SimAppPro?
Use the supported SimAppPro aircraft preset for full integration, then keep the MSFS controller profile free of conflicting automatic assignments.
Some presets send aircraft-specific events directly, while others expect selected in-simulator bindings. Follow the requirements shown by the active preset rather than mapping every FCU button to generic autopilot commands. Our explanation of custom profiles, input scanning and binding conflicts in MSFS 2024 covers the controls interface itself.
Manual MSFS assignments are a fallback for an aircraft without a dedicated preset. They can make knobs and buttons operate, but generic assignments usually cannot keep the FCU displays and annunciators synchronised. Running another input bridge alongside SimAppPro can also produce duplicate commands.
Does the Winwing FCU work with every MSFS 2024 Airbus?
No; complete operation depends on an aircraft-specific integration being available in the installed SimAppPro release.
The default Airbus, different A320neo implementations and third-party Airbus add-ons are separate software targets even when their FCUs look alike. Choose the preset by aircraft developer and model, not simply by the word Airbus. If the aircraft is absent from the supported list, expect manual controls to be possible but display feedback, managed-mode indications or button lights to be incomplete.
Why is the Winwing FCU blank or not responding?
A blank or unresponsive FCU usually points to a missing data connection, an unpowered virtual cockpit, the wrong aircraft preset or duplicate bindings.
| Symptom | Likely cause | Fix |
|---|---|---|
| FCU is absent from SimAppPro | USB cable, port or firmware communication problem | Reconnect through a direct USB port, try another data cable and establish stable detection before attempting firmware work. |
| Buttons work but displays stay blank | Windows sees the controls, but SimAppPro is not receiving aircraft data | Keep SimAppPro running, select the correct aircraft preset and test with the virtual aircraft powered. |
| Values move twice or jump rapidly | The same encoder is assigned through both MSFS and SimAppPro | Clear automatic MSFS assignments and use one integration path. |
| Push and pull actions are reversed or ignored | Generic autopilot events or the wrong aircraft profile are active | Load the aircraft-specific preset and remove substitute keyboard or autopilot bindings. |
| It works in one Airbus but not another | The aircraft use different internal variables | Switch to the preset made for the aircraft now loaded; do not reuse another Airbus profile. |
If the software still fails to connect, close both applications, reconnect the FCU, open SimAppPro and then launch MSFS 2024. Run both programs with the same Windows privilege level. A ready-to-fly aircraft is better than a cold-and-dark start for diagnosis because it removes electrical power from the list of possible causes.
How do I test the FCU push-pull modes?
Check that turning a knob changes its selected value, pulling it engages the selected Airbus mode, and pushing it requests the corresponding managed mode where the flight plan permits that mode.
Dashes or a managed-mode dot can be normal Airbus indications rather than a display fault. Our guide to Airbus FCU controls and managed versus selected modes explains what the virtual cockpit should show.
If the hardware and on-screen FCU agree but the aircraft still refuses to capture speed, heading or altitude, the setup may be working correctly and the problem may instead be the flight plan, flight-director state, throttle detent or active autopilot mode. Use these A320 autopilot and autothrust checks before remapping the panel again.