Project 1- Traffic Jam Assistant Feature

Project 1- Traffic Jam Assistant Feature

Aim:

Model Development of a single feature of Traffic Jam Assist using MATLAB & Simulink as well as Code Generation using Embedded Coder 

Objectives :

• Model Development as per MBD guidelines . Creation of Simulink Data Dictionary .
• Code Generation using Embedded Coder Generating Model Advisor Report .

Basic Working Principle :

• Traffic Jam Assistant is based on the sensors and the functionality of the Adaptive Cruise Control (ACC) with stop & go and Lane
  Keeping Support (LKS). When ACC ‘Stop & Go’ is turned ON, the Traffic Jam Assistant continuously analyses the speed of thesurrounding vehicles and compares it with the own driving speed. If the system detects dense traffic or a traffic jam at speeds less than 60 kmph, the driver can activate the functionality by the press of a button. The vehicle will now automatically follow the vehicle in front, takes over driving off, acceleration, braking and steering within the same lane. Information regarding the Traffic Jam Assistant will be available to be displayed to the driver in the Instrument Panel Cluster (IPC). The  Algorithm which the students need to implement here in this project is predominantly based on IPC units.

Simulink Model Developement:

Step1: Requirement Analysis

The Input Voltage , Input Switch and Enable switch are the inputs to the system  and Output Display is the Output from the system .

The Overall Model of Traffic Jam Assistant Feature is shown below:

Requirement 1

The Subsystem of the main model as per Requirement 1 is shown below:

• Input Signal “Input_Voltage” is compared against voltage values “VOLTAGE_MINIMUM_RANGE” & “VOLTAGE_MAXIMUM_RANGE”.
• Incoming input signal “Input_Voltage” must be greater than – equal to “VOLTAGE_MINIMUM_RANGE” and less than – equal to “VOLTAGE_MAXIMUM_RANGE”.
• Output signal from here is “Optimum_Voltage” which will be one of the inputs to the subsystem “DisplayUnit”.

`

Requirement 2 –DisplayUnit Subsystem

The Display Unit Model as per Requirement 2 is shown below:

• Input Signals are “Optimum_Voltage”, “Input_Switch”,“Enable_Display”. Signal “Enable_Display” must be saturated between the range 0 – 7. Output signal from the subsystem is “Output_Display”.
• Input Signal “Enable_Display” is compared against pre – defined set of values in a multiport switch. Total data ports in the multiport switch is 5.
• Multiport switch inputs 1 & 2 is connected to calibration signal “ON_MODE”, Multiport switch inputs 3 & 4 is connected to calibration signal “OFF_MODE” while Multiport switch input 5 is connected to calibration signal “STANDBY_MODE”.
• The output from Multiport switch is connected to the first input port of the Switch block. The third input port of the Switch block is connected to the calibration signal “NO_DISPLAY”.
• Meanwhile NOT value of input signal “Input_Switch” is compared in an AND gate against input signal “Optimum_Voltage” and the output from comparing if calibration signals “INTERRUPT_1” & “INTERRUPT_2” are equal. The output of the AND gate is the second input of the switch block.
• The output from the switch block is “Output_Display”.

Step2: Creation of Simulink Data Dictionary file (SLDD):

• First you go to model then click to link to data dictionary. Then click the new and create the sldd file and browse the file. After browsing the sldd file go to model worksplace and Update all input,output signal and calibration signals.
• A Simulink Data Dictionary (SLDD) file is created that contains input, output signals and calibration parameters used in the model. SLDD file is created by clicking on Modeling, then ‘Model Properties’, then ‘External Data’ and specifying a file name for the Data Dictionary.

Step3: Requirement Tagging:

• Requirements can be a tag to requirement 1 & requirement 2 to their corresponding subsystems with word files.

Step4: Solver configuration parameter:

• Solver type: Fixed
• Solver: discrete (no continuous states)
• Sample time: 0.01

     Code generation Parameters: 

• System target file: ert.tlc ( Embedded Coder)

 Step5: Model Advisor Check:

• Model Advisor Check on Modelling Standards for MAAB.
• Model Advisor Check completed with 16 Warnings and 127 check Passed
• There are warnings that are acceptable but the notable part is that there is not a single Failed result

   Model Advisor Report:

• Model Advisor report can be generated, we can choose the format HTML, PDF, or Word format.

      Html Report is generated and saved in the directory.

Step6: Code Generation Report

• Successfully conducted model build and generated code. The generated codes and files can be seen in the current directory.

CONCLUSION

• Developed a Model of a single feature of Traffic Jam Assist as per MAAB guidelines as well as created Simulink Data Dictionary using MATLAB & Simulink. Generated a code using Embedded Coder and generated a Model Advisor Report.