Project 2-Highway Assistant-Lane Changing Assistant

Highway Assistant-Lane Changing Assistant

Aim:

Model Development of a feature of Highway Assistant-Lane Changing Assistant using MATLAB and Simulink as per MAAB guidelines, producing Model Advisor Report as well as generating Code using AUTOSAR Coder.

Objective:

• Model Development in MATLAB Simulink as per MAAB guidelines.
• Code Generation using Autosar Coder.
• Creation of Simulink Data Dictionary.
• Mapping all the input & output signals into the Autosar Editor.
• Generating Model Advisor Report.

Highway Assistant – Lane Changing Assistant

Introduction to the Feature:

The Highway Assistant supports the driver and takes over the longitudinal and lateral guidance of the vehicle in monotonous driving situations on highways. The partially automated function can automatically start, accelerate, brake as well as steer the vehicle to a certain extent. The driver has to permanently supervise the system and be ready to take over the complete control of the vehicle at any time.

Fig: Lane Changing Assistant

Drivers are taught to assess surrounding traffic before changing lanes by checking their rearview and side mirrors and looking over each shoulder. However, even for those who follow this sequence of checks, the vehicle's blind spot – the area alongside and just behind the vehicle – is a constant source of danger and often the cause of serious accidents. Even vehicles approaching quickly from behind can pose a risk. To make changing lanes safer, this feature has been developed.

Basic Working Principle:

Highway Assistant is a partially automated driving function for a speed range of up to 180 km/h (112 mph) on highways. It combines the radar-based longitudinal guidance of Adaptive Cruise Control (ACC) with the video-based lateral guidance of lane-keeping support in one system. Highway Assistant can be supplemented by an automatic lane change initiated and monitored by the driver in a speed range of 60 – 130 km/h (35 – 80 mph).

The Lane Change Assistant works by using two mid-range radar sensors that are concealed in the rear bumper – one on the left, one on the right. These two sensors monitor the area alongside and behind the car. Powerful control software collates the sensor information to create a complete picture of all traffic in the area behind the vehicle. Whenever another vehicle approaches at speed from behind or is already present in the blind spot, a signal such as a warning light in the side mirror alerts the driver to the hazard. Should the driver still activate the turn signal to change lanes, the system issues an additional acoustic and/or haptic warning.

Calibration and Signal Data List:

Input Signals:

Name of the Signal	Data Type	Range
Highway_Input_Signal	uint8	0 - 255
Enable_Display	uint8	0 – 255
Input_Switch	uint8	0 – 255
Lane_Input_Signal	uint8	0 - 255

Local Signals:

Name of the Signal	Data Type	Range
Highway_Display_Mode_1	uint8	0 - 255
Highway_Display_Mode_2	uint8	0 – 255
Highway_Display_Mode_3	uint8	0 – 255
Highway_Display_Mode_4	uint8	0 – 255
Lane_Display_Mode_1	uint8	0 – 255
Lane_Display_Mode_2	uint8	0 – 255
Lane_Display_Mode_3	uint8	0 – 255
Lane_Display_Mode_4	uint8	0 – 255

Output Signals:

Name of the Signal	Data Type	Range
Display_Mode_1	uint8	0 - 255
Display_Mode_2	uint8	0 – 255
Display_Mode_3	uint8	0 – 255
Display_Mode_4	uint8	0 - 255

Requirements:

Requirement No.- 1 [Highway_DisplayUnit]:

Inputs to this particular subsystem are “Highway_Input_Signal”, “Enable_Display”, “Input_Switch”. These three input signals, when assigned to a particular value will give output signals of a specific value. The output signals are “Highway_Display_Mode_1”, “Highway_Display_Mode_2”, “Highway_Display_Mode_3”, “Highway_Display_Mode_4”. The requirement must be implemented in the form of a Stateflow logic.

Condition	Action
Highway_Input_Signal = 1 Enable_Display = off Input_Switch = on	Highway_Display_Mode_1 = 232 Highway_Display_Mode_2 = 183 Highway_Display_Mode_3 = 41 Highway_Display_Mode_4 = 94
Highway_Input_Signal = 1 Enable_Display = on Input_Switch = on	Highway_Display_Mode_1 = 213 Highway_Display_Mode_2 = 183 Highway_Display_Mode_3 = 9 Highway_Display_Mode_4 = 94

Requirement No.- 2 [Lane_DisplayUnit]:

