Projects:2018s1-181 BMW Autonomous Vehicle - Revision history

A1686465 at 23:58, 21 October 2018

2018-10-21T23:58:28Z

A1686465 at 11:31, 21 October 2018

2018-10-21T11:31:11Z

A1686465 at 11:10, 21 October 2018

2018-10-21T11:10:38Z

A1686465 at 11:09, 21 October 2018

2018-10-21T11:09:50Z

A1686465 at 11:08, 21 October 2018

2018-10-21T11:08:47Z

A1686465 at 11:07, 21 October 2018

2018-10-21T11:07:44Z

A1686465 at 10:39, 21 October 2018

2018-10-21T10:39:16Z

A1686465 at 10:30, 21 October 2018

2018-10-21T10:30:21Z

A1686465 at 09:54, 21 October 2018

2018-10-21T09:54:43Z

A1686465 at 09:51, 21 October 2018

2018-10-21T09:51:39Z

@@ Line 18: / Line 18: @@
 With autonomous vehicles being the future of transportation, research and development into autonomous vehicle systems are necessary to ensure passenger safety meets the required standards. This project is one in a series of autonomous driving algorithm projects by the University of Adelaide supported by BMW with the end goal to produce a fully autonomous vehicle system. This project focuses on developing an autonomous driving algorithm that will be used to adjust the steering wheel of a BMW research vehicle. A model predictive controller will be designed and developed in MATLAB and SIMULINK that will track the vehicles position and adjust the steering wheel angle such that the vehicle can follow a provided reference path.
-The Design of this controller consists of a reference path, the MPC and a vehicle model, modelling the lateral dynamics of the vehicle.
+The design of this controller consists of a reference path, the MPC and a vehicle model (modelling the lateral dynamics of the vehicle).
 ==Vehicle Model==
@@ Line 71: / Line 71: @@
 ==Conclusion==

@@ Line 1: / Line 1: @@
 ==Students==
-Corey Miller
+Corey Miller (Electrical and Sustainable Energy)
-Kaifeng Ren
+Kaifeng Ren (Electrical and Electronic)
-Muhammad Sufyaan Bin Mohd Faiz
+Muhammad Sufyaan Bin Mohd Faiz (Electrical and Electronic)
-Ovini Amaya Perera
+Ovini Amaya Perera (Electrical and Electronic)
-Yiduo Yin
+Yiduo Yin (Electrical and Electronic)
 ==Supervisors==
@@ Line 16: / Line 16: @@
 ==Project Description==
-This projects main focus is on MPC development for a steering system of the BMW autonomous vehicle. During this project, Model Predictive Controller toolbox in MATLAB Simulink will be used to develop the MPC controller which suits in our project. In addition, the vehicle model which was provided by Robert Dollinger in 2016 could not be used in Model Predictive Controller Toolbox in MATLAB due to errors.  Therefore, In the software part, a new vehicle model will be developed and a Model Predictive Controller will be developed and used in the simulation part of this project. New software call Driving Scenario Designer will also be used to develop the reference track for simulating the new vehicle model and controller.
+With autonomous vehicles being the future of transportation, research and development into autonomous vehicle systems are necessary to ensure passenger safety meets the required standards. This project is one in a series of autonomous driving algorithm projects by the University of Adelaide supported by BMW with the end goal to produce a fully autonomous vehicle system. This project focuses on developing an autonomous driving algorithm that will be used to adjust the steering wheel of a BMW research vehicle. A model predictive controller will be designed and developed in MATLAB and SIMULINK that will track the vehicles position and adjust the steering wheel angle such that the vehicle can follow a provided reference path.
 ==Vehicle Model==
@@ Line 72: / Line 64: @@
 ==Future Work==
-The MPC controller that we developed can only acquire good performance results when the speed is 18km/h. In some cases, there will be 1.5 meters oversteer on the Y position when the vehicle tries to track and approach the reference path at the beginning. Therefore, we thought this oversteer was caused by the set parameters which were not properly measured. These parameters include cornering stiffness and moment of inertia of the vehicle. Hence, as a further development, a parameter estimator may be required and developed.
+The MPC controller that was developed could only acquire satisfactory performance results when the speed is 18km/h (5m/s). In some cases, there will be approximately 1.5 meter deviation between the lateral position of the vehicle and the reference path. This deviation is a result of the vehicle model using simplified lateral vehicle dynamics. An example of how the dynamics could be improved comes from the front and rear tire forces. For small slip angles, the forces on the tire is assumed to be constant, hence the front and rear cornering stiffnesses are assumed constant. The tire forces on a vehicle are actually non-linear and hence a parameter estimator would be required to more accurately model this nonlinear vehicle dynamics. This parameter estimated could also be used as an input to the MPC along with the yaw of the vehicle to give the MPC more options in how to best optimise the steering angle output.
-Secondly, as I mentioned above that the vehicle can only perform well at 18km/h, so an adaptive MPC controller may be needed to allow the vehicle to follow the reference path at different speeds.
+As explained above, a vehicles dynamics change with increasing speed, and hence is non-linear. This means that the linear MPC designed in this project will only be accurate for a certain range of speeds. In order to improve the performance of the controller, an adaptive MPC is required. This adaptive MPC would contain multiple MPC settings for multiple speed ranges. The adaptive MPC is then able to determine which model should be implemented at any given time for a specific vehicle speed.
-By using the vehicle model, we observed that when the vehicle's velocity get close to 0, the state space model becomes unstable which is another problem that needs to be solved in the future work.
+As mentioned above, a coordinate manipulator submodule is required. This submodule would be responsible for detecting changes in the x-position and translating the coordinate system to allow the vehicle to perform U-turns.
 ==Conclusion==

