Autocode step function naming

We have a model ProjName.slx (a main model with reference models embedded). The reference models run at different rates (2ms, 10ms, 100ms, 1000ms). The autocode produces step functions ProjName_step0, ProjName_step1, ProjName_step2, ProjName_step3. Is there any control over this naming? Where is it set

Answer 1

[Mark McBroom]

Use the code mappings capability of Embedded Coder to control the names of the step functions. See the end of this web page:

https://www.mathworks.com/help/ecoder/ug/configure-default-code-generation-for-categories-of-model-data-and-functions.html#:~:text=Open%20the%20Embedded%20Coder%20app.%20In%20the%20C,opens%20the%20Code%20Mappings%20editor%20Data%20Defaults%20tab.

[Wayne Munslow]

Thank you for the reply. The link you provided is for 2022a documentation. However, my project has been developed in 2017b and the it appears that the example does not exist in 2017b. Can you help with how to view our code mappings in 2017b?

[Wayne Munslow]

Further to the above:

I have found a demo in 2017b (different name) which suggests that the step and initialize function names can be changed within a GUI which is launched by clicking "Configure Model Functions". However, that button is not visible in my project. Do you know what controls whether the button is visible or not?

[Mark McBroom]

Hi Wayne,

The documentation for this option lists the dependent configuration settings:

• The button appears only for ERT-based targets with Code interface packaging set to a value other than C++ class.
• This button requires an Embedded Coder� license when generating code.
• This button is active only if your model uses an attached configuration set. If your model uses a referenced configuration set, the button is greyed out. If you want to configure a model-specific step function prototype for a referenced configuration set, use the MATLAB� function prototype control functions described in the help section "Configure Function Prototypes Programmatically"

[Wayne Munslow]

Hi Mark,

Thanks for your answers. I also found out that, in the 2017b version we are using:

The first requirement is that the system target file is set to ert.tlc (or something derived from ert.tlc) – basically, your model needs to be set up to generate code with Embedded Coder.

After that, there are some limitations for using this feature, and perhaps your model is not compliant with the required settings which is preventing the button from being shown:

https://uk.mathworks.com/help/releases/R2017b/ecoder/ug/function-prototype-control.html#bq2nw87-5

For instance: “Function prototype control does not support multitasking models. Multirate models are supported, but you must configure the models for single-tasking.”

I have added this in case it is useful to others who stumble upon the answers