This step is also demoed with this video :

(ongoing...)

Step 1d : Copying modules from an assembly to its attached Simulink model

Previous steps explained .

• • how to add and remove module of an assembly from the Source Modules : step 1a

  • how to add modules to an assembly from the Source Models , i.e. its attached Simulink model : step 1b

  • how to remove modules to an assembly from the Source Models , i.e. its attached Simulink model : step 1c

In this step 1d, next synchronization possibility is explained : copying modules from an assembly to its attached Simulink model.

If you synchronize the assembly abl_model_step_1_vU1 already attached to model_step_0d by pressing Abl Sync :

• • modules of the assembly are FB_LatAcc_vU3 and FB_YawRate_vU3

  • modules of its attached Simulink model are the same but vU2 version

By selecting both modules from the assembly and pressing the Smk -> button :

versions of Simulink model modules have turned into vU3 :

This can be observed in the Simulink model too :

This is actually equivalent to the Chg Ver Simulink functionality explained previously :

What does happen when a module is in the assembly but not in its attached Simulink model?

Since it is not possible for MecaTroniX to decide where the user wants to copy the modules, these modules are copied to a temporary untitled Simulink model.

This is the example of the assembly abl_model_step_1_vU2 including modules FB_LatAcc_vU3 and FB_YawRate_vU3, and its attached Simulink model model_step_0 contains no module, by pressing Abl Sync :

If Smk -> button is pressed, then modules FB_LatAcc_vU3 and FB_YawRate_vU3 are copied to an untitled Simulink model ready for further use :

Comparison status between assembly and its attached Simulink model did not change :

Last action of synchronization that has to be explained is the synchronization of an assembly with an assembly to a Simulink model :

This is the purpose of next step 1e.

Published with MATLAB® R2013a