HARDWARE CALIBRATION AND REPRODUCIBLE TROUBLESHOOTING
Before learning a new manoeuvre, make sure the hardware is sending the input you intend. On the ground, move the sidestick, pedals, brakes, thrust levers, flaps and speedbrake while watching the corresponding cockpit response. Check that the control returns to the expected position and that its useful range is available. Look for duplicate assignments when two devices seem to be giving conflicting instructions. A profile change or reconnected device is a good reason to repeat this simple check. The objective is a dependable starting point, so an unexpected response during flight can be investigated without first wondering what the hardware sent.
Fenix's documented throttle calibration is reached through MCDU MENU, CONFIG and CONTROL CONFIG. Use the published instructions for the hardware in front of you, then verify IDLE, CL, FLX/MCT, TOGA and reverse in the cockpit. The detents are meaningful engine-control requests: the normal procedures depend on being able to select them reliably. A lever resting at a familiar physical mark is useful when the simulator recognises the intended detent there too. Check the indication after calibration rather than judging success only from how the lever feels. Keep the resulting working configuration available as a baseline. [35, Opening throttle-calibration instructions and embedded Fenix video]
When something changes unexpectedly, isolate one relevant change at a time. Record the simulator and Fenix build, aircraft variant, initial panel state, input and observed result. Include whether the problem can be repeated from the same starting state. A description such as an altitude selection followed by a particular FMA indication gives an investigation something concrete to follow. Keep a working setup before experimenting with another profile or assignment. This small amount of preparation can save a long evening of changing several things at once and then being unable to tell which one produced the improvement.