Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. Black Square Add-Ons
  5. TBM 850
  6. Binding, H-events and other information

Binding, H-events and other information

Scheduled Pinned Locked Moved TBM 850
43 Posts 4 Posters 3.2k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • GunStraussG Offline
    GunStraussG Offline
    GunStrauss
    wrote on last edited by
    #32

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

    1 Reply Last reply
    0
    • GunStraussG Offline
      GunStraussG Offline
      GunStrauss
      wrote on last edited by GunStrauss
      #33

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

      And lastly, the CWS-button on the Yoke?

      1 Reply Last reply
      0
      • Black SquareB Online
        Black SquareB Online
        Black Square
        Black Square Developer
        wrote on last edited by
        #34

        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)

        1 Reply Last reply
        1
        • GunStraussG Offline
          GunStraussG Offline
          GunStrauss
          wrote on last edited by
          #35

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

          BTW: Have you played with the new ground dynamics?

          1 Reply Last reply
          0
          • Black SquareB 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)
            GunStraussG Offline
            GunStraussG Offline
            GunStrauss
            wrote on last edited by GunStrauss
            #36

            @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?

            1 Reply Last reply
            0
            • GunStraussG Offline
              GunStraussG Offline
              GunStrauss
              wrote on last edited by
              #37

              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?

              1 Reply Last reply
              0
              • Black SquareB Online
                Black SquareB Online
                Black Square
                Black Square Developer
                wrote on last edited by
                #38

                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.

                1 Reply Last reply
                1
                • GunStraussG Offline
                  GunStraussG Offline
                  GunStrauss
                  wrote on last edited by
                  #39

                  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

                  1 Reply Last reply
                  0
                  • GunStraussG Offline
                    GunStraussG Offline
                    GunStrauss
                    wrote on last edited by
                    #40

                    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?

                    1 Reply Last reply
                    0
                    • Black SquareB Online
                      Black SquareB Online
                      Black Square
                      Black Square Developer
                      wrote on last edited by
                      #41

                      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.

                      1 Reply Last reply
                      1
                      • GunStraussG Offline
                        GunStraussG Offline
                        GunStrauss
                        wrote on last edited by
                        #42

                        Thanks, hope you'll be able to enjoy more spare time soon!

                        1 Reply Last reply
                        0
                        • Black SquareB 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)
                          M Offline
                          M Offline
                          MatzeH84
                          wrote on last edited by
                          #43

                          @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?

                          1 Reply Last reply
                          0
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes

                          • Login
                          • Don't have an account? Register
                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Users