Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.
You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks!
Offet: 089A 2Byte
Engine 1 Throttle lever, –4096 to +16384, same as 088C above
except that values written here are treated like axis inputs and are
disconnectable via offset 310A, and have the last written value
obtainable from offset 3330
Offset : 310A 1 Byte
Controls the joystick connection to the main flight controls.
Normally all zero, set the following bits to actually disconnect
the specific joystick axes (from least significant bit = 0):
3 Throttles (all).
4 See below (throttle sync control)
5 Elevator trim
6 Throttle #1
7 Throttle #2 (see next byte for others)
This feature is intended for use in protecting autopilot flight
from interference from axis flutter. In order to protect the user
from a broken or crashed application, all the flags are cleared 10
seconds after they have been set, so applications will need to
repeat the setting every few seconds.
If the user option is set to automatically disconnect the trim axis
in FS A/P vertical modes, the disconnection of Elevator inputs
via bit 0 above also disconnects Trim even if bit 5 is not also set.
This allows existing A/P or fly-by-wire applications to work
with those user implementations using a trim axis.
Additionally, bit 2^4 is available to switch “throttle sync” on. In
this mode all throttles are driven from the main throttle or
throttle 1 inputs, and other throttle inputs are discarded. (The
same option can also be used from an optional Hot Key).
See also offset 3109 above, and also offsets 3328–3339, which
provide the live axis values, post calibration. These would have
been applied to FS if not prevented by the flags above.
Applications can use these facilities to provide a responsive “flyby-
Offset : 3330 2 Byte
Throttle 1 Axis input value, post calibration, just before being
applied to the simulation (if allowed to by the byte at offset