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:

Name of the Signal	Data Type	Range
Input_Voltage	uint8	0 - 255
Input_Switch	boolean	0 – 1
Enable_Display	uint8	0 - 255

Output Signal:

Name of the Signal	Data Type	Range
Output_Display	uint8	0 - 255

Calibration Signals:

Name of the Signal	Data Type	Range	Initial Value
VOLTAGE_MINIMUM_RANGE	uint8	0 – 255	30
VOLTAGE_MAXIMUM_RANGE	uint8	0 – 255	50
OFF_MODE	uint8	0 – 255	2
ON_MODE	uint8	0 – 255	1
STANDBY_MODE	uint8	0 – 255	3
INTERRUPT_1	boolean	0 – 1	1
INTERRUPT_2	boolean	0 - 1	1
NO_DISPLAY	uint8	0 – 255	0

Local Signal:

Name of the Signal	Data Type	Range
Optimum_Voltage	boolean	0 - 1

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

The model is build according to the requirements:

• The above simulation model is created according to the requirement.

• The subsystem of the model is shown above.
• It contains the two subsystems of the Requirement 1, Requirement 2.

• First we have to create the sldd file.
• For that go into the modelling tab of the task bar.
• Under design category there is the Link to Data Dictionary option and then click on it.

• It will open a model parameter properties window.
• The by clicking on the new option, 'Data.sldd' file is created.
• Uncheck the 'Enable model access to base workspace' by doing this the data will not stored in the base workspace.

• Then open the model explorer from the same design category of modelling tab.
• In the model hierarchy of model workspace, the new tab of the external data is created.
• Then in the design option of the external data we have to add all the signals and parameters of the model.

• Then in the model explorer all the simulink signals are added.
• The minimum and maximum value, data type, storage class are given for the respective signal.
• The storage class for input signal, local signal and output signals is given as per the requirement.

• In the configuration parameter, solver type is selected as Fixed-step.
• The solver is selected as discrete (no-continuous states).
• And the sample time is 0.01 as per the requirement.

• Then in the code generation, System target file is selected as ert.tlc.

• In the coverage section, Enable coverage analysis is selected by checking the box.
• The structural coverage level is selected as Modified Condition Decision Coverage (MCDC).
• This will check for the total execution of the system during the simution of the model.

• Then all the subsystems of the requirements are tagged with the respective requirements.
• For that first open the word file containing all the details of the model.
• Then select the word requirement in the word file.
• After that right click on the subsystem of the requirement block.
• Then in the requirement section click on the Link to Selection in word.
• After that Requirement 1-Lead_Vehicle will appear in the requirement section as above.
• The same procedure is applied to the all other requirement block.

• In the modelling section click on the Model Advisor for generating the MAAB guidlines report.
• Select the model system for the report generation.
• After opening the new window, select the Modelling Standards for MAB in the by task section.
• After clicking on the Run Selected Checks, the summary of the report is generated showing the total pass cases, fail cases and the warnings.

• In the APPS tab select the Embedded Coder option for generating the code.
• It will open a new tab of the C CODE.

• Then in the C CODE, click on the build option.
• Then it will run for the code generation and shows the C code generated.

• If we click on the perticular block name in the C code then this block will appear on the screen with the blue colour this is called the traceability.

/*
* File: pROJECT.c
*
* Code generated for Simulink model 'pROJECT'.
*
* Model version : 1.23
* Simulink Coder version : 9.5 (R2021a) 14-Nov-2020
* C/C++ source code generated on : Sun Apr 24 15:44:45 2022
*
* Target selection: ert.tlc
* Embedded hardware selection: Intel->x86-64 (Windows64)
* Code generation objectives: Unspecified
* Validation result: Not run
*/

#include "pROJECT.h"
#include "pROJECT_private.h"

/* Exported data definition */

/* Definition for custom storage class: ExportToFile */
uint8_T Output_Display; /* '<S3>/Switch' */

