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!
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.
Hallo pizman,
ich baue zur Zeit das OVHD und hatte auch das Problem mit dem mehrmaligen Drücken der Taster und hatte schon vor, LeoBodnars zu kaufen. Dank dieses Artikels, durchgewurschelt mit meinem bißchen Englisch, habe ich es mit der richtigen Konfiguration - on press + release - fast hinbekommen. Nachdem ich im Modus release noch die 7 Haken bei "maskiere den Wert" entfernt habe, funktionierte alles tadellos.
Gruß Klaus
Hi Klaus, thank you for your precious help! so the solution is to leave all the tick on the 7 bytes?
for example Ovherad External Power:
on press: offset 0x7398 event 0 (leaved all 7 bytes)
release also set with 0x7398 event ?? (leaved all 7 bytes)
7398 1 Byte Read bits to get LED status :
0 ELEC EXT PWR ON
1 RAT&EMER GEN FAULT
2 Reserved
3 GPWS SYS FAULT
4 GPWS SYS OFF
5 GPWS G/S OFF
6 GPWS FLAP OFF
7 GPWS LDG FLAP3 ON
What about ECAM buttons (momentary)?
example 0x78ED 4 ECP DOOR Key down (see value 62 for UP event)
is to set the same thing of a korry in press 4 and in release 62 ?
What are you guys doing ???
Hi Klaus, thank you for your precious help! so the solution is to leave all the tick on the 7 bytes?
for example Ovherad External Power:
on press: offset 0x7398 event 0 (leaved all 7 bytes)
release also set with 0x7398 event ?? (leaved all 7 bytes)
This is clearly a OUTPUT Offset.
7398 1 Byte Read bits to get LED status :
0 ELEC EXT PWR ON
1 RAT&EMER GEN FAULT
2 Reserved
3 GPWS SYS FAULT
4 GPWS SYS OFF
5 GPWS G/S OFF
6 GPWS FLAP OFF
7 GPWS LDG FLAP3 ON
If you like to light a LED here you need to read the specific BIT .... So in Bitmask you must disable all bits expect the one you like to read !
BUT
With this offset you can NOT make a INPUT !!!
The Input for the EXT Power is.... Offset 78ED Value 33 (toggle)
********
Sorry,
I wanted to ask you about the inputs I was wrong to report the offset of the outputs that work very well.
For the input then Offset 78ED Value 33 do I have to disable all 7 bytes?
Another strange thing that happens on the inputs, to some even if all the contacts on mobiflight are verified that at the input does not detect anything. Some korry don't give the signal. I also tried to move them individually to another arduino and check that they have not exceeded 58 pins (usually I always keep around 50 no more) the signal is not taken (even if I check with debug). I have also checked the offset several times but nothing. An example is the IGN START mode which is between the two starters 1 and 2. for example the crank works and if I move the START mode offst to that position it doesn't even go there.