This step is also demoed with this video :

(ongoing...)

Step 6g : Other effects of capitalisation on modules, architectures and assemblies

As said previously, modules, assemblies and architectures are all managed in the same way.

As a result, they all can be capitalized : the first effect is to change their version to v###d### and to be copied to a remote storage device called server :

There is also an other effect. For library of modules, the Simulink SubSystem is ReadOnly :

As a capitalized is a reference fot the community, protecting its content does make sense.

If by mistake user attempty to modify this library, Simulink says it is not possible :

Remark : to perform this, the property 'Permissions' of a SubSystem is used :

It can be manually changed but it is not recommended.

This is the same for architecture :

For a captitalized assembly, its content can not be modified, for example with abl_FB_v000d000. In the ABL view :

If user attempts to remove module FB_LatAcc_v005d000, this message occurs :

If user attempts to change version of FB_YawRate_v005d000 to v000d000, this message occurs :

If user attempts to unattach the attached architecture (if any), this message occurs :

When in ABL view the assembly is capitalized, the St is not editable so that they can not be modified :

Published with MATLAB® R2013a