Embedded Coder changes function names from step to output

Question

Mike Bardill 2024-3-14

0
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2094416-embedded-coder-changes-function-names-from-step-to-output

评论： Mike Bardill 2024-3-18

We have recently upgraded to R2023b. We have noticed that when we generate code from models a lot of function names have changed from 'step' to 'output'. Whilst this is not a problem we are curious to understand what has caused this change. The code still builds and works fine.

MeasurementControllerMDLOBJ5.step(rtu_control_run,

Now:

// ModelReference: '<Root>/MeasurementController'

MeasurementControllerMDLOBJ5.output(rtu_control_run,

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

请先登录，再进行评论。

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

Answer 1

Mark McBroom 2024-3-16

0
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/2094416-embedded-coder-changes-function-names-from-step-to-output#answer_1426361

Not sure how the method name changed to output ... the default should still be step(). However, you can easily change back to "step" via code mappings:

https://www.mathworks.com/help/ecoder/ug/interactively-configure-cpp-interface.html

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

Mike Bardill 2024-3-18

Thanks. I noticed that the change seems to be anywhere that we generate code for a model reference block. We have a mixture of model reference and subsystem reference blocks in our models. I scanned the release notes going back to the version we moved up from but could not see anything obvious about this change. We don't need to force a change back to 'step' but I will note the configuration possibilities for future reference.

请先登录，再进行评论。