All Courses
All Courses
Courses by Software
Courses by Semester
Courses by Domain
Tool-focused Courses
Machine learning
POPULAR COURSES
Success Stories
AIM: To develop an algorithm for one of the features of the Highway Lane Changing Assistance, create a Simulink Data Dictionary for the given signals data lists, develop a model advisor report and generate a C code for it using AUTOSAR coder in SIMULINK Objective: Model development in MATLAB Simulink as per MBD guidelines…
Sanket Nehete
updated on 16 Oct 2021
AIM:
To develop an algorithm for one of the features of the Highway Lane Changing Assistance, create a Simulink Data Dictionary for the given signals data lists, develop a model advisor report and generate a C code for it using AUTOSAR coder in SIMULINK
Objective:
Overview:
Introduction to 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.
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 |
Procedure:
Creation of the Simulink data dictionary is the first step using calibration and signal data lists
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.
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 |
As per the requirement, there are three signals to the subsystem as shown below
These three inputs are used to develop an algorithm as per the given conditions using Stateflow logic. The output data is of ‘double’ data type, so converting it to the ‘unit8’ data type using the Data type conversion block.
The following figure shows the developed algorithms as per the given conditions using Stateflow logic.
Once the Stateflow logic is developed, resolving the ports for input and output
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 |
As per the requirement, there are signals to the subsystem as shown below
These three inputs are used to develop an algorithm as per the given conditions using Stateflow logic. The output data is of ‘double’ data type, so converting it to be the ‘unit8’ data type using the Data type conversion block
The following figure shows the developed algorithm as per the given conditions using Stateflow logic
Once the Stateflow logic is developed, resolving the ports for inputs and output.
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”.
The following figure shows the subsystem consisting of all the three requirements
The following figure shows the whole model created for the Highway Lane Changing Assistance with all input and output ports using Simulink
Now making the model in compliance with the AUTOSAR. So, all the input and output signals will be mapped into the Autosar Editor.
But prior to that, setting the System target file as autosar.tlc and make sure that in Solver set it to Fixed-Step
Then under the App, selecting the Autosar Component Designer
This will open Code Mapping – Autosar SW Component
XML changes:
For the S-R Interfaces of the model, renaming the ports with the prefix SRif_.
For the data elements of the model, renaming the ports with the prefix DE_.
For the Receiver ports of the model, that is input, remaining the port with the prefix Rp_.
For the Sender ports of the model, that is output, renaming the port with the prefix Pp_.
Now, mapping the Inports of the model
Outports of the model,
Now validating model as per the Autosar compliance
Once the model is validated, generate the Model Advisor report as per ISO26262 Standards and MAAB guidelines,
We can see that there is no error in the model advisor check for ISO 26262 and MAAB guidelines.
Now generating the C code for the developed model using Autosar coder.
.c code
Highway_Assistant.c
/*
* File: Highway_Assistant.c
*
* Code generated for Simulink model 'Highway_Assistant'.
*
* Model version : 1.1
* Simulink Coder version : 9.5 (R2021a) 14-Nov-2020
* C/C++ source code generated on : Sun Oct 17 00:04:06 2021
*
* Target selection: autosar.tlc
* Embedded hardware selection: Intel->x86-64 (Windows64)
* Code generation objectives: Unspecified
* Validation result: Not run
*/
#include "Highway_Assistant.h"
#include "Highway_Assistant_private.h"
/* Named constants for Chart: '<S2>/Highway_Display_Unit' */
#define Highway_Assistant_IN_Condition1 ((uint8)1U)
#define Highway_Assistant_IN_Condition2 ((uint8)2U)
/* Block states (default storage) */
DW_Highway_Assistant_T Highway_Assistant_DW;
/* Model step function */
void highway_assistant_step_1(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;
uint8 rtb_Display_Mode_4;
uint8 tmp;
/* Chart: '<S2>/Highway_Display_Unit' incorporates:
* Inport: '<Root>/Enable_Display'
* Inport: '<Root>/Highway_Input_Signal'
* Inport: '<Root>/Input_Switch'
*/
if (Highway_Assistant_DW.is_active_c3_Highway_Assistant == 0U) {
Highway_Assistant_DW.is_active_c3_Highway_Assistant = 1U;
Highway_Assistant_DW.is_c3_Highway_Assistant =
Highway_Assistant_IN_Condition1;
rtb_Highway_Display_Mode_1 = 232;
rtb_Highway_Display_Mode_3 = 41;
} else if (Highway_Assistant_DW.is_c3_Highway_Assistant ==
Highway_Assistant_IN_Condition1) {
rtb_Highway_Display_Mode_1 = 232;
rtb_Highway_Display_Mode_3 = 41;
if ((Rte_IRead_highway_assistant_step_1_Rp_Highway_Input_Signal_DE_Highway_Input_Signal
() == 1) &&
(Rte_IRead_highway_assistant_step_1_Rp_Enable_Display_DE_Enable_Display()
== 1) &&
(Rte_IRead_highway_assistant_step_1_Rp_Input_Switch_DE_Input_Switch() ==
1)) {
Highway_Assistant_DW.is_c3_Highway_Assistant =
Highway_Assistant_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_highway_assistant_step_1_Rp_Highway_Input_Signal_DE_Highway_Input_Signal
() == 1) &&
(Rte_IRead_highway_assistant_step_1_Rp_Enable_Display_DE_Enable_Display()
== 0) &&
(Rte_IRead_highway_assistant_step_1_Rp_Input_Switch_DE_Input_Switch() ==
1)) {
Highway_Assistant_DW.is_c3_Highway_Assistant =
Highway_Assistant_IN_Condition1;
rtb_Highway_Display_Mode_1 = 232;
rtb_Highway_Display_Mode_3 = 41;
}
}
/* End of Chart: '<S2>/Highway_Display_Unit' */
/* Chart: '<S3>/Lane_Display_Unit' incorporates:
* Inport: '<Root>/Enable_Display'
* Inport: '<Root>/Input_Switch'
* Inport: '<Root>/Lane_Input_Signal'
*/
if (Highway_Assistant_DW.is_active_c1_Highway_Assistant == 0U) {
Highway_Assistant_DW.is_active_c1_Highway_Assistant = 1U;
Highway_Assistant_DW.is_c1_Highway_Assistant =
Highway_Assistant_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 (Highway_Assistant_DW.is_c1_Highway_Assistant ==
Highway_Assistant_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_highway_assistant_step_1_Rp_Lane_Input_Signal_DE_Lane_Input_Signal
() == 6) &&
(Rte_IRead_highway_assistant_step_1_Rp_Enable_Display_DE_Enable_Display()
== 1) &&
(Rte_IRead_highway_assistant_step_1_Rp_Input_Switch_DE_Input_Switch() ==
1)) {
Highway_Assistant_DW.is_c1_Highway_Assistant =
Highway_Assistant_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_highway_assistant_step_1_Rp_Lane_Input_Signal_DE_Lane_Input_Signal
() == 6) &&
(Rte_IRead_highway_assistant_step_1_Rp_Enable_Display_DE_Enable_Display()
== 0) &&
(Rte_IRead_highway_assistant_step_1_Rp_Input_Switch_DE_Input_Switch() ==
1)) {
Highway_Assistant_DW.is_c1_Highway_Assistant =
Highway_Assistant_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>/Lane_Display_Unit' */
/* Switch: '<S4>/Switch' incorporates:
* Inport: '<Root>/Highway_Input_Signal'
* Switch: '<S4>/Switch1'
* Switch: '<S4>/Switch2'
* Switch: '<S4>/Switch3'
*/
tmp =
Rte_IRead_highway_assistant_step_1_Rp_Highway_Input_Signal_DE_Highway_Input_Signal
();
if (tmp > 0) {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S2>/Data Type Conversion'
*/
rtb_Display_Mode_4 = (uint8)rtb_Highway_Display_Mode_1;
} else {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S3>/Data Type Conversion'
*/
rtb_Display_Mode_4 = (uint8)rtb_Lane_Display_Mode_1;
}
/* End of Switch: '<S4>/Switch' */
/* Outport: '<Root>/Display_Mode_1' */
Rte_IWrite_highway_assistant_step_1_Pp_Display_Mode_1_DE_Display_Mode_1
(rtb_Display_Mode_4);
/* Switch: '<S4>/Switch1' */
if (tmp > 0) {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S2>/Data Type Conversion1'
*/
rtb_Display_Mode_4 = 183U;
} else {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S3>/Data Type Conversion1'
*/
rtb_Display_Mode_4 = (uint8)rtb_Lane_Display_Mode_2;
}
/* Outport: '<Root>/Display_Mode_2' */
Rte_IWrite_highway_assistant_step_1_Pp_Display_Mode_2_DE_Display_Mode_2
(rtb_Display_Mode_4);
/* Switch: '<S4>/Switch2' */
if (tmp > 0) {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S2>/Data Type Conversion2'
*/
rtb_Display_Mode_4 = (uint8)rtb_Highway_Display_Mode_3;
} else {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S3>/Data Type Conversion2'
*/
rtb_Display_Mode_4 = (uint8)rtb_Lane_Display_Mode_3;
}
/* Outport: '<Root>/Display_Mode_3' */
Rte_IWrite_highway_assistant_step_1_Pp_Display_Mode_3_DE_Display_Mode_3
(rtb_Display_Mode_4);
/* Switch: '<S4>/Switch3' */
if (tmp > 0) {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S2>/Data Type Conversion3'
*/
rtb_Display_Mode_4 = 94U;
} else {
/* Switch: '<S4>/Switch3' incorporates:
* DataTypeConversion: '<S3>/Data Type Conversion3'
*/
rtb_Display_Mode_4 = (uint8)rtb_Lane_Display_Mode_4;
}
/* Outport: '<Root>/Display_Mode_4' */
Rte_IWrite_highway_assistant_step_1_Pp_Display_Mode_4_DE_Display_Mode_4
(rtb_Display_Mode_4);
}
/* Model initialize function */
void highway_assistant_init_1(void)
{
/* (no initialization code required) */
}
/*
* File trailer for generated code.
*
* [EOF]
*/
.h code
Highway_Assistant.h
/*
* File: Highway_Assistant.h
*
* Code generated for Simulink model 'Highway_Assistant'.
*
* Model version : 1.1
* Simulink Coder version : 9.5 (R2021a) 14-Nov-2020
* C/C++ source code generated on : Sun Oct 17 00:04:06 2021
*
* Target selection: autosar.tlc
* Embedded hardware selection: Intel->x86-64 (Windows64)
* Code generation objectives: Unspecified
* Validation result: Not run
*/
#ifndef RTW_HEADER_Highway_Assistant_h_
#define RTW_HEADER_Highway_Assistant_h_
#ifndef Highway_Assistant_COMMON_INCLUDES_
#define Highway_Assistant_COMMON_INCLUDES_
#include "rtwtypes.h"
#include "Rte_Highway_Assistant.h"
#endif /* Highway_Assistant_COMMON_INCLUDES_ */
#include "Highway_Assistant_types.h"
/* Macros for accessing real-time model data structure */
/* Block states (default storage) for system '<Root>' */
typedef struct tag_DW_Highway_Assistant_T {
uint8 is_active_c1_Highway_Assistant;/* '<S3>/Lane_Display_Unit' */
uint8 is_c1_Highway_Assistant; /* '<S3>/Lane_Display_Unit' */
uint8 is_active_c3_Highway_Assistant;/* '<S2>/Highway_Display_Unit' */
uint8 is_c3_Highway_Assistant; /* '<S2>/Highway_Display_Unit' */
} DW_Highway_Assistant_T;
/* Block states (default storage) */
extern DW_Highway_Assistant_T Highway_Assistant_DW;
/*-
* 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>' : 'Highway_Assistant'
* '<S1>' : 'Highway_Assistant/Highway_Lane_Changing_Assistance'
* '<S2>' : 'Highway_Assistant/Highway_Lane_Changing_Assistance/Requirement1'
* '<S3>' : 'Highway_Assistant/Highway_Lane_Changing_Assistance/Requirement2'
* '<S4>' : 'Highway_Assistant/Highway_Lane_Changing_Assistance/Requirement3'
* '<S5>' : 'Highway_Assistant/Highway_Lane_Changing_Assistance/Requirement1/Highway_Display_Unit'
* '<S6>' : 'Highway_Assistant/Highway_Lane_Changing_Assistance/Requirement2/Lane_Display_Unit'
*/
#endif /* RTW_HEADER_Highway_Assistant_h_ */
/*
* File trailer for generated code.
*
* [EOF]
*/
Leave a comment
Thanks for choosing to leave a comment. Please keep in mind that all the comments are moderated as per our comment policy, and your email will not be published for privacy reasons. Please leave a personal & meaningful conversation.
Other comments...
Week 7 State of charge estimation
Aim1: Simulate the 3 test cases from harness dashboard and write a detailed report on the results Solution: Battery Management System (BMS) – A battery management system is the electronic system that manages the rechargeable battery, such as by protecting the battery from operating outside its safe operating area, monitoring…
23 Nov 2021 07:00 AM IST
Project 2-Highway Assistant-Lane Changing Assistant
AIM: To develop an algorithm for one of the features of the Highway Lane Changing Assistance, create a Simulink Data Dictionary for the given signals data lists, develop a model advisor report and generate a C code for it using AUTOSAR coder in SIMULINK Objective: Model development in MATLAB Simulink as per MBD guidelines…
16 Oct 2021 06:49 PM IST
Project 1- Traffic Jam Assistant Feature
Aim: To create a Simulink Data Dictionary, develop an algorithm for one of the features of the Traffic jam Assistance and generate a C code for it using Simulink. Objective: Model Development as per the MBD guidelines Creation of Simulink Data Dictionary Code generation using Embedded Coder Generating Model Advisor Report…
13 Oct 2021 11:22 AM IST
Project 1 (Mini Project on Vehicle Direction Detection
Aim: To make a model for vehicle direction determination and making the sldd file Introduction: Identifying the direction of the vehicle is one of the important & diverse features in Autonomous driving & Advanced Driver Assistance Features. This particular sub-feature of identifying the direction of vehicle…
05 Oct 2021 07:56 AM IST
Related Courses
8 Hours of Content
Skill-Lync offers industry relevant advanced engineering courses for engineering students by partnering with industry experts.
© 2025 Skill-Lync Inc. All Rights Reserved.