MobiFlight Community Support

Hi

I tried to install an arduino for some new displays, but it did not work and I want to permanently remove the arduino from mobiflight.
If I just disconnect the arduino, mobiflight will keep asking for it every time I start mobiflight, but how to remove the arduino permanently so it does not ask for more?

When I go to all my connected arduinos in mobiflight I can see it, and add devices etc, but I cannot remove it. I can just add and remove
I highlight the arduino I want to remove, but the button remove device ilight grey and cannot be used.

Why?
If I right click it, it is still not possible to choose remove device. Why can I not remove a programmed arduino from the system???

The arduino I want to remove is of course a mobiflight module. It is a Mega 2560 arduino.
The mobiflight software is on it but still it is not possible to uninstall it or remove it from moblight. The software asks for it every single time I restart mobiflight. WHERE IS IT AND HOW TO REMOVE IT, HELP!!!!

Update:
Have tried to remove the arduino, restart the computer, but still Mobiflight is asking where the ardunio card is, so there must be some kind of .ini file, right?
Have not located the place where such a file might be located.....

Hi sebpil,

if you remember how
a) a configuration is set up in MobiFlight and
b) how to set up a device,

then a MobiFlight module is removed in exactly the same way.

For each config that you create, MF saves the module to which the config belongs in addition to the config. The data for this is saved in the .mcc file.

If you now remove a module, you must also delete all configuration entries relating to this board from the .mcc file.
If the module is missing and these entries are still there, MF cannot know that you no longer need them.

If the module you want to remove is called the serial number SN-ceb-d3f, all entries in the .mcc file that belong to a device of this module are also saved in this file.

There are two ways to remove these entries from the .mcc file:

1. Remove all configs belonging to this module from the MF overview in the input and output lists. It is the safest method.

2. You get the .mcc file in an editor and search for the ID of the module. Now you should know how the file structure is structured
Each entry begins with <config guid .....> and ends with </config>
Each entry contains the serial of the module to which it is assigned. You now have to manually search for the <config guid ...> entry after you have found the serial for the entry and delete it up to and including </config> in the editor.

You repeat this until the serial is no longer found. However, this procedure can lead to errors, so caution is advised here.
Removing the entries directly in MobiFlight is the safer method.

Please make a backup before editing the file, then you are on the safe side.

After removing the entries, save the file, exit MF and restart. If there is no longer any indication of an orphaned module, you have done everything correctly.

You can now delete the module yourself by going to the MobiFlight Module tab in the menu under EXTRAS -> SETTINGS. Click on the module you want to delete. Now MF shows you the information about the module in the right half. You will note the port number, e.g. COM21.

Now start the Arduino IDE and go to the TOOLS menu and select in the middle on Board: the Arduino / Genuino Mega or Mega 2560. Port is then two lines below:
Here you select the one you should remember from the MobiFlights page. Check again in case of doubt.

Now go to the FILE -> EXAMPLES -> EEPROM menu and select the sketch eeprom_clear. You can start this sketch below the menu by clicking on the circle with the right arrow. The sketch is now loaded into the mega and runs there once. After 1 minute you can then leave the Arduino IDE and your MEga is completely deleted and can be used as normal.

You don't need to delete the devices on the Mega individually, they were also deleted with the eeprom_clear sketch.

Now your "old" module and its entries should no longer be requested by MF.

Finished!

Hi StephanHo

Lord, it must be an easier way, right?
If you can add a new arduino by a mouse click or two you should be able to remove it as easy as well.
All that searching for a serial etc, then the programmer of mobiflight has not thought of the most important thing, adding/removing arduinos.

Will take a look later in all my mcc files, but it will take a while, I have many of them. But what to remove etc to not make a mistake this rough way of removing a card makes me think twice before using mobiflight again.

Hi
I think you missunderstand Stephan or you missunderstand the whole system.

At First.... Mobiflight not care about removed Arduinos itelf..... Mobiflight not know how many Arduinos was connnected in the past. There is no List or so.
What You report here is a complete different system and this is verry important and usefull !

Everytime you LOAD a MCC File in Mobiflight ( Whatever by yourself or by Mobiflight Startup when it load the last used file) there is a internal Check.
Mobiflight simply check every single Config Line if the selected Device ( For example a Switch on Pin 15 at Mega XY) is connected to the system.
If a Device is miss you get this Error Warning. And this is also verry usefull to know for example a bad USB Port.... a broke Mega and so on. Additional we can handle here "orphaned" Modules..... So we can change a broke Mega by a new one and can simply "rebuild" the old configs to the new one without rewriting 50+ devices by hand.

So...

1. What happen in your System:
You remove a Mega Board.... And pretty sure there was one or more devices at this Board ( for example a LED) .
The MCC File you load ( or that is loaded by Mobiflight at startup) include 1 or more configs that are selected to Devices on exactly THIS Mega you remove.

2. Whot to do....
If you remove the mega temporary do nothing.... Cause you will install another one ( or this one again) in the future to make your Configs work again. If you compeltly Remove this Part forever then you still not need the configs..... So work tidy and correct and also delete the configs !
AGAIN.... Without the Devices ( you removed ) the corespondending configs make no longer sense and should not "trash" your file.


3. Why no "Rightclick Remove" Tool here.
Cause Nobody realy need it ..... And Mobiflight can not know what you like to do with your existing configs. Should it delete the whole config lines ?? What if those lines are also precondition indicators ?? Should it remove just the Devices from those Configs ?? Senseless to hold Configs without devices in a file.




Summary....
If you remove Hardware form a already assembled system then you must also rework the software..... You create the configs.... You also must delete them.


EDIT

Will take a look later in all my mcc files, but it will take a while, I have many of them.

As i explane above..... Only the files that work with exactly the removed Module and a active device on it will report a issue.