Project 1 (Mini Project on Vehicle Direction Detection

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

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.

Matlab Model:-

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

For the first requirement we have develop the subsystem where we did as per the statement. As per the statement we have 3 angular values, one each for left turn, right turn & straight drive (Calibration Values: Right_Turn_AngularLimit, Left_Turn_AngularLimit, SteeringWheel_YawDegreeInput). We have input as a SteeringWheel_YawDegreeInput and output signal as a C.

For these conditions we have used two nos switches.

For first switch suppose my input is equal to or grater than zero then Vehicle_Turn_Status will be Right_Turn_AngularLimit. Otherwise it will shift to another 2nd no switch where if my input signal SteeringWheel_YawDegreeInput will be equal to zero then SteeringWheel_YawDegreeInput will be SteeringWheel_YawDegreeInput otherwise Left_Turn_AngularLimit which is ourlast condition or we can say the negative value of the same.

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

For the second requirement we have developed another subsystem but its output will be used as its input aswell. In the second requirement output of the 1st requirement Vehicle_Turn_Status is compared against calibration values RightTurn_RoadSign, LeftTurn_RoadSign, Straight_RoadSign. These values are compared by the Relational operator. After comparing these values are confomed by CameraInput_RoadSign by logical operator we get the output which is 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	-	-

Creation of SLDD file:-

In the SLDD file we have attached all the signals, parameters as per the objective for errr free operation.

In the model we can also observe the tracing and tracebility of each and everyu signal.

Now we need to generate the test report of the same:-

For the test report generation we have entered in the configuration part where we have solver where we edit solver type as fised step and solver will be discrete(no continuous states).

In the code generation section we have choosed ert.tlc which is embedded coder.

Now for the test report we have to go to Apps(at he header)- Model Advisor

Then we have to select ok for the same model. If we want ot get the test report of any specific subsystem then we can also do the same by selecting the subsystem as per the image.

As per the image we can easily understand the By task sub blocks where we can select the est criteria and test blocks whichw e needed or required as per the standards or MAAB guidlines. then we run the selected checks. and after that we can genrate the report which is attached in the document.

The last job is the tracebility part or we can say traceibility of the requirement.

For this job firstly we need to copy our requirement in the word. Then select the requirement. after selecting the requirement we need to go to matlab model.

right click over the subsystem which is made as per the requirement one. then go to requirement and then link to selection in word.

After that we can see how requirement 1 is linked to this requirement subsystem. The benefit of this technique is suppose someone want to see that on which basis this subsystem has been developed so he can easily reach at that point without wasting the time to study the whole object of the system.

Conclusion:- I just want to clear that in this particular mini project what we have done.

1)- Create the model as per the requirement.

2)- Create the SLDD file.

3)- Go to the configuration for the Model advisor

4)- Gnerate the test report of the same as per selecting the blocks.

5)- Traceibilty of the system by adding requirement.