Duke Lvar Values Not Correct

jmarkows

Hey Nick,

Didn't really see a good topic to put this in, as it feels silly to make something so small/quick it's own topic.

I had a few spare buttons on the Logitech throttle I'm using for mixture, and I mapped the cowl flap open/close Lvars for the left and right flaps. The manual says that 0 is Open, 2 is Close, so by extension 1 is Off, however in practice it seems that 0 is Off, 1 is Open, and 2 is Close.

Just an FYI.

I suppose if anyone else finds discrepancies in the Lvar documentation this is probably a good place to collect them.

Black Square

This was one of the first issues reported with the Duke, actually. Thanks for posting it anyway! I always appreciate it, because it helps me make sure I've fixed all these things when I hear about them multiple times.

e4rthdog

There is also something going on with the AP_PITCH_LEVELER_ON Instead of turning on the ATT it turns on the GA mode. I saw a solution for spad.next but it would be nice to have it working as a toggle event and just assign it to a button.

Black Square

I know why it thinks it's in Go-Around mode (when no other vertical mode is selected, it has to assume GA mode, because the SimVar for go around mode doesn't work correctly...), but AP_PITCH_LEVELER_ON should definitely work. That's the same event that's triggered when you click on the attitude button in the virtual cockpit.

e4rthdog

@Black-Square said in Duke Lvar Values Not Correct:

I know why it thinks it's in Go-Around mode (when no other vertical mode is selected, it has to assume GA mode, because the SimVar for go around mode doesn't work correctly...), but AP_PITCH_LEVELER_ON should definitely work. That's the same event that's triggered when you click on the attitude button in the virtual cockpit.

I've tested it in FSUIPC and in Mobiflight and by just using the var goes to GA.. but just calling AP_PITCH_LEVELER_ON not passign any value or doing anything else.

Black Square

I just tried it here with the command in the MSFS controls settings, and it indicates attitude holding mode as expected. Have you tried it with the native control assignments menu? I would FSUIPC and Mobiflight to behave exactly the same, but if it works from within the simulator, then we know that something strange is going on. Do you know what the suggested solution in Spad.next is? That might give me a hint.

e4rthdog

@Black-Square I will try from native.

Take alook here in this post in this forum: ATT SPAD

Black Square

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.

e4rthdog

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

Black Square

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!

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)