Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?
-
No problem!
IAS:
(A:AUTOPILOT FLIGHT LEVEL CHANGE, Bool) if{ (L:var_iasHoldMode, bool) if{ (>K:FLIGHT_LEVEL_CHANGE) 0 (>L:var_iasHoldMode, bool) } els{ (A:AIRSPEED INDICATED, knots) (>K:AP_SPD_VAR_SET) 1 (>L:var_iasHoldMode, bool) } } els{ (>K:FLIGHT_LEVEL_CHANGE) (A:AIRSPEED INDICATED, knots) (>K:AP_SPD_VAR_SET) 1 (>L:var_iasHoldMode, bool) }The pitch sync button is not implemented in the currently public version of the King Air as it is in my newer aircraft, but you might have some luck with the following native command:
(>K:SYNC_FLIGHT_DIRECTOR_PITCH) -
Easy! Just toggle (L:var_optionalAutopilotModePanel, bool). Enjoy! Glad this has all been working for you so well.
-
Easy! Just toggle (L:var_optionalAutopilotModePanel, bool). Enjoy! Glad this has all been working for you so well.
@Black-Square said in Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?:
Easy! Just toggle (L:var_optionalAutopilotModePanel, bool)
AP_Panel_View#(L:var_optionalAutopilotModePanel, bool)
Hmmm... this code doesn't work :-( -
I'm not sure what the scripting looks like in FSUIPC, but if I were to give you RPN code to toggle the panel on and off the same way I did for the others, it would look like this:
(L:var_optionalAutopilotModePanel, bool) ! (>L:var_optionalAutopilotModePanel, bool) -
I'm not sure what the scripting looks like in FSUIPC, but if I were to give you RPN code to toggle the panel on and off the same way I did for the others, it would look like this:
(L:var_optionalAutopilotModePanel, bool) ! (>L:var_optionalAutopilotModePanel, bool)@Black-Square said in Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?:
I'm not sure what the scripting looks like in FSUIPC, but if I were to give you RPN code to toggle the panel on and off the same way I did for the others, it would look like this:
(L:var_optionalAutopilotModePanel, bool) ! (>L:var_optionalAutopilotModePanel, bool)
Wow, it works!
I guess FSUIPC requires RPN codes. -
Actually, if I take a guess at what you might have been trying to do with FSUIPC above, you might be able to get your code to work with the addition of one character, if it was useful to you.
AP_Panel_View#(>L:var_optionalAutopilotModePanel, bool)The ">" means that you would like to write the preceding value to the L:Var, not simply read it.
-
Actually, if I take a guess at what you might have been trying to do with FSUIPC above, you might be able to get your code to work with the addition of one character, if it was useful to you.
AP_Panel_View#(>L:var_optionalAutopilotModePanel, bool)The ">" means that you would like to write the preceding value to the L:Var, not simply read it.
@Black-Square said in Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?:
The ">" means that you would like to write the preceding value to the L:Var, not simply read it.
Checked
(>L:var_optionalAutopilotModePanel, bool)This code only switches the view from:
to this:
It doesn't switch back!
-
I have simplified this one already in the next version of the King Air that has yet to be released, but to be safe, here is the full code:
OPEN: (A:CIRCUIT ON:78, bool) if{ 1 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 0 (>L:var_environmentalBleedDisabled_L, bool) } 0 (>L:var_bleedState_L, number) ENVIR OFF: (A:CIRCUIT ON:78, bool) if{ 1 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 1 (>L:var_environmentalBleedDisabled_L, bool) } 1 (>L:var_bleedState_L, number) ALL OFF: (A:CIRCUIT ON:78, bool) if{ 0 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 1 (>L:var_environmentalBleedDisabled_L, bool) } 2 (>L:var_bleedState_L, number)Just replace the "_L" with "_R" for the right-hand engine.
-
I have simplified this one already in the next version of the King Air that has yet to be released, but to be safe, here is the full code:
OPEN: (A:CIRCUIT ON:78, bool) if{ 1 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 0 (>L:var_environmentalBleedDisabled_L, bool) } 0 (>L:var_bleedState_L, number) ENVIR OFF: (A:CIRCUIT ON:78, bool) if{ 1 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 1 (>L:var_environmentalBleedDisabled_L, bool) } 1 (>L:var_bleedState_L, number) ALL OFF: (A:CIRCUIT ON:78, bool) if{ 0 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 1 (>L:var_environmentalBleedDisabled_L, bool) } 2 (>L:var_bleedState_L, number)Just replace the "_L" with "_R" for the right-hand engine.
@Black-Square said in Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?:
here is the full code
-
I have simplified this one already in the next version of the King Air that has yet to be released, but to be safe, here is the full code:
OPEN: (A:CIRCUIT ON:78, bool) if{ 1 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 0 (>L:var_environmentalBleedDisabled_L, bool) } 0 (>L:var_bleedState_L, number) ENVIR OFF: (A:CIRCUIT ON:78, bool) if{ 1 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 1 (>L:var_environmentalBleedDisabled_L, bool) } 1 (>L:var_bleedState_L, number) ALL OFF: (A:CIRCUIT ON:78, bool) if{ 0 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 1 (>L:var_environmentalBleedDisabled_L, bool) } 2 (>L:var_bleedState_L, number)Just replace the "_L" with "_R" for the right-hand engine.
@Black-Square said in Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?:
Just replace the "_L" with "_R" for the right-hand engine.
Correction after testing...
The left one is fine, but the right one.... problem!For the right-hand engine I replace the "_L" with "_R" (as you wrote):
OPEN:
(A:CIRCUIT ON:78, bool) if{ 1 1 (>K:2:ENGINE_BLEED_AIR_SOURCE_SET) 0 (>L:var_environmentalBleedDisabled_R, bool) } 0 (>L:var_bleedState_R, number)When controlling the mouse - switch animation and indication "R BL AIR OFF" everything is normal.
But when controlling from the assigned RPN code - the switch animation works visually normally, but the "R BL AIR OFF" display does not go out!Video:
https://youtu.be/lgZ4bfgMBck -
I'm sorry. That's my fault. You also need to change the last number before the "(>K:2:..."
For the right engine, the three lines should contain...
if{ 0 2 (>K:... if{ 1 2 (>K:... if{ 1 2 (>K:...I hope that makes sense! Let me know.
-
I'm sorry. That's my fault. You also need to change the last number before the "(>K:2:..."
For the right engine, the three lines should contain...
if{ 0 2 (>K:... if{ 1 2 (>K:... if{ 1 2 (>K:...I hope that makes sense! Let me know.
@Black-Square said in Black Air King Air 350- "PITCH TRIM AP/YD" и " AP ENG" events ?:
Let me know.
Everything's fine now!
-
In the King Air, the condition levers use the native bindings, so any of the following should work:
>K:AXIS_CONDITION_LEVER_1_SET >K:CONDITION_LEVER_1_SET >K:CONDITION_LEVER_1_INC >K:CONDITION_LEVER_1_DEC