Inputs to this particular subsystem are “Enable_Display”, “Input_Switch”, “Lane_Input_Signal”. These three input signals, when assigned to a particular value will give output signals of a specific value. The output signals are “Lane_Display_Mode_1”, “Lane_Display_Mode_2”, “Lane_Display_Mode_3”, “Lane_Display_Mode_4”. The requirement must be implemented in the form of Stateflow logic.

Condition	Action
Lane_Input_Signal= 6 Enable_Display = off Input_Switch = on	Lane_Display_Mode_1 = 132 Lane_Display_Mode_2 = 185 Lane_Display_Mode_3 = 54 Lane_Display_Mode_4 = 67
Lane_Input_Signal= 6 Enable_Display = on Input_Switch = on	Lane_Display_Mode_1 = 127 Lane_Display_Mode_2 = 248 Lane_Display_Mode_3 = 186 Lane_Display_Mode_4 = 84

Requirement No.- 3:

Signals coming from both subsystems “Highway_Display_Mode_1” & “Lane_Display_Mode_1” are given as inputs to a switch block which will have input signal “Highway_Input_Signal” given as 2^nd input to the switch block. The corresponding output from this particular switch block is the output signal “Display_Mode_1”.

Signals coming from both subsystems “Highway_Display_Mode_2” & “Lane_Display_Mode_2” are given as inputs to a switch block which will have input signal “Highway_Input_Signal” given as 2^nd input to the switch block. The corresponding output from this particular switch block is the output signal “Display_Mode_2”.

Signals coming from both subsystems “Highway_Display_Mode_3” & “Lane_Display_Mode_3” are given as inputs to a switch block which will have input signal “Highway_Input_Signal” given as 2^nd input to the switch block. The corresponding output from this particular switch block is the output signal “Display_Mode_3”.

Signals coming from both subsystems “Highway_Display_Mode_4” & “Lane_Display_Mode_4” are given as inputs to a switch block which will have input signal “Highway_Input_Signal” given as 2^nd input to the switch block. The corresponding output from this particular switch block is the output signal “Display_Mode_4”.

Procedure and Steps:

The first step is the creation of the Simulink Data Dictionary File from the given calibration and signal data list. Then data dictionary should be linked to the specified simulink model.

folowing are steps for creating "SLLDD"

Design the data inside "SLDD" according to given data

NOTE: Some rule for "Design data" for iput/output/local signal we should choose"simulink signal"

for "constant signal" we should choose "simulink parameter"

for own data we choose "Alias type"

so we choose only "simulink signal" according to data

As per the first requirement, the first subsystem will have three inputs. They are Highway_Input_Signal, Enable_Display, and Input_Switch.

The input further goes to the chart. The chart will have the output as Highway_Display_Mode_1, Highway_Display_Mode_2, Highway_Display_Mode_3, and Highway_Display_Mode_4.

Inside the chart, we will implement Highway_Input_Signal, Enable_Display, and Input_Switch using AND blocks. The output is given in the State.

As per requirement 2, we will enable the subsystem using Lane_Input_Signal for a value of 6. Input for the block will be Input_Switch and Enable_display. Here, from and to blocks are used to make connections easy and readable.

EN_D= Enable_Display, IPS= Input_Switch, HIS= Highway_Input_Signal, HD1= Highway_Display_1,...., HD4= Highway_Display_4, LD1= Lane_Display_1,...., LD4= Lane_Display_4.

These inputs will further go to Chart, where the Stateflow logic will be written. The output of the chart are Lane_Display_Mode_1, Lane_Display_Mode_2, Lane_Display_Mode_3, Lane_Display_Model_4.

Inside the chart, the Enable_Display and Input_Switch are used to make logic for Lane Display output.

The main output is written inside the State for Lane_Display_Mode.

The input and output signals are then resolved.

The output of the Highway_Display_Mode and Lane_Display_Mode are provided to the Switch block. That is in total 4 switch blocks are used. The conditional input signal is taken as Highway_Input_Signal for all the blocks.

The final model of simulink

for no-one play with model we will put all this in a single subsystem. For hide the subsysten, we will mask the subsystem

signal has resolved

Requirement tagging of subsystem

steps

• first create word document file, save it same file and paste all data of requirement
• copy title of requirement and on subsystem
• Right click on subsystem select tag

Port mapping and code mapping and autosar editor

then under App, we will select the AUTOSAR component.

This will open Code Mapping - AUTOSAR SW Component.

For the Reciever port of the model, that is input, we will rename the port with the prefix Rp_.

For the Sender port of the model, that is output, we will rename the port with the prefix Pp_.

Modal advisor and it report

Steps

• go to modelind tab and click on it
• click on model adviser
• choose by task

according requirement select guidelines

and perform operation

Code generator and its file