What does the A320 RMP radio management panel do?

The Airbus A320 radio management panel (RMP) is the cockpit control head used to select a communications radio, tune its standby frequency and transfer it to active. It does not choose what the crew hears or which radio carries the microphone; those receiver-monitoring and transmit selections belong to the separate audio control panel.

In Aviation & Real-World Flying, treat the RMP as an interface rather than the radio itself. Three panels are normally fitted: RMP 1 and RMP 2 on the centre pedestal, with RMP 3 on the overhead panel. Our guide to the wider A320 cockpit layout shows how these panels relate to the MCDUs, display controls and other flight-deck systems.

A320 RMP and A320 radio panel controls

The A320 radio panel manages frequency selection, entry and transfer for compatible VHF radios and any fitted HF equipment.

The RMP does not set the transponder code, operate TCAS, control the autopilot or programme the flight plan. Those systems use separate controls. Our breakdown of radio, audio, COM/NAV and transponder controls explains the boundaries between them.

How do cross-selection and SEL give the Airbus RMP panel redundancy?

Cross-selection allows an operative RMP to tune a compatible transceiver normally associated with another panel.

Under normal operation, each RMP has an associated radio: for example, the captain's panel commonly manages VHF1 while the other panels manage their corresponding sets. If a panel becomes unavailable, another RMP can select that transceiver and enter or transfer its frequency. The SEL annunciation can then appear to draw attention to the cross-selected arrangement.

This three-panel architecture provides control redundancy, but it does not make every failure irrelevant. A radio can still be unavailable because of its own failure, an electrical-bus problem or the loss of equipment shared by more than one panel. Simulator add-ons also vary: some reproduce cross-selection and SEL logic, while simpler aircraft map the visible controls directly to COM1 and COM2.

How do you tune a VHF frequency on the A320 RMP?

Tune the standby frequency, verify it, transfer it to active and then configure the audio control panel.

1. Power the aircraft and RMP. Make sure the relevant electrical buses are supplied and the panel is switched on.
2. Select the intended radio. Choose VHF1, VHF2 or VHF3. In most simulator mappings, VHF1 corresponds to COM1 and VHF2 to COM2; VHF3 may be simplified, mapped differently or unavailable.
3. Enter the standby channel. Use the tuning controls until the complete assigned frequency appears in the standby display.
4. Check every digit. Compare the display with the ATC instruction, ATIS broadcast or chart.
5. Press transfer. The standby entry becomes active and the previous active frequency moves to standby.
6. Configure the audio panel. Select the required transmitter, enable receiver monitoring and set a usable volume.

A mistake we see constantly is changing the standby frequency without pressing transfer. The new number is visible, but the aircraft and ATC client remain on the previous active channel.

Why is my Fenix A320 RMP not setting frequencies and BeyondATC says COM is off?

This usually means the frequency is still on standby, the wrong simulator COM radio is being addressed, the radio is not powered, or another controller is overwriting the selection.

1. Establish normal electrical power. Use a stable external, APU or engine-generated supply and confirm that the RMP display is illuminated. A cold-and-dark Fenix aircraft may expose radio variables as unavailable until the appropriate buses and systems are powered.
2. Match VHF to the expected COM radio. If BeyondATC is using COM1, tune and transfer VHF1. If the client is configured to use COM2, use VHF2. Do not assume that selecting VHF2 will affect a client monitoring COM1.
3. Transfer the frequency to active. A valid number in the standby window is not enough. Press the transfer key and confirm that the new frequency occupies the active position.
4. Set the audio control panel. Select the corresponding VHF transmitter and enable its receiver monitoring. Selecting VHF1 on the RMP only selects that radio for tuning; it does not assign the microphone.
5. Check the client connection and aircraft integration. Confirm that BeyondATC is reading the intended aircraft and simulator radio. Exact integration options, radio assumptions and setting names vary with the installed Fenix and BeyondATC versions, so use the labels presented by those versions rather than relying on an older menu description.
6. Remove competing inputs. Temporarily disconnect radio hardware, disable duplicate COM bindings and turn off any simulator, copilot or ATC auto-tuning feature. A device or utility that repeatedly writes COM1 can make a manually entered frequency revert immediately.

