Save the Model

Step 5 of 5 in Build and Edit a Model Interactively

How to Tell If a Model Needs Saving

To tell whether a model needs saving, look at the title bar in the Simulink^® Editor. If a model in the model hierarchy needs saving, an asterisk appears in the title bar (known as the dirty flag: *).

To determine programmatically whether a model needs saving, use the model parameter Dirty. For example:

if strcmp(get_param(gcs,'Dirty'),'on')
	save_system;
end

Save a Model

To save a model for the first time, in the Simulink Editor, on the Simulation tab, click Save. Provide a location and name for the model file. For name requirements, see Model Names.

To save a previously saved model:

To replace the file contents, in the Simulink Editor, on the Simulation tab, click Save.
To save the top model with a new name or location, or to change from MDL to SLX format, in the Simulink Editor, on the Simulation tab, select Save > Save As.
Note
For details about the SLX format, see Upgrade Models to SLX.
To save a referenced model with a new name, location, or format, open it as a top model, then on the Simulation tab, select Save > Save As.
To save the top model in a format compatible with the earlier version, on the Simulation tab, select Save > Previous Version. See Export a Model to a Previous Simulink Version.

Model Names

Model file names must start with a letter and can contain letters, numbers, and underscores. The file name must not be:

A language keyword (e.g., if, for, end)
A reserved name: 'simulink', 'sl', 'sf'
A MATLAB^® software command

The total number of characters in the model name must not be greater than a certain maximum, usually 63 characters. To find out whether the maximum for your system is greater than 63 characters, use the MATLAB namelengthmax command.

To understand how MATLAB determines which function to call when you specify a model name, see Function Precedence Order.

What Happens When You Save a Model?

Simulink saves the model (block diagram) and block properties in the model file.

If you have any pre- or post-save functions, they execute in this order:

All block PreSaveFcn callback routines execute first, then the model PreSaveFcn callback routine executes.
Simulink writes the model file.
All block PostSaveFcn callback routines execute, then the model PostSaveFcn executes.

During the save process, Simulink maintains a temporary backup copy (named modelname.bak) for restoring in case of an error. If an error occurs during saving or during any callback during the save process, Simulink:

Restores the original file
Writes any content saved before the error occurred in a file named modelname.err
Issues an error message

When saving a model loaded from an SLX file, the original SLX file must still be present. Simulink performs incremental loading and saving of SLX files, so if the original file is missing at save-time, Simulink warns that it cannot reconstruct the file fully.

Save Models in the SLX File Format

Save New Models as SLX

Simulink saves new models and libraries in the SLX format by default, with file extension .slx. SLX is a compressed package that conforms to the Open Packaging Conventions (OPC) interoperability standard. SLX stores model information using Unicode^® UTF-8 in XML and other international formats. Saving Simulink models in the SLX format:

Typically reduces file size compared to MDL. The file size reduction between MDL and SLX varies depending on the model.
Solves some problems in previous releases with loading and saving MDL files containing Korean and Chinese characters.
Enables incremental loading and saving. Simulink optimizes performance and memory usage by loading only required parts of the model and saving only modified parts of the model.

You can specify your file format for saving new models and libraries with the Simulink preference File format for new models and libraries.

Upgrade Models to SLX

If you upgrade an MDL file to SLX file format, the file contains the same information as the MDL file, and you always have a backup file. All functionality and APIs that currently exist for working with models, such as the get_param and set_param commands, are also available when using the SLX file format. If you upgrade an MDL file to SLX file format without changing the model name or location, then Simulink creates a backup file by renaming the MDL (if writable).

If you save an existing MDL file by clicking Save on the Simulation tab, Simulink respects the file’s current format and saves your model in MDL format.

To save an existing MDL file in the SLX file format:

On the Simulation tab, select Save > Save As.
Leave the default Save as type as SLX, and click Save.
Simulink saves your model in SLX format, and creates a backup file by renaming the MDL (if writable) to mymodel.mdl.releasename, e.g., mymodel.mdl.R2010b.

Alternatively, use save_system:

save_system mymodel mymodel.slx

This command creates mymodel.slx, and if the existing file mymodel.mdl is writable it is renamed mymodel.mdl.releasename.

SLX files take precedence over MDL files, so if both exist with the same name and you do not specify a file extension, you load the SLX file.

Simulink Projects can help you migrate files to SLX. For an example, see Convert from MDL to SLX in a Project and Preserve Revision History.

Caution

If you use third-party source control tools, be sure to register the model file extension .slx as a binary file format. If you do not, these third-party tools might corrupt SLX files when you submit them.

