Project 1 (Mini Project on Vehicle Direction Detection

Mini Project - Vehicle Direction Determination

General 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 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 Mini 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

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 / 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	-	-

Main model :-

Requirement 1 & Requirement 2 subsystem :-

SLDD signals and Calibration Data :-

Requirement tagging :-

For requirement tagging right click on the subsystem> requirement > link to selection in Word.

MBD compliant :-

Go to Modelling>Model Advisor>

Select the Model/Subsystem :-

Select modelling Standard for JMAAB > Run Selected Check

Model advisor report:-

Code generation :-

Go to model configuration parameters > code generation > select target file as > browse – ert.tlc

Go to Apps> embedded coder >build > generate code

Code generation :-

Requirement 1 :-

In this subsystem the SteeringWheel_YawDegreeInput is given as the input the constant blocks are used to define the variables like Right_Turn_AngularLimit, Left_Turn_AngularLimit and Straight_Drive_Steering_Angle , the SteeringWheel_YawDegreeInput is compared by using switch block and the threshold is set as per the turn required. For right turn if steering wheel yaw degree is greater than 30 deg than it will be a right turn and if its lesser than or equal to zero than left turn and if not then straight road, for this 2 switch blocks were used and the output from the switch block is Vehicle_Turn_Status, which is used in another subsystem as input.

Requirement 2 :-

In this subsystem the input are Vehicle_Turn_Status and CameraInput_RoadSign, the Vehicle_Turn_Status is been compared with RightTurn_RoadSign, LeftTurn_RoadSign and Straight_RoadSign which ever one is equal that specific signal will get activated and then compared with CameraInput_RoadSign if both the signals are present than it will be considerd for this AND logic is been used and that signal will be coming out as Vehicle_Direction_Indicator.

Note :-

model file .slx , .sldd , Model advisor report are been attached.