This step is also demoed with this video :

(ongoing...)

Step 3a : Redesigning architecture 1

Previous step 3 lead to the very first architecture archi_training_vU0 :

producing upon it the assembly abl_training_vU0 used in this Simulink model

As mentioned before, signals mon_can_LatAcc and mon_can_YawRate from the "measurement monitoring zone" are missing.

These signals need to be brought back inside the architecture, that has to be modified.

Quite obviously, modification will consist in inserting a new room mon_, but where?

As we can see in the model above, these monitoring signals require ana and can decoding, then it comes :

and we remember that these signals are missing for the two feedback modules of the FB_ room :

then, a new architecture could be :

Moreover, architect decides that it would be more readable to put ana_ and can_ rooms together in a MEASUREMENTS zone and to put targets_ and FB_ rooms together in a CONTROL zone:

These considerations give the architecture archi_training_vU1 :

This architecture is attached to the assemby abl_training_vU1 which provides both modules mon_ana_BIS_v000d000 and mon_can_BIS_v000d000 dedicated to mon_ room.

Then by auto assembling this assembly, user will get :

As we can see, both modules FB_LatAcc_v000d000 and FB_YawRate_v000d000 are correctly fed with signals mon_can_YawRate and mon_can_LatAcc,

which is the purpose of architecture archi_training_vU1.

Signal mon_ana_YawRate and mon_can_YawRate are detected as not used and then connected to terminator.

This assembly can now be used in this Simulink model :

The piece of code computing the overall system monitoring flag mon_system is not used in the assembly.

In next step 3b, architect will redesign the architecture in order to take into account this monitoring flag and use it in the code.

Published with MATLAB® R2013a