Project 1 (Mini Project on Vehicle Direction Detection

Project 1 (Mini Project on Vehicle Direction Detection

AIM:

To develop a MATLAB Simulink model as per requirement and Identify the direction of the vehicle based on the camera input, tag the requirements to the Simulink model (tagging requirements to their corresponding subsystems), and also create the corresponding Data Dictionary & generate the code.

Procedure:

1. Creating two subsystems as per the given instructions in requirement document.
2. Attaching the requirement document.
3. Creating a Simulink data dictionary (SLDD).
4. Generating a model advisor report (With necessary tests selected).
5. Generation of code.

GENERAL OVERVIEW OF PROJECT:

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 is taking 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 in Wrong Way Detection etc.

OBJECTIVE OF PROJECT:

1. Development of MATLAB Simulink model as per requirement.
2. Tag the requirements to the simulink model; tagging requirement 1 & requirement 2 to their corresponding subsystems is fine.
3. MBD compliant changes, Data Dictionary creation & code generation is added advantage, and that is not scope of this project.
4. If choosing code generation, Storage class for Input signals: ImportedExtern; Storage class for Output signal: Export to File; Storage class for local signals: localizable; Storage class for calibration signals: Const.
5. Choose sample time for all signals as 0.01s

REQUIREMENTS OF PROJECT:

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).

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).

Signals & Calibration Data List:

Signal or calibration name	Signal type	Data type	Diamention	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	-	-

ADVANCE DRIVER ASSISTANCE ACE SYSTEM MINI PROJECT VEHICLE DIRECTION DETERMINATION

Vehicle examination is critical undertaking in different apllications.it is an important process in several purposes.variuos such application are driver assistance system ,electronic toll collection, intelligent parking system.pirticularly i wrongdoing anticipation and mischance examination the assignment cal give helpful data.One such application in order to enhance the detection of vehicles is to determine the direction of vehicles.using the incresing need for security consciousness.

Identifying the direction of vehicle is one of the important and diverse features in autonomous driving and advance driver assistance features this particular sub features of identifying the direction of vehicle is basically identifying the direction of vehicle is taking based on the camera input.

Camera reads the road signs and stores into its memory with unique value 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 n the recommended direction or not.

DESIGNING THE MODEL:

This the main model subsystem that having two inputs SteeringWheel_YawDegreeInput and CameraInput_RoadSign entering into the Vehicle Detection Determination subsystem and one output Vehicle_Direction_Indicator.

And there are 2 requirements are designed in two subsystem.

REQUIREMENT 1:

1) Vehicle_Turn_Status_Subsystem:

• 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 a 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 & the output of this requirement is a local signal (Signal Name: Vehicle_Turn_Status).

REQUIREMENT 2:

2)Vehicle_Direction_Indicator_Subsystem:

• Keep this requirement as a separate subsystem. Inputs to this requirement are a local signal from requirement 1 (Signal Name: Vehicle_Turn_Status) & an input signal from the 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 OF TAGGING:

All the requirements are tagged in order for better understandability, anyone who is reviewing the model or who is trying to update the model can get a clear idea of what logic is used in the system. from the requirement manager, we can see what are all are tagged and the description.

1)Firstly I wrote all requirement in word file then I select my first requirement then I return on model select my first subsystem right click on it then goto requirements and link to selection in word then my subsystem box is highlited and linked.in this way i link my second subsyem with requirement 2.

REQUIREMENT 1 TAG WITH SUBSYSTEM 1:

REQUIREMENT 2 TAG WITH SUBSYSTEM 2:

DEVELOPING SLDD:

All the inputs, outputs, calibration parameters are saved in SLDD so while simulation the model takes all the values and its parameters from the Simulink Data Dictionary

SIGNAL RESOLUTION FOR INPUT AND OUTPUT:

The inputs and output signals are resolved so the signals will take the values from sldd and pass them to the logical blocks. Otherwise, it may take some junk values if it is unresolved

MODEL UPDATE:

The model update is done by Ctrl-D. this is done to check for any static errors. If there are no errors coming the model is working fine without any errors.

SIMULATION:

The model is simulated too for checking for errors and warnings.

CONFIGURATION PARAMETER UPDATE:

