VALIDATE THE INPUTS BEFORE INTERPRETING THE FLIGHT MODEL
A hardware profile is part of the initial aircraft state. Confirm which device controls each axis and switch, then inspect the received cockpit input across the useful range. Remove unexplained duplicate assignments before evaluating handling. The test should include neutral, full travel, correct sense and any detent or button behaviour needed by the procedure. A profile that works for another aircraft can still send inappropriate commands here. If an unexpected command appears, separate the physical device, simulator assignment, external interface and aircraft response before attributing it to the flight model. [75, Flight-control/throttle calibration instructions] [21, PDF p. 113]
Fenix's documented calibration entry is MCDU MENU, CONFIG, CONTROL CONFIG. Use the current supported procedure for the actual hardware and verify IDLE, CL, FLX/MCT, TOGA and reverse afterwards. Match physical lever travel to the receiving indication rather than assuming that a desktop detent defines the aircraft's accepted position. A calibration problem near idle can affect ground movement or reverse interpretation; a problem near CL or a takeoff detent can change the normal thrust-mode chain. Check both levers and their independent indications. [75, Calibration entry and throttle procedure] [54, PDF pp. 36–40]
Keep pedal steering, tiller input and PEDAL DISC as distinct functions. The aircraft's tiller permits greater ground steering authority than the pedal range used for directional control. PEDAL DISC separates the pedals' nosewheel-steering input during the applicable rudder check; it is not a general rudder-disconnect command. After pushback, verify that the ground-handling disconnection and pin state have been resolved before taxi. A correct-looking pedal animation alone does not establish nosewheel steering availability or correct release from the tug. [21, PDF pp. 108–113] [23, PDF pp. 1048–1053]
External FCU and cockpit devices add another interpretation layer. Confirm whether knob acceleration, linked barometric controls or FD/LS synchronisation are selected, and verify the resulting behaviour on both sides. Fenix documents these as configurable functions. A linked barometer can make a second display change without a second hardware input; that is different from an unexplained duplicate assignment. Similarly, a target change and a mode request remain separate even when an external controller makes them convenient. Use FMA and actual response as the final crosscheck. [138, Controls: scrolling acceleration, EFIS baro linking and FD/LS sync] [21, PDF pp. 51–64]
For troubleshooting, preserve a working baseline and change one relevant input path at a time. Record the device model, profile, external software, initial state, exact action and received result. Where a support article offers a remedy for a particular device or legacy calibration issue, verify that scope before applying it elsewhere. Do not use a collection of unrelated sensitivity changes to compensate for a command that is being sent incorrectly. Once the input is known, a handling comparison between family members becomes evidence about the aircraft rather than about a changing hardware setup. [75, Calibration and symptom-specific supporting guidance] [135, Official reporting route]