Project 2 Adaptive Cruise Control

Main Project – Adaptive Cruise Control (ACC):

• Adaptive cruise control feature maintains the speed set by the driver. If the system spots a slower vehicle within its detection range, it gently reduces speed by releasing the accelerator or actively engaging the brake control system. If the vehicle ahead speeds up or changes lanes, the cruise control automatically accelerates to the driver’s desired speed.

Objective:

To create an model whicj meets the requirment asked in the question.

Procedure:

1) creation of SLDD file with given parameter list :

Signals & Calibration Data List:

Signal / Calibration Name	Signal Type	Data Type	Dimension	Min	Max	Initial Value	Units
CameraInput_LeadVehicle	Input	Uint8	1	0	255	-	-
RadarInput_LeadVehicle	Input	Uint8	1	0	255	-	-
CameraInput_DriveVehicle	Input	Uint8	1	0	255	-	-
RadarInput_DriveVehicle	Input	Uint8	1	0	255	-	-
Time_Gap	Input	Uint8	1	0	255	-	-
Set_Speed	Input	Uint8	1	0	255	-	-
Set_Gap	Input	Uint8	1	0	255	-	-
CruiseSwitch	Input	Boolean	1	0	1	-	-
SetSwitch	Input	Boolean	1	0	1	-	-
Acceleration_Mode	Output	Uint8	1	0	255	-	-
LeadVehicle_Speed	Output	Uint8	1	0	255	-	-
DriveVehicle_Speed	Output	Uint8	1	0	255	-	-
LeadVehicle_Detected	Output	Uint8	1	0	255	-	-

With the above data lists we created an SLDD file for the model that we will create in the following steps.

after creating the SLDD file we have to edit the solver setting as per the requirement asked above.

2)Solver Setting:

As they asked in the Question we have to select support Floating-point numbers as shown in the above figure.then asusal we have to select solver as fixed and discrete and with sample time of 0.01sec.

after this we have to create our model as per the requirements.

3)Model Creation:

Main subsystem:

Requirement 1– Lead Vehicle:

• Lead Vehicle is a vehicle which is driving in the road ahead of our drive vehicle. Two input signals (Signal Name: CameraInput_LeadVehicle & RadarInput_LeadVehicle).
• Ideally sensor fusion techniques will be deployed to process & analyze data from camera & radar. For complexity reasons, let’s not adapt to any such algorithms.
• We can simply add both the radar & camera inputs & the corresponding output is read as Speed profile output (Signal Name: LeadVehicle_Speed).
• Speed data of the lead vehicle is critical in implementing the Adaptive Cruise Control algorithm.

As per the requirement we created our Lead vehicle subsystem as below

Subsystem:

Under lead vehicle Subsystem:

Requirement 2 – Drive Vehicle:

• Drive Vehicle is the vehicle driven by the user & this is the vehicle which has ACC algorithm in it.
• Like the Lead Vehicle, Drive Vehicle algorithm also has 2 input signals (Signal Name: CameraInput_DriveVehicle, RadarInput_DriveVehicle) & one signal coming as an Input to this subsystem (Signal Name: Acceleration_Mode) – three inputs into this requirement in total.
• Like the above requirement, sensor fusion techniques will also be deployed here, for complexity reasons we are ignoring them.
• Two output signals come from this subsystem (Signal Name: DriveVehicle_Speed & LeadVehicle_Detected).
• Signal DriveVehicle_Speed is summation of three input signals mentioned above & LeadVehicle_Detected is renamed from Input Signal RadarInput_DriveVehicle by mere use of Signal Conversion block.

created our next subsystem as Drive Vehicle as per the above requirement.

We used signal copy block to copy the signal with same parameter and values but we have to resolve it as another signal as Leadvehicle_detected. from this subsystem there will be two outputs.

Requirement 3 – Adaptive Cruise Control Algorithm:

