MobiFlight Community Support

Dear All,

I have a case where I have couple of com port related items connected to my PC. On the same I have an arduino mega 2560 (lets assume on COM6) where I want to run Mobiflight. During the startup of Mobiflight it takes very long for the MF to locate the 2560 on COM6 to unpload the firmware. After the firmware update to 2560 on com6 is finished I see the other coms (other than com6) in MF modules as unknown / undetected devices.

Is this the normal way , to wait for a rather long time? or is there a way to tell MF to look only do business with the 2560 on COM6 ?

Thanks and best regards

Okan Sacli

Hi Okan Sacli,

which MF version do you use?

No, it is also not normal for other USB ports to appear unless an Arduino MEGA / UNO / Pro micro is connected to them.
Basically, the start-up process of MF including the module search should be completed within 10 seconds

Hi

May it is a wire problem. We got those reports with bad quality Cables and Hubs.

If problem still exist.... Please try o other Cable from Mega to Computer ( if you got one) ...... Also try to connect to a other USB Port or with/without a HUB.

In easy words.... Please test different Cable Options and find out if you see a change of the issue.

Thank you gents for the feedback. I assume it has nothing to do with cabling already tried.

Currently I am using 9.0 but the same happened with the previous versions as well

Attached is a screenshot of what happens on my PC.

https://drive.google.com/file/d/11FKl4loAA4W0pVbWY2x37_UbiFcxs5q7/view?usp=sharing

https://drive.google.com/file/d/11JnC7isQgF648vNnIZaz3-JoUD9_k_IJ/view?usp=sharing

The Airbus COMNAV (2 units) , TCAS and THrottle are all com port based equipment (which are seen as 4 unknows)

The USB-SERIAL CH340 (on COM6) is the MF unit

I have also attached the log file as well

https://drive.google.com/file/d/11NZIZWNDfgC16IoghvcdQXyGD5E25h8E/view?usp=sharing

in the log file i read the other com ports 7 4 3 and 5 are interpreted as potentially compatible module ?

Any tips ?

THanks

Okan Sacli

Hi again.

At first.... If you like join our DISCORD .... https://discord.gg/99vHbK7.
There we can share pics and screen and we can also talk to each other if needed.
Forum is nice for problems but in case there is no file Upload option here, all situations we need to share screenshots are much more comfortable on Discord !

About Porblem.
Looks like your "other Panels" are based on a Arduino Mega, also.
Thats a bad situation in case MF Detect them same way.
Our logic basically say "Detect all Com Ports..... Ignore stuff like Headsets, mouse, Printer and so on..... Check if there is a compatible Board ( Mega, Uno, Micro, Arcaze) and if yes "try" to migrate it for Mobiflight.

If possible please confirm what Controlers are used in the other Boards.

And another question.... Does MF ask you for installing Firmware on that Boards ??? Or do you already disable the "Auto Firmware Update" Option in Settings/MF Modules Tab ??

Hello

the other com port related items are the the radio units (capt and fo) , tcas unit and throttle unit fscockpit which uses FTDI CDM drivers..

MF tries to communicate with these devices for a long time but finally at the end only installs firmware on the MEGA 2560.

If there was an option in MF to be able to select the com ports to be searched.. for example we can tell MF to look for COM6 COM10 and COM3 as an examle and ignore the rest

I will gladly join the discord group

best regards

okan sacli

Hi All

Any suggestions on this topic ?

Thanks

Okan Sacli

https://github.com/MobiFlight/MobiFlight-Connector/issues/551