What does the Airbus A320 DCDU do in a simulator?
The Airbus A320 DCDU is the flight crew’s dedicated interface for controller–pilot data link communications (CPDLC). It displays ATC clearances and messages, then lets pilots select and send standard replies. In a flight simulator, it works only when the aircraft model and connected ATC or datalink system support it.
What does the A320 DCDU display?
The DCDU—short for Data Communication Display Unit and also described as the datalink control and display unit—presents the active ATC text conversation handled by the Air Traffic Services Unit (ATSU).
- Uplinked clearances, instructions and information from ATC
- Standard response choices such as WILCO, UNABLE, STANDBY or ROGER, where appropriate
- Downlinked replies and their transmission status
- Earlier sent and received messages through the message record
On equipped aircraft, two DCDUs give the captain and first officer access to the same ATSU dialogue; they are not separate communication channels. Their position and surrounding equipment are shown in our visual guide to the A320 cockpit controls and displays.
CPDLC uses structured messages rather than ordinary chat. The system offers replies permitted for that particular uplink: WILCO indicates that an instruction will be followed, while ROGER acknowledges information without carrying the same meaning. Crews should read every message element before responding.
How is the DCDU different from the MCDU and radio panel?
The DCDU handles the visible ATC datalink exchange, while the MCDU manages log-on, requests and broader flight-management tasks.
| Control | Main role | Typical use |
|---|---|---|
| DCDU | Active CPDLC dialogue | Read uplinks, choose replies, send responses and review messages |
| MCDU | Flight management and ATSU pages | Enter the flight identifier, log on to an ATC facility and prepare requests or reports |
| Radio management panel | Voice-radio frequency control | Tune or select the radio needed for voice communication |
A common mistake is trying to type a complete flight plan or free-form message on the DCDU. Route entry belongs in the MCDU, covered in our practical A320 MCDU and FMS programming walk-through. Airline operational messages using AOC or ACARS functions may also appear through MCDU pages or a printer rather than the DCDU, depending on the aircraft fit.
How do you use the A320 DCDU in a flight simulator?
In a capable A320 simulation, establish the datalink through the MCDU and use the DCDU to read, answer and monitor the resulting ATC messages.
- Confirm that the aircraft supports CPDLC. A textured or illuminated DCDU does not prove that it is functional. Some add-ons model the panel visually but do not connect it to simulator ATC or an online datalink service.
- Power and initialise the aircraft. Supply normal electrical power, adjust DCDU brightness if needed, and enter the correct flight identifier during cockpit preparation.
- Log on through the MCDU. Open the ATSU or ATC communication pages and enter the facility address required by the simulated controller or datalink service. Page names and authentication methods vary between add-ons.
- Wait for an accepted connection. A submitted log-on is not necessarily active. Check that the appropriate ATC facility has become the active data authority before expecting operational messages.
- Read the complete uplink. Use the DCDU scroll controls to inspect every page and message element. One uplink can contain more than one restriction or instruction.
- Select the appropriate response. Press the line key beside the offered reply. Do not choose WILCO unless the clearance can actually be followed; use UNABLE or STANDBY when those responses correctly describe the situation.
- Send and verify the reply. Selecting a response may only stage it. Press the applicable SEND control and confirm that the message changes to a sent state rather than remaining pending or failed.
- Create new requests through the MCDU. Level, route and similar pilot-initiated requests are normally prepared on the ATC request pages. The resulting exchange then appears on the DCDU.
CPDLC does not eliminate voice communication. A CONTACT or MONITOR instruction may require radio action, and urgent, ambiguous or failed exchanges should be resolved by voice under the applicable procedure. Our guide to controlling the A320’s voice radios explains the separate role of the radio management panel.
Why is the DCDU blank or not working in the simulator?
A blank A320 DCDU usually means the panel is unpowered, unsupported or not connected to an active CPDLC session.
- Completely dark panel: check aircraft electrical power and display brightness, then confirm that the add-on models a working DCDU.
- Panel lit but no messages: verify the flight identifier, facility address and accepted ATC log-on. Built-in simulator ATC text and multiplayer chat do not feed the DCDU unless the aircraft has an explicit integration.
- Log-on rejected: check for an incorrect facility identifier, mismatched callsign, duplicate connection or lack of datalink coverage in the service being used.
- Reply remains pending: make sure every message element has been reviewed, a valid response has been selected and SEND has actually been pressed.
- Messages appear only on another display: some simulations place CPDLC or ACARS functions on the MCDU, an electronic flight bag or an external client instead of modelling the cockpit DCDU fully.
We recommend checking implementation support before troubleshooting individual buttons. If the add-on documentation does not list functional CPDLC or ATSU integration, the DCDU is likely cosmetic rather than faulty.