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.

Model-

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

STEPS-
1) Create simulink data dictionary for given input,output and local signals. Keep storage class as auto for all the signals.

2)Select system target file as autosar.tlc from code generation. Also set solver as fixed step.

3)Port Mapping-
Performed port, interface and data elements mapping.



4)Model advisor check.
Run the model advisor check for Modeling Standards for ISO 26262,Model Referencing,Modeling Standards for MAB,Modeling Standards for JMAAB,Modeling Standards for MISRA C:2012.
Eliminate the as many warnings as possible to make the model MBD compliant.
Run the model advisor report again.
5) Code generation-
Click on Quick start from autosar code generation.
Select the options as shown bellow and click next.






Click Next for code generation.
Code-
/* * File: Project2.c * * Code generated for Simulink model 'Project2'. * * Model version : 1.18 * Simulink Coder version : 9.3 (R2020a) 18-Nov-2019 * C/C++ source code generated on : Mon Jul 25 10:50:18 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.h" /* Named constants for Chart: '<S3>/Chart' */ /* Named constants for Chart: '<S4>/Chart' */ /* Block signals and states (default storage) */ /* Model step function */ { /* Chart: '<S3>/Chart' incorporates: * Inport: '<Root>/Enable_Display' * Inport: '<Root>/Highway_Input_Signal' * Inport: '<Root>/Input_Switch' */ } } else { /* case IN_Condition_2: */ } } /* End of Chart: '<S3>/Chart' */ /* Chart: '<S4>/Chart' incorporates: * Inport: '<Root>/Enable_Display' * Inport: '<Root>/Input_Switch' * Inport: '<Root>/Lane_Input_Signal' */ } } else { /* case IN_Condition2: */ } } /* End of Chart: '<S4>/Chart' */ /* Switch: '<S2>/Switch' incorporates: * Inport: '<Root>/Highway_Input_Signal' * Switch: '<S2>/Switch1' * Switch: '<S2>/Switch2' * Switch: '<S2>/Switch3' */ /* Outport: '<Root>/Display_Mode_1' */ /* Outport: '<Root>/Display_Mode_2' */ /* Outport: '<Root>/Display_Mode_3' */ } else { /* Outport: '<Root>/Display_Mode_1' */ /* Outport: '<Root>/Display_Mode_2' */ /* Outport: '<Root>/Display_Mode_3' */ } /* End of Switch: '<S2>/Switch' */ /* Outport: '<Root>/Display_Mode_4' */ } /* Model initialize function */ { /* (no initialization code required) */ } /* * File trailer for generated code. * * [EOF]