Project 1 (Mini Project on Vehicle Direction Detection
Aim: To Develop a MATLAB Simulink Model for Vehicle Direction Detection as per requirement and generate a C-Code for it.
Objective:
- Development of MATLAB Simulink model as per requirement.
- Tag the requirements to the simulink model; tagging requirement 1 & requirement 2 to their corresponding subsystems is fine.
- MBD compliant changes, Data Dictionary creation & code generation is added advantage, and that is not scope of this project.
- Choose sample time for all signals as 0.01s
Overview:
- Identifying the direction of the vehicle is one of the important & diverse features in Autonomous driving & Advanced Driver Assistance Features. This particular sub-feature of identifying the direction of vehicle is basically identifying the direction the vehicle based on the camera input.
- Camera reads the road signs & stores into its memory with unique values for left turn, right turn & straight drive. Depending on the direction it is taking, final indication is given to the driver – as an indication if he is driving in the recommended direction or not.
- Vehicle Direction Determination can also be coupled along - side features like GPS systems to identify whether the vehicle is reaching its destination in an optimized manner. This sub feature can also be used along with Lane Detection, Highway Warning, Ramp Entry / Exit inWrong Way Detection etc.
Procedure for creating the MATLAB Simulink Model for Vehicle Direction Detection:
1. First In Matlab tool bar select Start Simulink button
2. After an dialouge box will open in that select create a Blank model
3. I saved my Blank model in the name of vehicle_direction_detection.
4. Now before creating the simulink model we need to creat a simulink data dictionary for the given set of Signals & Calibration Data List.
|
Signal / Calibration Name |
Signal Type |
Data Type |
Dimension |
Min |
Max |
Initial Value |
Units |
|
SteeringWheel_YawDegreeInput |
Input |
Int16 |
1 |
-180 |
180 |
- |
Deg |
|
CameraInput_RoadSign |
Input |
Boolean |
1 |
0 |
1 |
- |
- |
|
Vehicle_Turn_Status |
Local |
Int16 |
1 |
-180 |
180 |
- |
Deg |
|
Right_Turn_AngularLimit |
Calibration |
Int16 |
[1 1] |
-180 |
180 |
30 |
Deg |
|
Left_Turn_AngularLimit |
Calibration |
Int16 |
[1 1] |
-180 |
180 |
-120 |
Deg |
|
Straight_Drive_Steering_Angle |
Calibration |
Int16 |
[1 1] |
-180 |
180 |
0 |
Deg |
|
RightTurn_RoadSign |
Calibration |
Int16 |
[1 1] |
-180 |
180 |
30 |
|
|
LeftTurn_RoadSign |
Calibration |
Int16 |
[1 1] |
-180 |
180 |
-120 |
|
|
Straight_RoadSign |
Calibration |
Int16 |
[1 1] |
-180 |
180 |
0 |
|
|
Vehicle_Direction_Indicator |
Output |
Boolean |
1 |
0 |
1 |
- |
- |

Requirement - 1:
- Steering wheel input as yaw rate (Signal name: SteeringWheel_YawDegreeInput) is the input for this system.
- This is compared against 3 angular values, one each for left turn, right turn & straight drive (Calibration Values: Right_Turn_AngularLimit, Left_Turn_AngularLimit, Straight_Drive_Steering_Angle) to say which specific direction the steering wheel is turning towards.
- Use switch blocks to compare & develop this requirement. Keep this requirement in a subsystem & output of this requirement is a local signal (Signal Name: Vehicle_Turn_Status).
I saved my Blank model in the name of vehicle_direction_detection.
- In the simulink model select the modeling tab -> select model explorer.
- add simulink signal and add simulink parameters.
- For constant parameter and output signal we need to give name for header file and definition file. Note keep always same name for all the constant parameters and output signals add in the data dictionary.5. After the successful creation of the data dictionary for this vehicle_direction_detection model. Now we can create the model for the given requirements.

Requirement - 1:
- Steering wheel input as yaw rate (Signal name: SteeringWheel_YawDegreeInput) is the input for this system.
- This is compared against 3 angular values, one each for left turn, right turn & straight drive (Calibration Values: Right_Turn_AngularLimit, Left_Turn_AngularLimit, Straight_Drive_Steering_Angle) to say which specific direction the steering wheel is turning towards.
- Use switch blocks to compare & develop this requirement. Keep this requirement in a subsystem & output of this requirement is a local signal (Signal Name: Vehicle_Turn_Status)

- As per the given requirement-1 the created model is shown above.
- Switch block parameters.

After selected the model in the right side end of the corner we can see the three dotes. Click on the dote

Requirement – 2:
- Keep this requirement as a separate subsystem. Inputs to this requirement are local signal from requirement 1 (Signal Name: Vehicle_Turn_Status) & an input signal from camera (Signal Name: CameraInput_RoadSign), which confirms the occurrence of a road sign.
- Signal Vehicle_Turn_Status is compared against calibration values (Calibration Values: RightTurn_RoadSign, LeftTurn_RoadSign, Straight_RoadSign), if each of them is found equal, then each of the three corresponding output is compared against the camera input signal,
- Using a logical operator block, only one among them is finally given as output signal (Signal Name: Vehicle_Direction_Indicator).

Requirement – 2:
- Keep this requirement as a separate subsystem. Inputs to this requirement are local signal from requirement 1 (Signal Name: Vehicle_Turn_Status) & an input signal from camera (Signal Name: CameraInput_RoadSign), which confirms the occurrence of a road sign.
- Signal Vehicle_Turn_Status is compared against calibration values (Calibration Values: RightTurn_RoadSign, LeftTurn_RoadSign, Straight_RoadSign), if each of them is found equal, then each of the three corresponding output is compared against the camera input signal,
- Using a logical operator block, only one among them is finally given as output signal (Signal Name: Vehicle_Direction_Indicator).

- As per the given requirement-2 the created model is shown above.
- Switch block parameters.

- After selected the model in the right side end of the corner we can see the three dotes. Click on the dote and it will lead to creating subsystem. Rename the created subsystem as Requirement-2

I. Tag the requirement to the Requirement-1 subsystem:
- For tag requirements in Requirement-1 subsystem first click on the subsystem and then right click on it -> Goto Requirements -> select 'Link to selection in work'.
- Meanwhile in word document highlight which of the thing need to tag.

II. Tag the requirement to the Requirement-2 subsystem:
- Similarly for tag requirements in Requirement-2 subsystem first click on the subsystem and then right click on it -> Goto Requirements -> select 'Link to selection in work'.
- Meanwhile in word document highlight which of the thing need to tag.
8. Now a check is performed using Model Advisor tool in simulink to see whether the develped model meets the modeling standard

- Now before code generation we need to do some changes in the solver configuration and code generation settings for that in matlab
- under modeling tab -> select model setting. Then the model setting dialoug box will open now.


- To generate code select the substem named as vehicle direction detection and then In matlab on the simulink model file embedded coder tool box is availabele under APPS tab click on it.
- A new tab C CODE is open next to the APPS tab under that tab click athe Generate Code