@@ Line 59: / Line 59: @@
 Simulation 1 involved the vehicle performing a lane change maneuver in a double-laned road.
-[[File:Scenario1.jpg|200px|thumb|center|Scenario 1: Double lane change maneuver]]
+[[File:Scenario1.jpg|300px|thumb|center|Scenario 1: Double lane change maneuver]]
 From this simulation it can be seen that the vehicle was capable of following the reference path smoothly with minor steering angle adjustments. The maximum position deviation is approximately 1.5m, which can be improved upon with a more complex MPC and vehicle model.
-[[File:Scenario2.jpg|200px|thumb|center|Scenario 2: Intersection right turn]]
+[[File:Scenario2.jpg|300px|thumb|center|Scenario 2: Intersection right turn]]
 Scenario 2 saw the vehicle perform a right turn at a adelaide intersection. From the simulation it can be seen that the vehicle deviates from the reference path again by approximately 1.5m. As clipping isnt observed in the steering angle plot, this is not a result of the turn being too tight, but from the vehicle model and MPC not being as complex due to the simplified vehicle dynamics.
-[[File:Scenario3.jpg|200px|thumb|center|Scenario 3: Roundabout 3rd exit]]
+[[File:Scenario3.jpg|300px|thumb|center|Scenario 3: Roundabout 3rd exit]]
 Scenario 3 saw the vehicle entering and taking the 3rd exit when leaving a roundabout. This presents the biggest flaw in the current project model as the MPC cannot accomodate for changes in the longitudinal direction (changing in x-direction) such as a U-turn for example. As the mpc only tracks the lateral (y-position) of the vehicle, the vehicle begins drastically going off-course at the 3rd exit as the x-position decreases. It can also be seen that the vehicle is unable to perform such a tight turn as the steering angle is clipping its maximum range.

@@ Line 59: / Line 59: @@
 Simulation 1 involved the vehicle performing a lane change maneuver in a double-laned road.
-[[File:Scenario1.PNG|200px|thumb|center|Scenario 1: Double lane change maneuver]]
+[[File:Scenario1.jpg|200px|thumb|center|Scenario 1: Double lane change maneuver]]
 From this simulation it can be seen that the vehicle was capable of following the reference path smoothly with minor steering angle adjustments. The maximum position deviation is approximately 1.5m, which can be improved upon with a more complex MPC and vehicle model.
-[[File:Scenario2.PNG|200px|thumb|center|Scenario 2: Intersection right turn]]
+[[File:Scenario2.jpg|200px|thumb|center|Scenario 2: Intersection right turn]]
 Scenario 2 saw the vehicle perform a right turn at a adelaide intersection. From the simulation it can be seen that the vehicle deviates from the reference path again by approximately 1.5m. As clipping isnt observed in the steering angle plot, this is not a result of the turn being too tight, but from the vehicle model and MPC not being as complex due to the simplified vehicle dynamics.
-[[File:Scenario3.PNG|200px|thumb|center|Scenario 3: Roundabout 3rd exit]]
+[[File:Scenario3.jpg|200px|thumb|center|Scenario 3: Roundabout 3rd exit]]
 Scenario 3 saw the vehicle entering and taking the 3rd exit when leaving a roundabout. This presents the biggest flaw in the current project model as the MPC cannot accomodate for changes in the longitudinal direction (changing in x-direction) such as a U-turn for example. As the mpc only tracks the lateral (y-position) of the vehicle, the vehicle begins drastically going off-course at the 3rd exit as the x-position decreases. It can also be seen that the vehicle is unable to perform such a tight turn as the steering angle is clipping its maximum range.

