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
manners13
Posts: 3
Hi just trying to get a feel for if there's any thought on adding compatibility for HMI screens,
I've currently ordered one of the DWIN HMI 5" screens as its cheep and cheerful I ordered one without touch capability but they are available too. the plan is to put it in an Arduino powered FMC. I do a little bit of coding myself so hopefully i can figure something out to make it do as I need it to do but if anyone has any info on making it work so i can read up before it arrives the help will be greatly appreciated


:) TIA
2022-11-14 15:38
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi

I will say a direct support will not come. Those Display Systems ( instead of a simple 7Seg and LCD) need a complex Grafic. I donßt think this is compatible with our Firmware and our idea to make MF usabel with also UNO and Micro ( much smaller Mem)

BUT

Your request is a perfect example for our future new tool! ( I expect it comes with 10.0 cause it still work in Alpha Testings)
We plan for a new kind of Output ( And in the future step maybe also Input) that is no longer Device based. We "send" the Value simply to a IP Adress in the Network of the Computer.

Example:
We read with a Output Config the current Altitude... Lets say 10300 ft. Now we choose today for a Motor to show this on a Gauge or we choose for a Display to show the Number.
In the Future we can additional say "send this 10300 value to a special IP Address".

And here your Display come to the task.... Cause you can Set it to a own Controller ( Whatever Pico, Nano, Raspery, Mega and so on) and there is a own Firmware where you define the grafics and all this stuff..... The needed Information what value your Display need to show can now readed by that firmware from the know IP Adress we "store" the data via Mobiflight.

Hopefully in the future also the reversed idea work..... So Mobiflight also allow Input Configs that no longer need to use a Pin Button or a HID Joystick action.
I looking forward to say in a Input "Observe Data from IP Adress xxxxx" .... So your Touchscreen send a Signal for a Input to this "interface spot".... And MF detect it there and execute the needed action.

*******
Please stay calm.
the Output hopefully come soon. The Input is just a early idea !
Good Luck !
2022-11-15 14:57
Avatar
manners13
Posts: 3
Ok heres my thoughts on making it work,

as i want to use the screen for information rather than graphical output, i intend to create the cdu normal back ground colour using the dwin software then having a variable set to either the screen as a complete text blob just formatted correctly or have each line as seperate variables, these will need to be passed to the arduino over the usb and then sent using serial connection to the hmi to update the variables

always fun to play and find out what i can make\break :rolleyes:

i will keep some kind of update going as i progress through making the cdu

many thanks
2022-11-15 16:32
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
If you got programming skills this is also possible today.....

If we talk about a Arduino MEGA then we have 256kb of Mem .... But the Firmware uses only maybe 32kb of it.
So you have lots of Space to add own code.

In the Mobiflight Firmware there is already the part for the LCD Displays. So we be able to send 80 Chars ( 4x20) from MF to the Display.
In case we can controll more then 1 Display we can increase this again.

Solution....
You just need to programm your Display within the Artduino.... So your code is "behind" the MF Firmware.
And at the end you say the Data that is send to a imaginary LCD Display is no longer send to that display....
You just highjack this data and use it to feed your own Display Code for the HMI.

Means this is the same Idea like above.... Just you not need a own controller.... You could put it "on top" of a Mobiflight Arduino Board, and not use the future Data Comunication feature.
Good Luck !
2022-11-15 22:46
icon