Disregard

Edited April 28, 20233 yr by GCBraun

For the life of me, I cannot get my throttles to do what they are supposed to do. And yes, I've watched the video (Jonathan Beckett). I have the Saitek yoke, throttle quadrant and pedals. I'm trying to assign just one throttle. When I untick the reverser, everything is upside down (idle in ramp), when I tick the reverser, idle is all the way down in reverse.

Also my breaks don't work (pedals).

The only time I had similar issues was with the Headwind A330-900. But with the latest version, the problems have been solved.

6 hours ago, Christoph4445 said:

I cannot get my throttles to do what they are supposed to do.

I've assigned mine to "THROTTLEn_AXIS_SET_EX1" and set Axis Min to -8192 and Axis Max to 16383. The reverse thrust is handled with a button on my setup, so I can stop the lever at -8192 (which should be idle - some say that it is -8400)

Btw. Condition levers can be controlled with BVars:
B:ENGINE_FUEL_Lever_Mixture_1_Set
B:ENGINE_FUEL_Lever_Mixture_2_Set

And the autopilot buttons seem to be LVars, like this:
1 (>L:MSATR_FGCP_HDG, Number)

Edited April 28, 20233 yr by Lorby_SI

Deleted.

Edited April 28, 20233 yr by Fiorentoni

40 minutes ago, Fiorentoni said:

Would someone nice please write me a quick code for the following commands in the ATR?

a) AP on (or does the default command work here?)
b) YD on
c) IAS mode on
d) Power management switch to CLB

Thank you very much!

When you are sitting in the cockpit, go to "Scripting->Read LVARS from sim". Wait until the process has finished.

After doing that you have two options:

Option 1: direct button assignment:
- press the "+" to add a button
- click into the "key down.." box
- when the event selection dialog opens, immediately type "MSATR" and press "Enter". No mouse reqiured
- the treelist will be reduced to the LVars for the ATR.
- Take an educated guess which one might do what you want by looking at their names, then doubleclick it to assign it to your button.

Option 2: use it in a script
- on the RPN editor, click on the "Insert sim var" button
- when the event selection dialog opens, immediately type "MSATR" and press "Enter". No mouse reqiured
- the treelist will be reduced to the LVars for the ATR.
- Take an educated guess which one might do what you want by looking at their names, then doubleclick it to add it to your script
- Script code is always the same as I posted above. "1 (>L:MSATR_FGCP_AP, Number)"

(we all have to guess, TMBK there is no manual telling us which one is which (or if it even works...))
btw: the variable names are apparently sorted by panel. So the autopilot buttons would all be called L:MSATR_FGCP_something

 

Edited April 28, 20233 yr by Lorby_SI

6 minutes ago, Lorby_SI said:

When you are sitting in the cockpit, go to "Scripting->Read LVARS from sim". Wait until the process has finished.

After doing that you have two options:

Option 1: direct button assignment:
- press the "+" to add a button
- click into the "key down.." box
- when the event selection dialog opens, immediately type "MSATR" and press "Enter". No mouse reqiured
- the treelist will be reduced to the LVars for the ATR.
- Take an educated guess which one might do what you want by looking at their names, then doubleclick it to assign it to your button.

Option 2: use it in a script
- on the RPN editor, click on the "Insert sim var" button
- when the event selection dialog opens, immediately type "MSATR" and press "Enter". No mouse reqiured
- the treelist will be reduced to the LVars for the ATR.
- Take an educated guess which one might do what you want by looking at their names, then doubleclick it to add it to your script
- Script code is always the same as I posted above. "1 (>L:MSATR_FGCP_AP, Number)"

(we all have to guess, TMBK there is no manual telling us which one is which (or if it even works...))
btw: the variable names are apparently sorted by panel. So the autopilot buttons would all be called L:MSATR_FGCP_something

 

Thank you, I already figured out by guessing from your HDG example 🙂 Pretty straightforward, just replace HDG with AP, IAS, YD etc.

Trying to assign Xtouch knobs to HDG ALT etc ..to change the  values as normal and operate the autopilot rotary knobs

Having watched a spad next video which I stumbled on , apparently it seems the ATR  need TWO things to be added to make it work for some (hdg for example)  ...how do we achieve that in AAO ?

For example MSATR_SEL_HDG: 1  and MSATR_SEL_HDG_CHANGED is apparently needed to turn the knob (according to that video I watched)  .
no idea how to achieve that...any help appreciated  !

and what about something like BARO knob..which only seems to have 1 Lvar -    MSATR_BARO_VALUE_1: L    how would that get programmed to a rotary.. just assigning it as i normally would clockwise to increment , and opposite to decrement doesnt seem to work

 

Edited April 29, 20233 yr by vsukpadman

39 minutes ago, vsukpadman said:

Trying to assign Xtouch knobs to HDG ALT etc ..to change the  values as normal and operate the autopilot rotary knobs

Having watched a spad next video which I stumbled on , apparently it seems the ATR  need TWO things to be added to make it work ...how do we achieve that in AAO ?

For example MSATR_SEL_HDG: 1  and MSATR_SEL_HDG_CHANGED is apparently needed to turn the knob (according to that video I watched)  .
no idea how to achieve that...any help appreciated  !

