Hi there,
I'm not quite sure, but just in case....
If one Mega dies, how do i transfer an exisiting config, all devices and corresponding input/output-settings to a new one?
I'm working with 10.5.3, by the way...
Thx
#How to transfer config from one Mega to another
cedar mountain
tender night
Is the previous mega still accessible? If so, go into the modules dialog, click on it, and save the config as a .mfcc file (you should do this anyway to have a backup)
Then click on the new mega and load the file
cedar mountain
I'm not quite sure, whether this is completely correct.
In 10.5.3 i have to save my config anyway - mfmc for each controller and all devices like buttons and so on of all controllers in one mcc file.
You might be right regarding the information which device is connected to which controller.
But in the mcc file there are references from a specific config to a specific device on a specific controller. And these won't change.
Small example: one line in the mcc says: serial="KaiBusMega1/ SN-3F1-FDD"
And this information does not change.
OK, i could connect the second one make a "search and replace" on the mcc file, but i assume this won't work due to another serial number.
slim basin
the serial number of the arduino will be different (SN-3F1-FDD), because the whole idea is that they are unique enough that two boards will not have the same serial number with reasonable accuracy, and MobiFlight will be able to tell them apart if you have more than one.
When you restore the .mfmc to a different Arduino, you will either be presented with the "orphan serials" dialog when you open your .mcc or .mfproj (if you use the beta version) - and you can select from the list of connected Arduinos which one to use instead for your profile. And the beta version is trying to be even smarter and will see if it can find a match automatically for you.
tender night
I'm not quite sure, whether this is completely correct.
In 10.5.3 i have to sav...
.mfmc is the configuration of the board (what buttons are connected to what pins)
.mcc is the configuration of how inputs and outputs are mapped
There is no need to hand edit any of the files. As Tuomas said, when the .mcc file is opened, Mobiflight will notice your old board is missing and ask you to pick a new board to replace it.
cedar mountain
I know which file is what for ...
Ah, that's the trick, did not get a message like that.... i will test it again tomorrow.
But convenient is something different from an UI - perspective, isn't it? 😎