Project 2 Adaptive Cruise Control

Adaptive Cruise Control:

Objective of Main Project:

1. Developing Adaptive Cruise Control feature as per the Requirement Document using MATLAB Simulink.
2. Follow all the MBD related processes: Requirement Tagging & Traceability, SLDD creation, Configuration Parameter changes, Model Advisor check & Code Generation.
3. In Configuration Parameters: enable “Support Floating Numbers” under Code Generation settings.
4. Use Embedded Coder to generate the code.
5. If choosing code generation, Storage class for Input signals: ImportedExtern; Storage class for Output signal: Export to File; Storage class for local signals: localizable; Storage class for calibration signals: Const.
6. Choose sample time for all signals as 0.01s

Step1:

Create a sldd file according to the data given in question.

modeling > link to data dictionary > new( create new sldd file)

then access the sldd file from modeling> model explorer>Adaptive_cruise_control> expand external data> design data( input signal and parameters there)

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

Step2:

DEVELOPMENT OF ADAPTIVE CRUISE CONTROL SIMULINK MODEL:

Adaptive_Cruise_Control_Mode subsystem consist of three requirement subsystems,
Lead vehicle subsystem(Requirement_1),Drive vehicle subsystem(Requirement_2) & Adaptive Cruise Control subsystem(Requirement_3).

Step3:

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.

Step4:

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.

Step5:

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.

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

Symbol pane:

Step6:

The next step is solve signals and propagate them.

for signal resolve : select signal>right click signal > properties >signal name >check signal name
must resolve to simulink object>ok

Step7:

propogation of signal

select signal>right click signal > properties > check show propogated signals >ok

Step8:

Tagging of the system

select Lead_Vehicle(Requirement_1) subsystem right-clicks> requirements > link to selection in word

then
word file and information will be open of that subsystem. if we click on it

THIS SHOWS TAGGING IS DONE

same do for remaining Drive vehicle subsystem(Requirement_2) & Adaptive Cruise Control subsystem(Requirement_3).

Drive vehicle subsystem(Requirement_2) Tagging:

Adaptive Cruise Control subsystem(Requirement_3) Tagging:

Step9:

Now from model setting> solver configuration> type-fixed-step >solver- discrete solver>stepsize= 0.01seconds.

for code generatin

code generation>system target file >ert.tlc embedded codder.

Step10:

got to model advisor check>by task>ony check modelling standards with MAB>Run selected checks

Step11:

generate model advisor report

Report:

Step12:

generate code for model:

apps> embedded coder>generate code

Generated code

/* Model step function */
void Adaptive_Cruise_Control_step(void)
{
  uint8_T DriveVehicle_Speed;
  uint8_T LeadVehicle_Speed;

  /* Sum: '/Add' incorporates:
   *  Inport: '/CameraInput_DriveVehicle'
   *  Inport: '/RadarInput_DriveVehicle'
   *  UnitDelay: '/Unit Delay'
   */
  DriveVehicle_Speed = (uint8_T)((uint32_T)(uint8_T)((uint32_T)
    Adaptive_Cruise_Control_U.CameraInput_DriveVehicle +
    Adaptive_Cruise_Control_DW.UnitDelay_DSTATE) +
    Adaptive_Cruise_Control_U.RadarInput_DriveVehicle);

  /* Sum: '/Add' incorporates:
   *  Inport: '/CameraInput_LeadVehicle'
   *  Inport: '/RadarInput_LeadVehicle'
   */
  LeadVehicle_Speed = (uint8_T)((uint32_T)
    Adaptive_Cruise_Control_U.CameraInput_LeadVehicle +
    Adaptive_Cruise_Control_U.RadarInput_LeadVehicle);

  /* Chart: '/ACCLogic' incorporates:
   *  Inport: '/CruiseSwitch'
   *  Inport: '/SetSwitch'
   */
  if (Adaptive_Cruise_Control_DW.is_active_c3_Adaptive_Cruise_Co == 0U) {
    Adaptive_Cruise_Control_DW.is_active_c3_Adaptive_Cruise_Co = 1U;
    Adaptive_Cruise_Control_DW.is_c3_Adaptive_Cruise_Control =
      Adaptive_Cruise_IN_Acc_Off_Mode;

    /* Outport: '/Acceleration_Mode' */
    Adaptive_Cruise_Control_Y.Acceleration_Mode = 0U;
  } else {
    switch (Adaptive_Cruise_Control_DW.is_c3_Adaptive_Cruise_Control) {
     case Adaptive_Cruise_IN_Acc_Off_Mode:
      /* Outport: '/Acceleration_Mode' */
      Adaptive_Cruise_Control_Y.Acceleration_Mode = 0U;
      if (Adaptive_Cruise_Control_U.CruiseSwitch) {
        Adaptive_Cruise_Control_DW.is_c3_Adaptive_Cruise_Control =
          Adaptive_Cr_IN_Acc_Standby_mode;

        /* Outport: '/Acceleration_Mode' */
        Adaptive_Cruise_Control_Y.Acceleration_Mode = 1U;
      }
      break;

     case Adaptive_Cruise__IN_Acc_On_mode:
      Adaptive_Cruise_Con_Acc_On_mode(&DriveVehicle_Speed, &LeadVehicle_Speed);
      break;

     default:
      /* Outport: '/Acceleration_Mode' */
      /* case IN_Acc_Standby_mode: */
      Adaptive_Cruise_Control_Y.Acceleration_Mode = 1U;
      if (!Adaptive_Cruise_Control_U.CruiseSwitch) {
        Adaptive_Cruise_Control_DW.is_c3_Adaptive_Cruise_Control =
          Adaptive_Cruise_IN_Acc_Off_Mode;

        /* Outport: '/Acceleration_Mode' */
        Adaptive_Cruise_Control_Y.Acceleration_Mode = 0U;
      } else {
        if (Adaptive_Cruise_Control_U.SetSwitch) {
          Adaptive_Cruise_Control_DW.is_c3_Adaptive_Cruise_Control =
            Adaptive_Cruise__IN_Acc_On_mode;
          Adaptive_Cruise_Control_DW.is_Acc_On_mode =
            IN_LeadVehicle_Detected_Follow;

          /* Outport: '/Acceleration_Mode' */
          Adaptive_Cruise_Control_Y.Acceleration_Mode = 2U;
        }
      }
      break;
    }
  }

  /* End of Chart: '/ACCLogic' */

  /* Update for UnitDelay: '/Unit Delay' incorporates:
   *  Outport: '/Acceleration_Mode'
   */
  Adaptive_Cruise_Control_DW.UnitDelay_DSTATE =
    Adaptive_Cruise_Control_Y.Acceleration_Mode;
}

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

/* Model terminate function */
void Adaptive_Cruise_Control_terminate(void)
{
  /* (no terminate code required) */
}

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

CONCLUSION:

Hence we Developed Adaptive Cruise Control feature as per the Requirement Document using MATLAB Simulink

Note:The model file,Requirement tagging file,SLDD file,.c and .h file,Model advisor report were attached below.