Project 1 (Mini Project on Vehicle Direction Detection

Aim- Project 1 (Mini Project on Vehicle Direction Detection)

Mini Project - Vehicle Direction Determination

Main Objective-

• Development of Simulink model as per requirement.
• Tag the requirements to the Simulink model (Tagging requirements 1 & requirements 2 to their corresponding subsystem).
• MBD complaint changes, Data Dictonary creation & code generation is added advantage, that is not the scope of the project.
• 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.
• Choose sample time for all signals as 0.01s

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

Steps to consider

• Creating two subsystem inside a subsystem as per the given instruction in the requirement document.
• Attaching the requirement document.
• Creating the Simulink-data-dictionary(SLDD).
• Generating a model advisor report(with necessary tests selected).
• Generation of code.

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

SIMULINK MODEL:

Main System

• The Main System consists of two important subsystems i.e., Requirement_1 and Requirement_2.
• Apart from these subsystems, we have a constant block called 'SteeringWheel_YawDegreeInput' which is the input to the Requirement_1. Usually, we can use a Dynamic or Kinetic or mapped Steering blocks for higher end models but for the scope of this project we are just using constant blocks.
• A constant block called 'CameraUnput_RoadSign' is given as input to the Requirement_2 subsystem which is an enabled system and is set to ON only when there is a camera input.
• A display block with lamp for 'Vehicle_Directio_Indicator' which displays output for Requirement_2 i.e., output for the whole simulation.

Main_System

Inside Main_System

Requirement_1 Subsystem

• This subsystem satisfies the first requirement in our objectives.
• We used switches to compare the steering input with the calibration values i.e., Right_Turn_AngularLimit, Left_Turn_AngularLimit and Straight_Drive_SteeringAngle and appropriate output is given out as Vehicle_Turn_Status.

Requirement_2 Subsystem

• This subsystem satisfies the 2nd requirement conditions from our objective.
• It consists of three subsystem i.e., 'RightTurn_RoadSign','LeftTurn_RoadSign' and 'Straight_RoadSign', which are created with appropriate logics.
• The input 'Vehicle_Turn_Status' is compared with these three turning signals using relational operator.
• The output signal from each relational operator and road signs is combined to AND logical operator and is connected to Mux.

Conclusion- A Simulink model is created based on the given requirements and objective