User's Guide

User Guide for the Envoy Data Link
Document Number: UG-15000 Rev. A Page 28 of 173
Figure 3-1 Nominal Messaging Sequence for CPDLC Transfer
The aircrew can initiate a CPDLC session.
From the ATC menu, press LSK R6 (LOGON/STATUS). The ATC LOGON/STATUS 1/2 page
should autopopulate with the flight data and aircraft data. The aircrew must provide the ATC facility
ID they want to connect to.
Figure 3-2 ATC LOGON/STATUS 1/2 with ATSU, Enabling LOGON Prompt (LSK R6)
The Envoy can autopopulate all required inputs except for the ATSU ID. The aircrew must
manually input the ATSU ID in the LOGON TO field for initial connection. If unavailable from FMC
or other peripheral devices, required fields must be manually entered.
Table 3-1 LOGON/STATUS 1/2 Fields
LSK
LABEL
Description
L1
LOGON TO
Required. ATSU facility ID. Must be input by aircrew (4 to 8 characters).
L2
FLIGHT ID
Required. Call Sign, 7 characters max. comprising Agency Code (Airline ID), Flight
Number, and, optionally, single character Operational Suffix.
L3
TAIL ID
Required. Autopopulated from configuration.
R1
ORIGIN
Optional. Autopopulated with departure airport from FMC; or can be manually entered.
R2
DESTINATION
Optional. Autopopulated or manually entered. Arrival airport from FMC, 4 characters.
R3
CURRENT
AUTH
Read only. Autopopulated when CPDLC session is established.
R4
NEXT AUTH
Read only. Autopopulated from CDA