KA350 Condition Levers
-
@lemny it does work in Spad, see below how I have it implemented
In the client events page I have created the following events using the B:Vars
Below an example of axis setup in Spad.Next
axis range between 0 and 25 (Cut Off)
There's a delay in the axis movement so I added a check for the condition lever position != 0 so I could activate the repeat function to make sure no matter how fast I move the lever it will always catch up and get the position right - without such check of the condition lever position it would create an infinite loop (and we don't want to waste resource on that, right?! :) )axis range between 26 and 74 (Low Idle)
- the condition lever position must be != 1 in this caseaxis range between 75 and 100 (High Idle)
- the condition lever position must be != 2 in this caseThese are all script events hence I get the levers in the game in sync with my hardware all the time.
In case someone does not know where to find the Client Events page
Some extra 2 cents (out of topic)
There are some other events I have added you guys may find useful like events for the Radar, External Power, Pressurization Alt knob (yeah I also use the same event in the C414AW), for instance. Check it out!
Regards
Anderson
-
@anderson
I have tried to replicate this but I am not sure what the reference to Local:Joy_0X16D00X09C1_Slider is or where it came from. I do not have it on my system.@meh1951 you got to replace that by whatever the appropriate var for your hardware lever/switch/button is.
This var just tells spad.next whether that button/switch of your hardware position is pressed or not - for instance.
The key piece of information here is the PROP_PITCH2_SET (-25), that's the one that actually makes the lever move to the feather position in the game. -
@meh1951 you got to replace that by whatever the appropriate var for your hardware lever/switch/button is.
This var just tells spad.next whether that button/switch of your hardware position is pressed or not - for instance.
The key piece of information here is the PROP_PITCH2_SET (-25), that's the one that actually makes the lever move to the feather position in the game. -
@anderson
Could not get the feather to work that way but I did get it to work this way
Still have not got the Condition Levers to work :-(
@meh1951 for button 26 try to setup the following
Button Pressed -> Send PROP_PITCH1_SET - Event (-25) for Left Prop
For whatever the other button used for right prop set the following
Button Pressed -> Send PROP_PITCH2_SET - Event (-25) for Right Prop
The condition levers you got to create those events listed above first
Regards,
Anderson
-
@meh1951 for button 26 try to setup the following
Button Pressed -> Send PROP_PITCH1_SET - Event (-25) for Left Prop
For whatever the other button used for right prop set the following
Button Pressed -> Send PROP_PITCH2_SET - Event (-25) for Right Prop
The condition levers you got to create those events listed above first
Regards,
Anderson
-
@anderson
Yes I got feather wotking your way...thx
Yes I created the BVars and copied what you had minus the Joy
@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 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 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
