Data import export to workspace blocks.
Mat file logging.
To use a variable name without any modification select none.
Select the mat file logging option.
Mat file logging on sd card for px4 autopilots.
Step 1 configure a simulink model for mat file logging.
Mat file logging does not support outport blocks to which you apply the storage class importedexternpointer or storage classes that yield nonaddressable data in the generated code.
Code generation interface settings.
When you select this option the generated code saves to mat files simulation data specified in one of the following ways.
Scope blocks with the.
Select the enable mat file logging on sd card checkbox.
In the configuration parameters dialog box go to code generation interface and expand advanced parameters or type mat file logging in the search box.
Mat file logging does not support outport blocks to which you apply the storage class importedexternpointer or storage classes that yield nonaddressable data in the generated code.
For example the storage class getset causes the outport to appear in the generated code as a function call which is not addressable.
Also select the desired spi module and spi baud rate and ensure in the spi x pane that all configurations are as required.
Configuration parameters data import export see model configuration parameters.
For example the storage class getset causes the outport to appear in the generated code as a function call which is not addressable.
This example shows you how to perform mat file logging using simulink model on a micro sd card mounted on embedded coder support package for texas instruments c2000 processors.
From the mat file variable name modifier list select an option to add rt as prefix or rt as suffix to the variable name in the mat file.
On for the grt target off for ert based targets.
For example the storage class getset causes the outport to appear in the generated code as a function call which is not addressable.
Step 2 prepare model for simulation and deployment.