TBM850 Mapping 3 position Condition Lever Help

[meh1951]

Need some help mapping the 3 position lever to HC Bravo using SPAD.Next.

tia

I think I got it. Re-Purpose of the BKSQ KA 350 Condition Lever

First you need 4 variables. I have eight because I also have the BKSQ KA350

Since the 1.1 patch you should replace B:FUEL_1_Condition_Lever_X with BKSQ_ConditionLever works like a top.
:-)

[Melon]

@meh1951 I just use the Mixture 1 Axis. Just need to move the mixture lever to halfway for low idle and all the way for high idle, there is a pretty big dead zone between movement points.

[eker]

@melon Tried this - but touched the lever (my case a rotary switch) in flight with in flight shutdown.
It is only used in start/shutdown, I am only using the click spot - works fine for me.

[meh1951]

@melon
I can get it to work manually or in controls in FS2020. I'm trying to get some help using SPAD.Next

[meh1951]

@eker
I can get it to work manually or in controls in FS2020. I'm trying to get some help using SPAD.Next

[Franck]

Hello,
I cannot find B:Fuel_1_Condition_Lever_....
Do you have an idea why ?
Thanks for reply

[Phil7789]

@franck It seem that BVars are only available if you're in DevMode in MSFS. They currently are not accessible to the outside of the sim.

So while the above solution might work in DevMode it is not suitable for the "standard" sim

[arhuako]

@franck Hi, I am using this working config. Hope it helps.

[ianbot]

For those of you that use AAO, I had fiddle with things a bit. I found forum post from the Lorby dev (that I didn't bookmark) and ended up on this solution. I highlighted the key settings in blue:

Target the variable B:FUEL_1_Condition_Lever_Set, set the axis min and max to 0 and 2, respectively, and set the rounding to int.

[Voice of Reason]

@ianbot From the developer:

'I just wanted to let you know that I have added an L:Var for the condition lever in the next update. It will be "L:BKSQ_ConditionLever, number" (0-2). Now, perhaps you can all help me with something. I have seen this request in my other aircraft, and I have seen people who also insist on using the backup L:Var for the turbocharged mixture control in my Baron and Bonanza. Is there a reason that you don't all just use the default mixture control axis? I will admit that I do not check every possible type of hardware and binding software for every feature in my aircraft, but for something as simple as the default mixture axis, I didn't think it could cause this much trouble. I would really appreciate an explanation, if someone could spare the time. Thank you!'

Hope that helps and we look forward to any further useful replies.

[TheFly77]

@voice-of-reason There have been cases where using the default mixture axis caused unwanted effects in the engine behaviour. That is why a separate axis/events are preferred in my opinion.

[meh1951]

Thanks for;
The condition lever position can now be controlled via the L:Var L:BKSQ_ConditionLever
from 0-2. This should not be necessary, since the condition lever is most easily
controlled via the default mixture bindings; however, it was added for convenience.