Datalink

Datalink

vSMR receives Hoppie CPDLC requests and lets controllers send manual messages and PDC clearances. Use the PDC panel opened by Runtime Menu → vSID / PDC, and the Datalink menu attached to an aircraft. PDC is the interface label; CPDLC remains the underlying datalink protocol.

Note

The PDC panel label is included in the 2.0.2 stable feed and next-airac pack; older 2.0.1 builds may still show CPDLC.

The automatic PDC/CDM reminder workflow has been removed. There is no reminder runner, Delay, Cooldown or Check now action, and no reminder-related requirement to configure a .cdm alias.

Before you start

You need a Hoppie logon code, controller login callsign, the correct active airport and current EuroScope flight-plan/controller data. CDM time data is optional and comes from a bridge-enabled CDM plug-in through EuroScope Plugin Bridge, not VACDM HTTP. See Integrations.

Your Hoppie code is private. Never include it in a screenshot, log or support report.

Connect to Hoppie

1. Open Runtime Menu → vSID / PDC.
2. Enter Login and Password (the Hoppie logon code) in the PDC panel.
3. Select Connect and check the published connection state.

The connection action becomes Cancel while connecting and Disconnect when connected. Poll requests messages once while connected. Normal connected operation polls automatically.

Login details are saved, but the plug-in starts disconnected. Login and Password cannot be edited while connecting/connected.

Handle an aircraft request

vSMR associates incoming messages with the corresponding EuroScope flight plan. Open the aircraft's Datalink menu:

Action	Result
Confirm	Open the PDC composer with available data filled in
Message	Open the general message composer
Standby	Send STANDBY
Voice	Ask the pilot to contact you by voice
Reset	Reset this aircraft's Datalink state
Close	Close the aircraft menu

If necessary, add vSMR's Datalink clearance list item and Datalink menu function to the appropriate EuroScope list.

Compose a PDC

Select Confirm, then verify callsign, aircraft type, origin, destination, runway, SID, initial climb, squawk, next frequency, TSAT/CTOT, pilot request and any additional text before sending. When TOBT is missing, the message shortcut fills the additional message with CONFIRM TOBT AT VATS.IM/VDGS; review the text before sending.

The PDC and message composers use the standard vSMR title bar and compact fields. Editable values have light-grey backgrounds; read-only information is dark grey with muted text. Pilot request and additional message use full-height fields. The title-bar X performs the same action as Cancel and does not send a message.

Runway and SID come from the EuroScope flight plan. TSAT and CTOT use matching data published by the CDM bridge when available. Missing integration data must be checked or entered as appropriate; loading the bridge alone does not supply CDM values.

For the next frequency, vSMR looks for a suitable staffed origin controller in this order:

Delivery → Ramp → Ground → Tower → Approach/Departure → Center

At LFPG, north/south runway affinity is also used between otherwise suitable local positions. If no suitable origin controller exists, vSMR tries the coordinated next controller and then your own primary frequency.

CDM and Ready Startup

CDM data also drives time tokens, Rules and mode requirements. A ready_startup tag shows RDY in red until ASRT is published, then green. Left-clicking it invokes CDM's own Ready Startup toggle; CDM remains authoritative for permissions and state. This is not an automatic reminder.

See Display token reference and Integrations.

Troubleshooting

• Cannot connect: check the Hoppie code, login and network; do not expose credentials.
• Missing TSAT/CTOT: check the CDM plug-in, bridge/provider compatibility and the matching flight plan.
• Missing menu items: check the EuroScope list-item/function configuration.
• Looking for reminder controls: they were removed; the manual Hoppie workflows above are the supported path.