Hello, I am stuck at how to set the FENIX A320 RMP knobs for frequency selection. I am using Leo Bodnar BU0836X card to interface my rotary encoders that I'm using for my RMP. I am using this L:E_RMP1_OUTER. Its the same for both Inc and Dec with the difference being the value used for Inc or Dec (I'm assuming, lol) I've tried 1 and 0 and I get the freq to change 1 digit and the it stops, can't male it go past 1 digit. Trying to understand what I'm doing wrong, any help would be greatly appreciated.

 

Jose

The Fenix is very tricky in that regard. In general, LVars are unsuitable for this purpose, because they are only variables, not "events" of any kind. Meaning, there must be a process inside the aircraft logic that constantly scans all (!) these LVars and looks for changes. It would be much better if developers would always use InputEvents/Bvars - or custom K: events, like PMDG does - or ROTOR_BRAKE codes if they have to.

The Fenix is especially weird, because their knobs don't really follow the usual logic. IIRC the value of the LVar must be increased/decreased indefinitely using scripts. It is not enough to set the variable to a certain value. (Not at my computer at the moment. Maybe look for a Fenix AAO script package on flightsim.to? Doesn't matter if scripts are part of a StreamDeck package, the script themselves are hardware agnostic)

Something like this
(L:something, Number) ++ (>L:something, Number)

or even this
(L:something, Number) 2 + (>L:something, Number)

Edited July 30, 2025Jul 30 by Lorby_SI

outer ring inc script:
(L:E_PED_RMP1_OUTER, Number) ++ (>L:E_PED_RMP1_OUTER, Number)

outer ring dec script:
(L:E_PED_RMP1_OUTER, Number) -- (>L:E_PED_RMP1_OUTER, Number)


inner knob inc script:
(L:E_PED_RMP1_INNER, Number) ++ (>L:E_PED_RMP1_INNER, Number)

inner knob dec script:
(L:E_PED_RMP1_INNER, Number) -- (>L:E_PED_RMP1_INNER, Number)

 

Thank you so much for your help, i will attempt to do this.

Jose

It worked like a charm, I didn’t know how to do scripts until today, so thank you very much. One last question for brightness of PFD, ND, ECAM etc, there are decrease an increase LVARS, do you need a script to combine both INC and DEC to one potentiometer? 
 

Jose 

13 hours ago, sexyhova said:

It worked like a charm, I didn’t know how to do scripts until today, so thank you very much. One last question for brightness of PFD, ND, ECAM etc, there are decrease an increase LVARS, do you need a script to combine both INC and DEC to one potentiometer? 
 

Jose 

What kind of potentiometer? Does that register as an axis in AAO?

Here is an example of how to make this work (brightness of the PFD captain side)

I made a script like this:
Script group: "Test"
Script title: "FnxBrtCo"
Script code: "(L:Test-FnxBrtCo)·0.05·*·(>L:A_DISPLAY_BRIGHTNESS_CO,·Number)"

Note that the first LVar is named "scriptgroup-scripttile" - when you change the title or the group of this script, you have to change the name of this variable too. It is the so called "script variable". (You can also insert it with the button "Insert script var" on the script editor dialog)

Then I've assigned this script to a joystick axis (use the "Select Event" box on the axis dialog, go to the "Scripts" tab). I've set Axis Min 0, Axis Max 20, Rounding "Int". That way the LVar for the brightness will always be changed by 0.05 increments, like it does in the behavior code. When I move the axis, the brightness of the PFD changes accordingly. Sometimes it is lagging a bit - must be something in the plane internals(?).
 

Edited August 6, 2025Aug 6 by Lorby_SI

Thanks for all the help again, I’m trying to use this terr on nd lvar with a mom push button like in the real plane. The lvar works, but in order to have it work I have to maintain the button pressed. How can I fix this? Thanks again 

the link is the image of AAO 

https://files.fm/u/s8uvw24a9k

2 hours ago, sexyhova said:

How can I fix this?

See my first post above, those Fenix Button LVars have to be incremented by 2 every time you press your hardware button.

So either 
(L:something, Number) ++ (>L:something, Number)
on both Key Down and Key Up

or

(L:something, Number) 2 + (>L:something, Number)
only on Key Down

Edited August 23, 2025Aug 23 by Lorby_SI