and what about something like BARO knob..which only seems to have 1 Lvar -    MSATR_BARO_VALUE_1: L    how would that get programmed to a rotary.. just assigning it as i normally would clockwise to increment , and opposite to decrement doesnt seem to work

 

That is what the RPN scripts are for in AAO. I think that there is already at least one script collection for the ATR up on flightsim.to

ATR - No key shortcuts at all (not even the heading bug?) - Microsoft Flight Simulator (2020) - The AVSIM Community

It looks like not all knobs work the same in the ATR, there are some that are controlled by a sequence of LVars, and there are others that are controlled by BVars. 
I would assume that there is a BVar for every knob or button, but as the (Marketplace) model is encrypted, there is no way to tell for sure. 

Never mind if the title of the package on flightsim.to says that it is for the StreamDeck or other hardware. RPN scripts are not hardware specific. In most cases there is a script XML file in that package that you can import in AAO, and then assign those scripts to your encoders.

As always, it would be really great if the developer of the aircraft would add a simple PDF that lists all BVars and or LVars and required procedures. It doesn't feel right that we as "the community" have to invest a significant amount of our time into figuring this out ourselves. IMHO of course

Edited April 29, 20233 yr by Lorby_SI

Thanks for the swift reply ..I hadnt seen that one on flightsim.to   I had been looking, so it must be new..VERY helpful

I use those script files a lot in other aircraft that I grab from that site, so Im familiar with that process ..and AGREED ... they SHOULD provide this list of variables at the start  as FFX did so helpfully for the hondajet for example  !
thanks again..will come back if I need more help ! 

 

Back quicker than expected 🙂

the author of those scripts says in install
 

• Make sure the AAO InGame/FIP Panel is active!!!

What exactly am I installing for this ..is it this?..never seen that requirement before 

From your manual .. 
11. Web FIPs  

is that what we need ? 

Ive selected that under Gauges and its ticked, but none of his knob assignments seem to work so I guess ive not set that FIP up correctly?

 

Edited April 29, 20233 yr by vsukpadman

7 minutes ago, vsukpadman said:

From your manual .. 
11. Web FIPs  

From the AxisAndOhs Manual for MSFS (version 3.0 of AAO is required):
Chapter 6: InGame Panel

Edited April 29, 20233 yr by Lorby_SI

Thanks Lorby for all your help on this, and for a quite superb product. I have it doing all sorts to maximise my hardware on various aircraft. Got one question for you. When you posted the condition lever bvars, did you also successfully find you could write to them?
 

I'm using the map lvars to bvars method and have the correct inputs going into my local lvar. I can also 'sync lvar with bvar get' and can see my lvar changing correctly between 0,1,2,3 when I move the condition levers by hand. What is not working though is me writing to the Bvars. Any common mistakes there? 

I'm doing this in mapping settings, activate profiles, then restart the sim for each test. Hook is enabled.

LVar: (L:AAO_Fuel_Condition_Lever, Number)  - this is working, I can move my axis and see this updating correctly.
BVar get: (B:ENGINE_FUEL_Lever_Mixture_1)
BVar set: (L:AAO_Fuel_Condition_Lever, Number) (>B:ENGINE_FUEL_Lever_Mixture_1_Set)

 

 

"Chapter 6: InGame Panel"

Got it...perfect...all working now  ..much appreciated  !

Edited April 29, 20233 yr by vsukpadman

The BARO knob is a weird one:

INC
(L:MSATR_BARO_1_DELTA,·Number)·3·+·(>L:MSATR_BARO_1_DELTA,·Number)

DEC
(L:MSATR_BARO_1_DELTA,·Number)·3·-·(>L:MSATR_BARO_1_DELTA,·Number)

STD
1·(>L:MSATR_BARO_STD_1,·Number)

 

Edited April 29, 20233 yr by Lorby_SI

12 minutes ago, crap_landing_dave said:

Thanks Lorby for all your help on this, and for a quite superb product. I have it doing all sorts to maximise my hardware on various aircraft. Got one question for you. When you posted the condition lever bvars, did you also successfully find you could write to them?
 

I'm using the map lvars to bvars method and have the correct inputs going into my local lvar. I can also 'sync lvar with bvar get' and can see my lvar changing correctly between 0,1,2,3 when I move the condition levers by hand. What is not working though is me writing to the Bvars. Any common mistakes there? 

I'm doing this in mapping settings, activate profiles, then restart the sim for each test. Hook is enabled.

LVar: (L:AAO_Fuel_Condition_Lever, Number)  - this is working, I can move my axis and see this updating correctly.
BVar get: (B:ENGINE_FUEL_Lever_Mixture_1)
BVar set: (L:AAO_Fuel_Condition_Lever, Number) (>B:ENGINE_FUEL_Lever_Mixture_1_Set)

 

You don't have to do that anymore. See above, AAO manual, Chapter 6 "InGame Panel": when the AAO InGame Panel is acvtive (you can hide it), you can target BVars directly. No need for mappings with AAO V3 and beyond.

If you are using v3.00 of AAO, there is a conflict between the new MSES LVar logic and the LVar to BVar mapping. If you are still using the mappings, turn off the MSFS SU12 LVar processing in the "Application" menu.

AAO 3.0 bug list - AxisAndOhs Support - The AVSIM Community

Edited April 29, 20233 yr by Lorby_SI