Project 1 (Mini Project on Vehicle Direction Detection

Aim: Determining the direction of vehicle moving, while following MAAB guidlines.

Firstly we have to create sldd file, and add signals and its parameters and save the file.

Now converting documented requirement into model.Whenever there is a requirement it has to be in a subsystem.

Here we take 2 subsystem, namely Requirement_1, Requirement_2.

When all blocks are erroe free we create maab report.

Blocks used: - inport, outport, constant, compare to constant, switch.

1. Took one subsystem named as requirement-1. inport block named as steering wheel yaw degree input.
2. Now I compared input with three constants are Right_Turn_AngularLimit, Left_Turn_AngularLimit, Straight_Drive_Steering_Angle) with the help of relational operator block.
3. If the relational operator condition is true then we decide which input will go to execute with the help of switch block.
4. Three switch blocks are used to decide the which specific direction the steering wheel is turning towards.
5. If the first comparison is true then first switch true value will go for execution which is right turn.
6. If the first switch value is false the second witch value will go to execution.
7. If the second comparison is true then second switch true value will go for execution which is left turn.
8. If the second switch value is false the third witch value will go to execution.
9. If the third comparison is true then third switch true value will go for execution which is straight drive.
10. If third switch value is false the second port value will go for execution which is 0.
11. The vehicle turn status which is output signal was connected to outport vehicle_turn_status.

Requirement-2 subsystem: -

Here first we created subsystem for our 2^st requirement.

Blocks used: - inport, outport, compareto constant

1. Took one subsystem named as requirement 2. inport for this subsystem is output signal from requirement 1 which is vehicle turn status.
2. Now input Signal Vehicle_Turn_Statusis compared against calibration values RightTurn_RoadSign, LeftTurn_RoadSign, Straight_RoadSign.
3. If the condition is true then we decide which input will go to execute with the help of and relation operator block.
4. In the relation operator block if the both inputs Turn_RoadSign and Camerainput_roadsign are given value 1 then only the turn road sign given to merge block.
5. Merge block used here to decide which value will go for execution. If the and block gives value 1 then only the merge block will give value to outport that is Vehicle_Direction_Indicator.
6. The signal conversion block is used to signal conversion of merge block with edit parameter signal copy. Which means same signal will go forward.
7. If the first comparison is true then first and block value 1 will go for merge block which is right turn road sign.
8. If the and block value is 0 (false) the second and block value will go to execution.
9. If the second comparison is true then first and block value 1 will go for merge block which is left turn road sign.
10. If the and block value is 0 (false) the third and block value will go to execution.
11. If the third comparison is true then third and block value 1 will go for merge block which is straight drive road sign.
12. The merge block will only get input from only on AND block at a time. So, the only one turn indicator signal will go at a time.

Simulation model: -

For the requairement_1 and requairement_2 inport, outprt are connected properly.

Code compiled model (non-virtual Subsystem): - (treat as atomic subsystem)

Now the most important thing we created whole Simulink model as atomic subsystem. For the code generation we need to make sub system as atomic.

After Right click on subsystem in block parameter option we have to check the treat as atomic unit option.

Signal resolve and propagation: -

1. In signal properties you can resolve and propogate th signal.
2. If the signal is first type appear in system you have to resolve at otherwise propagate it.
3. Signal resolve and propagation is most important for code generation.

Requirement tagging: -

1. Requirement tagging is nothing but link your requirement document to the model subsystem which is related to that requirement.
2. It is given advantage to understand the model when someone new are handling this file.
3. We done requirement tagging on right click on subsystem under requirement parameter you can tag the requirement.
4. First you have to select the requirement in requirement document to tag with related subsystem. Also, the file has to be saved in same directory.

MAAB guideline check: - (model advisor)

Under modelling tab there is model adviser tab to check model with standard guidelines.

Tab on that tab this window will open to select model.

1. After selecting model, the model adviser checked for model first.

1. If some errors are occurred you can check for that under the MAB tab
2. There are also some warnings. if its greater than requirement solve the warning and check again for that warning.
3. You can check for individual error and warning also
4. If you are searching for particular block in system. you can click in report on any block it will take you to that block.
5. After checking for all model with standard guidelines you can generate model adviser report

Code generation settings: -

1. There are mainly two setting we have to do which are solver setting and code generation setting.
2. For code generation we can only used fixed step solver.
3. As per requirement we change the solver setting to fix step discrete and fixed step time as 0.01 sec.
4. For embedded code generation in system target file will always ert.tlc which is embedded coder. Which generate embedded c code.

Code generation steps: -

It is a simple step if your model has no error according to MAAB guidelines then you are good to go for code generation.

In tool bar under app section there is embedded coder option.

In that option the build code option is there. Once click on that tab your code will generate.

/*
 * File: Vehicle_Direction.c
 *
 * Code generated for Simulink model 'Vehicle_direction'.
 *
 * Model version                  : 2.0
 * Simulink Coder version         : 9.6 (R2021b) 14-May-2021
 * C/C++ source code generated on : Mon Apr  4 04:04:06 2022
 *
 * Target selection: ert.tlc
 * Embedded hardware selection: Intel->x86-64 (Windows64)
 * Code generation objectives: Unspecified
 * Validation result: Not run
 */

#include "rtwtypes.h"
#include "Vehicle_direction_types.h"

/* Exported data definition */

/* Const memory section */
/* Definition for custom storage class: Const */
const int16_T LeftTurn_RoadSign = -120;/* Referenced by: '<S5>/Constant' */
const real_T Left_Turn_AngularLimit = -120.0;/* Referenced by:
                                              * '<S2>/Constant1'
                                              * '<S2>/Constant4'
                                              */
const int16_T RightTurn_RoadSign = 30; /* Referenced by: '<S4>/Constant' */
const real_T Right_Turn_AngularLimit = 30.0;/* Referenced by:
                                             * '<S2>/Constant'
                                             * '<S2>/Constant3'
                                             */
const real_T Straight_Drive_Steering_Angle = 0.0;/* Referenced by:
                                                  * '<S2>/Constant2'
                                                  * '<S2>/Constant5'
                                                  */
const int16_T Straight_RoadSign = 0;   /* Referenced by: '<S6>/Constant' */

/*
 * File trailer for generated code.
 *
 * [EOF]
 */

Conclusion: -

The code generation for model-based development is possible with right solver and code generation setting and mainly due to model adviser check for standard MAAB guidelines. Hence, we can conclude that with proper setting and standard guidelines it will very easy to build a code for model. It will be cost efficient and time saving method of design and development of model. It will possible due to MATLAB. There are many software for same in modelling environment but for better understanding and easy to used we can always preferred MATLAB.