• Adaptive Cruise Control feature has 3 major modes of operation: OFF Mode, STANDBY Mode & ON Mode. This particular requirement has to be implemented as state machine logic in Simulink.
• The input signals to this state machine system are (Signal Name: Time_Gap, Set_Speed, Set_Gap, CruiseSwitch, SetSwitch).
• Also, the output signals (Signal Name: DriveVehicle_Speed & LeadVehicle_Detected) from requirement-2 is fed back as an input signal into this state machine block.
• Additionally, output signal (Signal Name: LeadVehicle_Speed) from requirement-1 is given as an input signal to this state machine block as well.
• Output from this subsystem is a signal (Signal Name: Acceleration_Mode) which governs the vehicular speed of the drive vehicle which automatically adjusts its speed & velocity to match the lead vehicle.

inside this Adaptive cruise control Algorithm we have to create an stateflow chart with following requirements.

this is the over all chart image as shown below.we will see creation of all states with its requirement.

Requirement 3a – ACC OFF MODE state logic:

• This is the default state inside state machine logic. Output signal Acceleration_Mode is at value 0 in this state.
• This state is governed by input signal CruiseSwitch.
• If CruiseSwitch is equal to 1, state ACC STANDBY mode will get activated. If CruiseSwitch is equal to 0, state ACC OFF mode will get activated, from either ACC ON mode or ACC STANDBY mode

Requirement 3b – ACC STANDBY MODE state logic:

• This is the second activated state inside state machine logic. Output signal Acceleration_Mode is at value 1 in this state.
• This state is governed by both input signals CruiseSwitch & SetSwitch.
• If CruiseSwitch is equal to 1, state ACC STANDBY mode will get activated. If CruiseSwitch is equal to 0, state ACC OFF mode will get activated, from either ACC ON mode or ACC STANDBY mode
• If SetSwitch is equal to 1, state ACC ON mode will get activated. If SetSwitch is equal to 0, state ACC STANDBY mode will get activated.

Requirement 3c – ACC ON MODE state logic:

This state will be activated when input signal SetSwitch is equal to 1. There are 6 sub states to this state logic: They are:

• LeadVehicle_Detected_Follow (Default)
• LeadVehicle_Not_Detected
• LeadVehicle_Detected_Resume
• LeadVehicle_Not_Detected_Resume
• LeadVehicle_Speed_lessthan_Set_Speed
• LeadVehicle_Speed_equal_Set_Speed

Requirement 3c (i) – LeadVehicle_Detected_Follow (ACC ON MODE):

• This is the default sub state inside ACC ON MODE state. Output signal Acceleration_Mode is equal to 2.
• Condition to transit from LeadVehicle_Detected_Follow to LeadVehicle_Not_Detected; Input signal condition LeadVehicle_Detected == 0.
• Condition to transit from LeadVehicle_Detected_Follow to LeadVehicle_Speed_lessthan_Set_Speed; Input Signals condition (LeadVehicle_Detected == 1) && (LeadVehicle_Speed < Set_Speed) || (Time_Gap < Set_Gap).
• 

Requirement 3c (ii) – LeadVehicle_Not_Detected (ACC ON MODE):

• Output signal Acceleration_Mode is equal to 1.
• Condition to transit from LeadVehicle_Not_Detected to LeadVehicle_Detected_Follow; Input signals condition [(LeadVehicle_Detected==1) && (DriveVehicle_Speed == Set_Speed) && (LeadVehicle_Speed >= Set_Speed) && (Time_Gap >= Set_Gap)]
• Condition to transit from LeadVehicle_Not_Detected to LeadVehicle_Speed_lessthan_Set_Speed; Input signals condition [(LeadVehicle_Detected == 1) && (LeadVehicle_Speed < Set_Speed) || (Time_Gap < Set_Gap)]

• 

Requirement 3c (iii) – LeadVehicle_Detected_Resume (ACC ON MODE):

• Output signal Acceleration_Mode is equal to 3.
• Condition to transit from LeadVehicle_Detected_Resume to LeadVehicle_Detected_Follow; Input signals condition [(DriveVehicle_Speed == Set_Speed) && (LeadVehicle_Speed >= Set_Speed) && (Time_Gap >= Set_Gap)]
• Condition to transit from LeadVehicle_Detected_Resume to LeadVehicle_Not_Detected_Resume; Input signal condition LeadVehicle_Detected==0.
• Condition to transit from LeadVehicle_Detected_Resume to LeadVehicle_Speed_equal_Set_Speed; Input Signal condition [(DriveVehicle_Speed < Set_Speed) && (LeadVehicle_Speed > DriveVehicle_Speed) && (Time_Gap >= Set_Gap)]
• 

