Got the throttles working using RPN scripts in AAO and two LVars:

Script Group: Honda

Script Name: ThrottleOne
Script Code: (L:Honda-ThrottleOne)·100·/·(>L:THROTTLE1_SET,·Number)
Assigned to an axis, Axis Min = 0, Axis Max = 100

Script Name: ThrottleTwo
Script Code: (L:Honda-ThrottleTwo)·100·/·(>L:THROTTLE2_SET,·Number)
Assigned to an axis, Axis Min = 0, Axis Max = 100

Be mindful that in AAO the script group name and the script name must be exactly as I specified above or the scripts won't work. The reason is the script variable at the beginning, its name is "L:scriptgroup-scriptname". 

Any ideas how the checklist and throttles to idle/cutoff LVARs are called?

Edited June 3, 20224 yr by GCBraun

Sorry, not really. But I think that setting L:THROTTLEn_SET to negative values makes the lever go down into cut off position.

The aircraft files are encrypted, so the only option to find out how things work is using the MSFS developer mode. Unfortunately MSFS crashes for me 2 out of 3 sessions with the HondyJet in dev mode.

Oh, how I REALLY wish that developers would just include instructions for external controls with their products...

Edited June 3, 20224 yr by Lorby_SI

Yeah, I got a CTD on my first flight, but turning AI traffic off may have helped. 

1 hour ago, Lorby_SI said:

Sorry, not really. But I think that setting L:THROTTLEn_SET to negative values makes the lever go down into cut off position.

The aircraft files are encrypted, so the only option to find out how things work is using the MSFS developer mode. Unfortunately MSFS crashes for me 2 out of 3 sessions with the HondyJet in dev mode.

Oh, how I REALLY wish that developers would just include instructions for external controls with their products...

It’s so weird because it feels like we’re in a golden age of FS peripherals, and yet…

40 minutes ago, Chapstick said:

It’s so weird because it feels like we’re in a golden age of FS peripherals, and yet…

And yet the whole matter is completely ignored by the platform provider and the makers of content alike

Edited June 3, 20224 yr by Lorby_SI

6 hours ago, Lorby_SI said:

But I think that setting L:THROTTLEn_SET to negative values makes the lever go down into cut off position.

This DOES work to get the throttles into cutoff. However, setting it to a positive value doesn't release them. 

Thanks for getting the throttles working though!

23 minutes ago, haskell said:

However, setting it to a positive value doesn't release them. 

Throttle 1 Cut:
(L:THROTTLE1_SET,·Number)·0·==·if{·-1·(>L:THROTTLE1_SET,·Number)·}

Throttle 2 Cut:
(L:THROTTLE2_SET,·Number)·0·==·if{·-1·(>L:THROTTLE2_SET,·Number)·}

Throttle 1 Release
0·(>L:THROTTLE1_SET,·Number)·50·(>L:HA420_ThrottlePos_L,·Number)

Throttle 2 Release
0·(>L:THROTTLE2_SET,·Number)·50·(>L:HA420_ThrottlePos_R,·Number)

 

Edited June 3, 20224 yr by Lorby_SI

I bought this aircraft yesterday, where can I download this Honda group script?? Mentioned at the beginning of the post.

THANK YOU! This works perfectly!

On 6/4/2022 at 12:27 AM, Lorby_SI said:

Throttle 1 Cut:
(L:THROTTLE1_SET,·Number)·0·==·if{·-1·(>L:THROTTLE1_SET,·Number)·}

Throttle 2 Cut:
(L:THROTTLE2_SET,·Number)·0·==·if{·-1·(>L:THROTTLE2_SET,·Number)·}

Throttle 1 Release
0·(>L:THROTTLE1_SET,·Number)·50·(>L:HA420_ThrottlePos_L,·Number)

Throttle 2 Release
0·(>L:THROTTLE2_SET,·Number)·50·(>L:HA420_ThrottlePos_R,·Number)

 

Can someone explain how should I use these?
Should I create 4 scripts (named Throttle 1 cut, Throttle 2 cut etc.) and assign these to a button, with Key Up / Key Down events?
I have tried but it isn't working. In fact, selecting one of these scripts for key events does not seem to be possible.

The developer is now supplying an excel document with events and variables. For the throttle cut it says the K: event is L:HA420_THROTTLEPOS_L and L:HA420_THROTTLEPOS_R which I have added as custom events but I cannot get these to work either.

Edited September 15, 20232 yr by orchestra_nl

