MobiFlight Community Support

Hello to the whole community.
I'm a new user of mobiflight, my name is Davide, I write from Italy and I apologize for my english, but I use the google translator.

I have a problem with the software and I hope you can help me.

Following the tutorials I connected the arduino card one, when I opened mobiflight it automatically uploaded the firmware.

On a bradboard I connected an LED with adequate resistance connecting the GND to the negative and pin 2 of the card to the LED positive.

I added an output led to pin 2 in the mobiflight setting but when I go to test it the LED lights up little, connecting a 20 04 display and setting it as tutorial in mobiflight modules after the upload does not appear the writing in the middle of the display and doing a test does not write anything.

To be sure I tried with the same configuration with the IDE of arduino to turn on the LED and write 4 lines on the display and everything works, so also the i2c address is correct.

Does anyone have any suggestions?

Hello to all

benvenuto a mobiflight mio amico

Following the tutorials I connected the arduino card one, when I opened mobiflight it automatically uploaded the firmware.

I think google translator just translate "ARDUINO UNO" into "arduino one".

Please Note:
Arduino UNO is not 100% compatible with mobiflight.... Some things work... others not work.
Please appology we currently not support UNO and can not give you a solution.
It´s HIGH recommend to use Arduino MEGA (or a cheap MEGA Clone) ! Here normaly all functions work fine.... and Issues get fixed as soon as possible !

So....
Please confirm you use a UNO at the moment..... And if Yes please switch to MEGA ! .... Then tryout your config again....
Pretty shure it work then... if NOT please ask again here and explane detailed your config !

Hello,
I confirm to use arduino UNO , I will immediately take a mega, is clone compatible?

you can give some examples of things that work with UNO, only to do some trial waiting for the mega.

thanks for your reply, we'll be back soon.

Hi again....

90% of users here work with "Chineese Clone Megas" . I can not 100% garantee that ALL work fine.... But we not get any reply about not working Boards... ( And if yes sebastian couild implement some exotic boards with a little hotfix) So this should be no problem !

About the UNO.....

Mobiflight was based for MEGA all the time.... 1 Year ago sebastian tryd to duplicate the software nearly 1:1 to the UNO and hope it workes..... But after some time and more user testings we get lots of bug reports.....
Sebastian first tryd to solve this.... But for every solved problem we get 2 new problems again.....

Finaly he think its not profitable to spent his time with the UNO if MEGA is already working fine..... Much better is to spent the time in new features like LCD Display and so on !

Summary.... I stop testing the UNO long time ago....I can´t tell you what exactly is working and what is bugged. So i can´t tell you if your problem is technical or by a wrong imput from youreself..... With a MEGA i can reproduce your problem and can give exact solutions !

Thanks for your answer.

I'm already testing a mega card and up to 5 minutes ago everything was fine, but it stopped working.
I loaded a sketch from IDE arduino and it works well, when load mobiflight, updates the fimware automatically and tells me that it went well but I do not see the card, if I manually redo the firmware update tells me that there was an error .
I paste the debug:

20/01/2018 22:57:19(263): Serialized Arcaze Extension Module Settings: <?xml version="1.0" encoding="utf-16"?>
<ArrayOfArcazeModuleSettings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" />
20/01/2018 22:57:08(394): Something went wrong when flashing with command
"C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avrdude" -C"C:\Program Files (x86)\Arduino\hardware\tools\avr\etc\avrdude.conf" -patmega2560 -cwiring -P\\.\COM9 -b115200 -D -Uflash:w:"C:\Users\david\Downloads\MobiFlightConnector-7.4.0\firmware\mobiflight_mega_1_8_0.hex":i
20/01/2018 22:57:08(394): Firmware Upload Exit Code: 1
20/01/2018 22:57:08(175): RunAvrDude : -C"C:\Program Files (x86)\Arduino\hardware\tools\avr\etc\avrdude.conf" -patmega2560 -cwiring -P\\.\COM9 -b115200 -D -Uflash:w:"C:\Users\david\Downloads\MobiFlightConnector-7.4.0\firmware\mobiflight_mega_1_8_0.hex":i
20/01/2018 22:57:08(175): RunAvrDude : "C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avrdude"
20/01/2018 22:57:08(175): MobiflightModule.disconnect: Already Disconnected Default at COM9
20/01/2018 22:57:08(159): MobiflightModule.disconnect: Already Disconnected Default at COM9
20/01/2018 22:57:08(159): ExecutionManager.AutoConnectStop:Stopped auto connect timer
20/01/2018 22:56:55(138): ExecutionManager.AutoConnectStart:Started auto connect timer
20/01/2018 22:56:55(122): MobiFlightCache.RegisterModule(:COM9)
20/01/2018 22:56:55(122): MobiFlightModule.GetInfo: 7.38.20.4.Display4R:3.2.Verde:3.3.Blu:7.39.16.2.Display2R:2.4.5.Encoder:, ,,
20/01/2018 22:56:51(964): MobiflightModule.connect: Connected to Default at COM9 of Type 7.38.20.4.Display4R:3.2.Verde:3.3.Blu:7.39.16.2.Display2R:2.4.5.Encoder: (DTR=>True)
20/01/2018 22:56:51(948): Firmware Upload Exit Code: 0
20/01/2018 22:56:43(191): RunAvrDude : -C"C:\Program Files (x86)\Arduino\hardware\tools\avr\etc\avrdude.conf" -patmega2560 -cwiring -P\\.\COM9 -b115200 -D -Uflash:w:"C:\Users\david\Downloads\MobiFlightConnector-7.4.0\firmware\mobiflight_mega_1_8_0.hex":i
20/01/2018 22:56:43(188): RunAvrDude : "C:\Program Files (x86)\Arduino\hardware\tools\avr\bin\avrdude"
20/01/2018 22:56:43(183): MobiflightModule.disconnect: Already Disconnected Default at COM9
20/01/2018 22:56:43(154): MobiflightModule.disconnect: Already Disconnected Default at COM9
20/01/2018 22:56:43(154): ExecutionManager.AutoConnectStop:Stopped auto connect timer
20/01/2018 22:56:38(706): MobiFlightCache.connect: Clearing modules
20/01/2018 22:56:38(675): ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
20/01/2018 22:56:33(689): MobiFlightCache.connect: Clearing modules
20/01/2018 22:56:33(673): ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
20/01/2018 22:56:32(861): Set Debug in ComboBox: logLevelComboBox
20/01/2018 22:56:28(742): ExecutionManager.AutoConnectStart:Started auto connect timer
20/01/2018 22:56:28(727): MobiFlightCache.connect: Clearing modules
20/01/2018 22:56:28(696): ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
20/01/2018 22:56:28(696): ExecutionManager.AutoConnectStart:Started auto connect timer
20/01/2018 22:56:28(680): MobiFlightCache.connect: Clearing modules
20/01/2018 22:56:28(680): MobiFlightCache.connect: Clearing modules
20/01/2018 22:56:28(664): ExecutionManager.autoConnectTimer_Tick(): AutoConnect Modules
20/01/2018 22:56:28(633): No updates necessary. Your version: 7.4.0.0, Latest version: 7.4.0
20/01/2018 22:56:28(319): Checking for updates
20/01/2018 22:56:28(288): MobiflightModule.disconnect: Disconnected at COM9
20/01/2018 22:56:28(208): MobiFlightModule.GetInfo: 7.38.20.4.Display4R:3.2.Verde:3.3.Blu:7.39.16.2.Display2R:2.4.5.Encoder:, ,,
20/01/2018 22:56:25(50): MobiflightModule.connect: Connected to Default at COM9 of Type Arduino Mega 2560 (DTR=>True)
20/01/2018 22:56:25(35): Checking for compatible module: VID_8087&PID_0A2A
20/01/2018 22:56:25(35): Found potentially compatible module Arduino Uno by VID/PID: VID_2341&PID_0043@COM8
20/01/2018 22:56:25(35): Found potentially compatible module Arduino Uno by VID/PID: VID_2341&PID_0043@COM7
20/01/2018 22:56:25(35): Found potentially compatible module Arduino Uno by VID/PID: VID_2341&PID_0043@COM6
20/01/2018 22:56:25(35): Checking for compatible module: VID_2341&PID_0043
20/01/2018 22:56:25(35): Found potentially compatible module: VID_2341&PID_0042@COM9
20/01/2018 22:56:25(35): Checking for compatible module: VID_2341&PID_0042
20/01/2018 22:56:25(35): Checking for compatible module: VID_2109&PID_2813
20/01/2018 22:56:25(35): Checking for compatible module: VID_1DD2&PID_22A0
20/01/2018 22:56:25(35): Checking for compatible module: VID_1DD2&PID_1150
20/01/2018 22:56:25(35): Checking for compatible module: VID_1532&PID_0208&MI_02
20/01/2018 22:56:25(35): Checking for compatible module: VID_1532&PID_0208&MI_01
20/01/2018 22:56:25(35): Checking for compatible module: VID_1532&PID_0208&MI_00
20/01/2018 22:56:25(35): Checking for compatible module: VID_1532&PID_0208
20/01/2018 22:56:25(35): Checking for compatible module: VID_1058&PID_25E1
20/01/2018 22:56:25(35): Checking for compatible module: VID_0D8C&PID_0012&MI_03
20/01/2018 22:56:25(35): Incompatible module skipped: USB Audio Device - VID/PID: VID_0D8C&PID_0012&MI_00
20/01/2018 22:56:25(35): Checking for compatible module: VID_0D8C&PID_0012&MI_00
20/01/2018 22:56:25(35): Checking for compatible module: VID_0D8C&PID_0012
20/01/2018 22:56:25(35): Checking for compatible module: VID_0C45&PID_760B&MI_01
20/01/2018 22:56:25(35): Checking for compatible module: VID_0C45&PID_760B&MI_00
20/01/2018 22:56:25(35): Checking for compatible module: VID_0C45&PID_760B
20/01/2018 22:56:25(35): Checking for compatible module: VID_09F3&PID_0064
20/01/2018 22:56:25(35): Checking for compatible module: VID_0781&PID_556C
20/01/2018 22:56:25(35): Checking for compatible module: VID_06A3&PID_A2AE&MI_01
20/01/2018 22:56:25(35): Checking for compatible module: VID_06A3&PID_A2AE&MI_00
20/01/2018 22:56:25(35): Checking for compatible module: VID_06A3&PID_A2AE
20/01/2018 22:56:25(35): Checking for compatible module: VID_06A3&PID_712C
20/01/2018 22:56:25(35): Checking for compatible module: VID_06A3&PID_0D05
20/01/2018 22:56:25(35): Checking for compatible module: VID_06A3&PID_0BAC
20/01/2018 22:56:25(35): Checking for compatible module: VID_06A3&PID_0763
20/01/2018 22:56:25(35): Checking for compatible module: VID_05E3&PID_0610
20/01/2018 22:56:25(35): Incompatible module skipped: Galaxy S8 - VID/PID: VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android
20/01/2018 22:56:25(35): Checking for compatible module: VID_04E8&PID_6860&MS_COMP_MTP&SAMSUNG_Android
20/01/2018 22:56:25(35): Incompatible module skipped: SAMSUNG Mobile USB Modem - VID/PID: VID_04E8&PID_6860&Modem
20/01/2018 22:56:25(35): Checking for compatible module: VID_04E8&PID_6860&Modem
20/01/2018 22:56:25(35): Checking for compatible module: VID_04E8&PID_6860
20/01/2018 22:56:25(35): Checking for compatible module: VID_046D&PID_C52B&MI_02
20/01/2018 22:56:25(35): Checking for compatible module: VID_046D&PID_C52B&MI_01
20/01/2018 22:56:25(35): Checking for compatible module: VID_046D&PID_C52B&MI_00
20/01/2018 22:56:25(35): Checking for compatible module: VID_046D&PID_C52B
20/01/2018 22:56:25(35): Checking for compatible module: VID_044F&PID_B108
20/01/2018 22:56:25(35): Checking for compatible module: VID_03EB&PID_2FEF
20/01/2018 22:56:25(35): Checking for compatible module: VID_0000&PID_000B
20/01/2018 22:56:25(35): Checking for compatible module: VID_0000&PID_0002
20/01/2018 22:56:25(35): Checking for compatible module: ROOT_HUB30
20/01/2018 22:56:25(35): ^(VID_1B4F&PID_9206|VID_2341&PID_8036|VID_2341&PID_0042|VID_2341&PID_0010|VID_8087&PID_0024|VID_1A86&PID_7523|VID_2A03&PID_0042|VID_0403&PID_6001|VID_2341&PID_0043|VID_2A03&PID_0043)
20/01/2018 22:56:24(941): MainForm() : Logger initialized Debug


I tried to close and reopen mobiflight but it does not work, I tried to do the same thing after the first upload that seems to be successful, but nothing to do.
I confirm that if I load an arduino sketch again, the card works.
What can I do?
Before it stopped working I was able to display data on two LCD displays with addresses 26 and 27, all in a very simple way until it stopped working.

Help me please ...

I not understand....

WHAT is stop ??

Do you mean the Board is not working and Mobiflight not "see" it ??
Or do you mean Mobiflight itself not work and can not be started ??

If board is problematic you should try a complete restart ( Use EEPROM CLEAR Sketch in arduino IDE to remove firmware)

If Mobiflight programm is not running THEN you pretty shure got a wrong config in use..... In That case please Delete/remove the current used file from its saveplace..... Then Mobiflight will start with the example file it was deliverd.....
Thats a old problem... if you make a misstake and save this.... Then Mobiflight will not running again..... the Autoload File ( Last used file you saved at last season) MUST be 100% correct !

Hi, I confirm that the problem was the card!

Everything has been solved with EEPROM CLEAR

Thank you very much