Behringer X-Touch mini works flawless

Discussion Hub Tools & Utilities
102

Ok, found the first step. I had to switch Spad.next to Beta version to get midi support.

103

Could you please, from SPAD.NEXT, print the documentation you used, to use it as en example ?
(device → device settings → summary → create documentation for only this device) ?

104

Hey guys, thanks for the awesome work everyone has done so far. I am also using “X-Touch-Mini-FS2020.exe” method and I spent better part of today messing with the configuration, trying to bind all controls for my Mooney and this is what I have so far: (Edit 1: this is the current setup that I have settled for)

image
image1358×363 62.8 KB

I am struggling to find event id for “Radio Master” and “Elev Trim” buttons, among others. I haven’t started playing with AP yet, but I am sure that Altitude Preselector will be an issue as well.

Any idea where I can find even ids for these (and really all Mooney) buttons?

PS: it’s awesome feeling controlling Garmin and COMs and NAVs via X-Touch Mini :slight_smile:

Edit 2: My current config can be found here if anyone is interested: M20R - Pastebin.com

2 Likes
105

It seems “index 4” is defined twice with different vars?

1 Like
106

You are right! Yeah, I spent almost whole of Sunday configuring this and looks like my brain and eyes were very exhausted at the end :slight_smile:

The 2nd “Index 4” should be “Index 12”. Will fix that later, thank you.

107

ok, so I kinda fixed my issue by deleting the bindings for the engine master and mode switches on my throttle. Rest of the throttle works, and with the x-touch mini I can also adjust everything smoothly by 1 or 100 increments.

Sad that it’s not a great solution and I have to sacrifice some realism using those switches but since I only use them once/twice I have to live with it for now, I guess.

108

wow 
 really impressed when i saw your video clip
I have been using lordys axis and ohs and cant get half the things that youve managed to get working
I dont suppose youd like to share with a little instruction set on how you achieved which a few weeks ago i thought was impossible


i couldnt even get the script that axis and ohs exported out onthtis site and uploaded onto flightsim.to for others to see.

cheers again
H

109

This solution looks awesome.

I hope someone can create a gui for mapping,
because editing json is not comfortable

1 Like
110

BTW: i have tested it with the FBW A32NX and it works great for the predefined functions

Big advantage to vJoy Solution: Button lights show state f.e. of FD

111

Would be great when someone could brief document the JSON
file in the github wiki for this project, i am sure there will be more
people finding interest in it

112

For this the Fader has to be set to max 1 in the behringer editor ?

113

Hi
Im using X-Touch-Mini-FS2020, and are having trouble setting it up.

Im flying in C172 G1000, and have set up some of the controls on the X-Touch, but I cannot access the G1000.

I do like this:

{
  "index": 12,
  "event_press": "G1000_PFD_SOFTKEY12"
},

But when pressing the key, I get this error:

on_note_data BTN: 12
Traceback (most recent call last):
File “site-packages\mido\backends\rtmidi.py”, line 171, in _callback_wrapper
File “main.py”, line 50, in handle_message
File “pushbutton.py”, line 63, in on_note_data
File “eventqueue.py”, line 37, in call
File “eventqueue.py”, line 27, in call
TypeError: ‘NoneType’ object is not callable
Exception ignored in: ‘rtmidi._rtmidi._cb_func’
Traceback (most recent call last):
File “site-packages\mido\backends\rtmidi.py”, line 171, in _callback_wrapper
File “main.py”, line 50, in handle_message
File “pushbutton.py”, line 63, in on_note_data
File “eventqueue.py”, line 37, in call
File “eventqueue.py”, line 27, in call
TypeError: ‘NoneType’ object is not callable
on_note_data BTN: 12

Seems like it is for everything about the G1000

Am I missing something?

Thanks

Michael

114

Did you copy the Mobiflight event module as I described in my post about 19 days ago

Also covers how you reference them in script like for GN430

{
“index”: 9,
“event_up”: { “event”: “MobiFlight.AS430_RightLargeKnob_Right”, “type”: “manual”, “value”: 1 },
“event_down”: { “event”: “MobiFlight.AS430_RightLargeKnob_Left”, “type”: “manual”, “value”: 1 },
“event_press”: { “event”: “MobiFlight.AS430_RightSmallKnob_Push”, “type”: “manual”, “value”: 1 }
},

3 Likes
115

Hi can I ask since I’m getting myself more confused by the second in my attempt to be able to control nd range and mode knobs 
is there no way to do this with axis and ohs 
will it only work using mobiflight.

Cheers

116

Folks

I am trying to implement a button that zeroes the elevator trim so that on handoff from AP you start with a neutral elevator surface (hate having to switch to external view just for this). I tried this based on examples above but it’s not quite right:

{
  "index": 8,
  "event_press": { "event": "AXIS_ELEV_TRIM_SET", "type": "manual", "value": 0 },
},

What am I doing wrong?

117

Apologies I am very new to this and only tried X-Touch-Mini-FS2020 and it seems to click with me and was free so not looked at anything else. Others in this forum, use axis and ohs with great success, so hopefully can help you.

118

Should it be zero or another value is all that I can think of you need to set the trim to level flight.

Cannot try I am afraid to see if I can experiment, FS2020 gets about 80% through loading and crashes to desktop. I think it is trying to logon to something. Uninstalled and reinstalled the whole 125Gb and still does it, so going to do a complete reinstall of windows and see if any joy. Gutted as not had any real issues with FS2020 before.

I think there was a auto windows update, but no FS2020 update??

119

The quoted range is -16383 to +16383 so I think zero would be zero. Hope you get your CTD sorted soon!

1 Like
120

Hi guys,

can someone explain how the conditional events like in the Mooney file here work, where
can i find a description of the possible code for the json file?

{
  "index": 3,
  "event_up": "VOR1_OBI_INC",
  "event_down": "VOR1_OBI_DEC",
  "event_press": {
    "type": "condition",
    "event": [ "{% set heading = (data.get_simvar_value('HEADING_INDICATOR') * 180 / 3.14) | round %}",
                 "{{ data.trigger_event('VOR1_SET', heading) }}"],
    "description": "Set CRS1 bug to current heading"
  }

And second question, how can is set simvars like KOHLSMAN_SETTING_STD
directly when there is no toggle event ?

121

Regarding this, I don’t see an Event ID with such a name (Event IDs).

This is what I’m using for setting altimeter, if that’s what you are looking for:

{
  "index": 1,
  "event_up": "KOHLSMAN_INC",
  "event_down": "KOHLSMAN_DEC",
  "event_press": "BAROMETRIC"
},

But there is “KOHLSMAN_SETTING_STD” in “config.schema.json” file, so I guess you could read it from MSFS.

This is how I understand that particular “event_press”:

It looks like it sets the variable “heading” to “HEADING_INDICATOR” pulled from MSFS, multiplies it by 180 and divides it by 3.14 and rounds it. Then sends “VOR1_SET” command with the value of variable “heading”.

I assume there is a logical difference between how “HEADING_INDICATOR” value is stored and what MSFS expects to receive from “VOR1_SET”, thus the need to multiple and divide. Otherwise you could just do “data.trigger_event(‘VOR1_SET’, data.get_simvar_value(‘HEADING_INDICATOR’))”.

But of course I could be completely wrong.