KA350 Condition Levers
-
@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 wayStill 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
-
@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
-
@anderson
Thank you buddy the first screen shot answered a ton of questions for me.
I will try this...
thanks for your support!
-
@anderson
Does this look close??
-
@anderson
Repeat has been implemented but still the same results -
@anderson
Gone through a lot of programming but it's still the same results -
@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
-
@anderson
Are you talking about the
While TURB ENG CONDITION LEVER:2 equals ?? -
@anderson not sure I know how to do that
?
-
@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
Was the screen shot at 28 correct?or is this
-
@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
-
@anderson
Changed the range still does not work.The logic works but the Levers never move