Duke Lvar Values Not Correct

[e4rthdog]

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

[Black Square]

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)

[Avionic]

@e4rthdog Using Mobiflight I have a line saying "(A:PLANE PITCH DEGREES, degrees) (>L:var_AP_PitchKnob)" in order to get the pitch wheel to go to current pitch just like it does, when you click the physical button.

[e4rthdog]

Thanks! I need to find out if i can do that in FSUIPC or i need to switch the profile from fsuipc to mobiflight

[e4rthdog]

Thanks it worked.

For anyone wondering how to do this in FSUIPC:

Page 49 of the advanced FSUIPC manual:

• Create a file myevents.txt in 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_HOLD to the press event of the button and the duke-att-wheel-rst preset to the release of the same button. In that way the AP goes to ATT mode at the current pitch.

[Russos]

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!

[Randolf]

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

[Russos]

Thank you!
Then I don't really understand the B event syntax for separate control for toggle switch

[SMN204]

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

LandingLightOn# (2K:LANDING_LIGHTS_SET)
LandingLightOff# (0K:LANDING_LIGHTS_SET)

Can you tell me how to write a correctly?

[Randolf]

@SMN204 don't have FSUIPC here to test, but try this:

LandingLightOn#2 (>K:LANDING_LIGHTS_SET)

LandingLightOff#0 (>K:LANDING_LIGHTS_SET)

[SMN204]

@Randolf said in Duke Lvar Values Not Correct:

@SMN204 don't have FSUIPC here to test, but try this:

LandingLightOn#2 (>K:LANDING_LIGHTS_SET)

LandingLightOff#0 (>K:LANDING_LIGHTS_SET)

It's working! Thank you!

[Rolo Bach]

Can't find on the manual any Lvar to set external power and heater. May be posted here?
Thanks.

[hangar_101]

@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

[hangar_101]

@Rolo-Bach for the Heater the LVAR:bksq_PreHeater will do the job (0 = OFF, 1 = ON)

[Rolo Bach]

Many thanks !!!