Yes, Throttle locks off, I had this working yesterday
Didn’t PMDG push another update recently? I seem to remember that the change log said something about external controls. What SET events or axis did you assign?
Thanks Lorby, very useful but how do I select the hardware item that I want to change, ( in this example the trim wheel of the Multi Panel) or is it that I have to work backwards from the events to work out which is the hardware item from the event itself? I can’t seem to find a reference to the component parts of this panel, just the smaller dialogue box for single/double click etc.
Congratulations on a super piece of software. It really is good.
Sorry guys, for people who have never used something like this to control the Autopilot/heading/vertical speed, is there a tutorial someone could do for us?
Unfortunately these things work differently in almost all aircraft. In the old days I would have pointed at the SDK documentation and the published simulator events and variables. But now with MSFS all developers are using LVars or HVars - that they invent themselves as they see fit. That means, that a procedure to control the autopilot that works for one plane might be (rather will be) useless in another.
I am still convinced that we can only tackle this as a community. It is just too much for one or a small group of individuals to figure out all these nooks and crannies of aircraft model operations, when those are so dissimilar. Generally speaking, I was hoping that AAO is the hammer, while we all build the house with it together… 
4 Likes
Selected throttle 1 from the assigned axis,
I have just tried to create a script similar to the propeller level example which I can get working but need to calibrate the axis
how do I select the hardware item that I want to change
When you open the config dialog, every panel that is attached is shown in its own GUI control. Click on the “Events” button. On the left hand side of the screen you see a list of the “panel events”. I was hoping that literals like “MP_TRIM_UP”, “MP_TRIM_DOWN” are kind of self explanatory…
To be honest, the Saitek Panels went kind of on the back burner when Logitech released their client. And there is always SPAD for people who want a more sophisticated functionality. Didn’t seem to make a lot of sense to duplicate all that. AAO is intended more for plug&play (although there are a lot of things possible with this app, just not all of them quite as pretty to look at)
1 Like
Nope, that is great. I was wondering if working backwards from the list to identify the item I wanted to change was the way to go. Now that I know that, I can proceed without much trouble.
What you said about Spad I find to be absolutely true and it was precisely that which made your creation even more attractive to me.
Selected throttle 1 from the assigned axis,
I have just tried to create a script similar to the propeller level example which I can get working but need to calibrate the axis
IMHO, this is the way to go with the DC6 throttle levers:
2 Likes
Thanks for your help, it’s working, convinced I had this working yesterday, ah well all good.
hello there,
Need help for the TBM, i find no way to assign the altitude reference to my alpha yoke with aao :
this doesn’t work 
can’t find a way to mmake it work…
can’t find a way to mmake it work…
AP_ALT_VAR_INC, AP_ALT_VAR_DEC require a proper value, they don’t work with “1”.
Spin your mouse wheel over the box to the right of the input field. Spin it over the left half for big changes, and the right half for small changes. Set a value of 100 or 1000.
Btw. in their own code, Asobo uses Scripts, not events. These are the defaults
(A:AUTOPILOT ALTITUDE LOCK VAR, feet) 100 + (>K:AP_ALT_VAR_SET_ENGLISH) (>H:AP_KNOB_Up, Number)
(A:AUTOPILOT ALTITUDE LOCK VAR, feet) 100 - (>K:AP_ALT_VAR_SET_ENGLISH) (>H:AP_KNOB_Up, Number)
Has anyone managed to connect the ADF frequency inner and outer knobs on the PMDG DC6. I’m trying to use one of the rotaries on the x touch mini to chnage teh frequency.
I can see it is obj 140 and obj 139, and have used a script below that changes obj 140 in the MSFS dev tool but doesn’t actual change the frequency number in red on the display. Also think the script below needs limiting to 99.
(L:dc6_140_obj,·Number)·1·+·(>L:dc6_140_obj,·Number)
I’ve tried using K rotor brake set to 14007 but that doesn’t seem to do anything either and neither does using ADFinnerdecrease in local simulator variables
Any help appreciated, I’m new to using scripts
I’m controlling ADF on my Logitech Radio Panel via spad.next, here’s what I use (might help you with AAO too):
- set DC_133_OBJ to 0 or 1 (selects ADF1 or 2)
- use Lvars ADFINNERINCREASE / ADFOUTERINCREASE (and xxxDECREASE) to change the stdby frequency
- set Lvar ADFFREQXFER to transfer stdby frequency
1 Like
Any help appreciated, I’m new to using scripts
The ADF knob controls seem to be split into two script parts, one that changes the frequency (L:ADFOuter/InnerIn/Decrease, Number) and the other that controls the animation of the knob (L:dc6_139/140_obj, Number). If you don’t care about the animation, the L:ADF vars are sufficient
Outer knob right
(L:ADFOuterIncrease,·number)·9·<·if{·1·s0·}·els{·-9·s0·}·(L:ADFOuterIncrease,·number)·l0·+·(>L:ADFOuterIncrease,·number)
Outer knob left
(L:ADFOuterDecrease,·number)·9·<·if{·1·s0·}·els{·-9·s0·}·(L:ADFOuterDecrease,·number)·l0·+·(>L:ADFOuterDecrease,·number)
Inner knob right
(L:ADFInnerIncrease,·number)·9·<·if{·1·s0·}·els{·-9·s0·}·(L:ADFInnerIncrease,·number)·l0·+·(>L:ADFInnerIncrease,·number)
Inner knob left
(L:ADFInnerDecrease,·number)·9·<·if{·1·s0·}·els{·-9·s0·}·(L:ADFInnerDecrease,·number)·l0·+·(>L:ADFInnerDecrease,·number)
FRQ/-- Button
(L:ADFFreqXfer,·number)·9·<·if{·1·s0·}·els{·-9·s0·}·(L:ADFFreqXfer,·number)·l0·+·(>L:ADFFreqXfer,·number)
ADF Button (with that one there is only the animation variable)
(L:dc6_133_obj,·bool)·!·(>L:dc6_133_obj,·bool)
(all scripts are based on the animation defintion file of the plane. In the file they are longer, but the code above is basically what they boil down to)
1 Like
Thanks for this, just tried the scripts out and work great much appreciated.
Just to help me with learning the scripts, I think I understand the logic of the if and els statement , essentially when the counter gets to 9 reset counter to zero, what does s0 mean?.
Why on the frequency transfer button does it have to have an if statement?
Is the bool statement effectively one statement or another such as binery 1,0 state?
Thanks for your help , much appreciated
what does s0 mean?.
“s0” stores the value in register 0 and “l0” retrieves it. This is a convenience method so you don’t have to write too much code. You can use as many registers as you like (s1/l1, s2/l2 etc.) There are at least three different ways to write this same script, and the registers are just my own preferred method.
Why on the frequency transfer button does it have to have an if statement?
No idea. That code is what I found in the amination definition file of the DC-6. From the looks of it, PMDG is generating all this code with a tool, and this is just what it spat out.
Is the bool statement effectively one statement or another such as binery 1,0 state?
“, bool” is not a statement, it is the “unit” of the variable (= the “type” in other programming languages). Baseline default is “, number”, that always works. “, bool” ist just another way of saying that the variable will only have the values 0 and 1.
Edit: my remark about the variable type is misleading. The “, unit” is, well, the unit - not the programmatic type. All variables are floating point numbers (except for the “String” of course). The simulator will automatically convert calls to the same variable into the unit that you have specified.
Examples:
(A:PLANE HEADING DEGREES TRUE, Degrees) - (A:PLANE HEADING DEGREES TRUE, Radians)
(A:PLANE ALT ABOVE GROUND, Meters) - (A:PLANE ALT ABOVE GROUND, Feet)
→ Same variables, different results, depending on the unit.
1 Like
Good afternoon,
I´m struggling a bit with the DC-6 (giro)autopilot. Is it possible to use a slider (in my case the one at the x-touch) for controlling the glide wheel ? I am able to use one rotary knob for incrementing or decrementing with the ap pitch inc and dec events but i would like to use the slider? Any help to remove the barrel out of my head are welcome.
Good afternoon,
I´m struggling a bit with the DC-6 (giro)autopilot. Is it possible to use a slider (in my case the one at the x-touch) for controlling the glide wheel ? I am able to use one rotary knob for incrementing or decrementing with the ap pitch inc and dec events but i would like to use the slider? Any help to remove the barrel out of my head are welcome.
That sounds tricky, if not impossible. The input events of the glide wheel don’t service an axis, they are sending single INC/DEC events: 44007/44008 (>K:ROTOR_BRAKE)
I can make the wheels turn with the slider, but how do I know if that also triggers what the wheels are supposed to do? (I don’t have time to actually fly the plane - or anything really. I can only give you programmatic hints.
Anyway, this is my script:
And this is the assignment
If this procedure is only actuating the animation of the wheels, then more thought needs to go into this.
Maybe a script like this could work:
(L:DC6-GlideWheel)·(L:DC6_GlideWheelRef)·>·if{·44007·(>K:ROTOR_BRAKE)·}·(L:DC6-GlideWheel)·(L:DC6_GlideWheelRef)·<·if{·44008·(>K:ROTOR_BRAKE)·}·(L:DC6-GlideWheel)·(>L:DC6_GlideWheelRef)
1 Like
You are right, the first script just move the glide wheel and with the second one I have also no success. But never the less many thanks for your suggestions.
I‘m now continuing using a rotary on my x-touch for the glide wheel.
It works for me, but it is probably not what you wanted. The slider only actuates the system and moves the wheel up or down, it doesn’t correspond to the wheel position (= moving the slider to the middle position does not mean that the wheel is zeroed).
Still, there may be a solution that does both, but it will be complex. Two scripts are required, one that handles the axis input from the slider, the other an autoscript that adjusts the glide wheel. This will have a delay when you move the slider too fast, but it will catch up eventually
1 Like
I just received my X-Touch Mini and can’t do anything with it. I’ve used the editor to setup the mini itself following instructions from this video but when I try and input anything whatsoever into AAO absolutely nothing is registering. I do see the X-Touch in the Hardware menu under connected Midi Devices (ID:1 in and ID:3 out) but can not register a single function from the device itself. I’m sure there’s something very basic I’m missing but I’ve been fooling around with it for a few hours now and am becoming very frustrated.
Any help appreciated.