|
External code initiates execution of the generated code by calling entry-point functions generated for the model. The type of function code that the code generator produces for a model depends on the modelling style and periodic rates represented in the model. For more information, see Configure Generated C Function Interface for Model Entry-Point Functions |
2.1 Initialize FunctionsInitialize entry-point functions implement startup behavior. In a model, Initialize Function blocks represent startup behavior explicitly. Abstandsensor_initializeInitialization entry point of generated code#include "Abstandsensor.h"
void Abstandsensor_initialize(void)
2.2 Terminate FunctionsTerminate entry-point functions implement shutdown behavior. In a model, Terminate Function blocks represent shutdown behavior explicitly. Abstandsensor_terminateTermination entry point of generated code#include "Abstandsensor.h"
void Abstandsensor_terminate(void)
2.3 Periodic FunctionsPeriodic entry-point functions implement model behavior that occurs at a fixed sampling rate. For a rate-based model, the code generator produces a periodic entry-point function for each rate used in the model. In a function-call (export-function) model, Function Call Subsystem blocks that specify a sampling rate represent periodic functions. Abstandsensor_stepOutput entry point of generated code. Must be called periodically, every 0.2 seconds.#include "Abstandsensor.h"
void Abstandsensor_step(void)
2.4 Aperiodic FunctionsAperiodic (asynchronous) entry-point functions implement component behavior occurring asynchronously. In a function-call (export-function) model, Function Call Subsystem blocks that do not specify a sampling rate represent aperiodic functions. No aperiodic functions represented in model. |
|
A data code interface maps model data interface elements, such as root-level inports and outports, to storage classes. A storage class specifies the appearance and placement of data elements in the generated code. Storage classes apply direct-access data communication. The list of storage classes available for mapping is determined by the Embedded Coder Dictionary that is associated with the model. You map model interface elements to storage classes in the model code mappings. |
3.1 InportsVariables that are generated in the code based on storage class specifications for model root-level inports.No inport is present in model. 3.2 OutportsVariables that are generated in the code based on storage class specifications for model root-level outports.No outport is present in model. 3.3 ParametersVariables in the generated code that represent model parameters and model parameter arguments that are generated in the code based on a storage class specification and flagged to be tunable or not tunable while the model code executes in the target environment.Abstandsensor_P.IR_Signal_roh_SampleTimeParameters for <Root>/IR_Signal_rohstruct {
...
real_T IR_Signal_roh_SampleTime;
...
} Abstandsensor_P;
Abstandsensor_P.Constant_ValueParameters for <Root>/Constantstruct {
...
real_T Constant_Value;
...
} Abstandsensor_P;
Abstandsensor_P.uDLookupTable_tableDataParameters for <Root>/1-D Lookup Tablestruct {
...
real_T uDLookupTable_tableData[8][1];
...
} Abstandsensor_P;
Abstandsensor_P.uDLookupTable_bp01DataParameters for <Root>/1-D Lookup Tablestruct {
...
real_T uDLookupTable_bp01Data[8][1];
...
} Abstandsensor_P;
3.4 Internal dataVariables in the generated code that represent signal data, blocks that have internal state, and data stores that are generated in the code based on a storage class specification and flagged to be measured or not measured while the model code executes in the target environment.No data stores in model; note that this report lists only data stores with non-auto default storage class and global data stores |