@@ Line 58: / Line 58: @@
 To test the performance of the MPC and vehicle model, the system was placed into 3 different scenarios that simulated real world traffic conditions. These scenarios were designed using Driving Scenario Designer MATLAB Application. All simulations were performed with a constant longitudinal velocity of 5m/s.
 Simulation 1 involved the vehicle performing a lane change maneuver in a double-laned road.
 [[File:Scenario1.PNG|200px|thumb|center|Scenario 1: Double lane change maneuver]
 From this simulation it can be seen that the vehicle was capable of following the reference path smoothly with minor steering angle adjustments. The maximum position deviation is approximately 1.5m, which can be improved upon with a more complex MPC and vehicle model.
 [[File:Scenario2.PNG|200px|thumb|center|Scenario 2: Intersection right turn
 Scenario 2 saw the vehicle perform a right turn at a adelaide intersection. From the simulation it can be seen that the vehicle deviates from the reference path again by approximately 1.5m. As clipping isnt observed in the steering angle plot, this is not a result of the turn being too tight, but from the vehicle model and MPC not being as complex due to the simplified vehicle dynamics.
 [[File:Scenario3.PNG|200px|thumb|center|Scenario 3: Roundabout 3rd exit
 Scenario 3 saw the vehicle entering and taking the 3rd exit when leaving a roundabout. This presents the biggest flaw in the current project model as the MPC cannot accomodate for changes in the longitudinal direction (changing in x-direction) such as a U-turn for example. As the mpc only tracks the lateral (y-position) of the vehicle, the vehicle begins drastically going off-course at the 3rd exit as the x-position decreases. It can also be seen that the vehicle is unable to perform such a tight turn as the steering angle is clipping its maximum range.

@@ Line 53: / Line 53: @@
 The model predictive controller subsystem takes the lateral position of the vehicle model as an input and compares it against the reference path's lateral position of where the vehicle be. Based off the deviation from where the vehicle is and where it should be, the MPC adjusts the steering wheel angle of the vehicle, turning the wheels to head the vehicle to follow the reference path. What makes model predictive control able to control a vehicle to follow reference path more accurately than other control strategies is its ability to "predict the future". During each timestep (in this projects case 20ms) the lateral position deviation problem is optimized over finite set of timesteps. This is known as the prediction horizon - how far the MPC sees into the future. For each of these future timesteps, the MPC calculates the required steering angle to optimize the deviation problem. The MPC then only executes finite range of these timestep steering angle commands. This is known as the control horizon - how long the MPC executes 1 optimization problem. The reason a control horizon does not execute all the prediction horizon estimated steering angles is that a contingency may occur (such as an object entering the vehicles path) that the optimization problem did not account for. Therefore at each timestep, a new optimization problem is solved with only the first few steps being sent to the steering wheel.
-When designing the MPC submodule, a prediction horizon of 20 samples (0.4 seconds into the future) was used as it provided the MPC a clear understanding of the path ahead while maintaining fast processing speed. A control horizon of 1 sample was used as the performance of the module was not improved from increasing the control horizon.
+When designing the MPC submodule in MPC toolbox in MATLAB, a prediction horizon of 20 samples (0.4 seconds into the future) was used as it provided the MPC a clear understanding of the path ahead while maintaining fast processing speed. A control horizon of 1 sample was used as the performance of the module was not improved from increasing the control horizon.
 For passenger comfort, constraints were set on the steering angle output of the MPC that was being sent to the vehicle. This constraints included reducing how far the steering angle could turn from -25 degrees to +25 degrees, allowing for wide turns. The rate of how quickly the steering wheel turn was also constrained to 25 degrees per second, allowing for a smooth transition into a turn without the steering wheel rapidly changing the direction of the vehicle.
@@ Line 59: / Line 59: @@
 [[File:MPC.PNG|400px|thumb|center|Developed Simulink MPC Model]]
 ==Simulation Results==
+To test the performance of the MPC and vehicle model, the system was placed into 3 different scenarios that simulated real world traffic conditions. These scenarios were designed using Driving Scenario Designer MATLAB Application. Simulation 1 involved the vehicle performing a lane change maneuver in a double-laned road.
+[[File:Scenario1.PNG|200px|thumb|center|Developed Simulink MPC Model]]

← Older revision		Revision as of 10:30, 21 October 2018
Line 50:		Line 50:
	The developed simulink vehicle model based off this state space model can be broken into 3 seperate sections. Section 1 takes all the relevant parameters from the matlab script file and loads them into the model to be used. Section 2 calculates the state vector and Section 3 uses the parameters inside the state vector to calculate the longitudinal and lateral position of the vehicle.		The developed simulink vehicle model based off this state space model can be broken into 3 seperate sections. Section 1 takes all the relevant parameters from the matlab script file and loads them into the model to be used. Section 2 calculates the state vector and Section 3 uses the parameters inside the state vector to calculate the longitudinal and lateral position of the vehicle.

		+	==Model Predictive Controller==
		+	The model predictive controller subsystem takes the lateral position of the vehicle model as an input and compares it against the reference path's lateral position of where the vehicle be. Based off the deviation from where the vehicle is and where it should be, the MPC adjusts the steering wheel angle of the vehicle, turning the wheels to head the vehicle to follow the reference path. What makes model predictive control able to control a vehicle to follow reference path more accurately than other control strategies is its ability to "predict the future". During each timestep (in this projects case 20ms) the lateral position deviation problem is optimized over finite set of timesteps. This is known as the prediction horizon - how far the MPC sees into the future. For each of these future timesteps, the MPC calculates the required steering angle to optimize the deviation problem. The MPC then only executes finite range of these timestep steering angle commands. This is known as the control horizon - how long the MPC executes 1 optimization problem. The reason a control horizon does not execute all the prediction horizon estimated steering angles is that a contingency may occur (such as an object entering the vehicles path) that the optimization problem did not account for. Therefore at each timestep, a new optimization problem is solved with only the first few steps being sent to the steering wheel.
		+
		+	When designing the MPC submodule, a prediction horizon of 20 samples (0.4 seconds into the future) was used as it provided the MPC a clear understanding of the path ahead while maintaining fast processing speed. A control horizon of 1 sample was used as the performance of the module was not improved from increasing the control horizon.
		+	For passenger comfort, constraints were set on the steering angle output of the MPC that was being sent to the vehicle. This constraints included reducing how far the steering angle could turn from -25 degrees to +25 degrees, allowing for wide turns. The rate of how quickly the steering wheel turn was also constrained to 25 degrees per second, allowing for a smooth transition into a turn without the steering wheel rapidly changing the direction of the vehicle.
		+
		+	The diagram belows shows the fully connected MPC system with an input longitudinal velocity and reference path (consisting of a lateral position at each timestep) and outputting the lateral position and steering angle of the vehicle.
		+
		+	[[File:MPC.PNG\|400px\|thumb\|center\|Developed Simulink MPC Model]]

← Older revision		Revision as of 09:54, 21 October 2018
Line 48:		Line 48:
	[[File:VM.PNG\|400px\|thumb\|center\|Developed Simulink vehicle model based off the above state space representation]]		[[File:VM.PNG\|400px\|thumb\|center\|Developed Simulink vehicle model based off the above state space representation]]

−		+	The developed simulink vehicle model based off this state space model can be broken into 3 seperate sections. Section 1 takes all the relevant parameters from the matlab script file and loads them into the model to be used. Section 2 calculates the state vector and Section 3 uses the parameters inside the state vector to calculate the longitudinal and lateral position of the vehicle.
−
−	~~== First Level System Design'==~~
−
−
−	~~==MPC System Design==~~

@@ Line 34: / Line 34: @@
 ==Vehicle Model==
-[[File:BicycleModel.png|100px|thumb|right|Bicycle model to describe the lateral dynamics of a vehicle.]]
+[[File:BicycleModel.png|200px|thumb|right|Bicycle model to describe the lateral dynamics of a vehicle.]]
 The vehicle model used for the system will be summarized using state space representation: modelling the physical vehicle as a set of input, output and state variables (variables that change over time depending on the input variables at a specific instance). The benefits that state space representation has over other modelling techniques is that it allows input data from multiple sources to be used simultaneously in the same model to estimate a single dynamic vehicle parameter and provides a convenient way to analyses multiple inputs and outputs. Comparing this to the frequency domain, state-space representation is not limited to systems with linear components and zero initial conditions and is more efficient than having to write input × output number of Laplace transforms to describe the system.
-[[File:SSM.PNG|100px|thumb|right|State space model used to represent the vehicle models lateral dynamics]]
+[[File:SSM.PNG|200px|thumb|right|State space model used to represent the vehicle models lateral dynamics]]
 To model the vehicle in state space representation, a linear single-track model (also known as the bicycle model) was used to describe the lateral dynamics of the vehicle. The bicycle model simplifies the dynamics of a vehicle by taking the front and rear axles and treating them as singular wheels. This simplifies the lateral dynamics of the vehicle by reducing the degrees of freedom from having 4 wheels to 2 wheels, hence fewer equations are required to describe the vehicle model.
-[[File:Parameters.PNG|100px|thumb|right|]]
+[[File:Parameters.PNG|200px|thumb|right|]]
 The state vector used in the vehicle model consisted of the vehicle slip angle (β), yaw (ψ), yaw rate and the lateral position (y). This allowed for the calculations of the vehicles longitudinal and lateral positions and yaw at each timestep with respect to a steering angle input (𝛿).The parameters for the state space model can be seen in the calculated parameters table.
-[[File:VM.PNG|300px|thumb|center|Developed Simulink vehicle model based off the above state space representation]]
+[[File:VM.PNG|400px|thumb|center|Developed Simulink vehicle model based off the above state space representation]]