Project 1- Traffic Jam Assistant Feature

Traffic Jam Assistant Feature

Introduction to the Feature:

Traffic Jam Assistant is one of the most common feature in Advanced Driver Assistance System. Traffic Jam Assistant helps the driver arrive more relaxed at their destination, even in dense traffic or in traffic jams. As a partially automated comfort function, the system takes over the longitudinal & lateral guidance of the vehicle. This means that the car can drive off, accelerate & brake automatically, as well as steer the vehicle within certain constraints. The driver has to permanently supervise the system & be ready to take over the complete control of the vehicle at any time.

Traffic Jam Assistant system helps to avoid rear end collisions in dense traffic conditions & traffic jams. In Traffic jams, the vehicle takes over driving off, acceleration, braking and steering within same lane.

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 the surrounding 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 press of a button. The vehicle will now automatically follow the vehicle in front, takes over driving off, acceleration, braking and steering within 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.

Problem Statement:

To develop one specific requirement of Traffic Jam Assistant algorithm which would predominantly feature in the IPC algorithm.Please note that the whole Traffic Jam Assistant is a very huge algorithm & only one small part of the logic is implemented here. Idea is to familiarize with concepts of Model Based Development in MATLAB Environment. The Project must be done keeping in mind the following processes & steps.

• This model must be developed in MATLAB Simulink as per MBD guidelines.
• Code Generation Profile must be in Embedded Coder.
• Simulink Data Dictionary must be created for the model & must be linked to the model.
• Model Advisor Report is mandatory & this will be followed by Code Generation.

Input Signals:

Output Signal:

Calibration Signals:

Local Signal:

Requirement No 1:

• 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 No 2 (DisplayUnit Subsystem):

• 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

•  Designing MATLAB Simulink Model:

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

• Input Signal “Input_Voltage” is compared against voltage values “VOLTAGE_MINIMUM_RANGE” & “VOLTAGE_MAXIMUM_RANGE”. Then their outputs are given as the input for AND block, the Output of which is Optimum_Voltage.
• Optimum_Voltage from the Req1, “Input_Switch”, and “Enable_Display” are the Input Signals. The output signal from the subsystem is “Output_Display”.
•  Signal “Enable_Display” must be saturated between the range 0 – 7.

• Input Signal “Enable_Display” is compared against a pre-defined set of values in a multiport switch. The total data ports in the multiport switch are 5. Multiport switch inputs 1 & 2 are connected to calibration signal “ON_MODE”, Multiport switch inputs 3 & 4 are connected to calibration signal “OFF_MODE” while Multiport switch input 5 is connected to calibration signal “STANDBY_MODE”. The output from the 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 the value of the input signal “Input_Switch” is compared in an AND gate against the 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”.

Data Dictionary creation:

• A new Simulink data dictionary is created and updated signals & calibration Data List as per our requirements.
• The very first thing that we will do is create a Simulink Data Dictionary using the given Signal and Calibration Data List.

  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)

Requirement Tagging:

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

 Model Advisor Check:

• Model Advisor Check on Modelling Standards for MAAB.

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

C:\skill lync mbd files\assignments\New folder\slprj\modeladvisor\trafficjammini\report_1434.html

 Code Generation Report:

  Code generation: 

• By using the Embedded coder app we can generate code and build our model.

 code generated--