Various configuration parameters are updated as per the code generation the solver type should be fix for code generation.

MODEL ADVISORY REPORT:

By running model advisor tool,I can see comomnly made modelling errors.

1)In this process click on model advisor then thier im select by product in that, select MAB and run selected check and the following result is pass successfully.

CODE GENERATION:

For this code generation go to APPS tab then embeded coder then choose c code and generate that code which has been attached to code window.

The c code generated is :

/*
 * File: Vehicle_direction_detection.c
 *
 * Code generated for Simulink model 'Vehicle_direction_detection'.
 *
 * Model version                  : 1.21
 * Simulink Coder version         : 9.3 (R2020a) 18-Nov-2019
 * C/C++ source code generated on : Thu Feb  9 16:24:15 2023
 *
 * Target selection: ert.tlc
 * Embedded hardware selection: Intel->x86-64 (Windows64)
 * Code generation objectives: Unspecified
 * Validation result: Not run
 */

#include "Vehicle_direction_detection.h"
#include "Vehicle_direction_detection_private.h"

/* External outputs (root outports fed by signals with default storage) */
ExtY_Vehicle_direction_detect_T Vehicle_direction_detection_Y;

/* Real-time model */
RT_MODEL_Vehicle_direction_de_T Vehicle_direction_detection_M_;
RT_MODEL_Vehicle_direction_de_T *const Vehicle_direction_detection_M =
  &Vehicle_direction_detection_M_;

/* Model step function */
void Vehicle_direction_detection_step(void)
{
  /* local block i/o variables */
  int16_T Vehicle_Turn_Status;

  /* Switch: '<S3>/Switch' incorporates:
   *  Constant: '<S3>/Left_Turn_AngularLimit'
   *  Constant: '<S3>/Right_Turn_AngularLimit'
   *  Constant: '<S4>/Constant'
   *  Constant: '<S5>/Constant'
   *  Inport: '<Root>/SteeringWheel_YawDegreeInput'
   *  RelationalOperator: '<S4>/Compare'
   *  RelationalOperator: '<S5>/Compare'
   *  Switch: '<S3>/Switch1'
   */
  if (SteeringWheel_YawDegreeInput > 0) {
    Vehicle_Turn_Status = 30;
  } else if (SteeringWheel_YawDegreeInput == 0) {
    /* Switch: '<S3>/Switch1' incorporates:
     *  Constant: '<S3>/Straight_Drive_Steering_Angle'
     */
    Vehicle_Turn_Status = 0;
  } else {
    Vehicle_Turn_Status = -120;
  }

  /* End of Switch: '<S3>/Switch' */

  /* Outport: '<Root>/Vehicle_Direction_Indicator' incorporates:
   *  Constant: '<S2>/LeftTurn_RoadSign'
   *  Constant: '<S2>/RightTurn_RoadSign'
   *  Constant: '<S2>/Straight_RoadSign'
   *  Inport: '<Root>/CameraInput_RoadSign'
   *  Logic: '<S2>/AND'
   *  Logic: '<S2>/AND1'
   *  Logic: '<S2>/AND2'
   *  RelationalOperator: '<S2>/Equal'
   *  RelationalOperator: '<S2>/Equal1'
   *  RelationalOperator: '<S2>/Equal2'
   */
  Vehicle_direction_detection_Y.Vehicle_Direction_Indicator[0] =
    (CameraInput_RoadSign && (Vehicle_Turn_Status == 30));
  Vehicle_direction_detection_Y.Vehicle_Direction_Indicator[1] =
    (CameraInput_RoadSign && (Vehicle_Turn_Status == 0));
  Vehicle_direction_detection_Y.Vehicle_Direction_Indicator[2] =
    (CameraInput_RoadSign && (Vehicle_Turn_Status == -120));
}

/* Model initialize function */
void Vehicle_direction_detection_initialize(void)
{
  /* (no initialization code required) */
}

/* Model terminate function */
void Vehicle_direction_detection_terminate(void)
{
  /* (no terminate code required) */
}

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

RESULT AND CONCLUSION:

Thus the model for vehicle direction determination model will be created as per given requirements also create a sldd file based on it. All input output signals are resolved and propageted. Then generate the model advisor report and the code is generated successfully.In this way I have done my project and get result satisfactory.