Hi Oliver,

I just get the AAO version 2.04 b43 and I am trying to setup my Bravo Throttle AXIS in AOA and I am stuck (I try to look "media" - but they are only for MSFS...)

First : how it works with axis 4 declared in P3D (V5.1 HF1) - I kept this one as reference

- Engine 4 throttle axis is assigned to lever 4 - reverse is checked
- On the Bravo, the reverse action is set in two step (just for your information)

   -14000 (>K:AXIS_THROTTLE_REVERSER4_SET)  which is reverse idle, sent by the small reverse lever
    16383 (>K:AXIS_THROTTLE_REVERSER4_SET)  for full reverse, sent by the detent switch when the lever is full down (it is a switch like it was with the venerable Saitek throttle) and if the small reverse lever is "on"...
    the reverse is cancelled by (>K:THROTTLE4_CUT)

The result on the VC throttle shows the lever a small step aft for idle reverse
(A:GENERAL ENG4 THROTTLE LEVER POSITION, percent) = -1.82
and full aft for the full reverse.
(A:GENERAL ENG4 THROTTLE LEVER POSITION, percent) = -25.00  corresponding at the aircraft.cfg, [GeneralEngineData], "min_throttle_limit" set as usual for reverse to -25

I am sorry, to make this long introduction but I think it was necessary.

Now, I am trying to configure the axis in AAO to achive the same result..

- I tried "Simulator Event "AXIS_THROTTLE1_SET" assigned to the corresponding Joystick Axis - red center marker left centered (-16383 to 16383, full range like in P3D)
- I tried  Simulator Axis "Throttle 2" assigned to the corresponding Joystick Axis - with red center marker full left.

None allow for the activation of the reverse, and VC lever stays in 0 position , don't go aft.
(A:GENERAL ENGx THROTTLE LEVER POSITION, percent) stay at zero (with sometimes a very brief -1.82 showing...)

I am sure, I am missing something - I did not try to view the video as they are "for MSFS". I am confused enough without adding other simulator behavior.

Nota : your solution with script for activating the "profiles" for the Honeycomb driver works like a charm - thanks 🙂

Cheers,

Gérard

Hello Gérard,

throttle assignments are not simulator global settings. They are specific to every aircraft. Some react to the simulator variables, some react to events, some process the P3D reverser axis, some don't. So the videos aren't really about MSFS, but about the plane that I use in there. The procedure is the same for every aircraft that works along those same lines.

So the first thing that I need to know is what aircraft you are trying to assign the throttle axis to. You will have to use different procedures for different planes, there is no one-profile-fits-all solution.

I don't have any Honeycomb hardware, and I have to admit, I don't understand a word of what you wrote above about reverser levers etc. 

Here is what I did for my airliners (Saitek TQs):

1. I've assigned the thrust lever axis so I have full forward travel from the detent to max.
2. Each axis has a Combo Button action assigned to the "button" in the detent and "suppress axis" activated.
3. I've put a dead zone around the "0" point on the left, and added detents where appropriate
4. I wrote RPN scripts for the reverser action itself that can be triggered with a button
5. These scripts I assigned to the button action in the detent, making sure that the "Up" events clears the reverse thrust (with whatever action is appropriate for the actual plane)

With this configuration, what will happen is this:

When I move the thrust lever forward, AAO is sending the throttle axis to the sim, the thrust lever in the VC moves forward. While the lever is moved, the detent button doesn't trigger, so I'm good regarding the Combo. When I pull the lever back into the detent, the button event fires and several things start to happen: first, the button acts as the Combo for the axis and prevents AAO from sending any more throttle axis values. Second, the button activates the script that causes reverse thrust to happen. When I move the lever up again, the opposite happens, the Up - event of the button cancels reverse, the Combo is turned off, and AAO is sending normal throttle axis values again.

Edited March 28, 20215 yr by Lorby_SI

Hi Oliver,

You are right, we don't need to go into the details of each hardware, but just stick to the standards Events.

I just want to have AAO managing the axis like P3D. No more but not less.

In any "standard" aircraft just conforming to the basic XML (no PMDG, no A2A, no special trick...) the axis drives the throttle by

Value (>K:AXIS_THROTTLEx_SET) as it is visible in the Standard.xml :

<AxEvent>AXIS_THROTTLEx_SET</AxEvent>   <AxScale>-127</AxScale>

and the reverse are achieved by setting a value to

 (>K:AXIS_THROTTLE_REVERSERx_SET) 

and are reset by

(>K:THROTTLEx_CUT)

This standard behavior is directly linked to the [GeneralEngineData], min_throttle_limit= a negative figure.

It looks like this is not taken into account by AAO which "filters" the negative values ???

I thought that linking the lever to the event (-16383 to + 16383) I would get the expected results.

How shall I define my AXIS in order to achieve the same behavior that the Axis definition in Prepar3D.

Cheers,

Gérard

 

Edited March 28, 20215 yr by gaab

Forgot to mention that "min_throttle_limit" is available with 

THROTTLE LOWER LIMIT

Percent throttle defining lower limit (negative for reverse thrust equipped airplanes)

Hello Gérard,

I'm not sure what to tell you, I have honestly never looked at it that way. My only point of reference is the SimConnect specification, because whatever else is in the sim is not accessible to me. P3D does its thing with controllers, and AAO does another thing. It was never my intention to replicate anything that the sim does natively - you already have that without using AAO.

Throttle assignments I do visually. I select either the throttle axis variable from the top list, or either the AXIS_THROTTLEn_SET or just THROTTLEn_SET from the event list in the second row. Since I cannot know what the aircraft wants / reacts to, I just go through all of them until I find one that works.

Then I adjust the blue triangles (= -16K, +16K) to the top and botton limits of the physical thrust lever and then pull the red triangle (= 0 = center) to the left until I get full travel on the thrust lever. Personally I then set a dead zone at the lower end, so the axis cannot be put into reverse. As described above I use the button actions to set up reverse instead.

If you want the same axis to send different events depending on position, that can be done with a parametrized RPN script, that looks at the axis value and then sends one event or another.

Edited March 29, 20215 yr by Lorby_SI