DAC Settling Time
# DAC Settling Time: Wait for Accuracy, Not Just Movement
DAC settling time is the interval required for the output to reach and remain within a specified error band after a stated update event. A useful specification always includes that band, the code transition and the load. A fast-looking edge alone does not establish precision settling.
For a precision control loop, waveform generator or converter test system, the relevant output is the signal at the receiving circuit. An external buffer, filter, cable or switched load can change when that signal becomes usable.
## 1. Find the last entry into the tolerance band
*Conceptual response with exaggerated ringing and tolerance band. There is no calibrated time axis. The yellow marker identifies the last crossing into the band, rather than the first crossing of the final value.*
A response can pass through the target and then overshoot. It may enter the acceptable band briefly, leave it and return later. The settling criterion is the final entry followed by remaining within the band over the specified observation interval. In noisy measurements, define a practical observation and decision rule rather than implying infinite certainty about every future sample.
Delay, large-signal motion and the final tail contribute differently. An update-to-output interval includes propagation latency if its reference event occurs before the analog response begins. An output-referenced measurement may exclude that delay. Always identify the timing reference used by the data sheet and by the system.
## 2. Translate the error band into volts
For a conventional N-bit DAC with analog span VSPAN and ideal code spacing VSPAN/2^N, a half-LSB tolerance is VSPAN/2^(N+1). At 16 bits over a 5-V span, this is about 38.1 µV. A one-LSB band is twice as wide, so the two settling specifications are not interchangeable.
Check whether a percentage specification refers to full-scale span or to the step amplitude. For a small code step those definitions can imply very different absolute tolerances. Also distinguish settling around the actual final output from absolute accuracy relative to the ideal transfer function. An output can settle quickly while retaining static offset, gain or INL error.
## 3. Use a simple model to estimate the tail
*Calculated first-order model, not measured device performance. The input step amplitude is taken equal to the analog span for the estimate. A real zero-to-maximum-code DAC step is slightly smaller than that span.*
For an ideal single pole, residual error magnitude is |ΔV| exp(−t/τ). To reach tolerance ε, the model gives t ≥ τ ln(|ΔV|/ε), provided the initial step exceeds the tolerance. This is a useful scale estimate for a linear tail, not a complete DAC settling model.
Taking |ΔV| = VSPAN and ε = VSPAN/2^(N+1) gives t/τ = (N + 1) ln 2. The values are approximately 6.24 time constants for 8 bits, 9.01 for 12 bits and 11.78 for 16 bits. With τ = 100 ns, the 16-bit estimate is 1.18 µs.
That result assumes an instantaneous applied step, no slew limiting, no overshoot and one dominant pole. Additional poles, zeros, thermal effects or nonlinear recovery can change the tail. Do not infer precision settling from a bandwidth number without checking whether the response actually fits the model.
## 4. Include slew rate, ringing and load
For a slew-limited output stage, |ΔV|/SR estimates the duration of large-signal movement when SR is the applicable slew rate. It does not include the final precision tail. Faster slew can coexist with longer ringing, so choosing the largest slew-rate number does not necessarily give the shortest settling time.
Capacitive load, output resistance and buffer stability affect the response. An RC filter can reduce noise or the peak of a DAC glitch impulse, while delaying the desired step. An external amplifier can introduce its own recovery, offset and settling limits. Evaluate the combined path under the actual loading conditions.
Small steps and large steps need separate attention. Large steps can emphasize slew limitations; small steps can expose switching transients and fine settling behavior. Include upward and downward transitions, major carries and any segment boundaries relevant to the architecture.
## 5. Build the timing budget around observation
A serial interface clock rate tells how quickly data can be transferred. It does not, by itself, specify how quickly the analog output settles. Distinguish the input-register write, transfer to the DAC core, propagation latency and the observation or acquisition event.
For a channel that requires a settled DC value on every update, allow the relevant update-to-settled interval plus the receiving circuit’s acquisition time and timing margin. Some operations can overlap, depending on buffering and interface design. Continuous waveform applications may instead use a specified frequency-domain error target; they cannot always be reduced to the reciprocal of one full-step settling number.
## 6. Verify the final small error
Record transition codes, reference span, supplies, temperature, load, tolerance and timing reference. Capture both the large excursion and the small tail without saturating the measurement path. A probe or amplifier that overloads during the step can create a recovery tail of its own.
Use adequate bandwidth and noise performance, and state any filtering or averaging. Inspect repeatability and timing variation as well as the average trace. When useful, form an error waveform by subtracting a stable final-value reference, while accounting for measurement offset and drift. Check that the waveform remains inside the chosen band throughout the required observation window.
## References
- [Analog Devices AN74: Component and Measurement Advances Ensure 16-Bit DAC Settling Time](https://www.analog.com/media/en/technical-documentation/application-notes/an74f.pdf) — delay, slew, ringing and precision measurement considerations.
- [Analog Devices AN-1444: Second-Order Effects to Consider for Continuous Precision DAC Updates](https://www.analog.com/en/resources/app-notes/an-1444.html) — interface timing, latency, loads and dynamic effects.