Input CM Range & RRI/RRO Near-Rail Behavior (INA)
← Back to:Instrumentation Amplifiers (INA)
Near-rail “RRI/RRO” does not mean constant linearity: the usable input common-mode window moves with gain, output swing, load, and protection leakage. This page turns CM range into a measurable headroom budget and a validation workflow, so rail-edge distortion and slow recovery can be predicted and eliminated before field deployment.
H2-1. Definition & misconceptions: Input CM range, RRI/RRO, and near-rail linearity
This section clarifies what “input common-mode range” and “RRI/RRO” truly guarantee, and what typically breaks first near supply rails (linearity, distortion, CMRR, and recovery). The goal is to turn vague “rail-to-rail” claims into measurable engineering boundaries.
- Full EMI/ESD standards and compliance details (only headroom impact is referenced).
- Complete application front-ends (bridge/RTD/ECG/etc.). This page only uses them as biasing examples later.
- Deep noise theory (only near-rail rectification / DC shift symptoms are mentioned).
Input CM range is the usable window of Vcm where the INA remains functional and predictable. It is rarely a single fixed number: the usable Vcm window can move or shrink with supply, gain, output voltage, load, and frequency.
- A “valid window” means: no hard clipping, no sudden gain compression, no abrupt CMRR collapse, and no pathological recovery tails.
- Near the edges, performance typically degrades gradually before it fails visibly.
“RRI/RRO” indicates near-rail operability under stated conditions—not guaranteed constant performance at the rails. Input and output limitations are separate: RRI does not imply RRO, and output swing can become the first bottleneck even if the input stage still works.
- RRO depends strongly on load (RL), output current, and capacitive stability limits.
- RRI depends on input headroom, internal nodes, and often gain/temperature/frequency.
“Works near the rails” is only meaningful when tied to a prioritized metric set. Typical near-rail failure modes show up first in distortion, CMRR, gain compression, and recovery—often before obvious clipping.
- No hard clip (output headroom remains).
- No abrupt gain compression / nonlinearity shift.
- THD/IMD does not spike at the window edge.
- CMRR does not collapse (especially under real wiring mismatch).
- Recovery time does not create long settling tails after overload/common-mode steps.
| Observed symptom | Most common near-rail cause to check first |
|---|---|
| THD worsens only when Vcm approaches a rail | Input stage headroom reduction → transconductance change → distortion rises before clipping; confirm with a Vcm sweep at fixed Vdiff. |
| No visible rail hit, but settling tail becomes long | Internal nodes saturate first (“hidden saturation”) or recovery spec is weak; check overload recovery and common-mode step recovery conditions. |
| Offset seems to drift when Vcm is near rails | Nonlinear junction/ESD paths rectify HF common-mode or leakage becomes dominant; verify with RF/noise injection and compare mid-supply vs near-rail. |
| CMRR collapses at the edges under real wiring mismatch | Effective CM-to-diff conversion increases near rails; treat edge performance as a guardband zone and validate with worst-case source imbalance. |
- Myth: RRI/RRO means linear operation right up to the rails. Reality: near-rail operation is condition-based; distortion/CMRR/recovery can degrade long before visible clipping.
- Myth: staying inside CM range guarantees low THD. Reality: “inside the range” may only mean “functional”; “linear enough” must be tied to THD/CMRR/gain-compression thresholds.
- Myth: output not hitting the rail means no saturation. Reality: internal nodes can saturate first, causing long settling tails and dynamic nonlinearity.
- Myth: “typical CM range” is enough for design decisions. Reality: worst-case corners (gain/load/temp/frequency) define real guardbands.
Diagram note: the “valid Vcm window” is a practical guardband zone, not a promise of constant THD/CMRR right up to the rails.
H2-2. How to read the datasheet: which plots/tables define the CM window
- Lock system conditions: supply (V+ / V−), target Vcm span, max Vdiff, gain, output bias (VOCM/Vref), and expected load.
- Check output swing vs load first: if swing headroom is insufficient, near-rail distortion will appear even when input CM is “in range”.
- Then locate CM range vs output (or equivalent conditions): many INAs have a CM window that depends on output voltage and gain.
- Verify gain-dependent shrink: higher gain often tightens the usable Vcm window due to internal node headroom.
- Finally check dynamic hazards: overload recovery / saturation recovery and any phase-reversal or input-clamp behavior notes.
CM range plots or tables that specify allowed Vcm as a function of output voltage (or explicit conditions tied to Vout).
The usable Vcm window is often coupled to output headroom. A “safe” Vcm at mid-output can become marginal if the output bias moves toward a rail.
Only “typical” CM range is shown, or the conditions do not match the target gain/load/temperature → plan a board-level Vcm sweep and keep extra headroom.
VOH/VOL headroom vs RL, output current limits, and any notes on capacitive load stability regions.
Output swing sets the feasible output bias and peak amplitude. If swing headroom is short, the “near-rail problem” may be output-limited, not input-limited.
Swing specs are only provided for light loads, while the real system includes filters/ADC sampling charge demand → treat as high-risk until measured.
Any plot/table that shows CM range changing with gain, or notes that internal headroom increases at higher gain.
Higher gain can increase internal node swing and tighten the CM window, even if the front-end is advertised as RRI.
CM specs are missing at the maximum planned gain → the worst-case design point is unbounded without bench validation.
Overload recovery time, output saturation recovery, and any common-mode step recovery plots.
Near rails, internal saturation can cause long settling tails even when the output never visibly hits a rail. Recovery time must fit the sampling/control cycle.
Recovery is not specified (only typical scope shots) → assume the edge is risky and validate with stress tests at the worst Vcm/gain/load.
Explicit “no phase reversal” statements, input clamp structures, allowable input current, and separation between normal operation vs absolute maximum.
Once clamp conduction or reversal behavior is triggered, the output can enter a “wrong-state” (sign inversion, large offset, or long recovery) rather than just mild distortion.
Reversal/clamp behavior is unspecified while the application can hit rails (startup transients, faults, long cables) → require larger guardbands or a different architecture.
If CM/swing/recovery data is only “typical” or does not match the system conditions, treat the edge as uncertain and reserve headroom. Use placeholders that are later filled by measurement:
- Static headroom: keep a margin of ΔVHR from each rail for both Vcm and Vout limits.
- Dynamic margin: ensure overload/common-mode step recovery TREC fits the sampling/loop timeline, or prevent the transient from entering the edge zone.
Diagram note: when a datasheet lacks condition-matched curves, the safest interpretation is “unknown edge behavior” until verified by a Vcm sweep at the worst gain/load.
H2-3. “Moving window” model: budget Vcm, Vdiff, and Vout swing together
“Input CM range” becomes actionable only when the system is constrained by output swing, gain, and biasing. This section converts a vague common-mode spec into a fill-in budget workflow and a window table that can be verified on the bench.
- Output #1: a minimal symbolic model (no invented numbers).
- Output #2: a reusable 5-step budget workflow + a “Vcm window vs gain/load/bias” table template.
Input common-mode (both inputs move together). This is the “window coordinate”.
Input differential signal, including peaks, faults, and overrange (use the worst-case Vdiffpk).
Output equals bias plus amplified differential: Vout = Vout_bias ± G·Vdiff.
Output headroom limits under real load: Vout_swing_hi and Vout_swing_lo.
Guardband headroom reserved from each rail: ΔVHR_in for input stage and ΔVHR_out for output swing.
Key takeaway: the Vcm window can shrink when Vout is pushed toward a rail or when gain increases internal node swing. A “rail-to-rail” label does not remove these coupled constraints.
Fix V+ / V−, the planned output bias (VOCM/Vref), expected load, and the required Vcm span in the application.
Use Vdiffpk that includes normal peaks, startup transients, and credible faults/overrange events.
Compute output extremes: Vout = Vout_bias ± G·Vdiffpk. This sets how close the output approaches each rail.
Apply Vout_swing_hi/lo (at the real load) and reserve ΔVHR_out. If violated, back-solve allowed gain, bias, or signal range.
For each (gain, load, bias) condition, record the guardbanded valid Vcm_lo/hi and note which metric fails first near the edges.
Use this template to document the “moving window” across operating corners. Keep the first-failure note short (THD/CMRR/recovery/clip).
| Supply | Gain (G) | Load | Vout_bias (VOCM) | Vout_swing_lo / hi | Vout_pk_lo / hi | Valid Vcm_lo / hi | First failure near edge |
|---|---|---|---|---|---|---|---|
| V+/V− | G | RL / equiv. | VOCM | lo/hi | lo/hi | lo/hi | THD / CMRR / recovery / clip |
| … | … | … | … | … | … | … | … |
Diagram note: the loop highlights that Vcm is not an independent spec; it must be validated under the same Vout and gain conditions the system will see.
H2-4. Single-supply near-rail operation: where to bias Vcm and Vout safely
The safest default is to bias both input common-mode (Vcm) and output (VOCM/Vref) away from the rails. Treat near-rail operation as an exception that must satisfy condition-based RRI/RRO limits and recovery constraints under the worst gain and load corner.
- Place Vout_bias (VOCM) inside the ADC’s comfortable range so output swing headroom is preserved on both sides.
- Keep Vcm away from rails by a guardband ΔVHR_in, unless condition-matched evidence confirms edge stability.
- When high gain is required, prioritize linearity and recovery over “absolute maximum swing”.
- Pushing Vcm to 0 V or VDD based only on a “RRI/RRO” label without matching gain/load/frequency/temperature conditions.
- Biasing Vout near an ADC endpoint where output swing becomes the first limiter (apparent “input CM” problems often start here).
- Ignoring hidden saturation: output may not visibly hit a rail while internal nodes saturate and recovery tails grow.
Vout_swing_hi/lo are valid at the real load; reserve ΔVHR_out from each rail.
Maximum gain does not shrink the usable Vcm window into the operating span.
Recovery (TREC) fits the sampling/loop timeline; no long tails after overload or CM steps.
No phase reversal risk; input clamps are not triggered by expected transients/faults.
Valid Vcm_lo/hi are documented with ΔVHR_in and ΔVHR_out, not just “typical” values.
As Vcm approaches a rail, internal headroom can reduce effective transconductance and distort transfer behavior before any hard clipping.
Hold Vdiff constant and sweep Vcm; watch for a knee in THD or gain as the window edge is approached.
CM-to-differential conversion can increase near the edges, making real wiring mismatch and common-mode noise more visible at the output.
Compare output error under common-mode disturbance at mid-supply vs near-rail Vcm. Treat large deltas as “edge-risk”.
Internal nodes can saturate first, creating long settling tails after transients even if the output never visibly clips.
Inject a controlled step/overrange event and compare settling tail duration at mid-supply vs near-rail bias points.
Diagram note: the recommended VOCM zone is intentionally narrower than the ADC range to preserve output headroom on both sides across corners.
H2-5. Dual supply & headroom: when ± rails are worth it
Adding a negative rail can be the most stable way to buy margin when the system must cover near-ground or high-side common-mode conditions without sacrificing gain or dynamic range. This section turns that choice into a decision rule and a short risk checklist.
More headroom reduces “edge operation”, so the guardbanded Vcm window is easier to keep valid across gain and load corners.
With internal nodes away from rail headroom limits, distortion knees move outward and overload tails are less likely.
Output bias can be placed in a “comfortable zone” without forcing near-rail conditions just to match an ADC input range.
A wider analog swing is not useful if the downstream range is still clipped by a single-supply domain. Bias targets must be re-anchored to the ADC range before choosing the negative rail magnitude.
A noisy − rail can inject low-frequency error or create “fake improvements” that vanish once the system is assembled. The − rail must be treated as a primary analog supply with proper decoupling and return paths.
Clamp/TVS paths and leakage references shift with supply domains. Re-check which nodes become forward-biased during transients and where leakage produces offset.
- The system must cover near-ground or high-side Vcm conditions and Vcm cannot be moved by biasing without breaking the application.
- Gain and dynamic range are not negotiable (reducing gain or shrinking Vdiff range is not acceptable).
- Single-supply operation repeatedly hits “edge behaviors” (THD knees, CMRR collapse, recovery tails) under worst gain/load corners.
Compare the guardbanded Vcm window and the near-rail “knee locations” with and without the negative rail under the same gain/load/bias corner. If the knees move outward and the window stays stable, the extra supply complexity is paying for real margin.
Diagram note: the decision focuses on “required Vcm coverage + non-negotiable dynamic range” first, then checks whether biasing or device choice can avoid edge behavior.
H2-6. What breaks near rails: compression, THD, CMRR collapse, rectification, phase reversal
- Gain compression: amplitude ratio drops or the response becomes slower as Vcm approaches a rail.
- THD knee: distortion stays calm then rises sharply near the edge.
- CMRR collapse: output becomes more sensitive to common-mode changes and wiring mismatch.
- Rectification offset: RF/common-mode disturbance turns into a DC shift through nonlinear junctions.
- Phase reversal (device-dependent): output polarity flips after an out-of-range input condition.
| Symptom | Likely mechanism | What to observe (Vcm sweep) |
|---|---|---|
| Gain compression | Input-stage headroom reduction changes effective gm or internal node swing | Gain vs Vcm shows a clear knee before any hard clipping |
| THD knee | Nonlinear transfer near headroom limit and/or output stage swing restriction | THD vs Vcm stays flat then rises rapidly near the edge |
| CMRR collapse | CM-to-diff conversion increases when internal margins are low | Output error becomes more sensitive to Vcm and source-R imbalance near rails |
| Rectification offset | Nonlinear junctions/clamps rectify RF/common-mode into DC shift | Offset vs Vcm drifts with disturbance strength; edge zones worsen it |
| Phase reversal (if present) | Input exceeds allowed range and pushes the internal stage into wrong operating region | A sudden polarity flip or step-like inversion during Vcm excursions |
Hold gain and load constant. Use a representative Vdiff amplitude (include realistic peaks).
Sweep Vcm from mid-supply toward each rail and record the first visible deviation.
Track three curves vs Vcm: gain, THD trend, and an offset/CMRR proxy. The “knee” defines where guardband should begin.
Diagram note: the curves are conceptual—only the “knee locations” matter for defining a conservative operating window with guardband.
H2-7. Dynamic events: CM steps, overload, recovery time, and “hidden saturation”
In industrial, motor-drive, and pulse-sampling systems, a common-mode step or a short overload can leave a long settling tail even when the output does not visibly clip. The key is distinguishing visible output saturation from internal node saturation and then designing margin and input energy control so recovery stays fast and predictable.
Fast Vcm movement from switching nodes, ground shifts, or high-side transients can create a momentary CM→diff conversion and a settling tail.
Short overrange pulses, hot-plug events, or fault spikes can push internal nodes beyond their linear region even if the output swing looks “fine”.
Once a nonlinear junction conducts, recovery may be dominated by charge removal and internal bias re-stabilization rather than by output swing alone.
- Vout clips near a rail (clear flat-top).
- Recovery shows a “release” from clipping, then normal settling.
- Primary lever: keep output bias and swing away from the rails.
- Vout may not clip, but the response becomes slower and distortion rises.
- A long settling tail appears after overload or CM step.
- Primary lever: avoid pushing internal nodes into protection/headroom-limited regions by limiting input energy and leaving margin.
A Vcm step can momentarily convert into an output error. The important quantity is the peak output deviation immediately after the step.
Recovery is defined by how long the tail takes to return within the system error band. A long tail is often the first sign of hidden saturation.
Hold Vdiff near zero (or very small), apply a controlled Vcm step, and record both peak error and tail length. A tail without obvious clipping points to internal-node limitation rather than pure output swing.
Use the guardbanded window approach: do not operate in edge zones where knees and hidden saturation become likely under worst corners.
Prevent transient events from driving clamps or internal nodes into deep nonlinearity. Small series impedance and controlled filtering can reduce the “tail driver”.
Do not bias Vout or Vcm into swing-limited corners just to “use the ADC range”. Safer bias zones reduce both distortion knees and recovery tails.
Diagram note: a long tail without obvious clipping is a strong indicator of hidden internal-node limitation rather than pure output swing.
H2-8. Co-design with ADC/reference: VOCM, ratiometric drift, and range mapping
The practical question is not “can the INA touch the rails” but “does the ADC ever clip, distort, or fail to settle under the real range and bias conditions”. This section focuses on range mapping and bias interfaces (VOCM). Anti-alias filter design and driver stability details are intentionally not expanded here to avoid cross-page overlap.
- Vout must stay inside the ADC valid range (no “near-rail optimism”).
- VOCM is the DC bias that centers the signal inside that range.
- Forcing the bias too close to the low rail often increases distortion and recovery tails.
- The ADC usually expects a recommended input common-mode (VOCM/VCM target).
- “No clipping” is not enough: a wrong VOCM can still degrade linearity and settling.
- Range mapping must satisfy both full-scale limits and the ADC’s common-mode comfort zone.
When sensor excitation and ADC reference track together, ratio-based scaling can reduce sensitivity to slow supply/excitation drift.
Ratiometric scaling cannot prevent near-rail distortion, clipping, hidden saturation, or recovery tails. Headroom and VOCM alignment still decide linearity.
Capture both Vcm range (wiring and environment) and Vdiff peak (including transients and overload cases that matter for recovery).
Compute Vout swing as VOCM ± G·Vdiff_peak, then verify both swing limits and “knee margins” (avoid edge zones where knees appear).
Confirm the ADC full-scale window and (for differential ADCs) the preferred input common-mode. “No clipping” is not sufficient if VOCM is outside the linear zone.
Add headroom guardbands on both input and output sides so the chain remains linear across temperature, load, and transient corners.
- ADC does not clip, but THD/linearity collapses → VOCM / ADC common-mode zone mismatch.
- Small signal looks fine, large transients recover slowly → hidden saturation driven by edge-zone operation or clamp engagement.
- Typical curves look safe, worst corners break → missing guardband across temperature/load/gain conditions.
Diagram note: the goal is window alignment with guardband—sensor ranges, INA swing limits, and the ADC full-scale/common-mode comfort zone must overlap under worst corners.
H2-9. Common sensor bias patterns: Vcm handling only
These patterns focus strictly on where input common-mode (Vcm) comes from, what can push it out of the valid window, and the smallest “hook” that pulls Vcm back to a controlled zone. Signal-chain details (filters, calibration, standards) are intentionally not expanded here.
Vcm naturally sits near the bridge excitation midpoint when wiring and resistances are balanced.
Bridge imbalance and long-lead resistance changes can shift Vcm, shrinking margin near the rails in single-supply systems.
Treat Vcm drift as a window-budget item and keep the operating point inside the “safe belt” around mid-supply/VOCM.
Vcm is set by the bus/high-side node and can be tens to hundreds of volts (often with fast movement).
The input stage can exit its CM window even when the differential signal is small, causing distortion and long recovery tails.
Use wide-CM, isolation, or controlled attenuation so the output remains in the low-voltage domain while Vcm lives in the high-voltage domain.
The input can be effectively floating, so Vcm is shaped by leakage and parasitic coupling rather than by a defined reference.
Without a controlled return path, Vcm can drift into edge zones and create sudden offsets, distortion knees, or slow recovery.
Provide a defined input bias/return path to pull Vcm into the mid-window region under worst leakage and coupling.
The body picks up strong environmental common-mode interference and the effective Vcm moves with contact conditions.
Large Vcm swing can drive the input stage into edge zones, creating baseline shifts, saturation-like artifacts, and long recovery tails.
Use a bias/RLD-style common-mode return that pulls Vcm back toward the window center and prevents edge-zone operation.
First identify the natural Vcm source, then name the dominant “pull-away” forces (imbalance, bus voltage, leakage/coupling, or body CM), and finally add the smallest return/bias hook that keeps Vcm inside the guardbanded mid-window region under worst-case conditions.
Diagram note: each pattern is defined by Vcm source, the dominant pull-away forces, and a minimal hook that keeps Vcm inside the guardbanded mid-window region.
H2-10. How protection and filtering steal CM headroom (window budgeting)
Protection components are not free: series resistance, clamp leakage, and RC dynamics can shift and narrow the effective Vcm window. The result is often “no obvious clipping, but worse distortion and longer recovery tails”. This section stays strictly on headroom and leakage budgeting (not on standards or protection topology selection).
Series resistance is multiplied by worst-case input bias current, producing a DC offset that effectively shifts the Vcm operating point.
Leakage can turn into a measurable offset through high source impedance or bias networks, and it often worsens close to supply rails.
Filtering can spread energy in time. Near-rail operation plus a long transient can increase the chance of hidden saturation and make settling tails longer.
Collect Ib,worst, Ileak,worst, Rs,total, Rsrc,eq, and temperature corners.
Convert bias and leakage currents into DC offsets using the budget forms, then translate them into window shift/narrowing.
Move the operating point away from edge zones so the final window remains valid under worst-case drift and wiring conditions.
Run a representative CM step or overload pulse near the intended Vcm region and check whether the settling tail grows after protection is added.
Diagram note: treat Rs drop and clamp leakage as explicit window-loss terms, then guardband the operating point away from edge zones where dynamic tails amplify.
H2-11. Verification method: Vcm sweep workflow, criteria, and measurement traps
A Vcm sweep exposes the real “edge zones” where gain compresses, THD rises, CMRR collapses, or recovery tails grow. The output of this test is a guardbanded operating window (Vcm vs gain/load) backed by repeatable pass/fail criteria.
Sweep Vcm from low to high, including both window edges and the intended operating region.
- Gain: G_low / G_mid / G_high
- Load: representative Rload (ADC/input network equivalent)
- VOCM/Vref: intended output bias point
- Vdiff stimulus: amplitude + frequency (and optional step/overload pulse)
- Temperature: room as baseline (expand to corners later)
Use one adjustable common-mode source and one differential stimulus. Combine them through a symmetric network so both inputs see the same Vcm while carrying equal-and-opposite Vdiff.
Use a differential driver for Vdiff and set common-mode with its VOCM/CM control. Validate that the actual pin-level Vcm reaches the target under load and frequency.
Track ΔGain relative to the mid-window baseline point and/or track THD at the chosen frequency to locate the “knee” near rails.
Record Vout_peak and compute headroom to both rails. Window edges often appear as margin-driven distortion or gain compression before obvious clipping.
Inject a small CM step or short overload pulse and measure time-to-return into the error band (±Eband). Hidden internal saturation can create long tails without rail hit.
These are representative parts for test fixtures and bias generation. They are examples, not requirements.
Buffer amp: OPA197, OPA192, ADA4522-2
Precision resistor networks: Vishay ACAS series; Susumu RG/RR series
ESD arrays: TI TPD series; Nexperia PESD series
TVS (generic): Littelfuse SMF series
Setup note: always measure the actual pin-level Vin_cm and Vin_diff; do not trust generator panel readings near compliance limits.
H2-12. Engineering checklist: schematic, layout, bring-up, and production sampling
A rail-to-rail label does not guarantee stable linearity at the edges. This checklist enforces a repeatable process: define Vcm/Vdiff/Vout budgets, preserve bias/return integrity on the PCB, verify the window with a Vcm sweep, and sample edge points in production.
Vcm/Vdiff/Vout budget is written, including overload and fault over-range cases.
A guardbanded operating window is defined (no edge-zone operation under worst-case corners).
Bias/return path exists so inputs never float; VOCM/Vref target keeps the system away from rails.
Worst-case leakage and Ib cannot pull Vcm outside the intended window.
Protection/series resistors are accounted as headroom costs (Ib×Rs and Ileak×Rsrc).
Window table is updated with those losses and still meets margin targets.
Differential inputs are symmetric: matched routing, matched impedance, and continuous return plane.
CM-to-diff conversion from layout is minimized (no avoidable asymmetry in the input path).
Protection parts are “near the connector” only if they do not break the bias/return path or add asymmetric leakage.
Effective Vcm window remains consistent when the protection network is populated.
VOCM/Vref nodes are low-impedance and properly decoupled; return currents do not share sensitive CM paths.
No unexpected Vcm ripple is injected by ground drops or shared returns.
Run the Vcm sweep first to locate knees and define the guardbanded window.
Knee points sit outside the intended operating zone under representative gain/load.
Test CM step / overload recovery near window edges to reveal hidden saturation tails.
Recovery returns into ±Eband within Z ms without long tails in the operating zone.
Repeat key edge points at temperature corners (at least cold/hot) to catch leakage-driven window shifts.
The guardbanded window remains valid across temperature.
Sample the window edge points (both sides). These points expose margin loss faster than mid-window tests.
Edge points meet THD/ΔGain/recovery criteria with guardband intact.
Log window-table fields per lot and temperature condition (even if only a subset is measured).
Drifts and shifts can be traced to a measurable parameter (not discovered as a field failure).
Example parts frequently used to build stable bias/return and measurement-friendly layouts. Use the checklist gates to validate, not part numbers.
Buffers: OPA197, OPA192, ADA4522-2, OPA388
Phoenix / WAGO terminal blocks (family examples)
Checklist note: production sampling should always include edge-zone points, because they reveal margin loss earlier than mid-window tests.
H2-13. FAQs: Input CM range, RRI/RRO behavior, and near-rail linearity
These FAQs close long-tail issues around near-rail distortion, early clipping, CMRR collapse, recovery tails, fixture limits, and fast CM-range validation. Each answer uses a fixed, data-first 4-line format.