• Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum

KA350 Condition Levers

Scheduled Pinned Locked Moved Steam Gauge Overhaul
48 Posts 5 Posters 3.2k Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by meh1951
    #20

    @anderson

    Does this look close??

    b558ad02-8120-4de3-b1e7-8fefda9b0d57-image.png

    b56e6a5f-cba1-4a74-bd07-d7b1754175ef-image.png

    f67a4f1b-70e9-4a2f-b307-ead7a7d53beb-image.png

    fb2fb243-3087-4989-b5e3-f11cb3bc1969-image.png

    M 1 Reply Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to meh1951 on last edited by meh1951
    #21

    @meh1951
    No I still have problems.
    Handle still not moving and Looping

    Just 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.

    hangar_101H 1 Reply Last reply
    0
  • hangar_101H Offline
    hangar_101H Offline
    hangar_101
    replied to meh1951 on last edited by
    #22

    @meh1951 you are almost there, notice you have not activated the repeat feature

    866dbfc4-6d55-401d-9419-cd71403c2d8f-image.png

    It should be ON

    You also can simplify the evaluation code by replacing the following line

    d6398601-6dbe-4d51-a47b-d56af26742dd-image.png

    by

    7bad4c3a-e8e2-40af-b834-1f07a30c208b-image.png

    Regards

    Anderson

    Hangar 101

    M 2 Replies Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by
    #23

    @anderson
    Repeat has been implemented but still the same results

    1 Reply Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by
    #24

    @anderson
    Gone through a lot of programming but it's still the same results

    ccd74373-ff83-4258-8ced-240cef332f5e-image.png

    hangar_101H 1 Reply Last reply
    0
  • hangar_101H Offline
    hangar_101H Offline
    hangar_101
    replied to meh1951 on last edited by hangar_101
    #25

    @meh1951 the very first condition should be

    5d09c751-f887-452d-977d-a4e25ed4a557-image.png

    Your condition is different

    Turb Eng Condition Lever Position:2 equals ((LOCAL:JOY .... <=100))

    Delete this Turb Eng Condition Lever Position:2

    Your condition
    f4e96980-2d85-444a-9627-6ef729e678d8-image.png

    The correct condition
    429dbb74-547d-4abf-9bf7-b61330a86df5-image.png

    There's no Turbo Eng Condition Lever Position:2 in the first line.

    Give it a try as indicated.

    Anderson

    Hangar 101

    M 1 Reply Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by
    #26

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

    hangar_101H 1 Reply Last reply
    0
  • hangar_101H Offline
    hangar_101H Offline
    hangar_101
    replied to meh1951 on last edited by
    #27

    @meh1951 yes, scripted event window should look like this

    4826de71-06b1-4448-be27-b83bbefe5bae-image.png

    Notice the first condition line just evaluates the lever position.

    Anderson

    Hangar 101

    M 2 Replies Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by meh1951
    #28

    @anderson not sure I know how to do that

    791de9c9-bd9a-43ed-a734-78c6bf992e97-image.png

    ?

    1 Reply Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by meh1951
    #29

    @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_101H 1 Reply Last reply
    0
  • hangar_101H Offline
    hangar_101H Offline
    hangar_101
    replied to meh1951 on last edited by hangar_101
    #30

    @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.

    Hangar 101

    M 1 Reply Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by meh1951
    #31

    @anderson
    Was the screen shot at 28 correct?

    or is this

    b556ae46-5a8d-400c-8e69-81450aaa587f-image.png

    hangar_101H 1 Reply Last reply
    0
  • hangar_101H Offline
    hangar_101H Offline
    hangar_101
    replied to meh1951 on last edited by
    #32

    @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

    Hangar 101

    M 3 Replies Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by
    #33

    @anderson
    Changed the range still does not work.

    The logic works but the Levers never move

    1 Reply Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by meh1951
    #34

    @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

    378a62aa-cdda-4d48-ae98-80efe8469c16-image.png

    999310c0-0a85-41fd-b4de-77f8576d5108-image.png

    5d31d633-7ed4-4360-8314-845fd9c26de1-image.png

    74d9f2f0-8ddf-4be6-962e-c670809fc330-image.png

    1 Reply Last reply
    1
  • M Offline
    M Offline
    meh1951
    replied to hangar_101 on last edited by
    #35

    @anderson
    Not working again...:-(

    hangar_101H 1 Reply Last reply
    0
  • hangar_101H Offline
    hangar_101H Offline
    hangar_101
    replied to meh1951 on last edited by
    #36

    @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.

    Hangar 101

    B 1 Reply Last reply
    0
  • B Offline
    B Offline
    bjratchf
    replied to hangar_101 on last edited by
    #37

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

    M hangar_101H 2 Replies Last reply
    0
  • M Offline
    M Offline
    meh1951
    replied to bjratchf on last edited by
    #38

    @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.

    B 1 Reply Last reply
    0
  • B Offline
    B Offline
    bjratchf
    replied to meh1951 on last edited by
    #39

    @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).

    1 Reply Last reply
    0

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Users