Duke Lvar Values Not Correct
-
Thanks for the link. Oooh, are you using the PMS50 GTN when you try this? I see in my code that the PMS50 won't work with the pitch leveler command, and I used "K:AP_ALT_HOLD" instead.
-
Thanks for the link. Oooh, are you using the PMS50 GTN when you try this? I see in my code that the PMS50 won't work with the pitch leveler command, and I used "K:AP_ALT_HOLD" instead.
@Black-Square said in Duke Lvar Values Not Correct:
Thanks for the link. Oooh, are you using the PMS50 GTN when you try this? I see in my code that the PMS50 won't work with the pitch leveler command, and I used "K:AP_ALT_HOLD" instead.
That was it! Thanks.
-
Delightful! Thanks for responding so that others with the same question will be able to search for this. I'm glad that's all it was!
-
Delightful! Thanks for responding so that others with the same question will be able to search for this. I'm glad that's all it was!
@Black-Square said in Duke Lvar Values Not Correct:
Delightful! Thanks for responding so that others with the same question will be able to search for this. I'm glad that's all it was!
One thing more. I was in flight and using K:AP_ALT_HOLD switched to ATT but it started ascending fast. I suppose i have to use another event also to just center the ATT wheel? When i press the ATT button it doesn't behave like this. It is centered.
-
Ah yes, I recall hitting that issue with the PMS50 too. I wish there was an easier solution, but simply writing the aircraft's current pitch to the pitch knob should solve the problem:
(A:PLANE PITCH DEGREES, degrees) (>L:var_AP_PitchKnob, number) -
@Black-Square said in Duke Lvar Values Not Correct:
Delightful! Thanks for responding so that others with the same question will be able to search for this. I'm glad that's all it was!
One thing more. I was in flight and using K:AP_ALT_HOLD switched to ATT but it started ascending fast. I suppose i have to use another event also to just center the ATT wheel? When i press the ATT button it doesn't behave like this. It is centered.
-
Thanks it worked.
For anyone wondering how to do this in FSUIPC:
Page 49 of the advanced FSUIPC manual:
-
Create a file
myevents.txtin the fsuipc directory -
Create a profile entry there like this:
duke-att-wheel-rst#(A:PLANE PITCH DEGREES, degrees) (>L:var_AP_PitchKnob, number)bind the duke-att-wheel-rst preset to the button you like.
I assign the
AP_ALT_HOLDto the press event of the button and theduke-att-wheel-rstpreset to the release of the same button. In that way the AP goes to ATT mode at the current pitch. -
-
Hello! I can’t understand how Left/Right Landing Light works
B:LIGHTING_LANDING_1_Toggle - is this a button to toggle?
(1 K:LANDING_LIGHTS_SET) - is this for the toggle switch? But what does the number 1 (or 2) before the letter K mean? There seems to be no such syntax in Mobileflight.Thank you!
-
Hello! I can’t understand how Left/Right Landing Light works
B:LIGHTING_LANDING_1_Toggle - is this a button to toggle?
(1 K:LANDING_LIGHTS_SET) - is this for the toggle switch? But what does the number 1 (or 2) before the letter K mean? There seems to be no such syntax in Mobileflight.Thank you!
-
@Russos
K:LANDING_LIGHTS_SET is the name of the event, and you should call it with parameter 0 for both OFF and 2 for ON.
If you want to control them separately, you'll need to use the B events.@Randolf said in Duke Lvar Values Not Correct:
K:LANDING_LIGHTS_SET is the name of the event, and you should call it with parameter 0 for both OFF and 2 for ON.
If you want to control them separately, you'll need to use the B events.I need one switch for both (left and right) for FSUIPC
I wrote it like this... probably wrong
Not workLandingLightOn# (2K:LANDING_LIGHTS_SET)
LandingLightOff# (0K:LANDING_LIGHTS_SET)Can you tell me how to write a correctly?
-
@Randolf said in Duke Lvar Values Not Correct:
K:LANDING_LIGHTS_SET is the name of the event, and you should call it with parameter 0 for both OFF and 2 for ON.
If you want to control them separately, you'll need to use the B events.I need one switch for both (left and right) for FSUIPC
I wrote it like this... probably wrong Not workLandingLightOn# (2K:LANDING_LIGHTS_SET)
LandingLightOff# (0K:LANDING_LIGHTS_SET)Can you tell me how to write a correctly?
-
@SMN204 don't have FSUIPC here to test, but try this:
LandingLightOn#2 (>K:LANDING_LIGHTS_SET)LandingLightOff#0 (>K:LANDING_LIGHTS_SET) -
Can't find on the manual any Lvar to set external power and heater. May be posted here?
Thanks.@Rolo-Bach here as I have it done using spad.next for External Power - it's mapped to a StreamDeck button
External Power On
External Power Off
StreamDeck example
-
Can't find on the manual any Lvar to set external power and heater. May be posted here?
Thanks.@Rolo-Bach for the Heater the LVAR:bksq_PreHeater will do the job (0 = OFF, 1 = ON)
