EXTERNAL TOOLS: ONE OWNER FOR EACH CONTROL
Fenix demonstrates external hardware integration using variables in the installed Cockpit_Behavior.xml. The example finds a switch VAR_NAME and writes explicit beacon-off/on values. Inspect the current installed file or current integration documentation rather than assuming a variable from an old profile retains its meaning. [79, VAR_NAME lookup and beacon-switch example]
Keep a commissioning table: physical input, tool, target event/variable, press/release behaviour and observed result. Compare direct-MSFS and tool-driven routes separately, disabling the competing binding during the test. Fenix names Axis And Ohs and SPAD.next as examples but does not support those third-party tools. A shared profile is a starting point for testing, not proof for every hardware combination. [79]