7 hours ago, orchestra_nl said:

Should I create 4 scripts (named Throttle 1 cut, Throttle 2 cut etc.) and assign these to a button, with Key Up / Key Down events?

This. 

7 hours ago, orchestra_nl said:

I have tried

What does that mean? What did you do, where and how did you "try" to create those scripts?

7 hours ago, orchestra_nl said:

In fact, selecting one of these scripts for key events does not seem to be possible.

Scripts appear on the normal event treelist dialog, just like the SDK events. They can be selected from the group that you've created them in.

7 hours ago, orchestra_nl said:

For the throttle cut it says the K: event is L:HA420_THROTTLEPOS_L and L:HA420_THROTTLEPOS_R which I have added as custom events but I cannot get these to work either.

LVars are not "Events", they don't "do" anything "just like that". LVars are variables, that require a certain value.That only the developer knows.

Edit: these are my scripts for the throttles (you can import the file into AAO - the app must be disconnected from the sim before you can import scripts)

https://www.dropbox.com/scl/fi/vsu59ql4m06urx3vv1s54/AxisAndOhsHondaScripts.xml?rlkey=rlmnw92t69q36nyzmeaq3sxkl&dl=0

If, how and where you assign them depends on your hardware. I've assigned the "Honda-ThrottleOne" and "Honda-ThrottleTwo" as axis with Min = 0 and Max = 100. The "Cut" and "Release" scripts I've assigned to buttons.

Edited September 16, 20232 yr by Lorby_SI

Thanks for your scripts! it seems to be working now!

3 hours ago, Lorby_SI said:

What does that mean? What did you do, where and how did you "try" to create those scripts?

I created those script in the RPN Scripts Editor. and started out with just the axes in the first post of this thread.

I made one change though: I used a different name for the script group:

Script Group: Hjet HA420

Script Name: ThrottleOne
Script Code: (L:Hjet HA420-ThrottleOne)·100·/·(>L:THROTTLE1_SET,·Number)
Assigned to an axis, Axis Min = 0, Axis Max = 100

Script Name: ThrottleTwo
Script Code: (L:Hjet HA420-ThrottleTwo)·100·/·(>L:THROTTLE2_SET,·Number)
Assigned to an axis, Axis Min = 0, Axis Max = 100

I figured this should work since I though I used the correct format.

When I added the ThrottleOne script to the first axis (as an event) , AAO crashed to desktop. After restarting AAO I was able to add both scripts to both axis on my Thrustmaster TCA quadrant.
It worked at first, but after a while both axes suddenly stopped working. 
When investigating, I noticed the event was now blank in both axes. When trying to add them again I noticed the whole scriptgroup was missing in the "select Simulator Event" window. The script group was still visible in the script editor but the event list did not show them.

Restarting AAO another time fixed that but I wasn't too sure I was doing things right.

Still, I continued and added the 4 throttle cut scripts. They showed up in the event list but I could not add them to a button. When I doubleclicked the script in the "select simulator event window" the "Key Down Event" stayed blank. I tried a few times until the whole script group again was missing from that list.

I figured to try again but keeping the "Honda" name in the scriptgroup but this morning I saw your reply and tried with the scripts you supplied which are working fine.

In your first post you wrote:

On 6/2/2022 at 7:33 PM, Lorby_SI said:

Be mindful that in AAO the script group name and the script name must be exactly as I specified above or the scripts won't work. The reason is the script variable at the beginning, its name is "L:scriptgroup-scriptname". 

I though I could safely change the scriptgroup from "Honda" to "Hjet HA420" as long as I made sure to change the variable name correctly but I must have misunderstood or have made a mistake somewhere. I also considered that perhaps variables names do not like having spaces in them.

Anyway, I am happy it works now and the name of the scriptgroup is not important so I'll leave it as it is. AAO has steep learning curve but that is to be expected from such a versatile tool.

24 minutes ago, orchestra_nl said:

Restarting AAO another time...

This behavior is definitely not normal. AAO does not crash, nor will assignments disappear just like that.  Sounds more like you have incompatible USB hardware that interferes and should be blacklisted (option in the Hardware menu)

2 hours ago, Lorby_SI said:

This behavior is definitely not normal. AAO does not crash, nor will assignments disappear just like that.  Sounds more like you have incompatible USB hardware that interferes and should be blacklisted (option in the Hardware menu)

The only hardware I have added recently is the Thrustmaster TCA quadrant+spoiler/flaps addon. I'll keep an eye on it.