MobiFlight Community Support

hi

is it possible to add the possibility to manage matrix keyboard. in fact i think about the possibility to use mobyflight to manage the fmc of airliner.
there is quite 70 buttons for one, so for the 2 fmc if we wire buttons one by one it will take 3 mega. with matrix keyboard it will take only 17 pins of the mega so it will be possible to use only one mega to the 2 fmc for key and led
i know that there is already a library
regard
L.S.

Not at the moment..... But Mobiflight is Open source. If You (or a other user) will do that you can contact Sebastian and if he accept your new version then it will be released.

Why we not plan it....
- Biggest Point is : There is no Limit for Arduinos in Use.... So its no problem if you use 3 Arduinos instead of 1.
- Matrix need new code that can have issues or slow down the firmware..... Again the term.... Why implement it if all is possible with current technic, too.
- Matrix is not more easy to wire ( i think its much more difficult finaly).... You need to wire every switch here too.... If you make a PCB then its no matter again if you make a matrix there or if you add connectors for 3 arduinos .

Summary.... Matrix have no benefit.... Matrix have only disadvantage. Only PRO Argument is saving some Money for Arduinos..... But here i think in a Cockpit that costs Hundrets or thousends of Dollars.... 10 $ for two additional Mega are unimportant
( Thats only my personal result) Maby Sebastian have other intentions

Not at the moment..... But Mobiflight is Open source. If You (or a other user) will do that you can contact Sebastian and if he accept your new version then it will be released.

Ha ok i thinking it was a freeware. is it a github where i can get the source code ?

Why we not plan it....
- Biggest Point is : There is no Limit for Arduinos in Use.... So its no problem if you use 3 Arduinos instead of 1.

yes it not a problem of the number of arduino. Chinese clone a really cheap. but for 70 buttons you have to use 140 wires and for 2 fmc ( for example) 280 wires. and you have to create 140 buttons on the software. with matrix keyboard you have to use less wire to connect the keyboard on arduino and the soft can create automatically the input using raw and col to assign offset.

- Matrix need new code that can have issues or slow down the firmware..... Again the term.... Why implement it if all is possible with current technic, too.

well i don't know if it will slow down the firmware. using matrix or using alone buttons, in the end the soft have to listen 70 or 140 more events.
all enhance or new devices need new code. i m new in mobiflight, it a really goo product and i hope will it continue to upgrade and accept more device. but code will be more complex and slow. fortunately pc are more and more powerful. every time you write a new line code you can introduce an issue.

Summary.... Matrix have no benefit.... Matrix have only disadvantage. Only PRO Argument is saving some Money for Arduinos.....

what do you mean by Matrix have only disadvantage, every keyboard use matrix

Regards
L.S.

Hi

The Bitbucket adress ..... https://bitbucket.org/mobiflight/mobiflightfc

****

About Wires.... You not need 140 seperate Wires for 70 Buttons...... The GRD can be shared through all buttons... So you only need 71 Wires to Arduino ( 70x Button Pin 1x GRD) ( But shure this One Ground Wire must go through ALL 70 Buttons.)

BUT In A MAtrix you also need this wires.... Every Button need a Connection to the specific Row and Collum.... Only difference is you not cable it to 70 Different Pins... You set it to your maby 9x9 Matrix Pins shared.
To prevent Ghost Keys you also need a resistor for every switch ( Ok... In a FMC there is no Double Key use normaly.... But a Matrix system MUST prevent Ghost Keys too in other parts)

As i said in older Topics.... A Matrix is interesting if you use a PCB.... Cause here you can work with printet circut for that difficult sharing Collums and Rows.....
BUT Here same argument.... If you use a PCB you can simply make 70 individual Rows for your buttons and you can add a connector where you can mount your Arduino direct ( So wires are not longer needed)

****

About slowing firmware..... I´m no programmer ! So my arguments are still theory !
I just think a button like now is pretty simple.... If Arduino Pin change status a easy call go through the Serial and Mobiflight see it.
With a Matrix every "Pin status change" must start a Loop that check what other Pin is change same Time. Then the logic must calculate what Button is pushed.

I Agree.... this is just a additional line and pretty shure it not slow down the hole system segnificant /whatever a multibuttonpress needs more code)..... But you must see....
The Mobiflight System must first define a Matrix... If we say we use a 8x8 Matrix basicly then you feel bad cause 8x8=64 You need 70 !
What happen if a user only need 20 Inputs.... Then he must use the 8x8 Matrix, too. ( Cause only 8x8 is possible in this example.)

If we plan with a custom Matrix where user can define collumes and rows himself then a big new tool must be written that generate the Matrix on Arduino for every user personal ( and not a premade solution) .
Thats maby the best idea.... But belive me.... Lots of beginners here will not be able to work with it cause its to difficult !

****
Summary.... Please appology my conservativ policy..... Just my personal thoughts !
You need to talk to Sebastian finaly.... He decide what will be implement and what not. !