Funatic

The important lesson here is to understand the role of the "Script Variable" - this is also available for events triggered from a button (the variable does reflect the number on the top right of the button assignment box). This allows you to remove the AutoScript for polling variable changes. How to deal with that number in the script is then easy to do. Regards, Funatic

Hi Daz, what you have done is not wrong - but far from "best practice" I recommend the following script: x 127 / near (>K:GEAR_SET) Save this script, then remove the "x" and instead press "Insert Script Var" - this will insert a variable that does contain the axis value (0..127). Dividing this value by 127 does give you a value between 0 and 1 - near is rounding to either 0 or 1. And then sending this value to the GEAR_SET event... Click on Update after inserting the script variable! Then in the Axis assignment select this script - and that's it. No need to create an aircraft automated script. You script will be triggered automatically on every axis level change... This was the "general purpose" approach. Especially for the "Gear Up/Down" you can do even easier: Change Axis Min to 0, Axis Max to 1. Select "GEAR_SET" as event - and you're done, not even required to create your own script... 🙂 Regards, Funatic

Hi @Rakes, what type of buttons do you use for A and B? Is it a push button or a switch? What exactly do you execute, when pressing those buttons? Do you know how to create scripts?

Hi @soloraj, you say "there is no response TO the physical x-touch mini". Does this mean when you press buttons and turn rotaries this is detected by AAO and the gauge is working? And it's only the LEDs not working on the physical x-Touch mini? Or nothing working at all? Regards, Funatic PS: I am reading here - but not regularly...

Hi @theflyguy, this might work fine for the buttons - but I can not recommend for the rotaries. What you are doing by using channel 11, is not setting the lights but setting the rotary - and the XTouch is then taking care of the LEDs itself. In Std mode the encoders are working like an axis. Sending values between 0 (leftmost) and 127 (rightmost). When sending a value to that channel 11, it does reset this internal position to that value. So far all good. Now you need to know, how AAO is detecting left turn/right turn - and it is doing this by comparing previous rotary value to current rotary value. If the number is increasing, then you are turning right. If the number is decreasing, then you are turning left. And now let's do an example: XTouch encoder is exactly in middle position, so it is sending value 64. You turn to the left - so next value received is 63. Which is smaller than 64, so left turn detected. Next "tick", value 62 - smaller than 63, so again left turn. NOW you are sending a new position to set the LED. Assume this leads to internal position 64. What's happening now, when you turn another tick to the left? XTouch will send value 63 - and this value is HIGHER than the one received before (62). And this will be interpreted as a RIGHT turn. So doing this will lead to strange behavior of the rotary - especially if turned fast.... 🙂 Regards, Thomas

Long time ago I did some testing with the bridge and managed to control the lights… Not straight forward, but it did work… Don‘t have that old code any more, but give it a try using the bridge Regards, Thomas

Hi Daz, yes, you can use the key up event or you can create a script including the var set as well as the "original" command and use this one for the keydown - both options will work... Regards, Thomas

yes, this is the only way I can think of keeping track which layer is currently active. As an alternative you can try if my gauge fits for you: X-Touch Mini Gauge for use with AAO (Axis and Ohs) » Microsoft Flight Simulator Unlimited number of layers, easy LED configuration depending on layer.... Regards, Thomas

No, there is no way to track from AAO which layer has been selected. Either use an additional button to switch the layer variable (means you have to press 2 buttons, one Layer button to change the layer and then another button to toggle the layer variable). Or - i would prefer this one - on every script triggered by the button, set the variable before executing the planned action. e.g. if you have Button 9 for FD on/off on Layer A and Strobe Lights on Layer B. Assume script for Button 9 on Layer A is (pseudo code, not working!) (L:FD, bool) ! (>L:FD, bool) ! and Button 9 on Layer B is (L:Strobe, bool) ! (>L:Strobe, bool) then change this code to something like 0 (>L:XTouch_Layer) (L:FD, bool) ! (>L:FD, bool) ! and Button 9 on Layer B to 1 (>L:XTouch_Layer) (L:Strobe, bool) ! (>L:Strobe, bool) So whenever you press a button, the layer variable will be set accordingly. However, if you switch layer but do NOT press any button, then the layer variable will NOT be adjusted... Got the idea? MC mode is a compatibility mode and is active if the MC Mode LED is lit (above the Layer A/B buttons) Regards, Thomas

Hi Daz, you can not identify if you are selected Layer A or B on the XTouch. So if you want to show different LED output, then you have to track this yourself (for example create your own variable, e.g. (L:XTouch_Layer), and set it via script. But will never be 100% accurate.) Then in the LED code you do something like (L:XTouch_Layer) 0 == if { LED Code for Layer A } (L:XTouch_Layer) 1 == if { LED Code for Layer B } But as mentioned, the hard part will be to set this variable properly. This is one of the reasons I chose to use MC mode for my XTouch Gauge and implement this layer stuff manually... Regards, Thomas