Challenge

Project 2-Highway Assistant-Lane Changing Assistant

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.

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 with the intention of changing lanes, the system issues an additional acoustic and/or haptic warning.

Problem Statement:

To develop one specific requirement of Highway Assistant – Lane Changing Assistant algorithm. Please note that the whole Highway Assistant – Lane Changing Assistant is a very huge algorithm & only one small part of the logic is implemented here. Idea is to familiarize with concepts of Autosar Software Component Development in MATLAB Environment by following the Model Based Development guidelines. The Project must be done keeping in mind the following processes & steps.

  • This model must be developed in MATLAB Simulink per MBD guidelines.
  • Code Generation Profile must be Autosar Coder.
  • Simulink Data Dictionary must be created for the model & must be linked to the model.
  • All the input & output signals must be mapped into the Autosar Editor.
  • Model Advisor Report is mandatory & this will be followed by Code Generation.

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

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 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 2nd input to the switch block. Corresponding output from this particular switch block is 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 2nd input to the switch block. Corresponding output from this particular switch block is 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 2nd input to the switch block. Corresponding output from this particular switch block is 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 2nd input to the switch block. Corresponding output from this particular switch block is output signal “Display_Mode_4”.

ANS)

Procedure and steps:

SLDD File creation:

first, I create an SLDD file from the given requirement document.so they gave me calibration and signal data list in the requirement document.

Simulink Model:

first I add inports and outports and one subsystem block for this model. This subsystem block I named as Highway Assistant – Lane Changing Assistant.

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.

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

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 2nd input to the switch block. Corresponding output from this particular switch block is 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 2nd input to the switch block. Corresponding output from this particular switch block is 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 2nd input to the switch block. Corresponding output from this particular switch block is 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 2nd input to the switch block. Corresponding output from this particular switch block is output signal “Display_Mode_4”.

Then we will make the model in compliance with the AUTOSAR.So, all the inputs and output signals will be mapped into the autosar editor.

But prior to that, we will set the system target file as autosar.tlc and make sure that in solver we will set the solver to fixed-step.

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

For the S-R Interfaces of the model, we will rename the port with the prefix SRIF_.

For the Data elements of the model, we will rename the port with the prefix DE_.

Then we will validate the model for AUTOSAR Compliance.

MODEL ADVISOR REPORT:

There are warnings that are acceptable but the notable part is there is not a single failed result.

