Pardon my ignorance but where do I add this script to?
I like the âKORG nanoKONTROL2â because it has more sliders and I would like to use two sliders for controlling propeller pitch and mixture.
In total there are 8 knobs, 8 sliders and 24 buttons which can be used.
Has anyone used this device with msfs2020 ?
1 Like
Nice to see you all having fun with the X-Touch! Did anybody get dialing the altitude to work? Every dial works, except the altitude. I assigned the obvious commands to it, but am having no luck with it.
Hereâs the code I have for the Altitude encoder. The index value is the number for the encoder knob Iâm using. This works in the A320NX, I donât ever fly the other planes so if this doesnât work with the Garmin systems (or anything else) I canât really help.
{
"index": 3,
"event_up": "AP_SPD_VAR_INC",
"event_down": "AP_SPD_VAR_DEC",
"event_press": {
"event": "SPEED_SLOT_INDEX_SET",
"type": "manual",
"value": 1,
"description": "A32NX - set AP Speed Hold to selected mode"
},
"event_long_press": {
"event": "SPEED_SLOT_INDEX_SET",
"type": "manual",
"value": 2,
"description": "A32NX - set AP Speed Hold to managed mode"
}
},
1 Like
I adopted A320 FCU knobs to fit on our X-Touch Mini, you can download the model for 3D printing here: https://www.thingiverse.com/thing:4702665
12 Likes
Sure, I mapped a knob (in button mode) to âIncrease/Decrease Autopilot Reference Altitudeâ, the only problem I have is that it changes by 1000 ft ( a consequence of also using a Honeycomb Yoke), I use the mouse for the final fine setting if I need 100 ft-precision.
1 Like
Thanks, I just did the method of @qwrtty wrong. Now i figured it out, it works totally great. Just not sure how I can map knobs my own way without much coding which I â â â â in
It is possible to have both 100 and 1000 increments on the same knob of the X-Touch, and without using any scripting. I have mine doing it. It is explained in the AAO thread a little over a month ago (I think).
1 Like
That looks like code for Speed mode ?
For Altitude I use following -
{
âindexâ: 4,
âevent_upâ: âAP_ALT_VAR_INCâ,
âevent_downâ: âAP_ALT_VAR_DECâ,
âevent_pressâ: {
âeventâ: âALTITUDE_SLOT_INDEX_SETâ,
âtypeâ: âmanualâ,
âvalueâ: 1,
âdescriptionâ: âA32NX - set AP Altitude Hold to selected modeâ
},
âevent_long_pressâ: {
âeventâ: âALTITUDE_SLOT_INDEX_SETâ,
âtypeâ: âmanualâ,
âvalueâ: 2,
âdescriptionâ: âA32NX - set AP Altitude Hold to managed modeâ
}
},
I find the Vertical Speed mode the strangest one to get working, in that I have to use the mouse to select the mode âmanuallyâ and than use following code to increment the V/S target -
{
"index": 5,
"event_up": "AP_VS_VAR_INC",
"event_down": "AP_VS_VAR_DEC",
"alternate_event_up": "AP_VS_VAR_INC",
"alternate_event_down": "AP_VS_VAR_DEC"
},
If I use the long code similar to the Altitude mode -
{
âindexâ: 5,
âevent_upâ: âAP_VS_VAR_INCâ,
âevent_downâ: âAP_VS_VAR_DECâ,
âevent_pressâ: {
âeventâ: âVS_SLOT_INDEX_SETâ,
âtypeâ: âmanualâ,
âvalueâ: 1,
âdescriptionâ: âA32NX - set AP VS Hold to selected modeâ
},
âevent_long_pressâ: {
âeventâ: âVS_SLOT_INDEX_SETâ,
âtypeâ: âmanualâ,
âvalueâ: 2,
âdescriptionâ: âA32NX - set AP VS Hold to managed modeâ
}
},
It just doesnât work! Any luck getting V/S mode selector to work?
Youâre right, I grabbed the wrong one. I forgot I had to move my knobs around because one of my encoders started going flaky. I also have the same as you for VS where you must manually move the knob first and it can be adjusted via the xtouch. I think itâs because thereâs no simvar input for pushing the VS knob. Iâm pretty sure all problems configuring button presses and such are due to the lack of simvars for the correct features. Sooooooo much stuff missing. 
2 Likes
Hi All !
Iâve received and configured my X-touch mini thanks to Maarten Tamboer (many thanks to him !) and all your shares here (many thanks to all 
) .
Thatâs a fantastic hardware addition at a low cost ! Still a few questions though.
With the A320NX I didnât find how to:
- switch QNH to STD mode
current rotary config :
{
âindexâ: 1,
âevent_upâ: âKOHLSMAN_INCâ,
âevent_downâ: âKOHLSMAN_DECâ,
âevent_pressâ: âBAROMETRICâ
},
- Engage VS mode (like already mentionned above)
current rotary config :
{ "index": 5, "event_up": "AP_VS_VAR_INC", "event_down": "AP_VS_VAR_DEC", "event_press": "AP_VS_HOLD" },
- Engage LOC mode
current button config :
{ "index": 11, "event_press": "AP_LOC_HOLD", "simvar_led": "AUTOPILOT_NAV1_LOCK" },
I didnât find a way to set up those functions although I used spad.next to monitor events. Letâs hope it will come later
Apart from that I have a few generic questions âŠ
- Is there anyway to manage the rotary leds ? The default led setup isnât very useful in an endless use. What could be interesting ( for example ) would be to enlight all the leds around the ALT rotary if you engaged Managed ALT mode.
- Is it possible to set two actions for a single button press ? If yes, what is the syntax ?
- Is it possible to set up Layer A / Layber B functions with Maarten Tamboer tool ? If yes, do you know how ? There are no sample configuraton using both layers included with the tool. Iâd like for example to setup the X-Touch for a TBM use : Layer A in a standard AP control mode, Layer B in a G1000/G3000 management mode (Iâll have a look to what is possible with Mobiflight, thanks for sharing that too).
Well, thatâs all for a first post here . have a nice day !
2 Likes
Setting up the 2 layers is easy:
Layer a is rotaries 1-8 + buttons 1-16
Layer b is rotaries 9-16 + buttons 17-32
2 Likes
Quite easy indeed - when you know it thanks !
Found the multi commands syntax âŠ
âevent_pressâ: [ âCOMMAND1â, âCOMMAND2â ],
1 Like
Headâs up, folks, Iâve been using the X-Touch Mini and AxisAndOhs and got most of the more common autopilot, avionics, and G1000 functions working.
Stay tuned for a guide, sometime in the future.
2 Likes
Has anyone tried to make the X-Touch mini work in combination with the honeycomb alpha and bravo with the working title CJ4 mod? Iâm going to try this and was wondering if anyone has already tried this. BTW looking forward to the guide from rottenbk.
Hi All,
I got a problem with Behringer x-touch mini and using the X-Touch-Mini-FS2020. However when I start MSFS 2020 and then run the x-touch mini-fs2020.exe, the python script gives this error:
OSError: unknown port âX-TOUCH MINI 1â
[1228] Failed to execute script main
The thing is, the x-touch mini works perfectly fine with my ableton software. So there is no issue with the detection etc.
I also have an audio interface with Midi in/outs, I think that could be the reason why the script canât connect to my behringer using pythonâs âmidoâ.
Anyone have any idea how to fix it?
I donât know the software you use to connect the X-Touch (I have FreePie + vJoy myself) but if you have a card with midi in/out, then âMidi 1â is probably reserved for it. Try changing to âMidi 2â or âMidi 3â in your sofwareâs setup. Thatâs what I had to do with my FreePie script.
Thank you, Iâve fixed it. So I changed the call to the Behringer in the python script to match the order in my system (0 MS midi, 1 my audio interface, 2 x.touch). The script was trying to call the x.touch in the â1â order.
Now it works, but not everything, just like the people above me noted. Trouble adjusting VS, etc.
Got it all working. I can now operate all the cockpit functions of the working title cj4 with my X-touch mini, honeycomb bravo and alpha. All from within the GUI of axis and ohs and therefore I bought AAO today on simmarket.
I used a combination of simple scripts and variable bindings. When the guide from rottenbk comes out it should be all straight forward. The list of simconnect variable s on the working title cj4 GitHub wiki is gold.
Many thanks Lorbi for a great piece of software!
1 Like