I got the same problem using the XTouch mini. All my buttons/knobs/slider not working! however, my online templates works completely. The lights status also reflected in my XTouch mini. I'd tried the unplug/plug the USB and re-started a couple of times but no joy! I also re-started the MSFS2020 but no luck. Please advise what would be possible cause.

 

(N.B. I haven't play the MSFS2020 for over 6 months, however I've updated to the latest version of AAO. Today, I've tried with different planes (Cessna172, FlyByWire Simulations A320neo), both are of same symptoms with online template functioned properly but not the actual XTouch mini)

My version of AAO is 4.54.8.0;

Windows 11 version 23H2

   (Quality Updates up to 2025-02 cumulative update KB5051989; Other Updates: Windows Configuration Update (KB5035942); Security Intelligence Update for Microsoft Defender Antivirus - KB2267602 (Version 1.423.36.0) - Current Channel (Broad) )

I've split this into a new topic. The other one was about the StreamDeck, not MIDI. Those devices work completely differently in AAO.

1 hour ago, bcip said:

Please advise what would be possible cause.

Sorry, no idea. What is a "online template" and where/how is it "working"? Never heard of this.

1. Maybe reset the X-Touch to default. Unplug the cable, hold down Layer A&B buttons, reattach the cable, keep holding down the buttons until the device stops blinking. Make sure that AAO is not running while doing this.

2. Also, make sure that the device ID and channel haven't changed. If that is the case, AAO will not be able to match the incoming events to the buttons that you made before. Try creating a new button assignment, see if it is picking up the button press.

Edited August 25, 2025Aug 25 by Lorby_SI

I've mentioned this on several occasions. The MIDI device must be first disconnected and connected to the usb port. Once this is done, AA&O must be closed and restarted in order for AA&O to recognize the MIDI device. The order of operations is crucial: first unplug and plug MIDI's usb cable from PC USB port; then close and reopen AA&O.  Of course, this done after the sim has been started.

It has to do with how Windows interacts with MIDI devices. Once you establish the correct sequence of operations, it's a nuisance, but at least it works fine.

I've reset the XTouch mini and followed the sequency as advised by flyforever. The midi device is now recognized and usable for the control as the scripts. Because I haven't used the XTouch for over 6 months and left it unplug, I suspect it has gone to a state which somehow unable to talk to AAO again. Thank you very much LORBY-SI and flyforever ! Have a nice day!

On 8/25/2025 at 4:44 PM, Lorby_SI said:

Sorry, no idea. What is a "online template" and where/how is it "working"? Never heard of this.

1. Maybe reset the X-Touch to default. Unplug the cable, hold down Layer A&B buttons, reattach the cable, keep holding down the buttons until the device stops blinking. Make sure that AAO is not running while doing this.

2. Also, make sure that the device ID and channel haven't changed. If that is the case, AAO will not be able to match the incoming events to the buttons that you made before. Try creating a new button assignment, see if it is picking up the button press.

Lorby, the "online template" was wrongly used. Its the "Desk Gauge" that displays the XT on my PC screen. Sorry for this mistake

After I followed the sequence suggested by flyforever, I looked further to check that I do not need to close and reopen the AAO, instead I went to do a "Rescan Devices" under AAO's "Hardware" menu, I works and the XT buttons/knots function normally. I wonder if there is any means for AAO to do a Rescan whenever it starts up? Is there any command in script to do a device rescan?

There is another issue I encounter a couple of time, the "Desk Gauge" did not come up the screen, I simply use a workaround to toggle the "Simconnect" off/on to recall it back. Again, is there a way to do this in using a startup script to ensure AAO could connect my XT? Thanks for your help!

 

19 hours ago, bcip said:

instead I went to do a "Rescan Devices" under AAO's "Hardware" menu, I works and the XT buttons/knots function normally. 

This does not work for me, I always have to unplug and re-plug the device. Just doing a "Rescan" achieves nothing for me.

19 hours ago, bcip said:

I wonder if there is any means for AAO to do a Rescan whenever it starts up? Is there any command in script to do a device rescan?

AAO always does a rescan when it starts. Otherwise it wouldn't know what devices are there and which aren't. And no, there is no command - I'm not sure that there should be. I mean, what's the difference - you have to do "something", at the very least unplug the device. What does it matter that you have to do the rescan in the menu - as opposed to doing it with a script?

Edited August 30, 2025Aug 30 by Lorby_SI

"This does not work for me, I always have to unplug and re-plug the device. Just doing a "Rescan" achieves nothing for me."

The rescan only meant to replace the sequence suggested action on "close and reopen AAO" (as suggested by flyforever) for the connection of XTouch only. 

I do agree with you that an unplug/re-plug of XT is needed before the "Rescan". Cheers!

Strange, it stopped doing this for me. The last few days my XT is always there, I don't have to do anything, it just works. New Win 11 update maybe?

I don't really know much about that gauge, it wasn't made by LORBY. What I do know is that it sets the XT to "MC" mode - and in that mode the device behaves differently. It can be reset by holding down the bottom left button "MC" and unplugging - replugging the device. MC MODE is indicated on the LED on the top right.

One thing that always used to interfere is the USB power management that Windows does. I normally turn that off (there is an option in the Tools-Menu of AAO - restart of the PC is needed after doing this).

Apparently there seem to be other things that can cause trouble, the Internet told me to "disable USB selective suspend for power management, check for driver conflicts with the "Intel Smart Sound For USB Audio" driver, try alternate USB ports/cables"