CODE GENERATION :
here code generation is done in autosar coder.
/*
* File: Project2_AUTOSAR.c
*
* Code generated for Simulink model 'Project2_AUTOSAR'.
*
* Model version : 1.7
* Simulink Coder version : 9.3 (R2020a) 18-Nov-2019
* C/C++ source code generated on : Tue Feb 8 12:11:02 2022
*
* Target selection: autosar.tlc
* Embedded hardware selection: Intel->x86-64 (Windows64)
* Code generation objectives:
* 1. Execution efficiency
* 2. RAM efficiency
* Validation result: Not run
*/
#include "Project2_AUTOSAR.h"
/* Named constants for Chart: '<S2>/Chart' */
#define IN_condition1 ((uint8)1U)
#define IN_condition2 ((uint8)2U)
/* Block signals and states (default storage) */
DW rtDW;
/* Model step function */
void untitled_Step(void)
{
sint32 rtb_Highway_Display_Mode_1;
sint32 rtb_Lane_Display_Mode_1;
sint32 rtb_Lane_Display_Mode_2;
sint32 rtb_Highway_Display_Mode_3;
sint32 rtb_Lane_Display_Mode_3;
sint32 rtb_Lane_Display_Mode_4;
sint32 tmp;
/* Chart: '<S2>/Chart' incorporates:
* Inport: '<Root>/Input_Switch'
*/
if (rtDW.is_active_c3_Project2_AUTOSAR == 0U) {
rtDW.is_active_c3_Project2_AUTOSAR=1U;
rtDW.is_c3_Project2_AUTOSAR = IN_condition1;
rtb_Highway_Display_Mode_1=232;
rtb_Highway_Display_Mode_3=41;
} else if (rtDW.is_c3_Project2_AUTOSAR == IN_condition1) {
rtb_Highway_Display_Mode_1=232;
rtb_Highway_Display_Mode_3=41;
if ((Rte_IRead_untitled_Step_Rp_Highway_Input_Signal_DE_Highway_Input_Signal
()== 1) &&
(Rte_IRead_untitled_Step_Rp_Enable_Display_DE_Enable_Display() == 1) &&
(Rte_IRead_untitled_Step_Rp_Input_Switch_DE_Input_Switch() == 1)) {
rtDW.is_c3_Project2_AUTOSAR = IN_condition2;
rtb_Highway_Display_Mode_1=213;
rtb_Highway_Display_Mode_3=9;
}
} else {
/* case IN_condition2: */
rtb_Highway_Display_Mode_1=213;
rtb_Highway_Display_Mode_3=9;
if ((Rte_IRead_untitled_Step_Rp_Highway_Input_Signal_DE_Highway_Input_Signal
()== 1) &&
(Rte_IRead_untitled_Step_Rp_Enable_Display_DE_Enable_Display() == 0) &&
(Rte_IRead_untitled_Step_Rp_Input_Switch_DE_Input_Switch() == 1)) {
rtDW.is_c3_Project2_AUTOSAR = IN_condition1;
rtb_Highway_Display_Mode_1=232;
rtb_Highway_Display_Mode_3=41;
}
}
/* End of Chart: '<S2>/Chart' */
/* Chart: '<S3>/Chart' incorporates:
* Inport: '<Root>/Input_Switch'
*/
if (rtDW.is_active_c1_Project2_AUTOSAR == 0U) {
rtDW.is_active_c1_Project2_AUTOSAR=1U;
rtDW.is_c1_Project2_AUTOSAR = IN_condition1;
rtb_Lane_Display_Mode_1=132;
rtb_Lane_Display_Mode_2=185;
rtb_Lane_Display_Mode_3=54;
rtb_Lane_Display_Mode_4=67;
} else if (rtDW.is_c1_Project2_AUTOSAR == IN_condition1) {
rtb_Lane_Display_Mode_1=132;
rtb_Lane_Display_Mode_2=185;
rtb_Lane_Display_Mode_3=54;
rtb_Lane_Display_Mode_4=67;
if ((Rte_IRead_untitled_Step_Rp_Lane_Input_Signal_DE_Lane_Input_Signal() ==
6)&& (Rte_IRead_untitled_Step_Rp_Enable_Display_DE_Enable_Display() ==
1)&& (Rte_IRead_untitled_Step_Rp_Input_Switch_DE_Input_Switch()
== 1)) {
rtDW.is_c1_Project2_AUTOSAR = IN_condition2;
rtb_Lane_Display_Mode_1=127;
rtb_Lane_Display_Mode_2=248;
rtb_Lane_Display_Mode_3=186;
rtb_Lane_Display_Mode_4=84;
}
} else {
/* case IN_condition2: */
rtb_Lane_Display_Mode_1=127;
rtb_Lane_Display_Mode_2=248;
rtb_Lane_Display_Mode_3=186;
rtb_Lane_Display_Mode_4=84;
if ((Rte_IRead_untitled_Step_Rp_Lane_Input_Signal_DE_Lane_Input_Signal() ==
6)&& (Rte_IRead_untitled_Step_Rp_Enable_Display_DE_Enable_Display() ==
0)&& (Rte_IRead_untitled_Step_Rp_Input_Switch_DE_Input_Switch()
== 1)) {
rtDW.is_c1_Project2_AUTOSAR = IN_condition1;
rtb_Lane_Display_Mode_1=132;
rtb_Lane_Display_Mode_2=185;
rtb_Lane_Display_Mode_3=54;
rtb_Lane_Display_Mode_4=67;
}
}
/* End of Chart: '<S3>/Chart' */
/* Switch: '<S1>/Switch' incorporates:
* Switch: '<S1>/Switch1'
* Switch: '<S1>/Switch2'
*/
tmp = Rte_IRead_untitled_Step_Rp_Highway_Input_Signal_DE_Highway_Input_Signal();
if (tmp > 0) {
/* Outport: '<Root>/Display_Mode_1' */
Rte_IWrite_untitled_Step_Pp_Display_Mode_1_DE_Display_Mode_1((uint8)
rtb_Highway_Display_Mode_1);
rtb_Lane_Display_Mode_2=183;
} else {
/* Outport: '<Root>/Display_Mode_1' */
Rte_IWrite_untitled_Step_Pp_Display_Mode_1_DE_Display_Mode_1((uint8)
rtb_Lane_Display_Mode_1);
}
/* End of Switch: '<S1>/Switch' */
/* Outport: '<Root>/Display_Mode_2' */
Rte_IWrite_untitled_Step_Pp_Display_Mode_2_DE_Display_Mode_2((uint8)
rtb_Lane_Display_Mode_2);
/* Switch: '<S1>/Switch2' incorporates:
* Switch: '<S1>/Switch3'
*/
if (tmp > 0) {
/* Outport: '<Root>/Display_Mode_3' */
Rte_IWrite_untitled_Step_Pp_Display_Mode_3_DE_Display_Mode_3((uint8)
rtb_Highway_Display_Mode_3);
rtb_Lane_Display_Mode_4=94;
} else {
/* Outport: '<Root>/Display_Mode_3' */
Rte_IWrite_untitled_Step_Pp_Display_Mode_3_DE_Display_Mode_3((uint8)
rtb_Lane_Display_Mode_3);
}
/* Outport: '<Root>/Display_Mode_4' */
Rte_IWrite_untitled_Step_Pp_Display_Mode_4_DE_Display_Mode_4((uint8)
rtb_Lane_Display_Mode_4);
}
/* Model initialize function */
void untitled_Init(void)
{
/* (no initialization code required) */
}
/*
* File trailer for generated code.
*
* [EOF]
*/
CONCLUSION:
Developed a model of a feature of Highway Assistant Lane Changing Assistant as per MAAB guidelines, produced Model advisor Report as well as Generated Code using Autosar coder.
Your portfolio, next

Ship work like this
in your own course.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.

Talk to a career counsellor

Free 20-minute call. We'll map the right course to where you want to work.

By submitting you agree to our Terms and Privacy Policy.