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

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 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 with the intention of changing 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 2nd 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 2nd 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 2nd 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 2nd input to the switch block. The corresponding output from this particular switch block is the output signal “Display_Mode_4”.

PROCEDURE:-

The first step is the creation of the Simulink Data Dictionary File from the given calibration and signal data list.

Simulink Data Dictionary for Lane Changing Assistant Feature

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

Subsystem for Highway_DisplayUnit

• 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

Chart for Highway_DisplayUnit

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

Stateflow logic for Highway_DisplayUnit

• Once the Stateflow logic is written, we will resolve the port for input and output.

Resolved Signal for Highway_DisplayUnit

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

Subsystem for Lane_DisplayUnit

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

Chart for Lane_DisplayUnit

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

Stateflow logic for Lane_DisplayUnit

• The input and output signals are then resolved.

Resolved Signal for Lane_DisplayUnit

• Once this is done we will propagate the signals to the output. Then the output of Highway_Way_Mode and Lane_Display_Mode are provided to the suitable output port. Here we use Goto block instead of the output block.

Output of Highway_DisplayUnit and Lane_DisplayUnit

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

Display_Mode output

Simulink Model of Highway Assistant-Lane Changing Assistant

• To give a better look we will put all this in a single subsystem. For better visualization, we will mask the subsystem with the appropriate image.

Final Model of Highway Assistant-Lane Changing Assistant

• Then we will make the model in compliance with the AUTOSAR. So, all the input & output signals will be mapped into the Autosar Editor.
• But prior to that, we will set the System target file as autosar.tlc
• We will make sure that in Solver we will set the solver to Fixed-Step.

Code Generation Setting

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

RecieverPorts of the model

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

SenderPorts of the model

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

S-R Interfaces of the model

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

Data Element of the model

• We then add the runnables

Runnables

• After this we configure the XML option

XML Options

• After this we proceed to map the inports, and outports to respective interfaces and data elements and also map the runnable.
• We then update the mapping done and run the validation check.

• Then we will validate the model for AUTOSAR Compliance.

AutoSAR Validation

• After port-mapping validation , we simulate the model first and then run Model Advisory Check for MAB guidelines under Modelling.

Model Advisory Report

• Once the mapping is done we will check for Model Advisor.
• Then after a successful check, we will Generate a Code. in AutoSAR Quick Start

Generated C code for the Model

• The following is the complete Generated C Code for the Model:

/*
 * File: LCA_SWC.c
 *
 * Code generated for Simulink model 'LCA_SWC'.
 *
 * Model version                  : 1.17
 * Simulink Coder version         : 9.5 (R2021a) 14-Nov-2020
 * C/C++ source code generated on : Wed Jul 27 03:27:06 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 "LCA_SWC.h"

/* Named constants for Chart: '<S2>/Highway_DisplayUnit_Chart' */
#define IN_Condition_1                 ((uint8)1U)
#define IN_Condition_2                 ((uint8)2U)

/* Named constants for Chart: '<S3>/Lane_DisplayUnit_Chart' */
#define IN_Condition1                  ((uint8)1U)
#define IN_Condition2                  ((uint8)2U)

/* Block signals and states (default storage) */
DW rtDW;

