MobiFlight Community Support

Welcome to the forum for MobiFlight! Feel free to reach out to the community in case you have questions, issues or just want to share great ideas or details about your latest home cockpit project.

You like MobiFlight? Donate via PayPal and support the MobiFlight development. Thanks! 

05/03/2024 - This forum is read-only

The community support for MobiFlight has moved exclusively over to our Discord server. Register for free and enjoy more interactive functions like image and video upload, voice chat. More than 7,000 registered users around the world make it a great experience!

See you on our MobiFlight Community Discord server.

A HUGE Thank You to everyone who participated in the forum, especially obviously to Pizman and Stephan who did an outstanding job over so many years providing an incredible service to the MobiFlight community.

The forum is still providing a lot of good content, hence we keep this information accessible.

icon
Avatar
JR111
Posts: 18
Hi

The developer of the AC I am mapping have removed a KEY_TOGGLE for LNAV and VNAV.
No EventID or LVAR for it either.

To trigger LNAV and VNAV I am using FSUIPC Mouse Macro and this works well. I can use my push buttons (physical) and OnPress it turns the LNAV and VNAV on respectively.

Problem here is the LED on my push button.

Is there a way to trigger the LED to ON when the OnPress is performed?

Thanks.
2021-01-08 22:35
Avatar
JR111
Posts: 18
Made some headway, but not quite there...

Input
LNAV Button SET ON
OnPress: Lua Macro, RJ85LNAVPress:press, value: 0.
OnRelease: FSUIPC Offset, 0x67A0, value: 1

LNAV Button SET OFF
OnPress: FSUIPC Offset, 0x67A0, value: 0
OnRelease: FSUIPC Offset, 0x67A0, value: 0
PreCondition: LNAV LED Button = 1

Output
LNAV LED Button
Offset: 0x67A0, Transform: $.

------------------------

When I press the button, LNAV mouse macro triggers. Then writes 1 to 0x67A0. LED on button comes on.
When I press the button (2nd time to turn off), LNAV mouse macro triggers (turns LNAV off in sim). But LED still reads "1".

Not sure how to get round this.

Thanks.
2021-01-09 16:30
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
This is unlogical overall.

1. The System can not work cause it "kill" itself and result is "1" for the LED at all time ( Wrong logic)

2. The Offset is maybe corrupted..... 67A0 is in a reserved Area.... If you use Custom systems its recommend to use also a custom Area like 66C0

3. Whatever this idea will work basicly ( with correct configs) .... It will be killed if you get unsync.
So for example if the LNAV is disabled by pressing the HDG or by a disconnection of the AP.

*************
Summary:
Build a "dummy" should be possible.... But with another logic like yours.
BUT
Realy usefull is only a solution with a Offset.... The LED should not be toggled improvisional.... it MUST show the Status of the virtual LED at all time by read it !
Good Luck !
2021-01-10 18:30
icon