i have probably greatly simplified what i am actually supposed to do!
(L:SteeringOn) is a simvar that I just invented. You are supposed to set it to 1 or 0 when you switch nosewheel steering on or off. I have no idea how the last part works and if the LVar that is involved in it will retain the value 1/0 or not. As I wrote above, some do, some don’t.
Scenario 1: (L:ASCRJ_LSP_NW_STEER,·Number) is not only the switch for NW steering, but it also holds the current state of the NW steering = it is 1 when steering is on and 0 when it is off. Then you would change the steering script that is assigned to the axis to this:
(L:ASCRJ_LSP_NW_STEER,·Number) 1 == if{ (L:Scripts-SteeringScript) (>K:STEERING_SET) }
and you only need the one script
Scneario 2: (L:ASCRJ_LSP_NW_STEER,·Number) does not retain the value and is just a trigger. Then it will probably always have the value 0 or 1, no matter if NW steering is on or not (like the CRJ HGS that I wrote about earlier). Then you need my invented LVar, and use it in a second script like this:
1·(L:SteeringOn)·-·(>L:ASCRJ_LSP_NW_STEER,·Number)·1·(L:SteeringOn)·-·(>L:SteeringOn)
Brilliant, thank you. I ended up at Scenario 1 but these tips are greatly appreciated for a scripting dunce like me 
Lorby do you have a forum?
I have some question with regards to Axis/Oh’s
@LorbySI, is there a way to add new simevents? I’ve tried to RPN script to map the throttle (Z) axis on a Thrustmaster T Flight 4. Script is (L:0·-·H135-ROTOR·COLLECTIVE)·(>K:THROTTLE1_AXIS_SET_EX1,·number) however not a lot seems to happen! Specifically this is for the H135 freeware helicopter.
strike my first answer
I have checked the code now. Yes, you can use K: events in scripts that are not in the AAO event list.
But I think that your script L-var is wrong - there shouldn’t be spaces in it.
If the script is called “MyScript” and the group is “MyGroup”, then the axis Lvar is
(L:MyGroup-MyScript)
But I can’t see in your script what is what, so I am guessing here.
Also, K: events don’t have a “unit”. The correct syntax is most likely:
(L:0-H135-ROTOR·COLLECTIVE)·(>K:THROTTLE1_AXIS_SET_EX1)
or
(L:0·-·H135-ROTOR·COLLECTIVE)·(>K:THROTTLE1_AXIS_SET_EX1)
…if that _EX1 event exists…
As a general adivce, you should refrain from using spaces when naming scripts, makes them hard to read. I recommend using the underscore instead “_”.
Ah, my bad! Thanks, I’ll give it a go when I get back in later Thanks
Ah, my bad! Thanks, I’ll give it a go when I get back in later 
Thanks
Actually, this is a big deal for me, the thanks are all yours! I have been searching for these hidden events (_EX1) for ages! I will add them to the native event list in version 2.05 right away, so you don’t have to bother with the script.
If I may ask, where did you find it? Are there more of them?
Hi, really appreciate your quick responses to all of this! I came across a list of events here - https://forum.simflight.com/topic/92097-crj-and-fsuipc/?do=findComment&comment=558269
Should add that I haven’t had a chance to test this yet. Life got in the way for a bit!
I came across a list of events here
Thanks! I found the source now, they are in the gauges.h Header file in the SDK (\MSFS SDK\WASM\include\MSFS\Legacy). Since I don’t use C++ a lot for my apps, I didn’t realize that they were there… I will make sure that all gauges.h events are properly represented in v2.05 of AAO, no matter if they have been documented officially or not.
2 Likes
…funny though that there are still events that are working but are not mentioned in either the SDK documentation nor in the gauges.h. Ah, well…
Hello,
I want to take on the behringer x touch Mini the fms knob large and small on one encoder with a combo or other Variante via push on the knob Button. everywhere have a solution for that?
Hi,
suddendly the Lorbi-SI AxisAndOhs Buttons on my Streamdeck wont work anymore. Even the options are vanished. Any Ideas?
Any Ideas?
Not really, sorry. I haven’t seen this before. But these things don’t happen “suddenly”. Try to recall what the last thing was that you did with the Elgato software.
To check on the profiles and plugins, they are here:
C:\Users\…\AppData\Roaming\Elgato\StreamDeck
And the Elgato software also has a Debug option:
Create your own plugin - Developer Documentation (elgato.com)
Hi, and first of all, many thanks for your fast response.
and you are right. These things somethimes are just appear to happen “Sunddenly” but there is always a reason. Unfortunately i can not say what my last move was. It was yesterday in the late evening.
But i did what you told me to do. And i had a look in the debuggin tool. I found some errors there. But i am not sure how to read them.
I fount two similar entrys in the “concole” eab of the debuggin tool. Both with :
“slight_smile: main.js:217 GET http://localhost:9080/webapi?json={“getvars”:[]} net::ERR_CONNECTION_REFUSED”
When i change the port in the application and in the settings.js files it is the same message with the new port number.
And i found this in the debuggin tool at “Sources\Page\main.js”
It seems for me that die streamdeck is not using the new port number. This screenshot was made whti a port number 9095.
But as far as i understand i have added every applikation to the firewall to allow communication.
May be there is a special place (at least for me) whre i have to look?
BR and many thanks
Not sure, I won’t claim to be a specialist in all matters IP. I can only state the obvious, that “something” is blocking access to the AAO WebAPI. You are running AAO “As Administrator”, right?
Here is something another user wrote to me a while ago, but I’m not sure if it applies here
Installed IIS on my machine and the problem was the same, localhost working ok, IP not , so started searching that problem specifically with IIS, and the solution found is that you have to add the IP to a list of listening IP addresses , with that command (from an elevated command prompt):
netsh http add iplisten ipaddress = your IP
It seems for me that die streamdeck is not using the new port number. This screenshot was made whti a port number 9095.
Then what you have there is an old version of the plugin. This is what it is supposed to look like in the main.js code:
xhttp.open(“GET”, AAO_URL + “?json=” + JSON.stringify(requestObj));
(the AAO_URL being the value from the settings.js)
or - you may have to completely shut down the Elgato software when changing the port? (=from the System Tray → context menu)
So, i did everything. Maybe it is time to start from scratch. Ich have saved everyting,
Here are my Versions:
Lorby Axis AndOhs V 2.04.b43
Stream Deck 4.9.3.13222
com.lorbysi.aao.streamdeckplugin_2_3
elgatosd_aao_v1.01
Are these the latest Versions?
Yes, those versions look OK. But if it was working before, the most important task still is to find out what “suddenly” happened.
If you want, send me an email with your proof of purchase. Address is on the last page of the AAO manual.
Hi, i found “COM2_RADIO_FRACT_DEC_CARRY” and it works fine. But i can not find the same for COM1. Any Ideas?