Simulink Variables in the Model Explorer NEVER Change? Why??????

Question

Thomas 2014-8-7

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/146745-simulink-variables-in-the-model-explorer-never-change-why

回答： Thomas 2014-8-7

Hi All,

I inherited a Simulink file because I was asked to continue someone else's work. I agreed to this, and now I would like to modify some of the constants called out in the model explorer. When I do this, the constants automatically revert back to their initial values when the run button is pressed.

Scenario:

Matlab starts, I open the Simulink file. There are no variables in the model explorer when I start, after I hit run the constants in the model explorer populate. I change values of constants in model explorer. I press 'run', the values revert back to their original value and completes its execution of the program.

How can I change the constants?! Is there a file setting that I can untick somewhere? What is going on?

Thanks, -t

Matlab 2011Ra Windows 7

4 个评论
显示 2更早的评论隐藏 2更早的评论

Andy L 2014-8-7

Given the amount of control you can have over simulink blocks it is very difficult to tell what this could be.

I would check to see if any of your sub-systems are masked? Coding in these masks can change the values of variables upon running the model.

Thomas 2014-8-7

Yes there are several layers of masks and I have followed a single variable to five locations, ALL locations of which use the variable in an equation, it does not try to update it. I will ask if I can post the file however, you would require the mss (hydrodynamics and vessel guidance) toolbox free from thor fossen's website to run it.

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Thomas 2014-8-7

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/146745-simulink-variables-in-the-model-explorer-never-change-why#answer_147825

A workaround has been found. Placing the variables in the model workspace instead of the base workspace has fixed the non-updating issue. This is a partial solution. All of the variables in the base workspace still load and are not modifiable. This works out fine though because the model workspace overrides the base workspace for any used variables.