If the virtual RMP works with hardware disconnected, the fault is in the hardware profile or bindings rather than the Fenix panel. If the active VHF1 frequency is stable but BeyondATC still reports COM as off, concentrate on power-state reporting, COM1/COM2 mapping and the client's aircraft integration rather than repeatedly retuning the same frequency.

Why can I tune the frequency but not transmit or hear ATC?

Correct RMP tuning is only one part of the radio path; the audio panel, push-to-talk assignment and ATC client must use the same radio.

• No reception: enable receiver monitoring for the active VHF set and check its volume, headset and simulator radio-audio levels.
• Reception but no transmission: select the same radio as the microphone source and verify the push-to-talk binding expected by the ATC client.
• Neither reception nor transmission: check electrical power, active-versus-standby position and VHF-to-COM mapping first.
• Only the wrong station is heard: confirm that COM1 and COM2 are not both being monitored and that the client is following the intended active set.

Selecting VHF1 on the RMP and selecting VHF1 on the audio panel are different actions. The first permits tuning; the second controls listening or transmitting. Our practical guide to COM and NAV radios in a flight simulator covers that complete signal path.

How does radio management panel NAV backup differ from normal MCDU tuning?

Normal A320 radio-navigation tuning is managed by the FMGC, with manual entries made through the MCDU's radio-navigation functions; guarded RMP NAV mode is a backup path.

During ordinary operation, the FMGC automatically tunes suitable navigation aids based on the flight plan and aircraft position. The crew can make an appropriate manual entry through the MCDU when a specific aid or ILS is required. This remains part of normal FMGC management.

If normal FMGC tuning is lost or degraded, the guarded NAV function allows an RMP to take direct control of applicable receivers. Depending on the aircraft standard, panel position and fitted equipment, that may include assigned ILS, VOR or ADF receivers. The guard helps prevent accidental entry into backup mode.

ILS, VOR and ADF availability is not identical across every A320-family installation. Receiver assignments, course-entry functions and the capability of RMP 3 can also differ. Simulator developers may model the full backup arrangement, support only VOR or ILS tuning, or leave some NAV keys non-functional. Tuning a receiver also does not automatically display its raw data; the appropriate navigation presentation must be selected separately.

A320 RMP simulator troubleshooting checklist

Work through these checks in order to separate an aircraft or add-on fault from simulator bindings, radio hardware and ATC-client configuration.

1. Check the aircraft state. Supply normal electrical power and switch on the RMP. If all panels are blank, suspect aircraft power or add-on state; if only one is blank, suspect that panel, its supply or incomplete modelling.
2. Test one basic radio operation. Select VHF1, enter a valid standby channel and transfer it. Avoid testing cross-selection, HF or NAV backup until ordinary COM1 tuning works.
3. Use only the virtual cockpit. Disconnect or disable external radio panels and test with the mouse. If the cockpit control now works, inspect hardware mappings and duplicate assignments. For Logitech or Saitek equipment, use our radio-panel fault and binding checks.
4. Inspect a skipped channel. Verify that the assignment is valid for the selected 25 kHz or 8.33 kHz channel spacing. Radio displays intentionally skip values that are not valid channels; an add-on or simulator using the wrong spacing can also refuse a legitimate assignment.
5. Check active versus standby. If the digits change but ATC stays on the old channel, press transfer and verify which side is active.
6. Check the audio path. If the active frequency changes correctly but there is no reception or transmission, inspect receiver monitoring, microphone selection, volume and push-to-talk rather than the RMP.
7. Watch for reversion. If a frequency changes and then snaps back, disable duplicate keyboard or controller bindings, radio-panel software, ATC auto-tuning and other cockpit automation one at a time. Reversion nearly always indicates a second source writing to the same simulator radio.
8. Verify the client mapping. Confirm that the ATC application is monitoring the same COM radio represented by the selected VHF set. Recheck its aircraft profile or integration after add-on or client changes.
9. Isolate the add-on. Where the client supports it, repeat a simple COM1 test in a known simulator aircraft. A failure across aircraft points to the simulator, hardware or ATC client; a failure confined to the A320 points to its aircraft state, event mapping or add-on integration.