MATLAB Answers

Opening a simulink file that was saved in R2018b version onto a R2017b version.

1,045 views (last 30 days)
Aidil AA
Aidil AA on 14 Nov 2018
Answered: Gijs van Oort on 20 Nov 2019
Hi guys, I have a Simulink file which was saved in the R2018B version of MATLAB, however, I only have access to the R2017B version of MATLAB. Is there any way for me to access the R2018b file? I do not have the R2018b version of MATLAB at all.

  4 Comments

Show 1 older comment
Walter Roberson
Walter Roberson on 14 Nov 2018
In theory it is possible .
If it is a mdl file then it is a text file that you can edit to change the version information .
If it is a slx file then you can unzip it to extract a directory of xml files . You can edit one of the xml files to change the version information and then you can zip it back up into a slx again .

Sign in to comment.

Accepted Answer

Gavin Walker
Gavin Walker on 3 Dec 2018
Simulink has a preference, in the Model File section, called "Do not load models created with a newer version of Simulink". You can temporarily turn this off rather than edit the model files to change version numbers.
If the model uses only basic blocks then it might be possible to load it in R2017b, but it could also crash MATLAB. As others have commented, using the "Export to Previous Version" feature is the supported way to take a model from a later release to an earlier one.
Remember to turn the preference "Do not load models created with a newer version of Simulink" back on afterwards.

  0 Comments

Sign in to comment.

More Answers (2)

madhan ravi
madhan ravi on 14 Nov 2018
Edited: madhan ravi on 14 Nov 2018

  2 Comments

Aidil AA
Aidil AA on 14 Nov 2018
thank you, but i have already read that before posting this question. the problem I have is that I do not have access to the newer model of MATLAB at all. I only have the r2017b version.

Sign in to comment.


Gijs van Oort
Gijs van Oort on 20 Nov 2019
Be careful with this. I have some experience with very bad things happening. I don't remember which Simulink versions were involved in that (probably 2015/2016?), and I don't even remember if we tried to load the model into an older or a newer Simulink version.
The problem was that, in comparison blocks (comparing two inputs, and you could set the operator to be one of <, <=, ==, >=, >, != ), the wrong operator was chosen. So, when opened with one (the correct) version of Simulink, the block was a X<Y block, and when opened with the other version of Simulink, the block suddenly became a X==Y block (I don't remember which operators were involved, but you get the idea).
The worst part is that no error or warning message at all was generated.

  0 Comments

Sign in to comment.

Sign in to answer this question.