Connect Hoppie ACARS to Microsoft Flight Simulator: enter the logon code, set your flight ID, use CPDLC, and fix common connection errors.
To connect Hoppie ACARS to Microsoft Flight Simulator, obtain a personal Hoppie logon code, enter it in a supported aircraft’s EFB or CDU, or in a compatible external ACARS client, set the correct flight ID, then log on to an active CPDLC station. External clients may also require SimConnect; Hoppie does not supply controllers.
Hoppie is an independent simulation data-link network rather than a feature built into Microsoft Flight Simulator 2020 or 2024. The aircraft or companion software must explicitly support it. A generic ACARS or ATSU page in the cockpit does not necessarily have a live Hoppie connection.
What do you need to use Hoppie ACARS?
You need a Hoppie network credential, compatible software and an internet connection; CPDLC also requires a controller operating an active station.
- A personal Hoppie logon code: request one through the official Hoppie registration service. This is a private network credential, not your flight number or ATC station identifier.
- A Hoppie-capable aircraft or client: look for Hoppie, ACARS, ATSU, AOC, DATALINK or CPDLC settings in the aircraft’s documentation and EFB. Feature support can differ between aircraft versions and platforms.
- Your operational flight ID: use the callsign filed for the flight, including the correct airline designator and number where applicable.
- An ATC logon address: the controller or network information must provide the station identifier. Do not guess it from the nearest airport or FIR.
- SimConnect when required: cockpit integrations often communicate with Hoppie directly, while standalone Windows clients commonly use SimConnect to read the aircraft state.
Hoppie is for flight simulation only and must never be used for real-world aviation communications.
How do I set up Hoppie ACARS in MSFS?
Set up Hoppie in either the aircraft or a compatible companion client, then initialise the flight before attempting an ATC logon.
- Choose one integration method. Use the aircraft’s built-in implementation when available, because messages then appear on its normal ATSU, CDU or EFB pages. Choose a standalone client when the aircraft lacks Hoppie support and the client explicitly supports your MSFS version.
- Obtain and copy your logon code. Enter the code exactly in the field labelled Hoppie, network, ACARS or logon code. Remove accidental spaces and do not substitute your email address, callsign or aircraft registration.
- Connect the software to MSFS. A built-in integration may only need internet access. An external client may need Microsoft Flight Simulator running in an active flight and a working SimConnect connection. If it reports that the simulator is unavailable, follow our SimConnect installation and repair checks.
- Load or enter the flight details. Set the origin, destination, route and flight ID where the implementation requests them. MSFS 2024 users can prepare and load a SimBrief operational flight plan, but importing a route does not authenticate Hoppie or replace the flight-ID entry.
- Initialise the data link. Depending on the aircraft, this may be under AOC INIT, ATSU INIT, DATALINK STATUS or a similarly named page. Wait for an online, connected or authenticated indication.
- Run the network test if one is provided. A successful test proves that the credential reached Hoppie. It does not prove that a particular ATC station is staffed or accepting CPDLC logons.
A mistake we see constantly is entering the same value in every box. Hoppie uses several identifiers for different purposes.
Which Hoppie code goes in each field?
The private logon code authenticates your software, the flight ID identifies your aircraft, and the station address selects the controller.
| Entry | What it means | Where it belongs |
|---|---|---|
| Hoppie logon code | Your private network credential | Aircraft EFB settings, data-link configuration or external client settings |
| Flight ID | The operational callsign used for the flight | AOC/ATSU initialisation or flight setup page |
| ATC station address | The controller’s CPDLC logon authority | ATC LOGON, NOTIFICATION or CPDLC page |
Treat the Hoppie logon code like an API key. Do not publish it in screenshots, stream overlays, shared configuration files or support posts. If it has been exposed, replace it through the registration service.
How do I use Hoppie CPDLC with a controller?
Use CPDLC only when the controller confirms that a compatible station is available and supplies or publishes the correct logon address.
- Establish the required voice contact. Confirm the controller’s CPDLC availability and logon authority rather than assuming every online position supports Hoppie.
- Open the ATC logon page. Enter the station address and check that the flight ID matches the callsign the controller sees.
- Send the logon request. Wait for an accepted or connected indication; the wording varies between aircraft and clients. Repeatedly sending requests will not make an offline station respond.
- Read the complete uplink. Use the appropriate standard response offered by the implementation, such as WILCO, UNABLE, ROGER or STANDBY. Do not execute a clearance until you understand it.
- Follow transfers and termination instructions. Log on to the next authority or terminate CPDLC when instructed, while retaining voice as the required backup.
AOC and CPDLC are related but separate functions. AOC pages handle operational messages and any supported weather or company requests; CPDLC carries controller–pilot messages. An AOC request can work without an ATC controller, but the available services depend on the aircraft or client implementation.
Does Hoppie work with Microsoft Flight Simulator ATC?
No, Hoppie does not convert Microsoft Flight Simulator’s built-in ATC into a CPDLC controller.
The simulator’s AI ATC, radio frequencies and menu-driven clearances remain a separate system, covered in our guide to handling the built-in MSFS ATC workflow. A Hoppie message will not automatically update an AI controller’s clearance, and an AI ATC instruction will not appear as a Hoppie uplink.
For online flying, the controller must support Hoppie and be logged into the appropriate station. Our MSFS online-network setup guidance explains the separate voice-client, callsign and flight-plan connection; Hoppie complements that connection rather than replacing it.
Why is Hoppie ACARS not connecting?
Most Hoppie connection failures come from a misplaced credential, a broken simulator link or an unavailable CPDLC station.
| Symptom | Likely cause | What to check |
|---|---|---|
| Invalid logon or authentication error | Incorrect Hoppie code or extra characters | Paste the personal code again without spaces; make sure it is not the callsign or station address |
| Client says MSFS is disconnected | SimConnect is unavailable or the flight has not loaded | Load into the cockpit, verify the client supports that MSFS edition and repair SimConnect if necessary |
| Network test passes but ATC does not answer | The station is offline, incorrect or not accepting CPDLC | Confirm the logon authority with the controller over voice |
| ATC rejects or cannot identify the flight | The flight ID differs from the filed callsign | Match the callsign exactly and remove unintended spaces or an aircraft registration entered in its place |
| ACARS or CPDLC menu is missing or disabled | The aircraft does not implement Hoppie, or its avionics are not initialised | Check the aircraft’s feature list, power its avionics and complete any required ATSU/AOC initialisation |
| Messages appear in one client but not the cockpit | The external client and aircraft are separate endpoints | Use the supported integration path; a standalone client does not automatically inject messages into every aircraft CDU |
Firewalls, security software and restricted networks can also block an external client. Allow the specific client to make outbound connections, but do not disable system security broadly just to test ACARS.
Can I use Hoppie ACARS on Xbox or PlayStation?
Console use depends entirely on the aircraft add-on providing a working, console-compatible Hoppie integration.
Windows companion clients and normal PC SimConnect workflows cannot simply be installed on Xbox or PlayStation. This affects the Xbox editions of MSFS and Microsoft Flight Simulator 2024 on PlayStation 5. Do not assume an aircraft’s PC data-link feature is present in its console release; verify that the console version explicitly supports external Hoppie communications.