KA350 Condition Levers

meh1951

@anderson
Are you talking about the
While TURB ENG CONDITION LEVER:2 equals ??

hangar_101

@meh1951 yes, scripted event window should look like this

Notice the first condition line just evaluates the lever position.

Anderson

meh1951

@anderson not sure I know how to do that

?

meh1951

@anderson
This is what I am supposed to have ... correct?

(([LOCAL:JOY_0X294B0X1901_Z_AXIS] >= 0) && ([LOCAL:JOY_0X294B0X1901_Z_AXIS] <= 25))

[TURB ENG CONDITION LEVER POSITION:2] != 0

B:FUEL_2_Condition_Lever_Cut_Off-Event

(([LOCAL:JOY_0X294B0X1901_Z_AXIS] >= 26) && ([LOCAL:JOY_0X294B0X1901_Z_AXIS] <= 74))

[TURB ENG CONDITION LEVER POSITION:2] != 1

B:FUEL_2_Condition_Lever_Low_Idle-Event

(([LOCAL:JOY_0X294B0X1901_Z_AXIS] >= 75) && ([LOCAL:JOY_0X294B0X1901_Z_AXIS] <= 100))

[TURB ENG CONDITION LEVER POSITION:2] != 2

B:FUEL_2_Condition_Lever_High_Idel-Event

hangar_101

@meh1951 correct. make sure repeat ON. If you want it to be exactly as the example I sent you use the is in range option for evaluating the axis value.

meh1951

@anderson
Was the screen shot at 28 correct?

or is this

hangar_101

@meh1951 it looks okay, notice you set range 0 thru 15 for Cut Off and 26 thru 75 for Low Idle, there's a gap between 16 thru 25. Recommend you change the Low Idle range to 16 thru 75.

Let me know if it works.(It should)

Anderson

meh1951

@anderson
Changed the range still does not work.

The logic works but the Levers never move

meh1951

@anderson
I got it! I don't know why but I was gonna work on and it was working today???
I really appreciate you sticking with be...I learned a bunch. Now I need to get some of this other stuff working. Thanks again!

For anybody else

meh1951

@anderson
Not working again...:-(

hangar_101

@meh1951 makes no sense unless you have the same lever setup somewhere else thus facing some sort of conflict. Verify that and also remove all mods but the KA mod itself from community folder.

bjratchf

@anderson how do you get those client events? My client events are blank, or it wants me to load an xml file containing them

meh1951

@bjratchf
You can't do the client events since the latest version of SPAD. They close that option (said it was experimental). But as long as long as you have 9.13.33 it should still work.
Need for BKSQ to give us the same kind of variables (LVars) as they gave us for the TBM850.

bjratchf

@meh1951 yeah. So far I've been using the SET_FUEL_VALVE to get it from cutoff to low idle and back. Honestly, very few situations exist where you'd need the high idle (max reverse).

meh1951

With the changes to SPAD we need Condition Levers like the one we got for the TBM 850. We need Condition Lever 1 & 2 please

hangar_101

@bjratchf & @meh1951 you got to manually create these events listed below

Once you have created them you just need to create the scripts for sending the events as needed, like the example below

I have the latest SPAD version installed and just tested the B350 condition levers, they are working just fine using the events listed above.

Hope it helps you!

meh1951

I think once you upgrade to 9.14.x they won't work anymore.

hangar_101

@meh1951 I have version 9.14.4 installed and it's working just fine. Can you share more details about your spad.next settings?

meh1951

@anderson
Yes 9.14.4 still works. It was 9.14.1 that did not. The SPAD guys said they would not guarantee this to work because it was never supposed to.

meh1951

Today I got Spad 9.15.2 and none of the condition Lever code is working