/* Const memory section */
/* Definition for custom storage class: Const */
const boolean_T INTERRUPT_1 = 1; /* Referenced by: '<S3>/Constant4' */
const boolean_T INTERRUPT_2 = 1; /* Referenced by: '<S3>/Constant5' */
const uint8_T NO_DISPLAY = 0U; /* Referenced by: '<S3>/Constant3' */
const uint8_T OFF_MODE = 2U; /* Referenced by: '<S3>/Constant1' */
const uint8_T ON_MODE = 1U; /* Referenced by: '<S3>/Constant' */
const uint8_T STANDBY_MODE = 3U; /* Referenced by: '<S3>/Constant2' */
const uint8_T VOLTAGE_MAXIMUM_RANGE = 50U;/* Referenced by: '<S5>/Constant' */
const uint8_T VOLTAGE_MINIMUM_RANGE = 30U;/* Referenced by: '<S4>/Constant' */

/* Real-time model */
static RT_MODEL_pROJECT_T pROJECT_M_;
RT_MODEL_pROJECT_T *const pROJECT_M = &pROJECT_M_;

/* Model step function */
void pROJECT_step(void)
{
/* local block i/o variables */
boolean_T Optimum_Voltage;
uint8_T tmp;

/* Logic: '<S2>/AND' incorporates:
* Constant: '<S4>/Constant'
* Constant: '<S5>/Constant'
* Inport: '<Root>/Input_Voltage'
* RelationalOperator: '<S4>/Compare'
* RelationalOperator: '<S5>/Compare'
*/
Optimum_Voltage = ((Input_Voltage >= VOLTAGE_MINIMUM_RANGE) && (Input_Voltage <=
VOLTAGE_MAXIMUM_RANGE));

/* Switch: '<S3>/Switch' incorporates:
* Constant: '<S3>/Constant4'
* Constant: '<S3>/Constant5'
* Inport: '<Root>/Input_Switch'
* Logic: '<S3>/AND'
* Logic: '<S3>/NOT'
* RelationalOperator: '<S3>/Relational Operator'
*/
if ((!Input_Switch) && Optimum_Voltage && (INTERRUPT_1 == INTERRUPT_2)) {
/* Saturate: '<S3>/Saturation' incorporates:
* Inport: '<Root>/Enable_Display'
*/
if (Enable_Display < 7) {
tmp = Enable_Display;
} else {
tmp = 7U;
}

/* End of Saturate: '<S3>/Saturation' */

/* MultiPortSwitch: '<S3>/Multiport Switch' */
switch (tmp) {
case 1:
/* Switch: '<S3>/Switch' incorporates:
* Constant: '<S3>/Constant'
*/
Output_Display = ON_MODE;
break;

case 2:
/* Switch: '<S3>/Switch' incorporates:
* Constant: '<S3>/Constant'
*/
Output_Display = ON_MODE;
break;

case 3:
/* Switch: '<S3>/Switch' incorporates:
* Constant: '<S3>/Constant1'
*/
Output_Display = OFF_MODE;
break;

case 4:
/* Switch: '<S3>/Switch' incorporates:
* Constant: '<S3>/Constant1'
*/
Output_Display = OFF_MODE;
break;

default:
/* Switch: '<S3>/Switch' incorporates:
* Constant: '<S3>/Constant2'
*/
Output_Display = STANDBY_MODE;
break;
}

/* End of MultiPortSwitch: '<S3>/Multiport Switch' */
} else {
/* Switch: '<S3>/Switch' incorporates:
* Constant: '<S3>/Constant3'
*/
Output_Display = NO_DISPLAY;
}

/* End of Switch: '<S3>/Switch' */
}

/* Model initialize function */
void pROJECT_initialize(void)
{
/* (no initialization code required) */
}

/* Model terminate function */
void pROJECT_terminate(void)
{
/* (no terminate code required) */
}

/*
* File trailer for generated code.
*
* [EOF]
*/