KA350 Condition Levers
-
@meh1951 how are controlling the lever? Are you using one of the Bravo axis for that?
Show a printscreen of the Spad.Next setup you have for controlling the lever.
As per the printscreen you have sent before I guess your setup will be something like
LOCAL: search for RX_AXIS in the Bravo device list
The condition lever setup
Cut Off setup
If you are going to use a different axis just replace the RX_AXIS by the correct axis name
There will be 3 entries for each lever
0 - 25 Cut Off
26 - 73 Low Idle
75 - 100 High IdleYou may change these range values to whatever range is best for you.
Regards,
Anderson
-
@meh1951
No I still have problems.
Handle still not moving and LoopingJust realized I am getting 0 and 1 in the data monitor not 0 to 100 for the TURN ENG CONDITION LEVER
Failed again. Been working on this way to long.
@meh1951 you are almost there, notice you have not activated the repeat feature
It should be ON
You also can simplify the evaluation code by replacing the following line
by
Regards
Anderson
-
@meh1951 you are almost there, notice you have not activated the repeat feature
It should be ON
You also can simplify the evaluation code by replacing the following line
by
Regards
Anderson
-
@meh1951 you are almost there, notice you have not activated the repeat feature
It should be ON
You also can simplify the evaluation code by replacing the following line
by
Regards
Anderson
-
@meh1951 the very first condition should be
Your condition is different
Turb Eng Condition Lever Position:2 equals ((LOCAL:JOY .... <=100))
Delete this Turb Eng Condition Lever Position:2
Your condition
The correct condition
There's no Turbo Eng Condition Lever Position:2 in the first line.
Give it a try as indicated.
Anderson
-
@meh1951 the very first condition should be
Your condition is different
Turb Eng Condition Lever Position:2 equals ((LOCAL:JOY .... <=100))
Delete this Turb Eng Condition Lever Position:2
Your condition
The correct condition
There's no Turbo Eng Condition Lever Position:2 in the first line.
Give it a try as indicated.
Anderson
-
@meh1951 yes, scripted event window should look like this
Notice the first condition line just evaluates the lever position.
Anderson
-
@meh1951 yes, scripted event window should look like this
Notice the first condition line just evaluates the lever position.
Anderson
-
@meh1951 yes, scripted event window should look like this
Notice the first condition line just evaluates the lever position.
Anderson
@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
-
@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
@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 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 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 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 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 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 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.
-
@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.
-
@anderson how do you get those client events? My client events are blank, or it wants me to load an xml file containing them
@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
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.
