This step is also demoed with this video :

(ongoing...)

Step 0j : Validity of a module

Once it is designed, a module aims to be used either in a Simulink model, or in an auto assembly :

As it will be explained in steps 2 & 3, the auto assembly automatically lays out modules of an assembly upon an architecture :

To achieve this task, a module must be valid, i.e. fulfill some conditions.

This check is automatically done when an auto assembly is requested, but it's possible to check the validity of a module at anytime by selecting it and press Valid? button :

When a module is valid, which is the case for FB_YawRate_vU2, the rank 2 GUI says so :

When it's not the case, the rank 2 GUI explains why. Here are the 7 conditions (may evolve according to the MTX release) :

• • Condition 1 : calibration script must exist. FB_YawRate_vU2Cond01Nok is not ok for condition 1

• • Condition 2 : Simulink library must be composed with only one SubSystem. FB_YawRate_vU2Cond02Nok is not ok for condition 2

• • Condition 3 : the SubSystem can be triggered or not, if triggered, it must be a function-call

• • Condition 4 : in previous releases, the SubSystem had to be masked, it is not requested anymore. FB_YawRate_vU2Cond04Ok is ok for condition 4

• • Condition 5 : in previous releases, first parameter of the mask had to be named St as sample time, it is not requested anymore. FB_YawRate_vU2Cond05Ok is ok for condition 5

• • Condition 6 : name of outputs must be specifically named. FB_YawRate_vU2Cond06Nok is not ok for condition 6

• • Condition 7 : name of inputs must be specifically named. FB_YawRate_vU2Cond07Nok is not ok for condition 7

Note that an invalid module in the MTX sense can be used as it. This validity is only required for :

• • auto assemble an assembly

  • capitalize a module (cf. Community functionalities step 6)

At this stage, main functionalities on MODULES have been explained :

Step 1 is dedicated to ASSEMBLIES.

Published with MATLAB® R2013a