MobiFlight Community Support

Just as the topic says. When i run the connector, it scans for arduinos, says it found one, asks if id like to update the firmware, then i get that error. after i hit ok, it goes to the mobiflight modules screen and shows my Micro as "Unknown" and wont let me do anything with it.

(ps i dont know how to turn on Debug logging.)

help, please

EDIT: NOT FIXED.

I used a new Pro Micro and it showed as a module, but won't let me upload anything to it.

Hi TangoCharlie,

first welcome to MobiFlight!

It is still a known issue with the pro micro that you have to restart MF after a firmware update. This issue is under development, so you have to restart MF until this issue is solved.

To activate the logging mode with debug goto the menu, EXTRAS -> SETTINGS. In the middle of the screen you will find the logging mode to activate.
But please note that the logging mode is only for test purposes. You will get delays if you use it for normal sim operations.

Thanks for the help. I reinstalled, restarted and it's now recognized. However I'm stuck in a loop where I'll add a device, upload it, and when I got to define the input, it states there are no devices on this module. I'll create another device, upload it, and the same thing happens.

I've tried saving and restarting, but I'm in a repeating cycle.

Thanks in advance.

EDIT: Will going to a Mega or other board be easier? Suggestions welcomed.

Hi

Swap to a Mega is always a good recommendation!

MEGA is the ONE AND ONLY board that was 100% compatible all the time ( And will be in the future garantee) All others was ( in the past) just experimental !

In case there are some Users ( join us within the last year) who love this Micro/Uno Stuff they work to handle it.... And they have sucess but have to rework our Firmware..... So for example they fully remove the Stepper Motor Support.... And then it work. But if you use it with regulary Firmware.... It "can" get problematic !
Problem is..... The Memory from the Micro/UNO is 32k .... the Mega got 256k.
And the Firmware have nearly 32k witch give the Uno/Micro just a little space for working Mem..... This can occure in a overflow and a crash.

Good News.... these "Micro FanBoys" work on it and hopefully the next firmware is more stable..... But for sure. Each new Device ( like 14Seg Displays) will enlarge Firmware again..... And same Trouble start again !

So from my point of view..... Use a Mega ( like 95%+ of users) and never again think about this problems !

**************

About first question.....
This can be a part of the Micro Problem..... BUT it can also be a issue in usage....

However I'm stuck in a loop where I'll add a device, upload it, and when I got to define the input, it states there are no devices on this module. I'll create another device, upload it, and the same thing happens.

WHAT Device do you create ???
Often user make the issue and create e.g. a LED..... And then they report there is no device in there INPUT Config items. For sure. A LED is a OUTPUT..... So it is not listed there.

Please Confirm:

1. Do you create a Input Device ( Button, Encoder) and THIS is NOT listed in a INPUT Config later ??
2. While create the second Device..... Is the FIRST still there or is it gone ?

Thanks Pizaman82. I think I'm going to just go with a Mega. But yes, the device I tried to create was an encoder.
I'll probably be back asking more questions!
Thanks again.

Hi! I am using the mega2560. Everything was working ok I programed few buttons and today when I opened again the Mobiflight connector informed me that I need to update the firmware. I pressed ok and the it said an error was occured.I changed the logging from info to debug. I pressed the reset button on the arduino, I restarted my computer and mobiflight and still the same error. Can you help me? The error is this one :

Error 8/31/2022 5:37:17 AM avrdude timed out! Something went wrong when flashing with command
"Arduino\hardware\tools\avr\bin\avrdude" -C"Arduino\hardware\tools\avr\etc\avrdude.conf" -patmega2560 -cwiring -P\\.\COM4 -b115200 -D -Uflash:w:"C:\Users\Alexander\Desktop\DESKTOP\AVIATION\3D COCKPIT\FILES\A320 MAKING COCKPIT SIMULATION\mobi\firmware\mobiflight_mega_2_2_0.hex":i

Hi Almarg
Welcome to Mobiflight!

Basically a Firmware Update can in rare cases occure in a Error. (Can have a lot of reasons but happen pretty rare gladly )

In those situations the best way to solve is a "reset" of the Mega.
Use the EEPROM Clear Sketch from the Arduino IDE to delete the whole Mega ( Including the EEPROM) and then its like brand new.
Means if you connect it and start MF then it will see a fresh board and ask you to use it ( flash firmware).
Normaly this solve 99% of those problems but have a disadvantage.
If you not have made a Backup of your device settings ( Save as mfmc file) then you have to create the devices once again....: Cause by the "reset" also the saved data on the board is gone.

*****

Another Point you should care:

Error 8/31/2022 5:37:17 AM ..... -"C:\Users\Alexander\Desktop\DESKTOP\AVIATION\3D COCKPIT\FILES\A320 MAKING COCKPIT SIMULATION\mobi\firmware\mobiflight_mega_2_2_0.hex":i

Its high recommend to install MF not into a windows secured folder !
So try to avoid C:/user or c:/programmfiles or so.
Best way to work with MF is to build a own folder like c:/MF or a own partition like D:/Flightsimstuff/Mobiflight....

I think this is not the main reason for your reported problem.... But i still recommend to do this to avoid trouble in the future !