Binding, H-events and other information
-
Decision height is (>K:INCREASE_DECISION_HEIGHT) and (>K:DECREASE_DECISION_HEIGHT). By alt set mode switch, do you mean the pull knob on the altitude preselector, or the three position switch to the left of the decision height knob? The former is L:var_VsAdjustMode, the latter is...
L:var_efisDecisionHeightSet = 0 is "NORM"
L:var_efisDecisionHeightSet = 1 is "DH SET"
L:var_efisDecisionHeightTest = 1 is "TEST"I don't have any immediate answers to some of your other questions, but I will get to them and see what I can say soon. Any delay today has been from the one afternoon I've taken off in weeks.
-
Thanks, hope you'll be able to enjoy more spare time soon!
-
What exactly did you try with the go around button? Like I said, the go around mode is up to the GPS developers to implement in several cases, so I can't promise that it will work with impunity.
The "Gyro" switches on the overhead are all controlled just by their respective circuits. I believe these are at the top of the XML file where I include advice to home cockpit builders:
Remote Compass (Gyro) Switch "A:CIRCUIT SWITCH ON:57, bool"
RMI Switch "A:CIRCUIT SWITCH ON:58, bool"
ADI 2 Switch "A:CIRCUIT SWITCH ON:59, bool"
HSI 2 Switch "A:CIRCUIT SWITCH ON:60, bool"Here are the inputs for the KNS81:
H:KNS80_bigInc
H:KNS80_smallInc
L:var_rnavKnobPulled
L:var_RNAV_VOLUME
H:KNS80_vorModeButton
H:KNS80_rnavModeButton
H:KNS80_dmeHoldButton
H:KNS80_useButton
H:KNS80_displayButton
H:KNS80_dataButtonThe outputs would have to be created in a similar fashion to what I had you do last time. I can't find the post or message where I gave you instructions on how to do that right now. If you could find it for me, I can advise further.
The Autopilot interface: Most are the expected default events. You can find all of this in the XML:
TestButton: 35 (>L:var_AutopilotStartupCounter, number)
MasterButton: (>K:AP_MASTER)
YawDamperButton: (>K:YAW_DAMPER_TOGGLE)
HalfBankButton: (A:AUTOPILOT MAX BANK ID, number) 1 < if{ 1 (>K:AP_MAX_BANK_SET) } els{ 0 (>K:AP_MAX_BANK_SET) }
SoftRideButton: (L:var_autopilotSoftRideMode, bool) ! (>L:var_autopilotSoftRideMode, bool)
FlightDirectorButton: (>K:TOGGLE_FLIGHT_DIRECTOR)
HeadingButton: (>K:AP_PANEL_HEADING_HOLD)
NavButton: (>K:AP_NAV1_HOLD)
ApproachButton: (>K:AP_APR_HOLD)
BackCourseButton: (>K:AP_BC_HOLD)
AltitudeButton: (>K:AP_ALT_HOLD)
AirspeedButton: (>K:FLIGHT_LEVEL_CHANGE) (A:AIRSPEED INDICATED, knots) (>K:AP_SPD_VAR_SET)VsSwitch:
UP:(A:AUTOPILOT FLIGHT LEVEL CHANGE, Bool) if{ (>K:AP_SPD_VAR_DEC) } els{ (A:AUTOPILOT VERTICAL HOLD, bool) if{ (>K:AP_VS_VAR_DEC) } els{ (A:AUTOPILOT ALTITUDE LOCK VAR, FEET) 0 > if{ 500 (>K:AP_ALT_VAR_DEC) } } }DOWN:
(A:AUTOPILOT FLIGHT LEVEL CHANGE, Bool) if{ (>K:AP_SPD_VAR_INC) } els{ (A:AUTOPILOT VERTICAL HOLD, bool) if{ (>K:AP_VS_VAR_INC) } els{ (A:AUTOPILOT ALTITUDE LOCK VAR, FEET) 33600 < if{ 500 (>K:AP_ALT_VAR_INC) } } }The EFIS heading knob uses the default bindings.
The EFIS course knob is as follows:
CLOCKWISE:(L:EFIS_NavigationSource, number) 0 == if{ (>K:VOR1_OBI_INC) } els{ (L:EFIS_NavigationSource, number) 1 == if{ (>K:VOR2_OBI_INC) } els{ (L:EFIS_NavigationSource, number) 2 == if{ (L:TDSGTNXI_OBSModeActive, bool) if{ (>K:VOR1_OBI_INC) } } els{ (L:EFIS_NavigationSource, number) 3 == if{ (L:var_RNAV_OBS, number) 1 + 360 % (>L:var_RNAV_OBS, number) } els{ (L:EFIS_NavigationSource, number) 4 == if{ (L:var_MLS_OBS, number) 1 + 360 % (>L:var_MLS_OBS, number) } els{ (L:EFIS_NavigationSource, number) 5 == if{ (L:var_ADF_OBS, number) 1 + 360 % (>L:var_ADF_OBS, number) } } } } } }COUNTERCLOCKWISE:
(L:EFIS_NavigationSource, number) 0 == if{ (>K:VOR1_OBI_DEC) } els{ (L:EFIS_NavigationSource, number) 1 == if{ (>K:VOR2_OBI_DEC) } els{ (L:EFIS_NavigationSource, number) 2 == if{ (L:TDSGTNXI_OBSModeActive, bool) if{ (>K:VOR1_OBI_DEC) } } els{ (L:EFIS_NavigationSource, number) 3 == if{ (L:var_RNAV_OBS, number) 0 > if{ (L:var_RNAV_OBS, number) 1 - (>L:var_RNAV_OBS, number) } els{ 360 (>L:var_RNAV_OBS, number) } } els{ (L:EFIS_NavigationSource, number) 4 == if{ (L:var_MLS_OBS, number) 0 > if{ (L:var_MLS_OBS, number) 1 - (>L:var_MLS_OBS, number) } els{ 360 (>L:var_MLS_OBS, number) } } els{ (L:EFIS_NavigationSource, number) 5 == if{ (L:var_ADF_OBS, number) 0 > if{ (L:var_ADF_OBS, number) 1 - (>L:var_ADF_OBS, number) } els{ 360 (>L:var_ADF_OBS, number) } } } } } } }PUSH:
(>H:EHSI_CourseSync) 50 (>L:var_efisCourseButtonAnim, number)@Black-Square said in Binding, H-events and other information:
VsSwitch:
Hi, the VS switch is still giving me headache. How would I implement that with FSUIPC..? Via LUA?
