Model Advisor error:Abnormal exit?

Question

李 2024-8-21，2:17

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2146774-model-advisor-error-abnormal-exit

编辑： Saurabh 2024-8-21，4:18

There were no errors when I ran the model and generated the code. But why does the Model Advisor report errors？

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

请先登录，再进行评论。

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

Answer 1

arushi 2024-8-21，3:44

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2146774-model-advisor-error-abnormal-exit#answer_1502159

Hi 李 ,

The Model Advisor in Simulink is a diagnostic tool that checks your model for potential issues, best practices, and compliance with modeling standards. It can report errors or warnings even if the model runs and generates code successfully. This is because Model Advisor checks for potential issues that might not immediately cause a failure but could lead to problems in specific contexts, such as embedded systems or safety-critical applications.

For example,Model Advisor might flag the use of pointers in Stateflow charts because pointers can lead to unsafe memory access or undefined behavior, especially in embedded systems where memory management is critical.

Hope this helps.

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

请先登录，再进行评论。

Answer 2

Saurabh 2024-8-21，3:50

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2146774-model-advisor-error-abnormal-exit#answer_1502164

编辑：Saurabh 2024-8-21，4:18

Hi 李,

Although it appears that you were able to generate the code successfully; there were some issues when you conducted model checks.There might be few workarounds/troubleshooting steps for this issue. Let's examine each one separately.

Check for Pointers in Stateflow charts: Pointers are not allowed in "Stateflow" charts. If Pointer operations are used in Stateflow charts, modify the specified chart to remove the dependency on pointer operations.
Check usage of floating-point expressions in Stateflow charts: identify equal to operations (==) in expressions where at least one side of the expression is a floating-point variable or constant. The condition would be if Expressions use equality comparison operations (==, !=, ~=) where at least one side of the expression is a floating-point variable or constant. Then modify the specified expressions to avoid equality comparison operations between floating-point expressions or it can be The “Model Advisor” could not determine the data types in expressions with equality operations then typecast the specified expressions explicitly to allow Model Advisor to determine the data types.
Check usage of unary minus operations in Stateflow charts: Identify unary minus operations applied to unsigned integers in Stateflow objects. The condition can be that the Unary minus operations are applied to unsigned integers in Stateflow objects then Modify the specified objects to remove dependency on unary minus operations. Or The Model Advisor could not determine the data types in expressions with unary minus operations then in this case typecast the specified expressions explicitly to allow Model Advisor to determine the data types.