Operations with Possible Compatibility Considerations when using SLX	What Happens	Action
Hard-coded references to file names with extension `.mdl`.	Scripts cannot find or process models saved with new file extension `.slx`.	Make your code work with both the `.mdl` and `.slx` extension. Use functions like `which` and `what` instead of file names.
Third-party source control tools that assume a text format by default.	Binary format of SLX files can cause third-party tools to corrupt the files when you submit them.	Register `.slx` as a binary file format with third-party source control tools. Also recommended for `.mdl` files. See Register Model Files with Source Control Tools.
Changing character encoding.	Some cases are improved, e.g., SLX solves some problems in previous releases with loading and saving MDL files containing Korean and Chinese characters. However, sharing models between different locales remains problematic.	See SLX Files and Character Encodings.

The format of content within MDL and SLX files is subject to change. To operate on model data, use documented APIs (such as get_param, find_system, and Simulink.MDLInfo.

Save Models with Different Character Encodings

MDL Files and Character Encodings
SLX Files and Character Encodings

MDL Files and Character Encodings

When you save a model, the current character encoding is used to encode the text stored in the model file. With MDL files, this can lead to model corruption if you save a model whose original encoding differs from current encoding.

If you change character encoding, it is possible to introduce characters that cannot be represented in the current encoding. If this is the case, the model is saved as model.mdl.err, where model is the model name, leaving the original model file unchanged. Simulink also displays an error message that specifies the line and column number of the first character which cannot be represented.

To recover from this error, either:

Save the model in SLX format (see Save Models in the SLX File Format).
Locate and remove characters one by one.
1. Use a text editor to find the character in the .err file at the position specified by the save error message.
2. Find and delete the corresponding character in the open model and resave the model.
3. Repeat this process until you are able to save the model without error.

It’s possible that your model’s original encoding can represent all the text changes made in the current session, albeit incorrectly. For example, suppose you open a model whose original encoding is A in a session whose current encoding is B. Further suppose that you edit the model to include a character that has different encodings in A and B and then save the model. If in addition the encoding for x in B is the same as the encoding for y in A, and if you insert x in the model while B is in effect, save the model, and then reopen the model with A in effect the Simulink software will display x as y. To alert you to the possibility of such corruptions, a warning message appears whenever you save a model in which the current and original encoding differ but the original encoding can encode, possibly incorrectly, all of the characters to be saved in the model file.

SLX Files and Character Encodings

Saving Simulink models in the SLX format typically reduces file size and solves some problems in previous releases with loading and saving MDL files containing Korean and Chinese characters.

Considerations for choosing a model file format:

Use SLX if you are loading and saving models with Korean or Chinese characters
Use SLX if you would benefit from a compressed model file
Whether you use SLX or MDL, Simulink can detect and warn if models contain characters unsupported in the current locale. For SLX, you can use the Model Advisor to help you, see Check model for foreign characters.

Export a Model to a Previous Simulink Version

You can export (save) a model created with the latest version of the Simulink software in a format used by an earlier version. For example, to share a model with colleagues who only have access to a previous version of the Simulink product.

To export a model in an earlier format:

In the Simulink Editor, on the Simulation tab, click Save. This saves a copy in the latest version of Simulink. This step avoids compatibility problems.
In the Simulink Editor, on the Simulation tab, select Save > Previous Version.
In the Export to Previous Version dialog box, from the Save as type list, select the previous version to which to export the model. The list supports 7 years of previous releases.
Click Save.

When you export a model to a previous version’s format, the model is saved in the earlier format, regardless of whether the model contains blocks and features that were introduced after that version. If the model does contain blocks or use features that postdate the earlier version, the model might not give correct results when you run it in the earlier version of Simulink software. In addition, Simulink converts blocks that postdate an earlier version into yellow empty masked Subsystem blocks. For example, if you use save_system to export a model to Release R2007b, and the model contains Polynomial blocks, Simulink converts the Polynomial blocks into yellow empty masked Subsystem blocks. Simulink also removes any unsupported functionality from the model. See save_system.

Save from One Earlier Simulink Version to Another

You can open a model created in an earlier version of Simulink and export that model to a different earlier version. To prevent compatibility problems, use the following procedure if you need to save a model from one earlier version to another earlier version.

Use the current version of Simulink to open the model created with the earlier version.
Before you make any changes, save the model in the current version by clicking Save on the Simulation tab.
After saving the model in the current version, you can change and resave it as needed.
Save the model in the earlier version of Simulink. On the Simulation tab, select Save > Previous Version.
Start the earlier Simulink version and use it to open the model that you exported to that earlier version.
Save the model in the earlier version.

You can now use the model in the earlier version of Simulink exactly as you could if it had been created in that version.

See also the Simulink preferences that can help you work with models from earlier versions: