16211·(>K:KOHLSMAN_SET)
But there are other events and H-Variables too that deal with setting standard pressure.
Hi Oliver,
I also purchased through JustFlight, and it appears as though the new version is still not available on their site yet. This is the last time I purchase anything from them. Would you please DM an update link to me?
Thank you!
Thank you again, it works.
And how to get the sync to the actual QNH?
And how to get the sync to the actual QNH?
Hey! You are supposed to figure this stuff out by yourself! 
(A:SEA·LEVEL·PRESSURE,·Millibars)·16·*·(>K:KOHLSMAN_SET)
… I think. There are several pressure related variables in the sim, I’m not sure which one is correct. That is probably more a question for a pilot, not a programmer…
What’s wrong with the “B” key?
I am sorry, I have no idea how a newbie like me could find out such things.
Thank you for your help.
I think that was meant as a joke, not a reprimand 
I am sorry, I have no idea how a newbie like me could find out such things.
We all started out as newbies. I know that it looks cryptic, but that cannot be helped. The usual starting point for searching is the SDK documentation, the written reference for the simulator variables and events. The RPN editor in AAO has a little bit of help built in, as you can use the “Filter” on the “Insert variable” and “Insert event” lists to search for things (in this case I searched for “pressure” in the variables, and “kohlsman” in the events). The rest is always a couple of minutes/hours/days of “trial and error”. And searching on the Internet.
I was somehow hoping that more users would rise to the occasion. RPN scripting has been around for decades in the Microsoft flightsims, and there is a ton of knowledge around in the community, and a great many resources available online. What somebody wrote about the matter 15 years ago for FSX is in most cases still valid in MSFS. Plus AxisAndOhs has several Import/Export features, that people could use to exchange scripts or templates, for example by sharing them on flightsim dot to (and some do, but not many).
I think that was meant as a joke
That is true. But it was with only one laughing eye. If I had to pay myself a standard programmers rate, answering these questions would have cost the equivalent of four entire days of addon sales.
But it is also important to revive the knowledge about RPN scripting and XML, in MSFS this is more important than ever IMHO.
Is there a way to put a pause between steps / actions in RPN scripts?
Sorry, pauses in script have not been implemented. I can look into that, but I’d like to know what the use case is, what do you need it for?
Hi,
I have a small question regarding this great little peace of Software (axisandohs):
Someone already got a working radio on the A320 via the X-Touch mini? I can’t figure out how to call the radio in the A320. Help would be very welcome.
Thanks!
Someone already got a working radio on the A320 via the X-Touch mini? I can’t figure out how to call the radio in the A320. Help would be very welcome.
The default COM events work fine for me:
VHF1
COM_RADIO_FRACT_INC, COM_RADIO_FRACT_DEC
COM_RADIO_WHOLE_INC, COM_RADIO_WHOLE_DEC
VHF2
COM2_RADIO_FRACT_INC, COM2_RADIO_FRACT_DEC
COM2_RADIO_WHOLE_INC, COM2_RADIO_WHOLE_DEC
Edit: in case that is what you mean, here is the code for the “CALL” buttons on the audio panel, each button needs its own script
1·(>L:XMLVAR_COM_Transmit_Channel,·Number)·0·(>K:PILOT_TRANSMITTER_SET)·1·(>L:XMLVAR_COM_1_VHF_L_Switch_Down,·Number)
2·(>L:XMLVAR_COM_Transmit_Channel,·Number)·1·(>K:PILOT_TRANSMITTER_SET)·1·(>L:XMLVAR_COM_2_VHF_L_Switch_Down,·Number)
3·(>L:XMLVAR_COM_Transmit_Channel,·Number)·2·(>K:PILOT_TRANSMITTER_SET)·1·(>L:XMLVAR_COM_3_VHF_L_Switch_Down,·Number)
Thank you for the quick response,
I am sorry for the confusion. I mean the A320NX and meant this com panel. Can’t get it working right. 
I’ve read so much good info here so Thankyou to Oliver and everyone on this thread but it’s all confused me a little! So let me try and ask a couple of simple questions as I know there are lots of people out there (some even here) in a similar situation.
I fly the passenger jets mostly and almost exclusively A32NX at the moment. I bought a Bravo throttle quadrant . I did the fixes to make throttle 2 work etc and set it up for 2 engine jet. I’m enjoying using it on this basic level but know there is way much more to get out of the quadrant. I tried the autopilot functionality and it seems to partly work / partly not work / partly do weird things!
It appears that to get the quadrant working fully for autopilot controls, especially the different inc / dec units and the ability to select managed v selected that:
-
It simply cannot be achieved through just FS2020 control settings?
-
There is no setup coming from Honeycomb, Aerosoft or ano any time soon that will make it fully functional in all the ways you’d want for a big jet? Ie fully configured big jet autopilots etc…
-
And waiting on a Good Samaritan to do it all and post their overall configuration on YouTube / forums could be a long wait - although much of this does seem to be discussed with some solutions above is thanks to all…
-
So is the only definite option right now open to me to get something like AAO and get programming…?
I’m okay if 4. is the best answer - it’s just an issue of my expertise end the time required to learn and do it all in especially the experience says something or someone will have fixed it in a month or two but if the recommendation is that’s the best way then I’ll get stuck in…
Really appreciate some simple advice from all you much more experienced simmers to a relative newbie - thanks all !!
(And I write here because I think this might be the best answer)
Tim
Can’t get it working right.
Define “right”. I really don’t understand what the issue is.
I just made a quick test with the above mentioned events in the default A320, and they work perfectly fine. I assign INC/DEC events for FRACT and WHOLE to two rotary encoders on the X-Touch and the ACT/STBY switch button to a, well, button. What more is there? The radios even work with the Saitek radio panel without any changes.
I don’t have any mods, so I can’t comment on what operation might be required for those. From my point of view it is the job of the respecive developers to document and publish the steps that are necessary to access/operate their code.
- No idea.
- Probably not. There are too many different airplanes. They may be able to make a preset for one or at least the defaults, but they will not play catch-up with all developers and their creations
- That would be ideal, if this could be done as a group effort. The community certainly is big enough
- If you learn the necessary skills and together with 3, that would be the ideal situation.
The actual problem here is, that all aircraft, all controls, all animations, everything, works differently in all addons. Nobody is following any strict rules of engagement or publishes instructions about how to operate their buttons, knobs and levers from the outside. In some cases it is simply impossible. We are even in a situation now, where modded default aircraft work differently than the original. Trying to create a set of templates that makes a specific controller work the same way for all airliners (let alone airplanes) is IMHO ultimately and utterly futile.
I would suggest that you simply download the demo version of AAO. It is fully functional, but it will shut down after 20 minutes (you can restart it though). Play around with it, check if you can assign your controls to your liking and how difficult or easy it is for you. Bear in mind, that in this thread we are mostly dealing with more or less exotic use cases. For a plain setup you don’t need to learn any programming. I am consciously using the official terms from the SDK documentation, so everybody has a frame of reference and something to put into Google. I could have masked all this and invented my own terminology (as many developers like to do) - but “that is not the way”.
Many thanks Oliver - that’s very helpful and I will get on with AAO. Cheers Tim
Sure, here’s one example (certainly not the only one): the WT CJ4 has passenger announcements (takeoff, landing, etc) which normally can be triggered via mouse by pressing a panel button, then turning a knob to select a specific choice in a menu that pops up, and then pressing another button to select and play it. All these actions can be triggered via HVARs, so I want to bind an RPN script to a single button on my StreamDeck that executes those steps in sequence, with a single button press.
Unfortunately this doesn’t work, nothing happens after the first action, and I believe this is because the 2nd / 3rd actions happen too quickly (before the menu gets opened). If I trigger them separately (e.g. on 3 different buttons) then everything works fine.
I don’t know if this would be of general interest, but if it’d be easy enough to implement I think it would be great to have.
Edit: While I was writing this I remembered that the StreamDeck has something like ‘Multi-Action’ buttons, and I believe a Pause action as well. So tomorrow I’ll try to play around with this, maybe this could be a work-around.
Though even if that will work, the ability to do this in AAO directly would make this much simpler, and it wouldn’t be tied to StreamDeck only…
Thanks!
Dirk
the ability to do this in AAO directly would make this much simpler
OK, I have added a “(SLEEP:xxxxx)” command to the RPN logic in version 2.04. If you want, send me your proof of purchase (order number, shop, date) as PM or email, and you can try it - see if it fits the use case.
Ahh, I found my mistake. The panel screen only refreshes when I press the VHF button after an INC or DEC. Thank you again for pointing in the right direction.
1 Like
Hi @LorbySI
I have a problem with setting altitude in A320, maybe you have an idea how to do it correctly?
This is the logic when increasing altitude from the knob:
Problem is that if I set some altitude with >K:AP_ALT_VAR_SET_ENGLISH plane starts to descend/climb right away, correct behaviour is to show selected altitude in panel and wait until mode select knob is pressed. After knob is pressed plane should start descend/climb.