Difference between revisions of "Matlab/Simulink files"

From OpenMBD
Jump to: navigation, search
(Created page with "Creating a custom S-function block requires that four files are added to the MatLAB/Simulink project.<br> *'''sfcn_<name>.m''': A function written in MatLAB code describing th...")
 
Line 1: Line 1:
Creating a custom S-function block requires that four files are added to the MatLAB/Simulink project.<br>
+
Creating a custom S-function block requires the addition of four files to the MatLAB/Simulink project.<br>
 
*'''sfcn_<name>.m''': A function written in MatLAB code describing the S-function block's basic characteristics, such as the number of input ports and the umber of dialog parameters.
 
*'''sfcn_<name>.m''': A function written in MatLAB code describing the S-function block's basic characteristics, such as the number of input ports and the umber of dialog parameters.
*'''sfcn_<name>_chk.m''': A function written in MatLAB code for checking prerequisites of using the block, such as that only a single block might be present in the model.
+
*'''sfcn_<name>_chk.m''': A function written in MatLAB code for checking prerequisites and/or dependencies of using the block, such as that only a single block might be present in the model.
 
*'''sfcn_<name>_mcb.m''': A function written in MatLAB code that is used for setting up the block's customized parameters. This arguments of the function are the actual parameters. The return value is an human readable information string.
 
*'''sfcn_<name>_mcb.m''': A function written in MatLAB code that is used for setting up the block's customized parameters. This arguments of the function are the actual parameters. The return value is an human readable information string.
 
*'''sfcn_<name>.tlc''': A function written in both MatLAB code and C-code, that can be seen as a transfer layer between the block's settings, input ports, output ports and the C-code.
 
*'''sfcn_<name>.tlc''': A function written in both MatLAB code and C-code, that can be seen as a transfer layer between the block's settings, input ports, output ports and the C-code.
 +
 +
== sfcn_signal_tower.m ==
 +
File location: ./blockset/toolbox/STM32/blocks<br>
 +
Each layer of the signal tower requires three input ports: one for each RGB color.<br>
 +
As there are four layers, a total of twelve input ports are created in the setup function.<br>
 +
Notice that the DataTtypeID of each port is set to 3, which means that the ports requires data of type uint8_T.<br>
 +
The range of a uint8_T variable is 0-255.

Revision as of 11:12, 28 February 2019

Creating a custom S-function block requires the addition of four files to the MatLAB/Simulink project.

  • sfcn_<name>.m: A function written in MatLAB code describing the S-function block's basic characteristics, such as the number of input ports and the umber of dialog parameters.
  • sfcn_<name>_chk.m: A function written in MatLAB code for checking prerequisites and/or dependencies of using the block, such as that only a single block might be present in the model.
  • sfcn_<name>_mcb.m: A function written in MatLAB code that is used for setting up the block's customized parameters. This arguments of the function are the actual parameters. The return value is an human readable information string.
  • sfcn_<name>.tlc: A function written in both MatLAB code and C-code, that can be seen as a transfer layer between the block's settings, input ports, output ports and the C-code.

sfcn_signal_tower.m

File location: ./blockset/toolbox/STM32/blocks
Each layer of the signal tower requires three input ports: one for each RGB color.
As there are four layers, a total of twelve input ports are created in the setup function.
Notice that the DataTtypeID of each port is set to 3, which means that the ports requires data of type uint8_T.
The range of a uint8_T variable is 0-255.