Comparator Hysteresis (VHYS): Built-In vs External, Sizing
← Back to:Comparators & Schmitt Triggers
Hysteresis (VHYS) is a single knob that trades robustness for accuracy: it stops chatter from noise and slow ramps, but it also creates a threshold “error band” and timing shift. This page shows how to size, compute, and validate VHYS so false triggers disappear without causing misses or unacceptable drift across real-world corners.
What this page solves: hysteresis stops chatter, but creates an error band
Hysteresis (VHYS) turns a fragile “single threshold point” into a two-threshold band (VTH+ / VTH−) so noise and slow ramps stop causing multi-toggling. The trade-off is an error band: the switching point depends on direction, so absolute threshold accuracy becomes a range.
A) Field symptoms that VHYS is meant to fix
- Slow ramp → multiple edges: the input lingers near the threshold and toggles repeatedly.
- Noise/ ripple → random triggers: small disturbances cross the threshold back and forth.
- Cable touch / movement: injected charge or EMI coupling causes false edges.
- Weak pull-up (open-drain): slow rising edges stay in the transition region longer.
- Too much VHYS: “no trigger” or late trigger (missed events) because the band is overly wide.
B) Root causes (kept strictly within VHYS scope)
C) The only three knobs used on this page (and how to choose fast)
- Slow edge or slow ramp near threshold → prioritize VHYS, then consider RC.
- Chatter persists with small noise → check source R × bias/leakage shifting the effective threshold.
- Missed triggers after adding VHYS → VHYS is too wide or the threshold center is not controlled (VTH+/VTH− must be computed and verified).
- RC “fixes everything” but response is now slow → re-balance: increase VHYS and reduce RC delay.
Definitions: VTH+, VTH−, and VHYS as a bidirectional threshold band
A hysteretic input does not switch at one single voltage. It switches at two thresholds: VTH+ on the rising direction and VTH− on the falling direction. The hysteresis size is VHYS = VTH+ − VTH−. This band is what blocks chatter: small noise can move within the band without flipping the output.
A) The page convention (keeps math and measurements unambiguous)
- VTH+: the VIN value where the output flips when VIN rises.
- VTH−: the VIN value where the output flips when VIN falls.
- VHYS: always defined as VTH+ − VTH− (a positive number).
This convention is independent of whether the comparator is wired “non-inverting” or “inverting”. The definition follows VIN direction, not output polarity.
B) How to read VTH+ / VTH− from a waveform (practical)
Built-in vs external hysteresis: what stays constant, what moves with VDD and temperature
“Built-in VHYS” is fast to use, but its value may change with VDD, temperature, and input structure. “External VHYS” is more controllable because it is set by resistor ratios and reference levels, but it introduces new error sources such as bias/leakage × source resistance and resistor tolerance.
A) Common built-in VHYS models (how to think about drift)
- Is VHYS specified as mV or as a fraction of VDD?
- Are VTH+ and VTH− both provided, or only a single “VHYS typ”?
- Is there a VDD or temperature dependence graph / range?
B) External VHYS is controllable, but adds error sources
- Keep divider/feedback node impedance reasonable; avoid “MΩ-first” designs unless leakage is proven small.
- Use stable resistor ratios (matched network) when threshold accuracy matters.
- Buffer/filter the reference node if feedback can inject noise into the threshold.
C) Selection rules: threshold accuracy vs anti-chatter robustness
- Prefer external VHYS with a controlled reference.
- Model Ibias/leakage × R and ratio tolerance as threshold error.
- Verify VTH+ / VTH− across VDD and temperature corners.
- Built-in VHYS is acceptable if its corner drift is validated.
- Expect VHYS to vary with VDD if supply-proportional.
- If slow edges dominate, prioritize VHYS and then tune RC / source impedance.
When the design cannot tolerate direction-dependent switching error, treat VHYS as a parameter that must be computed + verified, not merely “assumed from typ”.
Threshold math (external VHYS): compute VTH+ and VTH− step-by-step
External hysteresis is created because the threshold node depends on the output state. The output can be near VOH or VOL, so the switching condition must be solved twice: once for the rising direction (VTH+) and once for the falling direction (VTH−). The hysteresis is then VHYS = VTH+ − VTH−.
A) Canonical non-inverting threshold + positive feedback (symbol map)
- VIN drives the + input.
- The − input sees a threshold node formed by VREF and feedback from VOUT.
- R1, R2, Rf set both the threshold center and VHYS.
- VOH and VOL must match the real output swing (including load or pull-up).
B) Reusable template: solve the same node twice (VOH vs VOL)
- VHYS = VTH+ − VTH− (noise-tolerant band).
- Center (direction-averaged trip) must land where the system expects; otherwise VHYS may be correct but the whole window shifts.
C) Reverse design flow (from a target VHYS to resistor values)
- Pick a node impedance range: choose resistor magnitudes that do not amplify leakage/bias into large threshold shifts.
- Set a ratio for VHYS: adjust the feedback ratio so the computed VTH+ − VTH− matches the required noise margin.
- Re-center the threshold: tune the divider/reference so the band is centered on the desired trip region.
- Corner-check VOH/VOL: include load and pull-up; the output swing directly moves VTH+/VTH−.
- Corner-check Ibias × R and tolerance: treat these as additional threshold error that must fit inside the allowed band.
If the computed VHYS works only with “typ” VOH/VOL or with “zero leakage” assumptions, the design is not robust.
D) Why measured thresholds differ from math (must be budgeted)
How to size VHYS: noise, ramp rate, and false-trigger probability (a practical workflow)
VHYS is best sized as a margin budget, not as a guessed “typical” number. The input sees a mixture of random noise (σ) and deterministic disturbances (ripple / ground bounce / injected charge). A slow ramp increases the time spent near threshold, raising the chance of multiple crossings. The workflow below converts these effects into a VHYS target, then checks the cost as an error band and missed-trigger risk.
Step 1 — Estimate input disturbance at the comparator pin
- Random noise: use σ (rms) near the threshold region.
- Deterministic: peak ripple / ground bounce / injected transients (treat as peak).
- Measure at the comparator input node, not only at the source.
Step 2 — Choose a false-trigger tolerance using k·σ (not a single magic number)
Convert random noise into a peak-like margin using a selectable factor k. Larger k reduces false triggers but increases the error band and missed-trigger risk.
Step 3 — Account for slow ramp: time-in-band increases crossing opportunities
- Lower dV/dt near the threshold means longer time-in-band.
- Propagation / filter delays extend the effective “linger window”.
- Slow edges are often the hidden reason why tiny noise becomes repeated toggles.
Step 4 — Synthesize VHYS_min, then check missed-trigger and error-band cost
- Missed trigger: the signal must still cross VTH+ / VTH− under worst-case amplitude.
- Error band: direction-dependent threshold range must fit the system requirement.
- Center shift: VHYS may be right while the threshold center drifts out of spec.
Step 5 — Convert VHYS to resistor ratios and validate worst-case corners
- Use the threshold math template to map VHYS_target → R ratios.
- Corner-check VOH/VOL (load / pull-up), resistor tolerance, temperature drift.
- Include Ibias/leakage × R and reference-node impedance as additional threshold error.
A robust design satisfies VHYS_min and the threshold center range under worst-case conditions, not only at typical room temperature.
Slow ramp & chatter: why transitions linger and how hysteresis interacts with RC
Slow ramps create chatter because the input spends a long time near the threshold. During this “linger” window, even small noise can cross the threshold many times. Hysteresis adds a voltage band (VTH+ / VTH−) so noise can move inside the band without toggling the output. RC filtering can reduce noise, but it also reduces slope and adds delay—often making the linger problem worse if used as the primary fix.
A) Mechanism: long time-in-band + noise crossings → multiple toggles
- Low dV/dt makes the threshold region “wide in time”.
- Noise adds repeated crossings when only a single threshold point exists.
- VHYS turns that point into a band, preventing multi-toggling.
B) RC and VHYS are not interchangeable
C) Practical tuning order: VHYS first, then minimal RC
- Measure chatter under the slowest expected ramp (count extra pulses).
- Increase VHYS until multi-toggling disappears with margin.
- If short glitches still trigger, add the smallest RC that removes the glitch energy.
- Re-check response delay and missed-trigger risk across temperature and VDD.
Error vs robustness: VHYS creates an accuracy band and timing skew
Hysteresis improves robustness by preventing chatter, but it also creates two costs that must be written into system specifications: (1) an accuracy band because VTH+ and VTH− are different, and (2) a timing skew because the effective overdrive at the switching instant changes with the threshold band. Designs that need an exact trip point or tight edge timing must keep VHYS bounded.
A) Accuracy band: the trip is direction-dependent (VTH+ vs VTH−)
- There is no single “threshold point”. Rising and falling transitions use different thresholds.
- VHYS turns the trip into an interval, so the system must tolerate a direction-dependent band.
- When absolute thresholds matter, budget: accuracy band + offset/drift + node errors.
B) Timing skew: VHYS changes overdrive, which changes propagation delay
For a given input slope, moving the effective threshold shifts the crossing time. At the same time, the overdrive at the decision instant changes, and propagation delay typically depends on overdrive—especially in fast paths where small overdrive can slow and spread the timing.
- Voltage-domain cost: a wider band increases direction-dependent trip uncertainty.
- Time-domain cost: the crossing happens earlier/later, and delay can change with overdrive.
- High-speed timing chains should treat VHYS as a timing-budget parameter, not only a noise knob.
C) When VHYS must be small (accuracy or timing sensitive)
External hysteresis pitfalls: bias current × source R, leakage, and resistor tolerance
External VHYS can be precise only if the threshold node behaves like the math assumptions. In practice, tiny bias or leakage currents can create large threshold shifts when combined with high source or divider resistance. Resistor ratio drift moves both VHYS and the threshold center, and a noisy or high-impedance reference can turn the threshold into a jitter source.
Error mapping 1 — Ibias / leakage × resistance → threshold drift (ΔVTH)
- Lower node impedance (avoid MΩ-first designs).
- Buffer the source if Rsource cannot be reduced.
- Verify with temperature sweep under worst-case humidity/contamination.
Error mapping 2 — Resistor ratio drift → ΔVHYS and center shift
- Use matched resistor networks for ratio stability.
- Budget ratio tolerance/TC as threshold error, not as a “nice-to-have”.
- Verify VTH+ and VTH− corners, not only VHYS typ.
Error mapping 3 — VREF noise / impedance → threshold jitter
Built-in hysteresis characterization: how to read datasheets and what they omit
Datasheets often list VHYS as a simple number, but the switching behavior is defined by VTH+ and VTH− under specific conditions. Many parts provide only typical values and omit worst-case drift versus VDD, temperature, source impedance, and output loading. Treat built-in VHYS as a verify-required parameter unless min/max and corner conditions are explicitly stated.
A) Common datasheet formats for built-in hysteresis
- VHYS (typ): a single typical band width, often without min/max.
- VTH+ / VTH−: rising and falling switching thresholds (sometimes only one direction is shown).
- Test conditions: VDD, temperature point, input waveform and source impedance, output load or pull-up.
- Switching curve (if present): can hint symmetry, but rarely provides worst-case corners.
B) Readout traps: what “VHYS” may not guarantee
C) Engineering strategy: treat VHYS as verify-required (minimum checklist)
If a datasheet omits min/max and corner dependencies, the only safe assumption is “typical only”.
Measurement & validation: capture VTH+, VTH−, chatter rate, and worst-case corners
Validation should prove two things: (1) the switching thresholds VTH+ and VTH− (and therefore VHYS and center) remain within limits across corners, and (2) the design does not false-trigger under the worst expected slow ramp and injected disturbance. Use a repeatable test script so the results are comparable across boards and lots.
1) Measure VTH+ and VTH− with a slow ramp (or slow triangle)
- Drive a slow triangle/ramp into the DUT input, and probe VIN at the DUT pin and VOUT simultaneously.
- Use VOUT as the trigger; record VIN at the moment VOUT switches.
- Extract VTH+ (rising) and VTH− (falling), then compute VHYS and center.
2) Chatter test: inject controlled disturbance near the band and count toggles
3) Worst-case corners: VDD, temperature, source impedance, pull-up/load
4) Avoid measurement artifacts: probe capacitance and ground inductance
- Use a short ground spring (or coax-style probing) to avoid fake ringing.
- Probe VIN at the DUT pin; long leads can change the effective RC and the observed chatter behavior.
- If behavior changes significantly when probing, treat it as probe loading first, not as a design conclusion.
Engineering checklist (copy/paste): VHYS design review + bring-up tests
Use this checklist to lock hysteresis requirements into measurable acceptance criteria. Each line includes a Check, a measurable Threshold, and a concrete Action. Keep the scope strictly hysteresis-centric: VHYS sizing, threshold drift, chatter immunity, and corner validation.
A) Design review checklist (VHYS-centric)
| Check | Threshold | Action |
|---|---|---|
| Requirement statement is measurable | Defines: allowed band, allowed false-trigger rate, and allowed timing skew (if timing-sensitive) | Rewrite requirements into pass/fail metrics before choosing VHYS |
| VHYS budget complete (noise + ripple + slow ramp) | VHYS_min ≥ (Noise_pk + Ripple_pk + Ramp-linger margin) × Guardband | Increase VHYS or reduce coupling; treat slow-ramp linger as a first-class budget term |
| Accuracy band acceptable | VHYS_max ≤ allowed error band (and any phase/time error equivalent) | Reduce VHYS or re-define the detection method if absolute trigger point is critical |
| Threshold center stays within the intended window | Center = (VTH+ + VTH−)/2 remains within system limits across corners | Adjust divider/feedback ratio; lower impedance; buffer the source if needed |
| Bias/leakage-induced shift bounded | |Ibias|max × Rsource|max ≤ allowed center shift (include board leakage worst-case) | Lower R, add guard/cleanliness, conformal coat, or add a buffer stage |
| Resistor tolerance + TC accounted (external hysteresis) | Worst-case VHYS_min and center are valid across Rtol and temperature drift | Tighten tolerance/TC, reduce ratio sensitivity, or calibrate at production if allowed |
| VDD dependency captured | VTH+/VTH− and VHYS remain within limits at VDD_min and VDD_max | Prefer implementations with stable thresholds, or re-center using an external reference |
| RC interaction understood (if present) | RC does not push response time beyond system limit and does not create “linger” risk | Size VHYS first, then add only the minimum RC required for noise shaping |
| Open-drain pull-up corner included (if open-drain) | No chatter/regression across pull-up values and bus capacitance extremes | Reduce pull-up, improve edge conditioning, or increase VHYS with bounded accuracy impact |
| Verification plan exists before layout freeze | Defines test waveform, probes, corners, and pass/fail acceptance criteria | Do not rely on “typical VHYS”; treat VHYS as verify-required unless guaranteed |
B) Bring-up tests (lab script)
| Check | Threshold | Action |
|---|---|---|
| Threshold scan | Measure VTH+, VTH−, VHYS, center (VIN at DUT pin) | Fix probing first; then adjust divider/feedback or reduce Rsource |
| Chatter count near the band | Extra toggles per crossing (or false-trigger rate) meets system target | Increase VHYS or reduce injected coupling; re-check error band |
| Slow-ramp stress | No multi-toggling during slow ramps at worst noise/ripple condition | Re-size VHYS before adding heavy RC that breaks response time |
| Pull-up / load corner (open-drain) | No regression across pull-up extremes and bus capacitance | Change pull-up, edge conditioning, or VHYS; re-run chatter metric |
| Source impedance corner | VTH center and VHYS remain within limits across Rsource changes | Lower divider impedance, buffer the source, improve cleanliness/guarding |
| Touch / cable disturbance check | No false toggles under realistic cable touch/move scenarios | Increase VHYS or reduce coupling path; improve shielding and return path |
C) Freeze criteria (design is “done”)
- VHYS_min meets robustness budget across VDD and temperature corners.
- Center stays inside the allowed threshold window across source-impedance and pull-up/load corners.
- Worst-case corner meets the defined chatter metric (no multi-toggles / acceptable false-trigger rate).
- Bring-up logs include test conditions, probe method, and pass/fail results for reuse.
D) Copy/paste template (fill in per project)
| Check | Threshold | Action |
|---|---|---|
| [Fill] | [Fill] | [Fill] |
| [Fill] | [Fill] | [Fill] |
| [Fill] | [Fill] | [Fill] |
Applications (hysteresis-centric recipes): wake-up, alarms, zero-cross, and edge shaping
Each recipe stays hysteresis-centric: how to think about VHYS, what to verify, and what commonly breaks. Example part numbers are starting points for datasheet lookup and bench validation; final selection must be driven by the VHYS workflow and corner tests.
1) Battery wake-up / threshold wake
- VHYS goal: stop ripple and load-step noise from causing repeated wake pulses.
- Size logic: VHYS_min ≥ (battery ripple_pk + coupled noise_pk + slow-ramp linger margin) × guardband.
- Main pitfall: mega-ohm dividers save power but amplify bias/leakage errors and drift.
- Verify: scan VTH+/VTH− at VDD_min/max and T_low/high; run chatter count near the band.
- Example parts: TI TLV3691 (nanopower comparator), ADI LTC1540 (reference + programmable hysteresis).
2) Open-drain alarm line (wired-OR, cross-domain pull-ups)
- VHYS goal: prevent slow rising edges (large pull-up + bus C) from lingering near thresholds and chattering.
- Size logic: size VHYS first for noise immunity; then add only minimal RC if required.
- Main pitfall: pull-up value and bus capacitance are real corners; “lab looks fine” is not sufficient.
- Verify: sweep pull-up and bus capacitance; count extra toggles per crossing.
- Example parts: TI TLV3011 (open-drain + reference), TI TLV4082-Q1 (open-drain + integrated reference + internal hysteresis), onsemi LM393 (open-collector baseline).
3) Zero-cross / phase detect (mains or AC sync)
- VHYS goal: suppress noise at the crossing while bounding phase error caused by the hysteresis band.
- Size logic: choose VHYS_min from noise; cap VHYS_max from allowable time/phase error (band → time shift).
- Main pitfall: oversizing VHYS reduces chatter but moves the effective trigger point too far.
- Verify: inject ripple/noise near crossing and measure trigger time spread at worst corners.
- Example parts: onsemi LM393 (external hysteresis baseline), TI TLV3201 (higher-speed comparator family reference point).
4) Encoder / edge shaping (slow sensors, long cables)
- VHYS goal: convert slow/noisy edges into clean logic transitions and prevent double-count events.
- Size logic: set VHYS_min from cable-coupled noise_pk; keep VHYS bounded to avoid large timing skew.
- Main pitfall: heavy RC “debounce” can create delay and duty distortion; rely on VHYS first.
- Verify: slow ramp + injected noise; count edges and confirm stable state changes.
- Example parts: TI SN74LVC1G17 (Schmitt-trigger buffer, direct logic interface).
5) Custom brown-in / brown-out window (supervisor-like behavior)
- VHYS goal: define a stable power-valid window and avoid on/off oscillation near the threshold.
- Size logic: VHYS_min ≥ (rail ripple_pk + load-step droop/overshoot_pk) × guardband; VHYS_max ≤ allowed window width.
- Main pitfall: divider impedance and leakage can shift the window center at low voltage rails.
- Verify: power ramp up/down across VDD corners; run chatter count at the worst corner.
- Example parts: TI TLV6703 (1.8–18 V monitor comparator with internal reference, open-drain), TI TLV3011 (reference-based threshold starting point).
Reference examples (part numbers; starting points only)
These part numbers speed up datasheet lookup and bench validation. Selection must be driven by VHYS requirements, error-band constraints, and corner measurements.
- Ultra-low power wake / threshold: TI TLV3691, ADI LTC1540
- Open-drain alarm line: TI TLV3011, TI TLV4082-Q1, onsemi LM393
- Higher-speed timing / zero-cross reference point: TI TLV3201
- Logic-level edge shaping: TI SN74LVC1G17
- High-voltage rail monitoring: TI TLV6703
FAQs: Hysteresis (VHYS) — short, actionable, and measurable
These FAQs only cover VHYS: threshold band behavior, chatter immunity, drift/error injection, and quick validation. Each answer uses a fixed data structure: Trigger → Check → Threshold → Action.