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
karla
Posts: 21
I started my modular twin-engine panel over eighteen months ago: main panel with separate stripped-down PC, TFT and Air Manager instruments, a switch panel with switches, LEDs and levers using MF and Arduino and a radio stack with autopilot also using MF Arduino. There was on-and-off development resulting in all features working except occasional fail of COMs tuning. I replaced the COM encoder twice, rewired into Arduino four times, swopped COMs with NAVs and ADF controls, checked and rechecked and re-entered COMs settings.

Then I decided to carry out a trial. I removed all the devices in MF so that I could start over again, re-enter and re-configure and just test the COM.

Oops! I didn't save a .mfmc backup file - and during the past eighteen months I've never saved a .mfmc file.

I checked my PC external hard drive backup and the old hard drive from my PC that was replaced eight months ago. I searched for .mfmc - just in case - and looked under Mobiflight and Arduino folders with no luck.

Has anyone any suggestion before I start re-entering all the details into MF for: 36x switches, 5x rotaries, 11x encoders, 4x LEDs and 13x 7-segment displays?
2019-06-05 13:03
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Your reques confusing me..... :confused:

You say you have NOT saved your mfmc settings..... And you not find a older backup on your system.

How should somebody help you here ? We can not turn back the time. :w00t:
So the only suggestion is.... Make Backups in the future.



But good news.... Your system is pretty small. People with a full cockpit need to rebuild 1000+ devices if those mistakes happen. Your explaned system should take only 10-20 Mins normaly to rebuild.
Good Luck !
2019-06-05 15:03
Avatar
StephanHo
From: EDDG, Germany
Posts: 1867
Supporter
Hi karla,

the .mfmc files are reproducible if you have the modules left us still working.
Connect modules to USB, start MF. Then you open SETTINGS, then MOBIFLIGHT MODULES. You will now be shown the connected modules.
Click on the first module and then click on the floppy disk icon. The dialog for saving opens. Enter a name for the file and save the file. It now contains all devices of the module. You will do the same with the other modules as well.
When you are done, you have the corresponding .mfmc file for all modules.
You can now use this data to clone the modules or their devices.

However, if your .mcc file is gone, then you only have to re-enter all config manually. Here then only a backup could save you.
Are you sure you are missing a .mfmc file or is it more of the mcc file?
Grüße,
Stephan (Time: UTC+2)
2019-06-05 20:45
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
???

iconQuote:

Then I decided to carry out a trial. I removed all the devices in MF so that I could start over again, re-enter and re-configure and just test the COM.



Sounds for me that he connect the specific MEGA ( He request now for the old mfmc file) and "rework" the Device Settings. So its not possible to save that data now cause he overwrite it with pressing the UPLOAD Button while his testings! Currently the wrong data (testing state) is on the Board !

Stephans Comment sound nice but is not logical.....
If a User need a Mfmc File then the specific Mega stop working/ get lost / was rewritten with wrong data / get stolen / catching fire whatever.
So he have no longer acces to it.
Reversed..... If he got the Mega already to make your recommend "Save" again he would simply not need it cause it still work fine in this scenario..

***********
Good Luck !
2019-06-06 01:20
Avatar
karla
Posts: 21
Thanks for the responses.

I'd only wiped out the memory on one of the Megas - so not quite so much to re-input as I first thought. As it was, it took about three hours because I had to unbundle tied cable runs, trace similar coloured wires and so on. Two module .mfmc files are now saved in two different folders, just in case.

Anyway, I'm almost back where I want and I can now add new features: step-by-step.
2019-06-13 16:04
Avatar
pizman82
Moderator
From: ETSI, Germany
Posts: 6010
Supporter
Fine....

this is a good example that there is no correct way finaly....

I will say in my planned cockpit i would rebuild this board in less then 20 Minutes..... But i will otherwise need some hours more to build it at beginning.

For me a 100% tidy System is a "Must have" . I explane italready in other Topics.... A System with a clear Code for the "Names" of Devices is verry helpfull. this code should include things like Typ, What Mega, What Pin, What Element in Cockpit and so on. Finaly also the Config Line in Mobiflight should include this name. Verry helpfull is also if you mark your wires and devices with a strip of paper that include this code.
Finaly you have a Excel Sheet where you can identify the Code and see the corespondending Element.

Thats more work to build..... But in your case a short STRG-F Search in Excel would show me the needed devices for that MEGA.... So i not need to look for a wire or device cause Excel tell me what is set to what pin.

*************
WHATEVER B) B) B) B) I recommend basicly to make Backups of your Files (mcc and mfmc) everytime you add something new.....
Also not overwrite the backups..... Keep it on a save place and build a "history" ..... If you see a issue in a part you add 3-4 steps before you can "jump" back to this point. If you overwrite it and make only a single backup file then its unless if you "carry" a unseen issue over a while.
Good Luck !
2019-06-14 02:13
icon