(ongoing...)
This step in video : https://youtu.be/EoGymMWX76Y (it might be more convenient to copy/paste this link in your usual internet explorer).
From the starting model :
We will create two modules for the "Feedback control" part : one for the YawRate degree of freedom, and one for the LatAcc degree of freedom :
first, create the family of MODULES FB_LatAcc by getting in the MODULES view and pressing Creation on the left
Then, in a rank 2 GUI, user can enter the requested family name, leave a comment, and press Valid when completed :
Once the requested action is done, MTX acknowledges with a message in the informations zone. If you want to edit this message in the Web Browser, push the pushbutton Publish informations :
Remark : according to version, this interface may be closed automatically after creation.
Usually, publishing informations helps after an impossibility to access the requested action, when further investigations are needed.
For example, suppose that user entered an illicit family name, then MTX leaves a message in the informations zone saying that the request is not achievable and for which reasons :
If user pushes Publish informations, a new page in the Web Browser is open containing the informations :
now that the FB_LatAcc family has been created, a version is needed. As a user version, it starts with vU, as an example, let's begin with vU0.
(another type of version exists, this is the capitalized version, it is explained in Step 6 : Community functionalities).
enter a version and a comment and Valid :
module FB_LatAcc_vU0 is now created. To see what the module is made of, open it by selecting it and pressing Open :
Then, the library of the module is open :
According to options defaultMask (factory value 1) and defaultTrigger (factory value 1), a module is created with or without trigger/mask.
If both values are 1, the module is created as shown on the previous figure. 'Sample time' parameter will be defined by the sample time execution of the module.
Next step 0a explains the different ways to execute a module.
A calibration script is also created, in which variables necessary for the modules to run are coded by the user :
available in this folder :
(see next step 0a about how to calibrate a module)
At the stage of creation, the inside of the module is only made of two inputs and one output :
The output has been pre-named FB_output
Module FB_YawRate_vU0 can be created in the same way.
As we can see, when starting from a model, designing modules consists in defining piece of codes :
In next steps, other modules will be created, for measurements, targets, monitoring, etc...
Based on these modules, assemblies will be defined and auto assembly will be achieved upon architectures.
In this step 0, we've seen how to create a module :
Next step 0a deals with the execution of a module.