PID

Thermal control often has a contradictory feel: temperature rises slowly at first, then overshoots near the target.

The heater is at full power, but temperature takes a long time to rise. Increasing gains makes warm-up faster, but overshoot appears near the target. Integral action removes offset, but overshoot becomes larger. Filtering makes the display smoother, but control reacts late.

This is often blamed on bad PID tuning.

The core issue is not the three gains alone. Heat transfer is slow, heat storage is significant, and feedback is often delayed.

One of the most confusing closed-loop symptoms is a small error near the target that never disappears.

A valve command changes slightly, but flow does not change. A motor receives a small output, but the shaft does not move. A servo is almost at target, but remains stuck. A stage has a tiny position error, and the controller keeps correcting, but the mechanics do not respond.

The controller is computing. The output variable is changing. The device is not moving.

With proportional control alone, many systems get close to the target but remain slightly off.

Temperature stays 1°C below the target while the environment keeps removing heat. Motor speed stays a little low because load torque is always present. Liquid level remains slightly below target because leakage or outflow requires a baseline pump flow.

That long-lasting offset is steady-state error.

Integral action is valuable because it keeps accumulating as long as error persists. It slowly pushes output higher until the system can compensate for the long-term load.

When sensor readings are noisy, the usual fix is to add filtering.

Moving averages, first-order low-pass filters, median filters, and consecutive confirmations all make curves smoother. The display looks calmer, and alarms are triggered by fewer spikes.

In closed-loop control, filtering is not free.

While filtering suppresses noise, it also makes the controller see an older state. For display, slightly old data is often acceptable. For control, late feedback can become overcorrection.

A common closed-loop failure is easy to miss: the controller computes a larger output, but the actuator cannot produce it.

The heater is already at 100% power, but temperature still does not rise. The motor drive is current-limited, but speed cannot catch up. The valve is fully open, but pressure is still low. The pump is at full speed, but the level still changes too slowly.

In code, the controller is still trying. In the physical system, the output is already at its limit.

Many closed-loop systems behave normally on the bench, then become shaky, slow, overshooting, or unstable in the field.

The gains did not change. The algorithm did not change. The actuator did not change. The difference may come from an ordinary-looking detail: the sampling period.

A controller does not observe the world continuously. An embedded device usually repeats this sequence:

read sensor
-> compute error
-> update controller
-> write actuator output
-> wait for the next period

That period decides how often the controller sees the system, how often it corrects output, how much delay exists, whether noise is amplified, and what integral and derivative action actually mean.

The frustrating part of PID tuning is not that there are three gains. It is that the same gains can behave differently on another device, another load, or another sampling period.

A thermal loop heats faster after increasing proportional gain, but starts overshooting. Integral action removes steady-state error, then makes the loop overshoot more. Filtering makes the reading smoother, but the controller reacts late. Replacing a valve, motor, or heater makes yesterday’s stable gains unusable.

When a control system first becomes closed loop, the first problem is often not “it does not move.” It is “it keeps moving back and forth.”

Temperature overshoots and undershoots. Motor speed swings around the target. Liquid level control keeps opening and closing a valve. Pressure rises too high, then falls too low. Smaller parameters make the response too slow. Larger parameters make it oscillate.

It is easy to summarize this as: the PID is not tuned well.