/* Model step function */
void LCA50ms(void)
{
  sint32 rtb_Highway_Display_Mode_1;
  sint32 rtb_Highway_Display_Mode_3;
  sint32 rtb_Lane_Display_Mode_1;
  sint32 rtb_Lane_Display_Mode_2;
  sint32 rtb_Lane_Display_Mode_3;
  sint32 rtb_Lane_Display_Mode_4;
  sint32 tmp_0;
  uint8 tmp;

  /* Chart: '<S2>/Highway_DisplayUnit_Chart' incorporates:
   *  Inport: '<Root>/Enable_Display'
   *  Inport: '<Root>/Highway_Input_Signal'
   *  Inport: '<Root>/Input_Switch'
   */
  if (rtDW.is_active_c3_LCA_SWC == 0U) {
    rtDW.is_active_c3_LCA_SWC = 1U;
    rtDW.is_c3_LCA_SWC = IN_Condition_1;
    rtb_Highway_Display_Mode_1 = 232;
    rtb_Highway_Display_Mode_3 = 41;
  } else if (rtDW.is_c3_LCA_SWC == IN_Condition_1) {
    if ((Rte_IRead_LCA50ms_Rp_Highway_Input_Signal_DE_Highway_Input_Signal() ==
         1) && (Rte_IRead_LCA50ms_Rp_Enable_Display_DE_Enable_Display() == 1) &&
        (Rte_IRead_LCA50ms_Rp_Input_Switch_DE_Input_Switch() == 1)) {
      rtDW.is_c3_LCA_SWC = IN_Condition_2;
      rtb_Highway_Display_Mode_1 = 213;
      rtb_Highway_Display_Mode_3 = 9;
    } else {
      rtb_Highway_Display_Mode_1 = 232;
      rtb_Highway_Display_Mode_3 = 41;
    }

    /* case IN_Condition_2: */
  } else if ((Rte_IRead_LCA50ms_Rp_Highway_Input_Signal_DE_Highway_Input_Signal()
              == 1) && (Rte_IRead_LCA50ms_Rp_Enable_Display_DE_Enable_Display() ==
                        0) && (Rte_IRead_LCA50ms_Rp_Input_Switch_DE_Input_Switch
              () == 1)) {
    rtDW.is_c3_LCA_SWC = IN_Condition_1;
    rtb_Highway_Display_Mode_1 = 232;
    rtb_Highway_Display_Mode_3 = 41;
  } else {
    rtb_Highway_Display_Mode_1 = 213;
    rtb_Highway_Display_Mode_3 = 9;
  }

  /* End of Chart: '<S2>/Highway_DisplayUnit_Chart' */

  /* Chart: '<S3>/Lane_DisplayUnit_Chart' incorporates:
   *  Inport: '<Root>/Enable_Display'
   *  Inport: '<Root>/Input_Switch'
   *  Inport: '<Root>/Lane_Input_Signal'
   */
  if (rtDW.is_active_c1_LCA_SWC == 0U) {
    rtDW.is_active_c1_LCA_SWC = 1U;
    rtDW.is_c1_LCA_SWC = 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_LCA_SWC == IN_Condition1) {
    if ((Rte_IRead_LCA50ms_Rp_Lane_Input_Signal_DE_Lane_Input_Signal() == 6) &&
        (Rte_IRead_LCA50ms_Rp_Enable_Display_DE_Enable_Display() == 1) &&
        (Rte_IRead_LCA50ms_Rp_Input_Switch_DE_Input_Switch() == 1)) {
      rtDW.is_c1_LCA_SWC = 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 {
      rtb_Lane_Display_Mode_1 = 132;
      rtb_Lane_Display_Mode_2 = 185;
      rtb_Lane_Display_Mode_3 = 54;
      rtb_Lane_Display_Mode_4 = 67;
    }

    /* case IN_Condition2: */
  } else if ((Rte_IRead_LCA50ms_Rp_Lane_Input_Signal_DE_Lane_Input_Signal() == 6)
             && (Rte_IRead_LCA50ms_Rp_Enable_Display_DE_Enable_Display() == 0) &&
             (Rte_IRead_LCA50ms_Rp_Input_Switch_DE_Input_Switch() == 1)) {
    rtDW.is_c1_LCA_SWC = 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 {
    rtb_Lane_Display_Mode_1 = 127;
    rtb_Lane_Display_Mode_2 = 248;
    rtb_Lane_Display_Mode_3 = 186;
    rtb_Lane_Display_Mode_4 = 84;
  }

  /* End of Chart: '<S3>/Lane_DisplayUnit_Chart' */

  /* Switch: '<S1>/Switch' incorporates:
   *  Inport: '<Root>/Highway_Input_Signal'
   *  Switch: '<S1>/Switch1'
   *  Switch: '<S1>/Switch2'
   *  Switch: '<S1>/Switch3'
   */
  tmp_0 = Rte_IRead_LCA50ms_Rp_Highway_Input_Signal_DE_Highway_Input_Signal();
  if (tmp_0 != 0) {
    tmp = (uint8)rtb_Highway_Display_Mode_1;
  } else {
    tmp = (uint8)rtb_Lane_Display_Mode_1;
  }

  /* End of Switch: '<S1>/Switch' */

  /* Outport: '<Root>/Display_Mode_1' */
  Rte_IWrite_LCA50ms_Pp_Display_Mode_1_DE_Display_Mode_1(tmp);

  /* Switch: '<S1>/Switch1' */
  if (tmp_0 != 0) {
    tmp = 183U;
  } else {
    tmp = (uint8)rtb_Lane_Display_Mode_2;
  }

  /* Outport: '<Root>/Display_Mode_2' */
  Rte_IWrite_LCA50ms_Pp_Display_Mode_2_DE_Display_Mode_2(tmp);

  /* Switch: '<S1>/Switch2' */
  if (tmp_0 != 0) {
    tmp = (uint8)rtb_Highway_Display_Mode_3;
  } else {
    tmp = (uint8)rtb_Lane_Display_Mode_3;
  }

  /* Outport: '<Root>/Display_Mode_3' */
  Rte_IWrite_LCA50ms_Pp_Display_Mode_3_DE_Display_Mode_3(tmp);

  /* Switch: '<S1>/Switch3' */
  if (tmp_0 != 0) {
    tmp = 94U;
  } else {
    tmp = (uint8)rtb_Lane_Display_Mode_4;
  }

  /* Outport: '<Root>/Display_Mode_4' */
  Rte_IWrite_LCA50ms_Pp_Display_Mode_4_DE_Display_Mode_4(tmp);
}

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

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

• The .h code generated is

/*
 * File: LCA_SWC.h
 *
 * Code generated for Simulink model 'LCA_SWC'.
 *
 * Model version                  : 1.17
 * Simulink Coder version         : 9.5 (R2021a) 14-Nov-2020
 * C/C++ source code generated on : Wed Jul 27 03:27:06 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
 */

#ifndef RTW_HEADER_LCA_SWC_h_
#define RTW_HEADER_LCA_SWC_h_
#ifndef LCA_SWC_COMMON_INCLUDES_
#define LCA_SWC_COMMON_INCLUDES_
#include "rtwtypes.h"
#include "Rte_LCA_SWC.h"
#endif                                 /* LCA_SWC_COMMON_INCLUDES_ */

/* Model Code Variants */

/* Macros for accessing real-time model data structure */

/* Block signals and states (default storage) for system '<Root>' */
typedef struct tag_DW {
  uint8 is_active_c1_LCA_SWC;          /* '<S3>/Lane_DisplayUnit_Chart' */
  uint8 is_c1_LCA_SWC;                 /* '<S3>/Lane_DisplayUnit_Chart' */
  uint8 is_active_c3_LCA_SWC;          /* '<S2>/Highway_DisplayUnit_Chart' */
  uint8 is_c3_LCA_SWC;                 /* '<S2>/Highway_DisplayUnit_Chart' */
} DW;

/* Block signals and states (default storage) */
extern DW rtDW;

/*-
 * The generated code includes comments that allow you to trace directly
 * back to the appropriate location in the model.  The basic format
 * is <system>/block_name, where system is the system number (uniquely
 * assigned by Simulink) and block_name is the name of the block.
 *
 * Use the MATLAB hilite_system command to trace the generated code back
 * to the model.  For example,
 *
 * hilite_system('<S3>')    - opens system 3
 * hilite_system('<S3>/Kp') - opens and selects block Kp which resides in S3
 *
 * Here is the system hierarchy for this model
 *
 * '<Root>' : 'LCA_SWC'
 * '<S1>'   : 'LCA_SWC/Highway Assistant – Lane Changing Assistant'
 * '<S2>'   : 'LCA_SWC/Highway Assistant – Lane Changing Assistant/Highway_DisplayUnit'
 * '<S3>'   : 'LCA_SWC/Highway Assistant – Lane Changing Assistant/Lane_DisplayUnit'
 * '<S4>'   : 'LCA_SWC/Highway Assistant – Lane Changing Assistant/Highway_DisplayUnit/Highway_DisplayUnit_Chart'
 * '<S5>'   : 'LCA_SWC/Highway Assistant – Lane Changing Assistant/Lane_DisplayUnit/Lane_DisplayUnit_Chart'
 */
#endif                                 /* RTW_HEADER_LCA_SWC_h_ */

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

RESULTS:-

• According to MAAB criteria, a model of the Highway Assistant-Lane Changing Assistant feature was developed.
• The Simulink Data Dictionary is created and linked with the developed model.
• All the input & output signals are mapped into the Autosar Editor.
• Model Advisor Report is also generated for MAB guidlines
• Code is generated successfully using Autosar Quick start to generate report.

CONCLUSION: A simulink model of the Highway Assistant-Lane Changing Assistant feature was developed and all the objectives of the project are met.