THEMA:

If a model configuration gets renamed by using the corresponding DC-16 menu it still keeps the old name within the "Model" folder, leading to confusion when creating backups. It's then no longer possible to identify a specific model configuration by filename.
This problem gets even worse if someone has several similar models, creates a basic common model configuration and then makes copies of that configuration for every unique model by using the DC-16 copy function, adapting every copy to the needs of the corresponding model by changing the name and some settings. In this case the files all have the same name, just with a leading running 4-digit number.

Proposal: In case a model name gets changed by DC-16 menu the DC-16 should also change the configuration file name within the "Model" folder to the same name as would be choosen for a model newly created with that name from ground up.