Binding Duke Autopilot trim to Honeycomb Alpha/Bravo
-
I'm trying to bind Century autopilot trim to Alpha/Bravo, any thoughts without having to build extensive Lvar to do it?
Thanks in advance -
Ok, thanks JetNoise, I have a copy of SPADNext, but it's about a year and a half years old, v9.12.123, will that work?
-
-
@brodsky I think in AAO you'll have to create a script to in/de-crease the Lvar value on each press. Mine looks like this:
(L:var_AP_PitchKnob, number) 0.5 (L:Duke-APPitch) * - 15 min -15 max (>L:var_AP_PitchKnob, number)And I saved it in group
Duke, calledAPPitch(the(L:Duke-APPitch)is the parameter value passed to the script that you get with the button Insert script var).
Then I create two button bindings, one with value1and one with-1to increase or decrease the value. Looks something like this
Then I even managed to get it working with the rotary knob on the HC Bravo, when VS is selected on the left knob. I can elaborate on that if anyone's interested.
-
@MatzeH84 you can use Lvars in FSUIPC like I described here.
just replace the lines with something like this:
DukeAPPitchInc#(L:var_AP_PitchKnob, number) 0.5 + 15 min (>L:var_AP_PitchKnob, number)
DukeAPPitchDec#(L:var_AP_PitchKnob, number) 0.5 - -15 max (>L:var_AP_PitchKnob, number) -
@Randolf Hi Randolf, i just registered on the forums after reading this, you've managed to do exactly what i'm looking for, and i'd be really grateful if you could please run me through the steps to get the pitch trim functioning with only VS selected. So far i have it working, but it functions with every selection on the left hand knob. My assigned buttons are also 12 and 13...i notice (one of) yours is 14.
I'm pretty much an AAO beginner and am working it out as i go, so apologies for mentioning anything that is probably very obvious.
Thanks
-
@Jamie-G I exported an AAO template with scripts and bindings for the Duke (tested with Grand Duke piston version) for the autopilot buttons of the HC Bravo. It includes all of the autopilot related buttons and knobs in the top row of the Bravo (except IAS), make sure you don't have them already bound, to avoid conflicts.
In addition to button bindings (which you may have to replace with your controller, not sure how the bindings are exported) it includes two scripts in group
Duke:
PlusMinus- bound to the right rotary knob, sends either the standard PLUS/MINUS events, or when VS selected, adjusts AP pitch instead.
SelectPitch- bound to the VS position of the left knob with parameter 1 on press and 0 on releease.EDIT: I shared more AAO templates and will keep updating them here:
https://gitlab.com/randolf.lemmont/fs-bksq-duke-modsYou can import the template (in the Templates menu), it will be named
Duke Bravo APand then apply it to your aircraft configuration.
Let me know if it works, I've never made a template export before :) -
@Randolf Randolf, thank you so much for doing this! And for the really quick response. Its folks like you that makes these kind of communities :) So i've taken what you've done, made my own duplicate template and kind of just used the bits i need. Its good because it also helps me learn how to do it too. Seems to be functioning perfectly so far.
Thanks once again mate, you are a legend!
Jamie
-
Just to update, I shared some AAO templates, including update of the one posted above, and some other stuff, here:
https://gitlab.com/randolf.lemmont/fs-bksq-duke-modsWill also keep updating, when I add something new. For example I'm working on additional state-saving of variables not saved by the plane, using AAO scripts. Seems like fun.
