8 hours ago, damoncmor said:

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.

That is not possible with SimConnect. Every Event can only have one single value - period. There are no additional parameter codes or anything. And that is not only with AAO, this is true for all SimConnect clients (=your SD software too!).

So I'm afraid that I don't really understand what you are trying to tell me. Can you write it down as RPN code? What exactly is being sent? Is there more than one event in play? This is actually not uncommon, first call "prepares" the internal code of the plane to receive instructions, second call then sends the actual data.

I am certain that we had a thread about this (=FSLabs Airbus) here in the forum, but I cannot find it anymore.

 

Unfortunately, I am not that well versed about how all this works. I have only been able to learn about this through watching the real time logging feature in FSUIPC and clicking buttons in the cockpit to see the actual rotor codes that are being used. In most instances when you click on something you see a control code along with the corresponding rotor parameter (and sometimes several codes are shown for one apparent click). In the pilots deck plugin, for example, for a single control code you can specify more than one parameter to send. And in some odd cases, for the FSLAB A320, a different control code (it could be a rotor code but I am not sure) can be sent with yet another parameter. I think there seems to be an entanglement of nomenclature with control codes, parameters and rotor brake codes. In AAO, I did try one instance where I sent two different codes with a single rotor event by using the key down and key up events. That seemed to work.

In any case was able to completely port over the functionality of the Stream Deck buttons that activate all the A320 EFIS/MCP features (via pilots deck plugin and control/rotor codes) and replicate it using AAO and X-Touch mini hardware all by using the rotor brake event and the correct parameter given by the FSUIPC log and other published control lists. In a few cases I wasn't able to bring over a couple of odd camera and panel views. But overall,  the AAO software was a godsend, it really made the job easy and works super well and the immersion factor went sky high as well. Thanks!