Closed-loop control (PID)
0. Objective
The purpose of this lab is to get experience with PID control, discover which works best for the system (P, PI, PID, PD)
1. Prelab
In order to transmit my time v.s. duty cycle data via the BLE, I get a unique UUID D4FAA1B0-CA9E-457F-BBE3-537DC0B77EBB
by using an online UUID gnerator, and added a new characteristics called PIDstring
in my ble_arduino.ino code.
1
2
3
4
5
6
7
8
//////////// BLE UUIDs ////////////
#define BLE_UUID_PID_STRING "D4FAA1B0-CA9E-457F-BBE3-537DC0B77EBB"
//////////// Global Variables ////////////
BLECStringCharacteristic tx_characteristic_PIDstring(BLE_UUID_PID_STRING, BLERead | BLENotify, MAX_MSG_SIZE);
// Add BLE characteristics
testService.addCharacteristic(tx_characteristic_PIDstring);
Also, added a corresponding entry in connection.yaml.
1
PID_STRING: 'D4FAA1B0-CA9E-457F-BBE3-537DC0B77EBB'
Finally, add notify to retrieve data.
1
2
3
4
def receiver(stub, bytearr):
print(ble.bybtearray_to_string(bytearr))
ble.start_notify(ble.uuid["PID_STRING"], receiver)
2. Task A: Don’t Hit the Wall!!
Switched to Pololu ToF library
To get a native support, I follow the lab instructions, switched my ToF library from Sparkfun to Pololu and replaced all statements by using the Pololu library link that lab instructions provided. However, when I setup everything and ready to go, the serial monitor keeps telling me Failed to detect and initialize sensor!. After I checked our ToF chip, it is VL53L1X
, not VL53L0X, so the correct library should be this. I go over the code library and did not find setProxIntegrationTime()
function.
The code shows two ToF sensors initialization, set in long-distance mode with 50000us (50ms) timing budget and 50 ms inter-measurement period.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
#include <VL53L1X.h>
// The number of sensors in your system.
const uint8_t sensorCount = 2;
// The Arduino pin connected to the XSHUT pin of each sensor.
const uint8_t xshutPins[sensorCount] = { 8, 7 };
VL53L1X sensors[sensorCount];
void setup()
{
// Disable/reset all sensors by driving their XSHUT pins low.
for (uint8_t i = 0; i < sensorCount; i++)
{
pinMode(xshutPins[i], OUTPUT);
digitalWrite(xshutPins[i], LOW);
}
// Enable, initialize, and start each sensor, one by one.
for (uint8_t i = 0; i < sensorCount; i++)
{
// Stop driving this sensor's XSHUT low. This should allow the carrier
// board to pull it high. (We do NOT want to drive XSHUT high since it is
// not level shifted.) Then wait a bit for the sensor to start up.
pinMode(xshutPins[i], INPUT);
delay(10);
sensors[i].setTimeout(500);
if (!sensors[i].init())
{
Serial.print("Failed to detect and initialize sensor ");
Serial.println(i);
while (1);
}
// Each sensor must have its address changed to a unique value other than
// the default of 0x29 (except for the last one, which could be left at
// the default). To make it simple, we'll just count up from 0x2A.
sensors[i].setAddress(0x2A + i);
sensors[i].setDistanceMode(VL53L1X::Long);
sensors[i].setMeasurementTimingBudget(50000);
sensors[i].startContinuous(50);
}
}
void loop()
{
get_tof();
}
void get_tof()
{
sensors[0].read();
if (sensors[0].timeoutOccurred()) { Serial.print(" Front ToF TIMEOUT"); }
sensors[1].read();
if (sensors[1].timeoutOccurred()) { Serial.print(" Side ToF TIMEOUT"); }
}
PID library
There exist an Arduino PID library written by Brett Beauregard but has out of date, an enhanced version with greater accuracy than the legacy is called ArduPID by PowerBroker2.
For proportional, it is used to control the output in proportion to the error, it will react immediately to an error value and try bring the process value close to the set point. The higher the proportional gain, the faster the reaction of the controller.
Too Low: Controller reaction speed will be slow, and may not be stable.
Too High: Controller may overshoot and start oscillating.
1
2
3
4
5
kp = pIn;
curInput = *input;
curSetpoint = *setpoint;
curError = curSetpoint - curInput;
pOut = kp * curError;
For integral, it will continue to accumulate over time until the set point is reached. The longer it takes to reach the setpoint, the more the integral influences the output.
Too Low: Controller may neverreach the setpoint and may be slow.
Too High: Controller may overshoot and start oscillating.
1
2
3
4
5
6
7
8
9
ki = iIn * (timer.timeDiff / 1000.0);
lastError = curError;
curInput = *input;
curSetpoint = *setpoint;
curError = curSetpoint - curInput;
iOut += (ki * ((curError + lastError) / 2.0)); // Trapezoidal integration
iOut = constrain(iOut, windupMin, windupMax); // Prevent integral windup
For derivative, it looks at the ramp rate or how fast the process value is reaching the setpoint, and limits the output to prevent overshooting.
Too Low: Controller may react normally, but no means of limiting overshoot.
Too High: Controller may be unstable, and have undesired reaction to distortion on the actual value.
To prevent the derivatie kick issue, instead of adding (Kd * derivative of Error), I subtract (Kd * derivative of Input). This is known as using “Derivative on Measurement”.
1
2
3
4
5
6
kd = dIn / (timer.timeDiff / 1000.0);
lastInput = curInput;
double dInput = *input - lastInput;
dOut = -kd * dInput; // Derrivative on measurement
Below code shows the combined implementation of the PID calculation.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
kp = pIn;
ki = iIn * (timer.timeDiff / 1000.0);
kd = dIn / (timer.timeDiff / 1000.0);
if (direction == BACKWARD)
{
kp *= -1;
ki *= -1;
kd *= -1;
}
lastInput = curInput;
lastSetpoint = curSetpoint;
lastError = curError;
curInput = *input;
curSetpoint = *setpoint;
curError = curSetpoint - curInput;
double dInput = *input - lastInput;
if (pOnType == P_ON_E)
pOut = kp * curError;
else if (pOnType == P_ON_M)
pOut = -kp * dInput;
iOut += (ki * ((curError + lastError) / 2.0)); // Trapezoidal integration
iOut = constrain(iOut, windupMin, windupMax); // Prevent integral windup
dOut = -kd * dInput; // Derrivative on measurement
double newOutput = bias + pOut + iOut + dOut;
newOutput = constrain(newOutput, outputMin, outputMax);
*output = newOutput;
PID Tuning
Starting with P = 0.01, I = 0, D = 0
and have a setpoint = 300
. Since I have my deadband set to 35
, the maximum duty cycle should be 225 - 35 = 220
. To differentiate forward and backward, the duty cycle can be negative to represent backward, therefore setOutputLimits(-220, 220)
. The last setup is add setWindUpLimits(-10, 10)
using the default value 10 to prevent integral wind-up. In the loop part, capture the ToF reading and feeds into PID input.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
#include "ArduPID.h"
ArduPID myController;
double input;
double output;
double setpoint = 300;
double p = 0.01;
double i = 0;
double d = 0;
void setup()
{
myController.begin(&input, &output, &setpoint, p, i, d);
myController.reverse(); // Uncomment if controller output is "reversed"
myController.setOutputLimits(-220, 220);
myController.setBias(0); // Bias
myController.setWindUpLimits(-10, 10); // Groth bounds for the integral term to prevent integral wind-up
myController.start();
}
void loop()
{
get_tof();
}
void get_tof()
{
sensors[0].read();
if (sensors[0].timeoutOccurred()) { Serial.print(" Front ToF TIMEOUT"); }
int distance = sensors[0].ranging_data.range_mm;
input = distance; // Send data to PID input
myController.compute(); // Calculate PID
// Deadband settings
if(output > 0)
output += 35;
else if(output < 0)
output -= 35;
Serial.print(distance);
Serial.print(", ");
Serial.print(output);
Serial.print("\n");
}
I tested P-value starting from 0.01 up to 0.5, and I found P = 0.1
is the one that can let the car reaches full duty cycle with a tiny oscillation. Then I start turning D from 1 up to 20, and found D = 18
is the best choice.
P = 0.1, I = 0, D = 18
, able to reach the setpoint without collisions.
Video Demo
P = 0.01, I = 0, D = 0
, able to reach the setpoint without collisions, but too slow.
Video Demo
P = 0.1, I = 0, D = 10
, fast but overshoot.
Video Demo
P = 0.1, I = 0, D = 1
, hit the wall.
Video Demo
The reason I choose to do PD control without integral is because when I add the integral, it becomes very hard to tune and control. Use proportional as the main factor to control the speed, then by adjusting the derivative to eliminate overshooting. During the expirements, I found it is hard to let the car stop exactly 300mm away from the wall, even there is a 1mm offset, will trigger the deadband and let motors screaming, in the future I would add a tolerance on it. Also, the sampling rate is limited by ToF ranging frequency, which is 100ms/sample, if the car goes in full speed, may need a high sampling rate, otherwise it is too late to tap on the break paddle.