Set up the FlyByWire remote MCDU for the A32NX or A380X in MSFS, connect a tablet or phone, and fix blank pages and network errors.
To use the FlyByWire remote MCDU in Microsoft Flight Simulator, install and run SimBridge, load and power the A32NX or A380X, then open the MCDU web address in a browser. Use localhost on the simulator PC, or the PC's local IPv4 address from a phone or tablet on the same network.
FlyByWire remote MCDU setup
The remote MCDU needs a supported FlyByWire aircraft, the separate SimBridge application and a web browser; installing the aircraft alone does not expose the browser interface.
- Install or update the aircraft and SimBridge. Use the FlyByWire Installer to keep the A32NX or A380X and SimBridge compatible. SimBridge is an external application, not something placed manually in the Community folder.
- Start SimBridge. If Windows Firewall asks for permission, allow it on trusted private networks. Public-network access is unnecessary.
- Load and power the aircraft. Start Microsoft Flight Simulator, select the FlyByWire A32NX or A380X and wait for the aircraft to initialise. Establish electrical power so the cockpit MCDU is operating.
- Open the local MCDU page. Use the address displayed by SimBridge. With its default port, the direct same-PC address is usually
. If SimBridge shows a different port or landing page, follow the address it provides. - Connect another device. Replace
localhostwith the simulator PC's local IPv4 address. For example, if the PC is192.168.1.25, enteron the phone or tablet. - Select the correct aircraft or unit. If the browser interface presents a choice, select the MCDU belonging to the loaded A32NX or A380X.
You can find the PC's local address by running ipconfig in Windows and reading the IPv4 address for the active Ethernet or Wi-Fi adapter. Ignore addresses belonging to VPNs, virtual adapters or disconnected connections. A PC connected by Ethernet and a tablet connected by Wi-Fi can still communicate if both are on the same normal home network.
How do you use the remote MCDU after connecting?
The browser becomes another control head for the live aircraft MCDU rather than a separate flight-management computer. Button presses affect the aircraft immediately, and changes made in the cockpit appear in the remote display.
Enter the route, procedures and performance data exactly as you would in the cockpit. Our step-by-step Airbus MCDU programming workflow covers the usual INIT, F-PLN and PERF sequence, including how to check discontinuities.
The A32NX and A380X do not have identical page layouts, so follow the pages presented by the loaded aircraft rather than expecting every key or prompt to match. Avoid entering data from the cockpit and remote device simultaneously, as duplicated key presses are easy to miss.
Does the remote MCDU replace the EFB or SimBrief?
No. The remote MCDU only displays and controls the aircraft's MCDU; it does not replace the flyPad/EFB, configure SimBrief or create an independent flight plan.
For the A32NX, our explanation of how the flyPad and cockpit systems divide their tasks shows where payload, ground-service and tablet functions belong. If you want imported operational data, you must separately configure SimBrief for the A32NX or A380X.
A common mistake is assuming that a plan visible in the EFB proves the remote MCDU is configured correctly. These are separate connections. If the remote screen and keys respond but a route, SID or STAR is missing, investigate the aircraft's flight-plan import, navdata and MCDU entries rather than the local network.
Why is the FlyByWire remote MCDU not working?
Most failures can be isolated by testing the local browser address first and only troubleshooting the network after it works on the simulator PC.
| Symptom | Likely cause and fix |
|---|---|
ERR_CONNECTION_REFUSED or site cannot be reached | SimBridge is stopped, the port has changed or the URL is wrong. Start or restart SimBridge and use the exact address it displays. Enter http://, not https://. |
| Works on the PC but not on a phone or tablet | Do not use localhost on the second device; that points back to the device itself. Use the PC's IPv4 address, allow SimBridge through the private-network firewall and avoid guest Wi-Fi, which commonly blocks communication between devices. |
| Page opens but the MCDU is black | Confirm that the FlyByWire aircraft is loaded, initialised and electrically powered. The remote interface does not support a stock Airbus merely because its cockpit has a similar MCDU. |
| Display is frozen or buttons have no effect | Refresh the browser once, then restart SimBridge if necessary. Update the aircraft and SimBridge together; mismatched builds and switching between the A32NX and A380X without reconnecting can leave a stale session. |
| Connection drops after the tablet sleeps | The browser or Wi-Fi connection has been suspended. Wake the device and reload the page; keeping the screen awake during MCDU entry prevents repeated reconnections. |
If the local address also fails, changing router settings will not help: fix SimBridge, its port or the aircraft session first. If local access works, concentrate on the PC's active IPv4 address, firewall permission and network isolation. Do not disable the firewall or forward the SimBridge port to the internet.
Can you use the FlyByWire remote MCDU on consoles?
No. This workflow requires the PC versions of the FlyByWire aircraft and the SimBridge executable. Xbox and PlayStation versions of Microsoft Flight Simulator cannot run SimBridge or PC Community-folder packages, even if the remote browser itself is on a phone or tablet.