Inconsistent code generation of Block parameters with Embedded Coder

4 Ansichten (letzte 30 Tage)
Ghassen
Ghassen am 27 Mai 2024
Beantwortet: Abhas vor etwa 17 Stunden
I'm trying to generate C++ code via Embedded Coder.
This simple model contains some variables a,b,b1, where their constant values are implicitly set under .mat file
#
This is one of the block parameters:
When I generate code, I get the following
// Parameters (default storage)
struct P_controller_module_T {
double a; // Variable: a
// Referenced by: '<Root>/a'
double b; // Variable: b
// Referenced by: '<Root>/b'
double b1; // Variable: b1
// Referenced by: '<Root>/b1'
};
However in another model I have the following block parameters (constant values are also implicitly set under .mat files) :
But when generating code I get the following :
double Kp_lat_Value; // Expression: Kp_lat
// Referenced by: '<S11>/Kp_lat'
How do I keep the suffix "_Value" consistent ?
  1 Kommentar
prabhat kumar sharma
prabhat kumar sharma am 3 Jun. 2024
I suggest comparing the code generation properties. Go to the Modeling tab, select Model Properties, then Code Generation. Comparing all the attributes in both models will likely identify the attribute affecting this.

Melden Sie sich an, um zu kommentieren.

Antworten (1)

Abhas
Abhas vor etwa 17 Stunden
To ensure consistent naming of parameters in the generated C++ code using Embedded Coder, follow these steps:
  1. Configure Code Generation Settings: Open your Simulink model, go to "Modeling" > "Model Settings", and navigate to "Code Generation" > "Identifiers". Set the naming conventions for parameters to include the suffix "_Value".
  2. Set Identifier Format Control: In the "Identifiers" section, ensure that the naming rule for parameter identifiers specifies the desired suffix, such as "_Value".
  3. Use Data Dictionaries or Workspaces: Ensure that parameters defined in a .mat file are correctly linked to the model using a Simulink Data Dictionary or the base workspace, and that their names match the desired convention.
  4. Review Parameter Naming Rules: For MATLAB variables or Simulink.Parameter objects, define them with the desired suffix in the model workspace or data dictionary, and set their "CoderInfo.StorageClass" to an appropriate class like "ExportedGlobal".
You may refer to the below MathWorks documentation link to know more abut Code Generation Identifiers: https://www.mathworks.com/help/ecoder/ref/code-generation-pane-symbols.html
I hope this helps!

Kategorien

Mehr zu Deployment, Integration, and Supported Hardware finden Sie in Help Center und File Exchange

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!

Translated by