vsTASKER 7 User Manual
×
Menu
Index

Properties

 
Properties
1

Name

1. Name
Name of the Simulink object. Must be unique.
 
2

Model

2. Model
Name of the Model as defined in the .mdl file.
 
3

Simulink File

3. Simulink File
Model file to be parsed and used.
Reload the .mdl file for updating Input/Output.
Call the Simulink editor (tries to open/edit the file from a command line. mdl extension must be bounded with Simulink)
 
4

Source Code

4. Source Code
Directory where the Simulink Coder generates all the files for the current model.
 
5

Generated Files

5. Generated Files
List of all generated code files in (4)
 
List of all #define found in some of the generated header files (4). They will be added in the makefile. They are read-only.
 
6

Cycling

6. Cycling
Select from the list the appropriate frequency for the object, according to the Fixed-step defined in the Simulink Coder configuration window.
 
Fixed Hz: when checked, the selected frequency is not according to the RTC but according to the wall clock.
With a fixed frequency, even if the simulation engine is accelerated or slowed down, the number of calls per seconds will remain the same.
 
7

Solver

7. Solver
Select here the same solver as the one selected in the Fixed-step defined in the Simulink Coder configuration window.
 
8

Disabled

8. Disabled
Exclude the Simulink object from the code generation.
Disabled Simulink object will not be included into the items using it (entities but not only) without the need to remove it from all users.
Disabling is error prone while removing might leave dangled pointers.
 
9

Interface

9. Interface
vsTASKER parses the .mdl file and tries to extract all Inputs and Outputs parameters for corresponding structures.
Not all of them shall be used.
The parameters names are listed without underscores. Corresponding unit (if any) is expressed in brackets. For i.e: V DES [m/s] lists the parameter V_DES whose value is in meter per second.
10

Code

10. Code
This part is the vsTASKER interface code between the data belonging to the simulation engine and the data pertaining to the Simulink model.
The Initialization part is called at each simulation phase. For i.e, the INIT/RESET phase can be used to initialize the Simulink Input parameters.
 
The Input part is called before the Simulink model tic() function. Use this code block to extract all the necessary data from the simulation engine objects to set the Input parameters of the Simulink model.
In the following example, we are extracting the requested speed and altitude of our aircraft to set the corresponding Input parameters.
 
The Output part is called after the Simulink model tic() function. Use this code block to extract all the necessary data from the Output parameters of the Simulink model to set the simulation engine objects.
In the following example, we are extracting the computed speed and heading in our model to update our aircraft.
The Input and Output blocks are called at the frequency set in (6).
11

Help

11. Help
Any description of the Simulink object can be put here and will be used for the automatic document generation (see Make Documents)