Problems with moving Simscape from 2014b to 2015b
2 Ansichten (letzte 30 Tage)
Ältere Kommentare anzeigen
I have a Simscape model in Simulink that takes block inputs as workspace variables and I call it in a script. At my school the campus computers have Matlab 2014b, but our individual licenses are for 2015b so I have 2015b at home and 2014b at school. When I put the model from my home computer on google drive and then downloaded it to the campus computer all the variables in the blocks were changed to default values. For example, the tire blocks had their tire force values changed to the defaults from my magic tire coefficient variables.
Has anyone else experienced this problem? Is there a solution, I just want to be able to save my work?
0 Kommentare
Antworten (1)
Martin
am 4 Okt. 2023
MathWorks does not guarantee behavior when files are saved in a newer release and then opened on an older release. In this case, the parameters names in the code of the block have likely changed, so it does not see a match, and sets the parameters to defaults. MathWorks does try to make things work the other direction (saved in an older release and opened in a newer one) via forwarding.
A few things that you could do include matching the two versions if possible or using a .MAT file to hold your parameter values. With a .MAT file, you could populate the parameters in the workspace. When reopening in the older release, you would still need to go to the block to put in the correct workspace names for the parameters, but you would not lose the actual numerical data that you have.
0 Kommentare
Siehe auch
Kategorien
Mehr zu Simscape Driveline finden Sie in Help Center und File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!