Is it possible to assign a button on the X-Touch mini (via AAO) to also pass rotor codes to FSX? I have found that it is possible to pass codes to FSX using the stream deck and the AAO plugin. In the AAO app you can select Rotor Break as an event but I don't see where I can also pass the required code. 

You can either create an RPN script in AAO and assign that to the StreamDeck action or you do it directly in the SD action:

1. Select type "S:" for the write event
2. Enter the RPN code into the box, like "12345 (>K:ROTOR_BRAKE)"

Edited April 13, 20224 yr by Lorby_SI

I am a newbie when it comes to RPN coding (but willing to learn if I can get the x-touch rotaries to command the A/P in FSLABs a320 in FSX-SE). I basically have all the A/P functions working on the Streamdeck now. I would like to port that functionality over to the X-touch mini via AAO (and not the AAO SD plugin). Are there any resources for learning RPN scripting for FSX in order to do that?

23 minutes ago, damoncmor said:

I am a newbie when it comes to RPN coding (but willing to learn if I can get the x-touch rotaries to command the A/P in FSLABs a320 in FSX-SE). I basically have all the A/P functions working on the Streamdeck now. I would like to port that functionality over to the X-touch mini via AAO (and not the AAO SD plugin). Are there any resources for learning RPN scripting for FSX in order to do that?

How exactly did you "get the AP functions working on the SD"? And what is keeping you from doing the same with the X-Touch? 

If you just want to send ROTOR_BRAKE events, use the normal button assignment. The "Key Down Event" has a little box to the right of it where you can dial in any numercial value that you want to send to the ROTOR_BRAKE. No need for RPN scripts.

Edited April 13, 20224 yr by Lorby_SI

Oh I see the box to the right. Didn't know what the function of that box was. Will give it a try. Thanks for your superb support!

I could not find what the roll box does in the manual, what does the roll do?

Also, the menu item to import scripts in AAO is greyed out. How do I get that option working?

6 minutes ago, damoncmor said:

Oh I see the box to the right. Didn't know what the function of that box was. Will give it a try. Thanks for your superb support!

I could not find what the roll box does in the manual, what does the roll do?

Also, the menu item to import scripts in AAO is greyed out. How do I get that option working?

Roll: It repeats the action n times when you press the button (only) once.

Import Scripts is only avaliable when you are not connected to the sim. Click on the green LED to disconnect.

Edited April 13, 20224 yr by Lorby_SI

"Roll" is mentioned in chapter 3.6.2 of the manual "Sending values to events". Which is about what I wrote above, namely how to send specific values to an event.

Ok. I just did a real quick example. to bring up the MCDU you can bind a rotor brake code of 65911 to a button (lets say a SD button). Push the SD button and the MCDU appears as a popup. In AAO I assigned a x-touch button the key down event of ROTOR_BRAKE and put 65911 in the box and saved. when I push the x-touch mini button nothing happens. Does that make sense?

13 minutes ago, damoncmor said:

Does that make sense?

None whatsoever. Can you post a screenshot of your assignment?

What software are you using on the StreamDeck to send those events?

Edited April 13, 20224 yr by Lorby_SI

Try this:

Go to Scripting -> RPN Scripts Editor

Put this into the editor box:

65911 (>K:ROTOR_BRAKE)

Press the "Test" button at the top. Does it work now?

Yah the script didn't work. Ok sorry.  I am getting all confused. To use SD buttons to send rotor codes to FSX I was using the Pilots Deck plug in. In my many hours of playing around with all of this I could have sworn that I also used the AAO plugin to bind SD buttons to send rotor codes to FSX because the AAO plugin does accept a rotor_brake code event. So It could be that I never used the AAO plugin (it does work with the standard sim events) to send rotor codes after all. Upon careful inspection It doesn't seem to work (only with the pilots deck plug in).

So I guess to send rotor codes to effect simulator responses I would need to do some scripting. 

You must be doing something wrong with that assignment. I just checked, a value of 65911 would definitely be sent to the sim when entered correctly into the value box.

Make sure that you are not using multiple "things" at the same time. Your other plugin could potentially override all other inputs of the same event.

The only way I can test any interference is to shut down SD (along with the pilot deck plugin) . I also restarted AAO and hit the X-touch button linked the Rotor_Brake event 65911. Still no dice. I am wondering if the pilot deck plugin passes the code to FSUIPC (I am using 4.975a version) and it is actually FSUIPC doing the work. Don't really know. It would be fantastic if I could get the rotor codes working without any scripting. Also, a question for later once this is ironed out. The Pilot deck plug allows several codes to be sent with one button press. Would that be possible in AAO?

As a follow up. Here is a crazy idea. Is it possible to use AAO to 'press' buttons on the StreamDeck?

After some study I have some better understanding of the problem. You are correct. It turns out that AAO is sending the rotor brake code and for the most part the simple ones work perfectly. The standard way this is done is the use of the control code for rotor_brake (66587) with the passed parameter codes as the desired rotor codes. In the case of MCDU popup (rotor code 65911) it is not straightforward. The event ROTOR_BRAKE always uses control code 66587 with the passed parameter code being the desired rotor code. So in this case if you select rotor_brake as the event and 65911 as the passed parameter then control 66587 is sent with param 65911. In the FSLABs a320 a button linked to this event does nothing. In order to make the MCDU popup work the A320 requires you to send a control of 65911 with param of 0. I haven't figured out how to do that yet in AAO. Instead of selecting events is there a way just to select a control number with the rotor code as the passed parameter?