Challenge

Project 2-Highway Assistant-Lane Changing Assistant

Aim : To design highway lane assistance model which is AUTOSAR component

Objective :

  • To develop one specific requirement of Highway Assistant – Lane
  • Changing Assistant algorithm.
  • 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.
  • 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.

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.

The model designed as per given details

Inside the subsytem

Tagging and traceability

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.

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

Tagging and traceability

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

Tagging and traceability

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

Solver Settings

Code Generation Settings

SLDD

Input signals storage class is ImportedExtern, Output signal is export to file and local signals are localizable

Model Advisor MAB Test

AUTOSAR Settings :

XML Settings

S-R Interfaces

Data Element

Runnables Init and Timing Event

Sender Ports

Receiver Port

Inport

Outport

Validating the Model

AUTOSAR Component Code Generation

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.