Binding, H-events and other information

GunStrauss

Lastly, for now :)

It seems like the autopilot switches use a combination of default and custom events. Maybe you could provide a list of recommended events for the autopilot?

And the CRS knob on the EFIS, do I need to map it for each NAV-mode?

Black Square

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_dataButton

The 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{
	(&gt;K:AP_SPD_VAR_DEC)
}
els{
	(A:AUTOPILOT VERTICAL HOLD, bool) if{
		(&gt;K:AP_VS_VAR_DEC)
	}
	els{
		(A:AUTOPILOT ALTITUDE LOCK VAR, FEET) 0 &gt; if{
			500 (&gt;K:AP_ALT_VAR_DEC)
		}
	}
}

DOWN:

(A:AUTOPILOT FLIGHT LEVEL CHANGE, Bool) if{
	(&gt;K:AP_SPD_VAR_INC)
}
els{
	(A:AUTOPILOT VERTICAL HOLD, bool) if{
		(&gt;K:AP_VS_VAR_INC)
	}
	els{
		(A:AUTOPILOT ALTITUDE LOCK VAR, FEET) 33600 &lt; if{
			500 (&gt;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{
	(&gt;K:VOR1_OBI_INC)
}
els{
	(L:EFIS_NavigationSource, number) 1 == if{
		(&gt;K:VOR2_OBI_INC)
	}
	els{
		(L:EFIS_NavigationSource, number) 2 == if{
			(L:TDSGTNXI_OBSModeActive, bool) if{
				(&gt;K:VOR1_OBI_INC)
			}
		}
		els{
			(L:EFIS_NavigationSource, number) 3 == if{
				(L:var_RNAV_OBS, number) 1 + 360 % (&gt;L:var_RNAV_OBS, number)
			}
			els{
				(L:EFIS_NavigationSource, number) 4 == if{
					(L:var_MLS_OBS, number) 1 + 360 % (&gt;L:var_MLS_OBS, number)
				}
				els{
					(L:EFIS_NavigationSource, number) 5 == if{
						(L:var_ADF_OBS, number) 1 + 360 % (&gt;L:var_ADF_OBS, number)
					}
				}
			}
		}
	}
}

COUNTERCLOCKWISE:

(L:EFIS_NavigationSource, number) 0 == if{
	(&gt;K:VOR1_OBI_DEC)
}
els{
	(L:EFIS_NavigationSource, number) 1 == if{
		(&gt;K:VOR2_OBI_DEC)
	}
	els{
		(L:EFIS_NavigationSource, number) 2 == if{
			(L:TDSGTNXI_OBSModeActive, bool) if{
				(&gt;K:VOR1_OBI_DEC)
			}
		}
		els{
			(L:EFIS_NavigationSource, number) 3 == if{
				(L:var_RNAV_OBS, number) 0 &gt;
				if{ (L:var_RNAV_OBS, number) 1 - (&gt;L:var_RNAV_OBS, number) }
				els{ 360 (&gt;L:var_RNAV_OBS, number) }

			}
			els{
				(L:EFIS_NavigationSource, number) 4 == if{
					(L:var_MLS_OBS, number) 0 &gt;
					if{ (L:var_MLS_OBS, number) 1 - (&gt;L:var_MLS_OBS, number) }
					els{ 360 (&gt;L:var_MLS_OBS, number) }

				}
				els{
					(L:EFIS_NavigationSource, number) 5 == if{
						(L:var_ADF_OBS, number) 0 &gt;
						if{ (L:var_ADF_OBS, number) 1 - (&gt;L:var_ADF_OBS, number) }
						els{ 360 (&gt;L:var_ADF_OBS, number) }

					}
				}
			}
		}
	}
}

PUSH:

(&gt;H:EHSI_CourseSync) 50 (&gt;L:var_efisCourseButtonAnim, number)

GunStrauss

Perfect! Great.

Forgot about the documentation you've made in the XML, sorry for that.

Here is the thread about the KNS-81:
https://community.justflight.com/topic/5881/radio-setup-input-device/8

BTW: Regarding classic navigation devices. One of the beta-testers of the upcoming Learjet flew the Baron 58 with the KLN-90B. There is a rumor that it will be included in the Dukes?

https://www.fsdeveloper.com/forum/threads/msfs-kln-90b-integration.457361/

GunStrauss

Forgot to answer about the TOGA button. Just wanted it to animate and do whatever it's supposed to do :)

Black Square

Thank you so much for sharing that link. I will usually go to great lengths to locate something like that, but I couldn't find any clear reference to the KNS81 by searching in the forums.

It's far more than a rumor that the KLN90B will be included in the Dukes. It's in the Just Flight news section, in the product descriptions, in the manuals on the store pages, and in the screenshots. I hope you will enjoy.

The TOGA button will likely only animate using the Asobo template if you use >B:ENGINE_TOGA_1_Toggle instead of >K:AUTO_THROTTLE_TO_GA. The new B:Var system is both a blessing and curse to developers.

GunStrauss

Cool, looking forward to the Dukes and the KLN90B. Any chance of introducing it to the Bonanza and Barons also?

GunStrauss

I tried to map the EFIS NAV Source button by incrementing EFIS_NavigationSource, but it did not work.

Is it possible to map this button somehow?

Black Square

EFIS_NavigationSource is read only, I believe. The events for the buttons on the EFIS panel are...

H:EHSI_NavSource
H:EHSI_SystemSource
H:EHSI_TestReference
H:EHSI_SolidBearing
H:EHSI_HollowBearing

GunStrauss

Great, thanks

Backtracking to the TOGA button, I did not manage to get it animated, even after following your instructions and applying the code-change.

Black Square

Does it animate when you click it in the virtual cockpit, or just not when you issue a command like K:AUTO_THROTTLE_TO_GA?

GunStrauss

I’ll check when back to my FS-computer in a few days… (maybe not, but don’t remember)

GunStrauss

Not able to press the TOGA button at all with the mouse.

GunStrauss

BTW: What events would you recommend for adjusting the Barometric pressure and toggle Standard barometric pressure?

And lastly, the CWS-button on the Yoke?

Black Square

I don't know what the issue is with the TOGA button on your end. Like I said, it may not actually be in the model on the publicly available version of the TBM. You can still issue the TOGA command and it will work with whatever GPS software has the capability, but I suggest waiting until the next TBM update for the button animation, if you don't mind terribly.

(>K:KOHLSMAN_INC)
(>K:KOHLSMAN_DEC)
(>K:BAROMETRIC_STD_PRESSURE)

(L:var_PilotCws, bool)

GunStrauss

Thanks, looking forward to the updates of your previous models down the road.

BTW: Have you played with the new ground dynamics?

GunStrauss

@Black-Square

Regarding the UP/DOWN rocker. Is it correct that the altitude can be set to less than 0 feet? It's not showing less than 0, but let's say you press it |Down| once when you have it set at 300 feet. The display then shows as zero, but now let's say you would like to use the VS switch to set it at 2 000 feet. It should be four presses, but at first press, you're at 300, so then not possible to use the VS switch to set 2 000 feet as an example, you would then get closest to 1800 or 2300 feet.

I understand that this is a very minor issue, and also something I could fix with the mapping software (already did), but if this is intended behavior of the instruments, I would ofc like to keep it the way it was. If not, maybe something you could look at for the next updates?

GunStrauss

Auto Fuel Selector Switch;
when using "L:var_AutoFuelSelectorSwitch, bool", the auto fuel selector on the announcer panel does not turn off, but if moving the switch with the mouse; it turns off. Any idea as to why?

Black Square

Ah, I had to check the currently public version, because the next version of the TBM no longer uses L:var_AutoFuelSelectorSwitch.

In the current version, use A:CIRCUIT SWITCH ON:40 AND L:var_AutoFuelSelectorSwitch.

When the next version is released, use only the circuit, not the L:Var.

GunStrauss

Thanks, btw, the question I asked about in the previous post concerning the rocker, it's a very minor 'issue', but a bit curious as to how it's intended to work; at least I made it so with the hardware mapping that it's not possible to set the data for altitude to less than zero with the rocker.

Also another question about the altitude selector:
https://community.justflight.com/topic/6092/bendix-king-kas-297b-altitude-selector

GunStrauss

I guess this is one of my last questions regarding the TBM and mapping :)

Decision height, is it possible to map the decision height knob, and alt set mode switch?