Deadband is a deliberately quiet zone in a control or alarm system - a range of values within which a small change produces no action at all. Far from being a flaw, it is a design tool that stops valves from hunting, keeps relays from chattering, and silences nuisance alarms. This guide explains what deadband is, the different places it appears, and how it relates to hysteresis.
Deadband in one line: Deadband is a range around a target value or threshold within which changes in the input produce no change in the output - used to prevent constant switching, valve hunting, and repeated nuisance alarms caused by small fluctuations or noise.
On/off control: A tank level controller might start a pump at 80% and stop it at 60%. The 20-point gap is the deadband; without it, a pump sitting right at a single switching level would rapidly cycle on and off as the level jittered, wearing out the pump and its starter. Control valves: Deadband allows the controller to ignore tiny errors so the valve does not constantly reposition (hunt) in response to signal noise, saving wear on the actuator and packing.
Alarms: Alarm deadband keeps an alarm from clearing and re-triggering as the process variable hovers around the alarm limit. If a high-pressure alarm trips at 50 psi, a deadband of 2 psi means it will not clear until pressure drops below 48 psi - preventing a storm of alarm and return-to-normal messages. Reporting by exception: SCADA and RTUs use a deadband so a value is only transmitted when it changes by more than a set amount, cutting needless traffic on cellular and radio links.
The two terms overlap and are often used interchangeably, but there is a shade of difference. Deadband generally describes a band of no response around a value. Hysteresis specifically describes when the switching point depends on the direction of travel - the point where something turns on differs from the point where it turns off. The pump example above is technically hysteresis: on at 80%, off at 60%.
In everyday plant language, engineers say deadband for both, and configure it as a single number in the controller, RTU, or SCADA point. Choosing the value is a balance: too little and you get chatter and nuisance alarms; too much and the system responds sluggishly or misses meaningful changes.
To prevent constant switching and unnecessary action from small fluctuations or noise. It stops pumps from rapidly cycling, keeps control valves from hunting, and prevents alarms from repeatedly clearing and re-triggering.
A margin that must be crossed before an alarm clears after it has tripped. If a high alarm sets at 50 psi with a 2 psi deadband, it will not clear until the value falls below 48 psi, preventing repeated nuisance alarm messages.
With report-by-exception, an RTU or SCADA point only transmits a value when it changes by more than the deadband. This cuts needless updates over cellular and radio links while still capturing meaningful changes.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.