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
StevenDobler
Posts: 7
Hello,

I've spent a lot of time the last few weeks working with MobiFlight and have a couple of observations and suggestions. GREAT Software and thanks for all the hard work you have done to provide it to the flight simulator community!!

1) When using an LCD that used Pin 20 & 21 I noticed that Pins 20 & 21 are still in the pull down menu, suggesting that they are still available. Maybe delete them from the pull down menu when they are used by the LCD.
2) It might be nice to move devices in the list under the MobiFlight board up and down to group them together if so desired
3) It's nice that you can see which buttons are pressed in the log screen, but it might be nice to have a separate tab that displays the status of each switch, similar to the Windows Joystick calibration that shows a round icon for each button that toggles when a button is pressed.
4) Even when the names of devices are under 16 characters, I found when I assigned names to each of the 69 switches, LEDs, LCDs, Display modules, stepper motors and servos, it sometimes gives an error. I started using names such as "P40_PushButton_1. I had to shorten all of the names. Maybe it's because of the underscore?
5) I would be nice to have a "CLEAR" button that clears the log window. In addition to the log window, it might be nice to single line text box that shows the information about the last button that was pressed. A little easier than watching the log screen scroll by.
6) Possibly have MobiFlight search the standard path name where the Arduino IDE is usually installed and if it find it there fill this information automatically for the user rather than having the user browse to its location.
7) When you click on the "Extra" menu have "Settings" be the first item on the list rather than "Manage Orphaned Serials"
8) When you click on the "Settings" sub-menu have it go to the "MobiFlight Modules" tab rather than the "General" tab since the MobiFlight Module tab is the one most used
9) When you click on the "MobiFlight Modules" tab have it select the 1st MobiFlight board and automatically expand the list of devices under that board.
10) When you select add a device, have a help button or mouseover that provides information about what each box is used for.
11) I like that the LCDs show the message 'MobiFlight Rocks' when MobiFlight start because it lets you know things are working. Maybe have something similar for the LED display modules, perhaps cycling through the numbers to let you know those modules are working too.
2020-12-13 22:49
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Hi
Big Thanks for your ideas. A Software always need new and fresh inspiration !
You know Sebastian is the "BigBoss" ..... so my comments are just my personal opinion and not a Yes or No.

*************
iconQuote:

1) When using an LCD that used Pin 20 & 21 I noticed that Pins 20 & 21 are still in the pull down menu, suggesting that they are still available. Maybe delete them from the pull down menu when they are used by the LCD.


100% Agree. This should be easy to implement. I also think about that in the past and wondering why it is not already included.
*
iconQuote:

2) It might be nice to move devices in the list under the MobiFlight board up and down to group them together if so desired


Technical Yes... Whatever we create that devices just one time and then we jut use them and never go into this tab again. Instead of a "free" moving a sequence by Name alphabetic OR by Pin Number would be logical. The "seuqnce by creating time" is the only that make no sense to me.
*
iconQuote:

3) It's nice that you can see which buttons are pressed in the log screen, but it might be nice to have a separate tab that displays the status of each switch, similar to the Windows Joystick calibration that shows a round icon for each button that toggles when a button is pressed.


For my opinion not needed. I create a Button.... I named it.... then i know what device is this button. A Latching switch i see the position . A Momentary is always released.
If realy a "scan" is needed for this rare situation i use Logging Mode to see "what" device is pressed by toggle the specific switch.

*
iconQuote:

4) Even when the names of devices are under 16 characters, I found when I assigned names to each of the 69 switches, LEDs, LCDs, Display modules, stepper motors and servos, it sometimes gives an error. I started using names such as "P40_PushButton_1. I had to shorten all of the names. Maybe it's because of the underscore?


With 51 Devices in the past it work. May with 68 we again get the same Problem. With long names and lots of devices there can be a Memmory overdrive i think.
I personaly already recommend to not use "real Text" for the names. More logical and easy is a "Code" System. Like A12C14D
For example the first Char represent a-z the name of Mega . The second Number is the Pin. the 3rd a-z represent the Device Typ.... A= LED B= Button e.g. The 4th Number represent the Cockpit Part. 1 = MCP, 2= Overhead Hydraulics e.g..
Simply build unique 6-8 Characters long Device names. Also use them to label the wires.... the Parts and to write Excel Lists.
BUT YES..... If its possible Sebastian should chck this.... Make it possible or make a limit in legth.... A Error is no good solution !

*
iconQuote:

5) I would be nice to have a "CLEAR" button that clears the log window. In addition to the log window, it might be nice to single line text box that shows the information about the last button that was pressed. A little easier than watching the log screen scroll by.


Not needed for my Opinion. Whatever a simple new feature that should be no big deal. So YES
*
iconQuote:

6) Possibly have MobiFlight search the standard path name where the Arduino IDE is usually installed and if it find it there fill this information automatically for the user rather than having the user browse to its location.


NO. There exist no standard.... And if it would exist it´s pretty sure in "c:/programFilesx86" we fully against!
Everybody who install a programm should be able to know himself WHERE he installed it !

*
iconQuote:

7) When you click on the "Extra" menu have "Settings" be the first item on the list rather than "Manage Orphaned Serials"
8) When you click on the "Settings" sub-menu have it go to the "MobiFlight Modules" tab rather than the "General" tab since the MobiFlight Module tab is the one most used


Both Agree. Whatever also a Element we not use every day. Your in testing process already and need it. But if your Cockpit is finished you will open the settings tab maybe 1 time per month! BUT.... Yes this would be more logical.

*
iconQuote:

9) When you click on the "MobiFlight Modules" tab have it select the 1st MobiFlight board and automatically expand the list of devices under that board.


NO. I agree to do so if you got only One Board active. But if you got more then one it´s not logical to have to close the first one if you like to open the second.
So.... With one Board i agree. With 2 or more boards non should be selected by default !

*
iconQuote:

10) When you select add a device, have a help button or mouseover that provides information about what each box is used for.


I´m not a friend of Tooltips personaly. If you get experience they are no longer needed and more disturbing as helping.
For beginners helpfull but there are also other solutions. What i agree..... MF need a better Tutorial that explane the users the Information already (you like to include in tooltips)

*
iconQuote:


11) I like that the LCDs show the message 'MobiFlight Rocks' when MobiFlight start because it lets you know things are working. Maybe have something similar for the LED display modules, perhaps cycling through the numbers to let you know those modules are working too.


I not need this. If i install a element and i press TEST ( the first time after wire it) i KNOW if it run. So it will also run for the next 10 Years. I personaly never see the sense here why it show MF Rocks. But sure.... Technical it should be possible that all 7Seg show 12345678 at Startup and go Blank after MF is get into RUN mode.
Good Luck !
2020-12-14 11:47
Avatar
StevenDobler
Posts: 7
Thank you so much for taking the time to address each one of my suggestions. I appreciate the effort. Since I am relatively new to MobiFlight and only use one Arduino Mega at this time I agree with all of your answers since you guys are the experts. Once again, thank you for creating this tool and continuing to enhance it over time. You have done amazing things for the Flight Sim community!!
2020-12-18 00:40
icon