IRS KNOBS et al

[clop6719]

Hello,

I'm trying to use the X Touch mini to change the IRS knobs in the overhead of the FBW 320. This is a 3 portions knobs. I want to use it as close to reality, I mean :

-45 degres from vertical line-> OFF

0 degrees from vertical line-> NAV

45 degrees from vertical line-> ATT

For doing this I think I need to use a script that will count a fixed number of CW or CCW clicks before changing the value of the variable or the event. Is there any script over there that I can use? any help?. 

Thanks

 

 

[Lorby_SI]

1 hour ago, clop6719 said:

Hello,

I'm trying to use the X Touch mini to change the IRS knobs in the overhead of the FBW 320. This is a 3 portions knobs. I want to use it as close to reality, I mean :

-45 degres from vertical line-> OFF

0 degrees from vertical line-> NAV

45 degrees from vertical line-> ATT

For doing this I think I need to use a script that will count a fixed number of CW or CCW clicks before changing the value of the variable or the event. Is there any script over there that I can use? any help?. 

Thanks

 

 

I would assign this as an Axis that calls a script which will in turn sets the asset that controls the knob in the plane using the script variable.

Don't know what specific asset is controlling that knob in the FBW but I am guessing an LVar?
So you would make a script
Group: FBWA320
Name: IRS_1_Axis
Code: (L:FBWA320-IRS_1_Axis) (>L:fbwlvarforcontrollingtheknob, Number)

The "script variable" is always "L:group-name" and, when assigned to an axis or button, it will contain the value passed by the control.  In this case set the axis to Axis Min = 0, Axis Max = 2 and "Rounding = Int" and the script variable will only contain the values 0, 1, 2. On the hardware, each "third" of the total range will then send one of the values.

This is all just in theory though. And I personally think that it works better with an Inc/Dec assignment to buttons, so every "click" on the rotary encoder moves the assigned knob. Yes, the range is very small when doing this, it just "feels" better to me.

Edited January 6, 2024 by Lorby_SI

[clop6719]

13 hours ago, Lorby_SI said:

I would assign this as an Axis that calls a script which will in turn sets the asset that controls the knob in the plane using the script variable.

Don't know what specific asset is controlling that knob in the FBW but I am guessing an LVar?
So you would make a script
Group: FBWA320
Name: IRS_1_Axis
Code: (L:FBWA320-IRS_1_Axis) (>L:fbwlvarforcontrollingtheknob, Number)

The "script variable" is always "L:group-name" and, when assigned to an axis or button, it will contain the value passed by the control.  In this case set the axis to Axis Min = 0, Axis Max = 2 and "Rounding = Int" and the script variable will only contain the values 0, 1, 2. On the hardware, each "third" of the total range will then send one of the values.

This is all just in theory though. And I personally think that it works better with an Inc/Dec assignment to buttons, so every "click" on the rotary encoder moves the assigned knob. Yes, the range is very small when doing this, it just "feels" better to me.

Thanks, But (correct me if I'm wrong) with this approach, I cannot use the midi encoders knobs. It will only work with potentiometers kinda knobs.

Again, Thanks for your help

[Lorby_SI]

1 hour ago, clop6719 said:

Thanks, But (correct me if I'm wrong) with this approach, I cannot use the midi encoders knobs. It will only work with potentiometers kinda knobs.

Again, Thanks for your help

OK, so I will correct you. 🙂

This will definitely work with the rotary encoders on the X-Touch, they can be assigned as Axis. They actually are the same thing as the slider, they send values between 0 and 127 when you turn them. So they are "naturally" axis, AAO actually has to apply some tricks to make them appear as the left/right turn for button assignments...

Edit: actual operation of the encoders may depend on what mode you set for the X-Touch: MC or default.

Edited January 7, 2024 by Lorby_SI

[clop6719]

On 1/6/2024 at 10:23 AM, Lorby_SI said:

I would assign this as an Axis that calls a script which will in turn sets the asset that controls the knob in the plane using the script variable.

Don't know what specific asset is controlling that knob in the FBW but I am guessing an LVar?
So you would make a script
Group: FBWA320
Name: IRS_1_Axis
Code: (L:FBWA320-IRS_1_Axis) (>L:fbwlvarforcontrollingtheknob, Number)

The "script variable" is always "L:group-name" and, when assigned to an axis or button, it will contain the value passed by the control.  In this case set the axis to Axis Min = 0, Axis Max = 2 and "Rounding = Int" and the script variable will only contain the values 0, 1, 2. On the hardware, each "third" of the total range will then send one of the values.

This is all just in theory though. And I personally think that it works better with an Inc/Dec assignment to buttons, so every "click" on the rotary encoder moves the assigned knob. Yes, the range is very small when doing this, it just "feels" better to me.

Thanks for the help and for opening the possibilities for the MIDI devices. I'll try that one!!!!

[clop6719]

Just for the record. It worked as you explained!!. Thanks for the help!