Two different reasons a control loop "ignores" small changes — and why mixing them up leads to the wrong fix.
Both deadband and hysteresis stop a control loop from reacting to every tiny fluctuation, and both exist to prevent excessive actuator cycling — a valve, relay, or heater chattering on and off far more often than it needs to. That's where the similarity ends. Deadband is a single, symmetric "do nothing" zone the engineer deliberately configures around one setpoint. Hysteresis is a property — often physical and inherent to a sensor or actuator — where the switching threshold itself depends on which direction the input is currently moving. One is a band around a point. The other is a loop with two different points.
Deadband is deliberately configured by the control engineer: pick a setpoint, add a tolerance range around it, and the controller simply takes no action at all while the process variable stays inside that range — normal sensor noise and small fluctuations never reach the actuator. A thermostat that ignores swings within ±0.5°F of its setpoint is using deadband. Hysteresis is a different mechanism entirely, and often isn't "configured" at all — it's frequently a physical property inherent to a sensor, relay, or actuator, where the input has to travel further in one direction than the other before the output changes state. A thermostat that turns heating ON at 68°F but doesn't turn OFF again until 70°F is using hysteresis: the ON threshold and the OFF threshold are two different values, not one band, and which one applies depends entirely on whether temperature is currently rising or falling. Both prevent rapid on/off cycling right at a single crossing point — they just do it with fundamentally different logic.
False — they're genuinely different mechanisms that happen to produce a similar-looking result (less switching). Deadband is a single insensitive zone around one setpoint, symmetric in both directions — it doesn't care whether the value is rising or falling, only whether it's inside or outside the band. Hysteresis specifically means two different switching thresholds depending on the direction of travel — there is no single band the value can sit inside; instead there's a loop, and which threshold matters depends on where the input came from. A system can have one, the other, both, or neither.Confusing the two in troubleshooting has a real cost: adjusting a controller's configured "deadband" setting when the actual chattering cause is a sensor's physical hysteresis (or vice versa) changes the wrong parameter, and the chattering the technician was trying to fix often doesn't improve at all.
Explains the real difference between deadband (a single, deliberately-configured no-action zone around one setpoint) and hysteresis (a property, often physical, where the switching threshold depends on the direction the input is moving) — using a side-by-side comparison of a deadband trace held inside a symmetric band and a classic rising/falling hysteresis loop.
Deadband is a range around a setpoint — typically symmetric — within which the controller takes no corrective action whatsoever. It is a parameter the control engineer chooses explicitly, precisely to prevent an actuator from responding to every trivial fluctuation or sensor noise around setpoint. A thermostat configured to ignore swings within ±0.5°F of its setpoint, or a level controller that only acts once the tank level is more than 2% away from target, is using deadband: one setpoint, one band, symmetric in both directions.
Hysteresis describes a system whose response depends on which direction the input is currently traveling — the threshold that triggers a change when the input is rising is different from the threshold that triggers a change when it is falling. This is frequently a physical characteristic inherent to a sensor, relay, or mechanical actuator (contact bounce, magnetic hysteresis in a relay coil, mechanical backlash), though it is sometimes deliberately added in software for the same anti-chatter reason as deadband. The classic example: a thermostat that turns heating ON at 68°F (falling) but does not turn it OFF again until the temperature rises all the way to 70°F — two distinct thresholds, not one band, with the switching logic and result plotted as a rectangular loop (input value on one axis, output state on the other) that gives the phenomenon its name.
Both mechanisms reduce excessive switching/chattering, which is why they get lumped together informally. But they are configured, diagnosed, and fixed differently. Deadband is a single tunable parameter in the controller — widen it, and the system tolerates larger swings before reacting at all. Hysteresis is about the gap between two separate thresholds — it can come from the controller's own logic, but just as often it is a property of a specific sensor or relay that the controller software has no setting for. In field troubleshooting, mistaking one for the other is a common and costly error: widening a controller's configured deadband does nothing to fix chattering that is actually being caused by a sensor's physical hysteresis characteristic (or a worn relay with excessive contact bounce), and the technician ends up changing the wrong parameter while the real cause goes untouched.
Yes. A controller can be explicitly configured with a deadband around its setpoint while the sensor or output relay it uses also exhibits its own physical hysteresis. The two effects stack — the loop won't react within the deadband, and even once outside it, the relay or sensor may still apply its own direction-dependent threshold before actually switching.
No. Some hysteresis is deliberately designed in (as with the two-threshold thermostat) precisely because it prevents rapid on/off cycling that would otherwise wear out contacts, valves, or motors. Problems arise when hysteresis is unexpectedly large, inconsistent, or undocumented — for example, a relay that has degraded and now has far more contact bounce/hysteresis than it did when new, causing erratic switching that wasn't part of the original design.
Deadband applies to both. In on/off control it means the actuator doesn't switch at all inside the band. In a PID loop, a deadband is sometimes applied around the error signal itself — the controller's output stops changing when error falls inside the deadband, even though the underlying PID math is still running, specifically to stop the output from chasing noise once the process is "close enough" to setpoint.
Check the controller's configuration first — if no deadband is configured (or it's set very narrow) and the process variable is noisy right at setpoint, that's a deadband fix (widen the band). If a deadband is already configured and reasonably sized but the actuator is still chattering, look at the sensor or relay itself: a sensor with a large or drifting response, or an aging relay/contactor, is a hysteresis-related hardware issue that a deadband setting can't correct.
Yes, in common usage. Thermostat "differential" or "swing" settings that specify separate turn-on and turn-off temperatures are describing configured hysteresis — the same concept, just using HVAC industry terminology rather than the general controls-engineering term.
Try our SCADA Studio
More calculators, simulators, and guides for this discipline.