This step is also demoed with this video :

(ongoing...)

Step 2a : Auto assembly upon an empty architecture

Assembly abl_FB_vU0 has been created and is available :

As explained in step 1a, the ABL view describes the content of the assembly :

As we can see, assembly abl_FB_vU0 contains modules FB_LatAcc_v000d000 and FB_YawRate_v003d000.

The aim is to auto assemble these modules upon the architecture archi_empty_vU0.

First step is to attach and architecture to this assembly.

As source Models has been used in step 1a to attach a Simulink model to the assembly, source Archis must be used to attach an architecture to the assembly :

As a consequence, exactly like modules and after having pushed Archis button, available families of architectures are displayed in the right table :

As we would like to attach the architecture archi_empty_vU0, first select archi_empty and press the left arrow :

Then it appears the available versions of the family archi_empty, this version can be selected and press the left arrow :

Then comes the acknowledgment message :

The architecture archi_empty_vU0 is then attached to the assembly abl_FB_vU0 :

Moreover, there are three pushbuttons available for this attached architecture :

• • the Open Archi pushbutton : it opens the attached architecture

  • the Valid ? pushbutton : it defines wether the architecture is valid or not (see step 5a), which is required to auto assemble. For this empty architecture, this is the case :

• • the cross x pushbutton : to unattach the attached architecture. When requested, this action requires a confirmation through a rank 2 GUI :

As a result, there is no architecture attached to the assembly abl_FB_vU0 anymore :

The pushbutton AUTO enables to auto assemble and assembly upon its attached architecture, :

As the attached architecture has been unattached, it is of course not possible to auto assemble. Then appears the following message : :

Re attach archi_empty_vU0 to the assembly, then, the auto assemble can proceed. As a result :

• • the Simulink model abl_FB_vU0 is created :

• • and has been calibrated as said by the acknowledgment message :

The Simulink model is located in this folder :

Note that the delivered Simulink model is named like the assembly abl_FB_vU0.

The way inports and outports are connected to the assembly depends on two options :

• • connectionTypeForAblInputs : for the inports

  • connectionTypeForAblInputs : for the outports

Basically, choice is between inport/outport or goto/from or demuxed inport/outport or demuxed goto/from (for details, refer to the step about options 7d).

If we take a look inside the assembly :

As we can see, modules have been automatically layed out and connected with goto/from/BusSelector/BusCreator.

Each module is named by its family name and is linked to its library.

Moreover, each module is triggered by a function call generator set at the sample time entered in the assembly.

This sample time is available inside each module for calculus through the variable St.

Note there is a Rate Transition each time a signal enters a module. This is an option. For explanations and purpose of this option, see step 7e.

This assembly is ready for use in a Simulink model.

As an example, Simulink model model_step_2a uses this auto assembly.

These are configurations to consider:

• • redundant signals

  • signals used internally

  • emitted signals but not used

  • invalid function call connection

Next steps deal with these configurations.

Published with MATLAB® R2013a