MobiFlight Community Support

I also put in for a feature request, but would also like to add some thoughts into the forum. The basic concept is really when adding multiplexers to treat them as potential inputs or outputs for other devices. The specific case I am focused on at the moment is inputs and encoders. At the moment an encoder can only be bound to a _pin1 and _pin2, which would be on the main arduino board. I have forked the connector and firmware projects and went through the code and also did some preliminary vetting. So the device objects & controls are handled within the firmware and put out '30,MUX-01,x,y' for mux's and '6,Encoder,x' output to serial comms. I was thinking it might be possible to extend 'MFEncoder' with '_IsMux' and '_MuxName' which could potentially bind MFEncoder to MFDigInMux inputs. Default '_IsMux' would by 0. If mapped to a Mux, would be 1 and '_MuxName' could be bound to port via MFDigInMux:_name and still leverage is MFEncoder's _pin1 & _pin2 fields, but would be a pair of input pins on MFDigInMux.

Hi

Here the Forum is the wrong adress.

Our basic intention is still the same like in the past.... If you need more devices simply use more Megas.
For sure we meanwhile allow Multiplexer and Shifters in case some users ask for this over and over again.... But we say its not our intention to reduce the number of Megas by implement more advanced stuff.
So ( for my point of view) choose for a Encoder a special Mux Device and there 2 Pins is more advanced as choose for 2 Pins of a Mega who still exist without need any additional Mux Device.

BUT

We have some users like you who work on those ideas. Join our DISCORD https://discord.gg/99vHbK7 or be directly a part of the Github Team... https://github.com/MobiFlight

We pretty sure not block those ideas.... And user can share there "advanced" Firmwares.... But you need to talk to Sebastian if he like to implement those in our Main Brand.
I don´t think so.... But he is the Boss... Simply talk to him !