It's surprisingly difficult to drive a wheeled robot in a straight line. No two motors have exactly the same performance, and there may also be differences in the floor surface. If we want a robot to follow a more complicated trajectory or to have some indication of where it has traveled, we need to be able to measure how far each wheel has traveled, that is, how many times the left and right wheels have rotated. This is called **odometry**.

Besides the distance traveled, we also want to control the motors in such as way that the robot's movements are both accurate and smoothly executed. Regardless of whether the robot is traveling in a straight line, a gradual curve, or turning around, we want to set the left and right motors to operate at a specified speed and be able to accurately maintain that speed.

Additionally, we want to gradually change the motor speed rather than make very sudden changes. This reduces the wear and tear on the motor and gear train, and the robot's movements also appear smoother. This is called **slewing** the speed. We set a **slew rate**, which is the maximum speed at which the speed of the motor is permitted to change. You can also think of this as a maximum acceleration rate.

To do all this we can measure the speed of the motors themselves using the motor encoders, then use that to determine the difference between the intended and actual motor speeds.

It turns out that we can find such a fancy motor controller in the field of Control Engineering; it's called a **PID Controller**.

On a typical robot with a motor on the left and a motor on the right side, to go forward one motor will be going clockwise, the other motor counter-clockwise. It's entirely typical of DC brushed motors to have a difference in performance in each direction, so it's entirely typical that such a robot will not run in a straight line. So having motor encoders and a PID controller is **exactly** how one fixes this problem.

See: PID Rug Bump Challenge, Robot Chassis Dynamometer

### What is a PID Controller?#

A **Proportional–Integral–Derivative** or **PID Controller** is a general-purpose mechanism for regulating the output of any kind of system through the use of a *feedback loop*. The feedback signal provides an indication of the current output of the system and is used to alter the system so that its output matches the desired value. PID Controllers are used to control oven temperatures and in automobile cruise controls. One of its first industrial uses was as an automated steering system for ships.

What sets a PID Controller apart from simpler controllers is that it combines three types of **control terms** to quickly reach and stay at the desired system output value, minimising overcorrection and maximising stability. These three control terms are what forms its acronym: *Proportional*, *Integral*, and *Derivative*. Because of this a PID Controller is also sometimes called a *three term controller*.

### How does it work?#

A PID Controller uses two numbers, the **Set Point** (SP) or *target value* of the system, and the **Process Variable** (PV), the *output value* providing the feedback from the system. When the SP and the PV are equal the output from the algorithm is zero and no change is necessary. When there is a difference between SP and PV we consider that the controller's *error*. Our aim is to reduce that error to zero.

Term | What It Does | Considerations |
---|---|---|

Proportional Term | multiplies the error value by a fixed gain value to determine the corrective value influencing the system output (this value is described as a proportional to the output). | because a "P-only" controller is using the value of the error to generate its corrective value, it will overshoot its target, then undershoot, with smaller and smaller oscillations until the error approaches zero. Unfortunately, as the output of the system oscillates closer and closer to its target the amount of correction also approaches zero, so the controller never gets there. |

Integral Term | integrates the error value into the correction over time so that it minimises this overshoot and pushes the output towards the target value. | the amount of integral applied to the formula needs to be carefully tuned, otherwise this can create its own form of oscillation. Given this tuning is quite tricky to get right, there is generally some overshoot and therefore oscillation in a PI controller. If the PID controller is used for position control the I term is used; for a motor controller the value is set to 0 since it actually represents the position of the motor if we're sampling at a fixed rate. |

Derivative Term | projects the rate of change of the corrective value, and reduces its amount as the system nears the target. This allows the controller to move towards its Set Point as fast as possible, with as little oscillation as possible. | the Derivative Term is intended to smooth the operation of a PI Controller, but the value of the Derivative must also be tuned. If either the P or D are too high it can cause the system to oscillate. |

The more I read about PID controllers the more I found that tuning the control terms is considered something of a black art. There are a number of constants in the formula, and tweaking them is done by trial and error, in other words: guessing. I did learn one rule of thumb for a PD controller: start at three zeros, then turn up the P until it oscillates, then back off to half that value. Then do the same thing with D.

### Slew Rate#

To add another twist to a robot motor controller, as mentioned above we don't want to tell the motors to go from zero to a projected speed immediately, or from full speed to stopping suddenly, as that would both overly stress the motors and drive system, and cause the robot's movements to be very jerky, perhaps even causing it to crash. We want to gradually *slew* the value so that it changes at a maximum rate, called a **slew rate**. This is measured in some measure of motor speed per unit of time.

For example, when experimenting with a motor controller written in Python, the motor speed is set as a value between 0.0 and 1.0, where half-speed is 0.5. We might set a slew rate of 0.2 per second, meaning that it would take 5 seconds to go from a stop (0.0) to full speed (1.0).

### Conclusions#

All in all, we've now got requirements for a robot motor control that includes a Proportional Term, Integral Term, Derivative Term, and a Slew Rate.

See: PID Controller on Wikipedia

### Links#

**PID Controller**from Wikipedia (note the animation of adjusting P,I,D values in the*Manual tuning*section)**Improving the Beginner’s PID – Introduction**by Brett Beauregard**PID for Dummies****Going Straight with PID**, from RaspberryPi.org- PID Autotune by Brett Beauregard (C++)
- Build a PID Controller with Python 2019 from Onion.io
- pimotors on github, by the author of Pootle's Place blog
- RobotPID (Complete PID in Python with integral etc.)
- Robert O'Hanlan's Robot PID
- Programming PID Control (Society of Robots)
- Reading encoder Tue Apr 10, 2018 12:04 am
- pigpio example: Python Rotary Encoder
- simple-pid in Python
- ivPID in Python
- PID controller, blog post

The rest needs a lot of cleanup, titles, etc.

- https://www.microchip.com/forums/m337816.aspx
- https://github.com/MrYsLab/razmq/blob/master/razmq/encoders/encoders_pigpio.py
- https://onion.io/2bt-pid-control-python/
- https://pypi.org/project/simple-pid/ (too simple)
- http://code.activestate.com/recipes/577231-discrete-pid-controller/ (also too simple)
- https://www.oreilly.com/library/view/intelligent-iot-projects/9781787286429/26242fa7-713e-4e5d-b1dc-b5566a39d5b7.xhtml
- https://www.element14.com/community/community/raspberry-pi/blog/2019/02/12/pid-based-dc-motor-controller-project
- https://www.phidgets.com/docs21/DC_Motor_-_PID_Control
- http://robotsforroboticists.com/pid-control/
- https://www.stuffaboutcode.com/2014/10/raspberry-pi-initio-robot-driving.html
- https://github.com/martinohanlon/initio