Keys, controllers and MIDI

Any instrument’s controls can be driven from a keyboard, a game controller, a button box or a MIDI controller: the baro knob, the heading bug, COM swap, the autopilot keys, the navigator’s keys and knobs, gear, flaps and more.

Map an instrument’s controls

1. Unlock the panel and touch Customize, then Keys & MIDI. The instruments that can be driven light up: Map mode: touch an instrument.
2. Touch an instrument, then Map beside the control you want, such as Baro +.
3. Press the key, push the controller’s button (or an axis past half way), or move the MIDI knob, fader or pad.

That’s it: the control is mapped. A held key repeats a knob’s turn; a MIDI knob turns as you turn it. Map another adds a second input to the same control, and × on an input takes it off.

Panel in the same bar maps the panel’s own actions, such as the next page, the lock and the lights. Touch Done when you’re finished.

External hardware

To map by what a control does rather than by instrument (for a button box or a MIDI controller laid out as a cockpit), open Settings → External hardware, or Hardware in map mode. The controls are in groups: Radios, Autopilot, Navigator, Transponder & Audio, Controls and Panel.

The Navigator group has the navigator’s keys: Direct-To, MENU, ENT, CLR, FPL, PROC, BACK, the large and small knobs and the knob’s push. They go to the navigator you touched last (else the one shown last), and work as its own keys: the NEXT’s, a GNS’s, or a G1000-style display’s FMS keys.

These mappings work on any screen, the panel or Avionics: no instrument needs to be on the page. On an iPhone, map from Settings.

Mappings are kept on each device.