Error Updating Model Reference SIM Targets (an error occured during the call to make)

Question

Daniel Sadono 2021-9-8

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1448919-error-updating-model-reference-sim-targets-an-error-occured-during-the-call-to-make

评论： Daniel Sadono 2021-9-24

error.png

Hello allm

I have two big separated models on simulinks, each of them can be simulated without any problems on matlab 2018B. Now I tried to integrate them into one massive models. Each of those models consists of many subsystems and codes. After I integrate them, I tried to make an adjustment to the models so they can be performed flawlessly.

when I simulate it, an "updating model reference SIM target (1 of 5)" was performed and it took 1.5 hour only for the first one and it ended with an error stated " an error occurred during the call to make, is not recognized as an internal or external command" , as shown on the attachment.

I tried actually to uncomment that subsystem to check if the other subsystems can still be performed, and it ended up perfect, which mean the simulation can be run. The problematic subsystem actually consists of signals which connected only into 3D lookup tables.

does anyone has idea or solution to encounter this problem?

Thank you

Regards

Daniel

0 个评论
显示 -2更早的评论隐藏 -2更早的评论

请先登录，再进行评论。

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

Answer 1

Mark McBroom 2021-9-19

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/1448919-error-updating-model-reference-sim-targets-an-error-occured-during-the-call-to-make#answer_790799

The error is coming from the mingw compiler that Simulink is using to compile/link the code generated from model "machine". Do you have access to Visual Studio? If so, use the mex -setup command to switch compilers to see if the code will compile/link with Vis Studio.

3 个评论
显示 1更早的评论隐藏 1更早的评论

Mark McBroom 2021-9-24

Rapid accelerator mode speeds up a simulation by generating C code from the entire simulink model and runnning the compiled code. The error you were getting is occuring when Simulink is trying to compiile and lnk the code for rapid accelerator mode. You could change rapid accelerator mode back to normal mode and your model should simulate properly.

Daniel Sadono 2021-9-24