Duke (Piston + Turbine) LVAR for MobiFlight
-
If you want to emulate the behavior of the knob in the simulation, then all you should have to do is read the value of the knob's pull state to determine whether to add 100 or 1,000 feet. In RPN, that would look something like this:
(L:var_AltitudeSelectorKnobPushed, bool) if{ 100 } els{ 1000 } (>K:AP_ALT_VAR_INC)Unfortunately, there is no convenient way for me to adjust the units on the ETM. For the EDM 800 in the Piston Duke, the units can be changed at any time by pressing both buttons (click spot between the two buttons) at any time, but for the ETM, the unit setup is something that can only be done by a professional when the unit is installed in the aircraft, so I did not implement it.
The startup configuration is controlled by the phase of flight selected in the free flight menu, or as part of a custom mission. For instance, if you select a starting position on the ramp, the aircraft will be cold and dark. If you select a starting location on the runway, it will be ready for takeoff, and if you select a starting position on final approach, the aircraft will be configured for approach and landing. You can edit these files, or copy and replace them with another to change the loading configuration. For instance, if you wanted to start on the ramp fully ready for taxi and takeoff, you would just replace the apron.flt file with the runway.flt file. There are other features of my aircraft that are saved between flights, but the main items, such as whether the engines are running, are controlled by the simulator.
-
@Black-Square said in Duke (Piston + Turbine) LVAR for MobiFlight:
the units can be changed at any time by pressing both buttons (click spot between the two buttons) at any time
I've setup these knobs on two touch buttons, will dual input trigger the same response as with the 'click spot' with the mouse?
-
@GunStrauss Unfortunately not. I would have had to approach the button input events in a completely different way for that to work, but I never even considered that someone would want to make that happen from their hardware. Sorry to add another button to your layout.
-
"var_altitudeAlertLatching",2
-
I coded in the LVAR for the ALT ALERT, however after I press it, the ALT ALERT stops flashing momentarily then starts flashing again. I've got identical style coding for the MASTER WARNING and MASTER CAUTION and those two function correctly after I press my button to cancel the warning/s. Can you please assist with what I might need to do differently with the ALT ALERT? thanks, John.
-
Did you set L:var_altitudeAlertLatching to 2? Setting it to zero would cause the behavior you're describing, while setting it to one would cause it to activate and stay activated.
-
Hi, thanks - I already have it set it to '2' because I thought that was correct for RESET (and that's what worked for the Master Warning and Master Caution). So, for the RESET ALT button you're saying I should set it to 1, and not 2?
And if I want a visual display button LED to trigger / flash, should I use the same LVAR with an ON VALUE of 1 (and OFF VALUE of 0)?
-
I just triple checked the code after your original post, and it's definitely
2 (>L:var_altitudeAlertLatching, number)that should do the trick. It functions no differently than the master caution and master warning. Perhaps a video might help me diagnose?For the LED, you should just check if L:var_altitudeAlertLatching == 1 to turn on the LED, since 0 or 2 are off conditions.
-
Thanks, however what is the 'number' at the end of "2 (>L:var_altitudeAlertLatching, number)" ?
I'm actually using the Pilot Deck plugin in the Elgato, so the coding is just "var_altitudeAlertLatching" and then there is a value assigned for button presses ... I have 2 set for 'ON' and 0 set for 'OFF'. Please see attached 2 pics ... you'll see the exact same principle is used for both the Master Warning and Alt Alert, except the former functions correctly and the latter does not.
-
Thank you for sharing! I think that was actually extremely helpful! I believe it's the "Reset Switch to Off Position after pressed" option that's causing the trouble. If I understand correctly, that means that it will set L:var_altitudeAlertLatching back to 0 after you release the button, which will cause it to trigger and proceed right back to 1. I don't think this would happen with the master alerters, just because of how they get triggered from their respective annunciators, but I would have to check. Although I don't use the Stream Deck, I think it might work perfectly if you just uncheck that box. Either way, please let me know how it does with the box unchecked, as that might give me another hint.
-
Many thanks for looking into it. I'd actually tried deselecting that option a little while back as I'd been thinking along the same lines, but it didn't work. I have now experimented with a number of trial and error options and got it to work, but with a strange setup (although it now works well) ... I simply reversed the setting so now have ON VALUE = 0 and the OFF VALUE = 2. I also had to change the Control States (Output Value), so that ON = 1 and OFF = 0, but 'ON ERROR' I've had to make it display a button that indicates to me I've cleared the alert. So, now I get a warning bar' showing (not flashing though - can't get it to flash) when the ALT ALERT is triggered, then an 'alert cleared' button display until such times as the alert clears itself after whatever the preset timeframe is (5 to 10 seconds). In theory, it wants to display an 'error' during that time because it doesn't recognise it as being on or off.
-
L:BKSQ_ShowCopilotInterior
I'm glad you got the altitude alteter working. I will have to think about why it works with that configuration to see if I have any further suggestions for you.
-
I'm encountering an issue where I've assigned the K:AP_PITCH_LEVELER_ON to my personal VS AP button (to switch to ATT mode), however when I do that GA lights up instead on the AP panel. Is there an error here in that VAR?
Also I don't understand how/why there is a AP GO-AROUND MODE (AUTO THROTTLE to GA), because I didn't think the Duke had any kind of auto throttle?
-
K:AP_PITCH_LEVELER_ON should do the trick, but it's possible that pressing it a second time in some circumstances could result in what you're seeing. Unfortunately, the MSFS variable to detect when go-around mode is activated is broken, so I've had to do some of my own process of elimination for the GA indicator. Looking at my code, I can see many questions I could ask in an attempt to get to the bottom of this, but let me start here: Is the pitch control mode working when you adjust the target pitch with L:var_AP_PitchKnob?
The Duke has no auto throttle, but the go-around mode can be used to position the flight director at 8° nose up with wings level for initial climb out.
