CPDLC

ACARS can exchange CPDLC messages through the Hoppie ACARS network. It uses the callsign from your loaded flight, so you can prepare CPDLC before starting flight tracking.

Before your flight

Open the global ACARS settings and enter:

1. Your VATSIM CID.
2. Your Hoppie logon code.

You can request a code from the Hoppie registration page. The code belongs to you, not to a virtual airline or a particular flight. Both settings remain available when you switch airlines.

The Hoppie code is the credential used for CPDLC delivery. ACARS does not put it in the message history, desktop alerts, or application logs.

Preparing CPDLC

Load a flight from search, a bid, or the normal SimBrief flow. ACARS takes the callsign from that flight and marks CPDLC as ready. You do not need to start the PIREP first, and ACARS does not fetch a second copy of the SimBrief OFP.

Open Messages, select Network, and enter the ATC station you want to contact. Select Log on to send the request.

ACARS does not poll Hoppie while it is only in the ready state. Polling begins after the first logon request, in line with Hoppie's guidance for aircraft clients. ACARS checks again after 20 seconds when it expects a reply. Normal checks are spaced at a randomized 45 to 75 seconds, and network requests time out after 15 seconds.

The logon reply appears in the same feed. A CPDLC problem does not stop flight tracking, prefiling, flight updates, or PIREP filing.

Using Messages

Messages is a panel that can stay open while you move between pages. It opens on the right by default. You can change the preferred side in global settings, or drag the panel wherever it works best for your layout.

The tabs filter one message history:

1. All shows every message.
2. Network shows inbound and outbound CPDLC traffic.
3. Dispatch shows messages from dispatchers, other users, and SOP prompts.

The Messages button in the app rail and titlebar shows the unread count. Opening the panel marks the visible history as read.

Responding to messages

A message that needs a reply includes its available actions in the card. For example, a clearance can show WILCO and UNABLE, while another message may show AFFIRM, NEGATIVE, or ROGER. The controls are disabled while the reply is being sent to prevent a double submission.

SOP promptUser messages use the same feed, but they remain acknowledgment-only. Selecting the check records the original prompt time, the acknowledgment time, and the response duration in the ACARS log. Selecting it again has no effect.

Notifications

New inbound network, dispatcher, and SOP messages produce three cues:

1. A short alert in the bottom-right corner of the app.
2. A notification from the native C# desktop shell.
3. The configured ACARS notification sound.

The message still waits in Messages if an alert disappears. Notifications never send a CPDLC response for you.

Briefing and flight flow

The briefing is an operations workspace with a flight summary and separate OFP sections. SimBrief and schedule data remain read-only. Only the fields already owned by ACARS, such as aircraft, loadsheet choices, and airline PIREP fields, can be changed.

Starting the flight does not reconnect CPDLC or clear the message feed. Prefile and later flight updates continue to use the same prepared flight data.

Troubleshooting

Hoppie limits a callsign to one active client. If another client is using the same callsign, close it or wait for its callsign lock to expire before retrying.