Requirement 3c (iv) - LeadVehicle_Not_Detected_Resume (ACC ON MODE):

• Output signal Acceleration_Mode is equal to 1.

Requirement 3c (v) - LeadVehicle_Speed_lessthan_Set_Speed (ACC ON MODE):

• Output signal Acceleration_Mode is equal to 4.
• Condition to transit from LeadVehicle_Speed_lessthan_Set_Speed to LeadVehicle_Not_Detected; Input signal condition [(LeadVehicle_Detected == 0) && (DriveVehicle_Speed == Set_Speed)]
• Condition to transit from LeadVehicle_Speed_lessthan_Set_Speed to LeadVehicle_Speed_equal_Set_Speed; Input signals condition [((LeadVehicle_Speed*1.25>=DriveVehicle_Speed) && (LeadVehicle_Speed * 0.75<=DriveVehicle_Speed)) && (DriveVehicle_Speed < Set_Speed) && ((Time_Gap<=1.25*Set_Gap) && (Time_Gap >=0.75*Set_Gap))]

Requirement 3c (vi) - LeadVehicle_Speed_equal_Set_Speed (ACC ON MODE):

• Output signal Acceleration_Mode is equal to 5.
• Condition to transit from LeadVehicle_Speed_equal_Set_Speed to LeadVehicle_Not_Detected_Resume; Input signal conditions is [(LeadVehicle_Detected == 0) || (DriveVehicle_Speed <= Set_Speed)]
• Condition to transit from LeadVehicle_Speed_equal_Set_Speed to LeadVehicle_Detected_Resume; Input signal conditions [(DriveVehicle_Speed < Set_Speed) && (LeadVehicle_Speed > DriveVehicle_Speed) || (Time_Gap >= Set_Gap)]
• Condition to transit from LeadVehicle_Speed_equal_Set_Speed to LeadVehicle_Speed_lessthan_Set_Speed; Input signals conditions [(LeadVehicle_Speed

After all this creation of this stateflow chart we have to define the variables using symbols pane.

we have to select all variables as input other than the Acceleration_mode which is an output.

after this creation of this stateflow chart we have our model in our hand to generate the code. but, before that we have to connect the Acceleration_mode output from this subsystem to the DriveVehicle Subsystem with an unit delay block as shown in the figure . this unit delay block is used to transmit the signal with an delay of mentioned sample time 0.01 sec compared to all other signals in this model.

Requirement Tagging: To do the requirement tagging select the heading of the particular word file in MS Word and go to the subsytem , where we need to tag the requirement and do the below procedure as shown in the figure,

So whenever user using the subsytem by right clicking to the subsytem we can read the required tagging given, For this we have to save the word file in same folder to resolve the signal,

After resloving the signal it will show in Blue indication,

To propogate the signal

MODEL ADVISOR CHECK:

Here we reduce the error of 1 fail system and 29 warnings to 18 warnings as shown below

Model Advisor check is done to rectify the errors as well as to ensure the model is following MAB guidelines.
The system target file of code generation is changed to embedded coder.
After model advisor check, the code for the model is developed.

This is generated by selecting the APPS---->embedded coder---->Build, and by this the C-code folder will be formed in the same
folder.
Also, the data containing code is stored in the file where the model is located as _ert_rtw file.

CONCLUSION

• MATLAB model has been developed as per the requirement
• Variables are stored in the data dictionary(.SLDD File).
• Chart is designed as per the given logic
• Signals are resolved and propagated.
• Model Adviser check is done and the report is obtained as per the MAAB guidelinees
• C-code is generated for the model design
• All files are uploaded with this report as an zip file.

RESULT:

Thus the requirement of the customer is fullfilled by creating an model which meets the requirements provided.