123 Main Street, New York, NY 10001

Conductivity / Resistivity Meter: AC Excitation, PSD AFE, ΣΔ ADC

← Back to: Industrial Sensing & Process Control

Center idea

A conductivity/resistivity meter is built by driving the probe with a controlled AC excitation and extracting the in-phase and quadrature response (I/Q) with PSD/lock-in and a ΣΔ ADC, so true solution resistance can be measured while polarization, leakage, and EMI are rejected. The result is an auditable pipeline—excitation → I/Q demod → calibration (cell constant K) → temperature compensation—plus evidence fields that prove accuracy in the field.

H2-1. Mission, Scope, and What This Page Solves

This page is a build-and-verify guide for an EC (conductivity) / resistivity meter front-end. It focuses on the signal chain and evidence needed to reach stable readings while preventing electrode polarization, drift, and noise-induced false changes.

A conductivity meter becomes reliable only when the design is treated as a coherent I/Q measurement problem: the excitation source and the demodulation reference must be phase-related (or phase-calibrated), and both in-phase (I) and quadrature (Q) components must be observable. In practice, I tracks solution-dominant conductivity, while Q is the early-warning channel for interface and parasitic effects (electrode double-layer behavior, cable capacitance, leakage paths).

Reference signal chain: DAC → Cell → AFE → PSD → ΣΔ → Output Measurement recipe: frequency/amplitude, I/Q demod, calibration, temp comp Debug checklist: polarization vs leakage vs cable pickup vs EMI

Minimum Evidence Set (must be declared for reproducibility):

  • Excitation: frequency f_exc, amplitude (V_exc or I_exc), waveform (sine / square / synthesized)
  • Demod: I/Q outputs, demod low-pass bandwidth (ENBW) and update rate
  • Coherence: clocking relationship between DAC and PSD reference (shared clock or phase-calibration method)
  • Temperature: measured T, reference temperature T_ref, compensation model
  • Calibration: standard values used, residual error after calibration
  • Stability: drift slope over a fixed standard (e.g., 10 min / 1 h)
Conductivity / Resistivity Meter — Signal Chain & Evidence Nodes Coherent excitation + I/Q demod makes polarization and parasitics diagnosable. AC DAC f_exc, V_exc Coherent ref Waveform Excite Driver Compliance Output Z Protection Electrode Cell Solution R Interface Cdl/Rct Polarization risk Cable C / leakage TIA / AFE Stability (Cload) Leakage/guard Noise floor Anti-Alias Phase error EMI shaping Bandwidth ΣΔ ADC Fs / decimation Group delay Mains notches PSD / Lock-in I/Q demod Phase calibration ENBW / update I Q Algorithms & Outputs Anti-polarization actions Calibration → σ / ρ @ T_ref Drift + confidence flags Evidence nodes to capture in validation 1) f_exc, V_exc/I_exc 2) I/Q vs time 3) I/Q vs frequency 4) T + T_ref model 5) Calibration residuals 6) Drift slope in a standard 7) EMI sensitivity (mains/motor)
Figure 1. System map for an EC / resistivity meter. The key design move is making excitation and demodulation coherent so that I/Q can separate solution behavior from interface and parasitic effects.
Cite this figure: Conductivity/Resistivity Meter System Map — include excitation (f, amplitude), I/Q definition, and temperature reference in the caption.

H2-2. Measurement Fundamentals You Actually Use (EC, Resistivity, Cell Constant)

Fundamentals here are limited to what changes design choices: what the meter outputs, how cell constant (K) sets the measurable range, and what must be declared so results are reproducible across probes, frequencies, and temperatures.

Conductivity (σ) expresses how easily ionic current flows through the solution, while resistivity (ρ) is its inverse (ρ = 1/σ). In engineering terms, the meter is estimating a solution-dominant impedance and then mapping it to σ (or ρ) using the probe geometry. The geometry enters as the cell constant K (set by electrode spacing and area), and K effectively becomes the “range knob” for the whole analog front-end.


Why K dominates range planning (the practical view):

  • High K probes push the same solution toward a larger effective resistance → smaller signal, more noise sensitivity.
  • Low K probes push toward higher current → higher polarization risk, AFE headroom limits, and more self-heating artifacts.
  • The right AFE (TIA gain, ADC range, excitation amplitude) is therefore chosen after K and expected σ range are known.
Evidence Field Why it must be declared What it controls
Cell constant (K) Same σ can look different with different geometries. Signal magnitude, TIA gain choice, headroom limits.
Excitation: f_exc + amplitude Frequency shifts polarization and parasitic dominance; amplitude shifts SNR and electrochemical risk. I/Q accuracy, drift behavior, saturation risk, EMI susceptibility.
Temperature model + T_ref σ is strongly temperature dependent; without a declared model, numbers are not comparable. Final output normalization, calibration transferability.
Derived values (TDS / salinity) These are mappings from σ, not direct measurements; mapping must be stated to avoid ambiguity. Displayed units, conversion curves, customer expectations.

Derived outputs (TDS / salinity): in most meters these are computed from conductivity using application-specific conversion curves. They should be treated as declared transforms (document the curve/standard), not as independent sensor measurements. Keeping this boundary clear prevents scope creep and preserves auditability.

Range Planning: K × σ → Signal Scale & Frequency Window Use this to choose an excitation band and know what error mechanism will dominate first. Expected conductivity σ (low → high) Signal scale after K (small → large current) LOW σ Noise-limited Increase SNR MID σ Best window Stable I/Q HIGH σ Headroom / interface Avoid saturation Lower K → larger current / higher interface stress High K probe Mid K probe Low K probe Recommended excitation band (start point) Decision Output Declare K, f_exc, amplitude T model + T_ref Watch-outs LOW σ: noise floor MID σ: best stability HIGH σ: headroom Interface/Cable Q First picks Choose f to reduce polarization, then validate via I/Q Interpretation If Q grows or drifts with frequency/cable length, parasitics or interface effects dominate and must be mitigated before trusting σ. If I is stable but σ changes with temperature, the compensation model or temperature sensing placement is the limiting factor.
Figure 2. Range-planning map that ties probe geometry (K) and expected conductivity (σ) to the dominant error mechanism and a practical starting point for choosing an excitation band. Treat I/Q behavior as the acceptance test.
Cite this figure: Range Planning (K × σ) → Frequency Window — include K, excitation settings, and the temperature reference used for reported σ/ρ.

H2-3. Probe & Electrode Physics: Polarization, Double-Layer, and Why DC Fails

Electrode polarization is not a chemistry footnote—it is an electrical interface that stores charge and distorts low-frequency measurements. Treating the probe as a frequency-dependent impedance is the prerequisite for stable conductivity/resistivity readings.

The conductivity cell can be modeled as a solution resistance in series with an interface network. The interface is commonly represented by a double-layer capacitance (Cdl) and a charge-transfer resistance (Rct). Together with cable capacitance and leakage paths, the interface makes the measured impedance strongly dependent on frequency and time.

Polarization signatures (how it shows up in data):
  • Baseline drift in readings at fixed conditions (time-domain signature).
  • Apparent higher resistance at low excitation frequency (frequency-domain signature).
  • Phase shifts where quadrature grows and the I/Q ratio changes with frequency or cable length.

DC excitation fails because it continuously biases the interface, driving charge accumulation and slow relaxation. This produces drift that cannot be separated from solution resistance. In contrast, AC excitation with coherent demodulation isolates the component that is strictly synchronous with the excitation. The in-phase channel (I) tracks the solution-dominant contribution, while the quadrature channel (Q) is a sensitive indicator of interface/cable capacitance and leakage-induced phase error.


What to measure (validation evidence):

Measurement How to run it Interpretation
I/Q vs frequency (3+ points) Hold standard solution and temperature constant; sweep f_exc across low/mid/high bands. If Q grows or changes shape strongly with frequency, interface or cable capacitance dominates the error.
I/Q drift vs time (10 min / 1 h) Fix f_exc, amplitude, and temperature; log I and Q over time in a stable standard. If I drifts with Q, polarization/interface state is changing; if I drifts with Q stable, suspect electronics or temperature modeling.
Cable sensitivity check Repeat I/Q at multiple cable lengths or with added capacitance. If Q scales with cable, the front-end needs better stability/guarding or a different excitation band.
Equivalent Circuit: Cell + Interface + Parasitics Goal: separate solution-dominant behavior (I) from interface/parasitic signatures (Q). AC Source f_exc Amplitude Conductivity Cell Solution R dominant in I Interface Cdl Rct polarization-sensitive Parasitics Cable C Leakage TIA / AFE Stability Noise Guarding PSD I (in-phase) Q (quadrature) What changes with polarization • Drift over time (baseline) • Low-f looks like higher R • Q grows / phase shifts Validation evidence • I/Q vs frequency (3+ points) • I/Q drift vs time in a standard • Cable sensitivity check (Q scaling) I tracks solution R Q reveals interface/parasitics
Figure 3. Equivalent circuit for the conductivity cell. The interface network (Cdl/Rct) and parasitics (cable capacitance, leakage) are highlighted because they drive polarization-related drift and phase/Q behavior.
Cite this figure: Cell Interface Equivalent Circuit (Cdl/Rct) — include how I/Q is used to diagnose interface and cable effects.

H2-4. Selecting AC Excitation: Frequency, Amplitude, Waveform (DAC Strategy)

Excitation settings should be chosen as a verifiable operating point inside an error window, not as a fixed “default frequency.” The goal is to pick a band where I is stable and Q remains bounded under the intended probe, cable, and environment.

Frequency controls which error mechanism dominates. Too low, polarization and drift grow; too high, cable capacitance and phase error inflate Q and reduce interpretability. The recommended workflow is validation-driven: sweep a few candidate frequencies in a standard solution, then repeat with the longest expected cable to confirm that Q does not explode.

Practical frequency selection (repeatable steps):
  • 3-point sweep (low / mid / high): record I and Q in a standard at fixed temperature.
  • Choose a band where I is flat and Q is bounded (Q/I below a declared threshold).
  • Stress test with cable length and EMI exposure; reject bands where Q scales aggressively.

Amplitude should be large enough to lift I above the noise floor but not so large that the interface becomes nonlinear (seen as worsening drift and Q growth with amplitude). Amplitude selection is therefore limited by both electrochemical behavior and electronics: driver compliance, AFE headroom, and ADC full-scale must not be violated in high-σ or low-K conditions.

Waveform selection must be done from a PSD perspective. A near-sine concentrates energy at the fundamental, simplifying lock-in extraction. Square or multi-tone waveforms can be used, but harmonics interact with frequency-dependent impedance and nonlinearity, creating mixing that contaminates the baseband I/Q estimate. If a non-sine waveform is used, harmonic management (filtering or declared harmonic ratios) becomes part of the measurement specification.


Evidence fields (must be declared in the build spec):

  • Excitation: f_exc, amplitude (Vrms/Irms), waveform type (sine / square / synthesized)
  • Spectral purity: THD or harmonic ratio target (especially for sine/synthesized)
  • Coherence: reference source (shared clock / NCO) and phase-calibration method
  • Acceptance: declared I/Q stability criteria (e.g., Q/I threshold) in a standard and with max cable
Excitation Design Window (Frequency × Dominant Error) Pick an operating band where I is stable and Q is bounded under probe + cable + EMI. Low f High f Excitation frequency (f_exc) Polarization Drift / low-f bias Stable Window I flat, Q bounded Cable C Phase/Q inflation 50/60 Recommended band Acceptance test I stable Q/I < threshold Spec Outputs Frequency Chosen band + 3-pt sweep Amplitude SNR vs nonlinearity Waveform Fundamental purity Coherence Ref + phase calibration Evidence I/Q vs f + max cable Rule of thumb Reject frequencies where Q scales sharply with cable length or where drift increases over time in a stable standard. Document f, amplitude, waveform, and coherence so results can be reproduced across probes and builds.
Figure 4. Excitation design window. Frequency and waveform choice should be validated by I/Q behavior in a standard solution and stressed by cable length and EMI exposure before being locked into the specification.
Cite this figure: Excitation Design Window (Polarization ↔ Cable C) — include the acceptance test (I flat, Q/I bounded) and the declared evidence set.

H2-5. Front-End Architecture: TIA/AFE for Microamps to Milliamps (PSD-Ready)

The analog front-end must preserve linearity, stability, and phase integrity so that lock-in PSD produces interpretable I/Q. Most “mystery drift” and “Q explosions” are caused by TIA instability, leakage, and phase error—not by the conductivity model.

Two sensing styles with selection criteria TIA stability with cable/electrode capacitance (Rf/Cf) Leakage + guarding rules for µA ranges Anti-alias vs “digital-only” filtering boundary

Two sensing styles (what changes in PSD behavior):

  • Voltage-sense across a reference element: simpler signal chain, easier headroom planning, but phase is influenced by more parasitics (routing, reference element, and cable return paths).
  • Current-mode TIA: converts probe current to voltage at the earliest point, often producing cleaner PSD inputs for small signals, but it is highly sensitive to cable/electrode capacitance, input bias, and leakage.

TIA stability must be treated as a first-class specification. Cable capacitance and electrode interface capacitance act as a load that reduces phase margin. The Rf/Cf network defines the closed-loop pole/zero placement and therefore the ringing risk. Even mild ringing can be interpreted by PSD as quadrature energy, producing false Q growth and misleading phase signatures.

Leakage and guarding (µA range survivability):
  • Input bias current and board/connector leakage can be comparable to the probe signal at low conductivity/high K.
  • Driven guard and short, clean input routing reduce surface conduction and parasitic capacitance to aggressors.
  • Protection placement must avoid adding leakage to the high-impedance node; use controlled paths and keep the “quiet node” small.

Anti-aliasing strategy: ΣΔ ADCs provide digital filtering, but they cannot prevent strong out-of-band interference from entering the analog path and mixing back into the demodulated band through nonlinearity or overload recovery. A modest analog anti-alias/EMI filter that preserves phase in the demod band is often required to keep I/Q interpretable.


What to measure (PSD-readiness checks):

Check How to run it Pass/fail meaning
Noise in demod band Measure TIA output noise density; integrate over the planned PSD ENBW. Predicts I resolution and the minimum detectable σ change; must match system targets.
Step response with real load Apply a small excitation step using representative probe + cable; observe Vout settling/ringing. Ringing that overlaps the demod band will appear as Q/phase artifacts; stability must be improved.
Overload recovery Force a controlled overload (high σ / low K condition); verify recovery time and baseline restoration. Slow recovery can create false drift and demod offset; indicates headroom/AA/ADC limits.
PSD-Ready Analog Chain (Probe → TIA → AA → ΣΔ → PSD) Phase integrity and stability determine whether Q is diagnostic or misleading. Probe + Cable Solution R Cdl/Rct Cable C Leakage TIA Rf Cf Stability AA / EMI Filter Phase-preserving Anti-alias ΣΔ ADC Decimation Group delay Overload PSD I (in-phase) Q (quadrature) Where phase errors enter (and inflate Q) • Cable C / leakage • TIA ringing • AA phase shift • ADC delay/jitter PSD-readiness checks 1) Noise integrated over ENBW 2) Step response (ringing/settling) with real cable/probe 3) Overload recovery in high-σ / low-K conditions
Figure 5. PSD-ready analog chain. The probe/cable impedance and TIA stability dominate phase integrity. Phase errors and ringing inflate Q and can masquerade as polarization or conductivity changes.
Cite this figure: PSD-Ready Analog Chain (Phase Error Entry Points) — include ENBW-based noise integration and step-response stability evidence.

H2-6. PSD / Lock-In Demodulation: Synchronous Detection Done Correctly

Lock-in PSD should be treated as a parameterized signal-processing block that outputs a complex response (I + jQ). Correct results require coherent reference generation, defined bandwidth (ENBW), and a repeatable phase calibration procedure.

The core operation is synchronous detection: multiply the sampled signal by a reference sine and cosine at f_exc, then low-pass filter. The in-phase (I) channel captures the component aligned with excitation; the quadrature (Q) channel captures the 90° component. I/Q enables separation of solution-dominant behavior from interface/parasitic dominance, provided the reference is coherent and phase is calibrated.

Reference generation (avoid phase wander):
  • Coherent clocking: DAC excitation and demod reference must be derived from a shared clock domain or a shared NCO.
  • Phase stability: reference drift causes I↔Q leakage and makes Q unusable as a diagnostic.
  • Frequency accuracy: small frequency offsets broaden the effective demod bandwidth and raise noise.

The demod low-pass filter defines a tradeoff between noise and responsiveness. The effective noise in I is the analog front-end noise integrated over the PSD equivalent noise bandwidth (ENBW). A narrow ENBW reduces noise and improves resolution but slows update rate and transient response. For stable readings, ENBW must be chosen alongside the TIA noise and settling behavior rather than as a fixed digital default.


Evidence fields (must be recorded in validation and specs):

  • Demod filter: LPF cutoff, ENBW, update rate, and group delay
  • Phase calibration: procedure to minimize Q in a known resistive standard; stored phase offset and residual Q range
Step Action What to record
1) Choose standard Use a resistive reference condition (known standard solution or equivalent resistive load region). Standard ID, f_exc, amplitude, temperature.
2) Adjust phase Apply a phase offset to the demod reference until Q is minimized. Phase offset φ0, residual Q after calibration.
3) Lock settings Freeze ENBW/update rate and verify stability over time. ENBW, update rate, I/Q drift in the standard.
Lock-In PSD Signal Flow (I/Q) — Coherent, Bandwidth-Defined Reference coherence + ENBW + phase calibration makes I/Q interpretable and reproducible. Reference Generator Shared clock NCO @ f_exc Coherent with DAC ADC Stream Samples @ Fs From ΣΔ output split Multiply × sin(ref) Multiply × cos(ref) LPF ENBW Update rate LPF ENBW Update rate I Output in-phase Q Output quadrature Phase Calibration Adjust φ0 → minimize Q Record residual Q Evidence fields ENBW + update rate + φ0 calibration record → enables reproducible I/Q and comparable σ/ρ outputs.
Figure 6. Lock-in PSD flow. A coherent reference (shared clock or shared NCO), declared ENBW/update rate, and a recorded phase calibration (φ0 with residual Q) make I/Q stable, interpretable, and reproducible across builds.
Cite this figure: Lock-In Signal Flow (I/Q, ENBW, Phase Cal) — include ENBW, update rate, and φ0 calibration evidence.

H2-7. ΣΔ ADC Integration: Sampling, Notches, and “Quiet” Clocking

ΣΔ ADC configuration must be selected as part of the lock-in measurement system: coherence between f_exc and sampling, predictable group delay, and “quiet” clocking determine whether I/Q is stable and reproducible. High resolution alone does not guarantee phase-correct demodulation.

Coherent sampling plan (Fs vs f_exc) Group delay as an I/Q error budget item 50/60 Hz rejection strategy (avoid vs notch) Clock/ground coupling that mimics σ change

Coherence planning: ensure the demod reference and the sampled data stay phase-consistent across the observation window. This can be achieved by deriving excitation and demod reference from a shared clock/NCO and selecting an output data rate (ODR) that keeps the observation window aligned to an integer number of excitation cycles. If coherence is broken, energy leaks between I and Q, the effective demod bandwidth broadens, and apparent conductivity “noise” rises even in a stable standard.

Digital filter group delay: ΣΔ ADCs introduce deterministic group delay that depends on decimation and digital filter configuration. The delay itself is not harmful if it is constant and accounted for, but it becomes a phase error when configuration changes occur without re-calibration. Any change to ODR/decimation/filter should be treated as a phase-affecting change that requires I/Q validation or a refreshed phase calibration.

50/60 Hz rejection options:
  • Avoid harmonics: choose f_exc away from mains and low-order harmonics that commonly couple through grounding and cabling.
  • Leverage notches: select ΣΔ ODR/filter configurations that place deep attenuation near 50/60 Hz when mains coupling is unavoidable.
  • Prevent mixing: keep analog stages out of overload and avoid nonlinearity so mains does not fold into the demod band.

“Quiet” clocking and grounding: clock jitter and ground/clock coupling can masquerade as conductivity change by modulating phase and amplitude. This is most visible when excitation is derived from MCU timers while the ADC clock is sourced differently. A stable clock plan (shared reference, controlled jitter) and clean return paths reduce I/Q wandering and reduce false Q growth under mains interference.


What to measure (integration evidence):

Measurement How to run it Interpretation
I/Q under injected 50/60 Hz In a standard, introduce controlled mains coupling (routing/cable proximity or injected ripple) and log I/Q statistics. Reveals whether rejection is achieved by frequency choice, notches, and analog robustness; Q growth indicates phase/coupling issues.
Phase/jitter sensitivity Compare clock sources (MCU timer vs stable reference); measure I/Q variance and drift rate at fixed f_exc. Identifies when clock cleanliness is limiting; rising Q noise floor indicates phase noise leaking into demod outputs.
Config-change repeatability Change ODR/decimation/filter; verify that phase calibration still holds (Q remains bounded in resistive standard). Quantifies group-delay-driven phase shifts; triggers recalibration policy for firmware/config updates.
Coherent Sampling Map (Fs / ODR / Decimation vs f_exc) Place f_exc away from mains/harmonics or align rejection notches; keep clocking coherent and delay predictable. Frequency map Low High frequency 50/60 Mains zone f_exc band Notch integer cycles Sampling chain Fs / ODR Decimation Group delay phase impact I/Q accuracy needs recal if config changes Evidence to record Fs/ODR + decimation/filter + group delay + clock source + mains strategy (avoid/notch) + I/Q stability under injected 50/60 Hz. Any ODR/decimation/filter change → re-check Q in resistive standard and refresh phase calibration if needed.
Figure 7. Coherent sampling map. Place f_exc away from mains/harmonics or align rejection notches via ODR/filter choice. Track group delay as a phase budget item; configuration changes must trigger I/Q validation.
Cite this figure: Coherent Sampling Map (Fs, Decimation, Mains) — include group-delay-driven phase implications and injected 50/60 Hz stability evidence.

H2-8. Anti-Polarization Algorithms: Frequency Hopping, Duty Cycling, and Electrode Health

Anti-polarization is a closed-loop control problem: keep the electrode interface within a regime where measurements remain linear and reproducible. Beyond “use AC,” algorithmic actions such as duty cycling and frequency hopping reduce net charge accumulation and expose interface dominance early.

Duty-cycled excitation (charge balance) Frequency hopping / multi-point probing Polarization onset detection (I/Q + drift) Minimal device-side conditioning hooks

Duty cycling reduces the effective DC bias at the interface by alternating measurement windows with recovery windows. During the pause, interface charge relaxes and drift slope decreases. The tradeoff is update rate: recovery time and ENBW must be planned so that the reported value remains stable while the system avoids sustained polarization.

Frequency hopping (or lightweight multi-frequency probing) improves robustness because interface/parasitic contributions are more frequency-sensitive than solution resistance in the intended operating window. Comparing I/Q across two or three frequencies allows detection of curvature that indicates interface dominance, enabling compensation strategies or a controlled shift to a more stable band.

Detecting polarization onset (trigger examples):
  • Q growth or rising |Q|/|I| indicates increasing capacitive/interface dominance.
  • Drift slope (dI/dt or dσ/dt) rising in a stable standard indicates accumulating interface bias.
  • Impedance curvature across two/three frequencies suggests interface terms outweigh solution R.

Electrode health hooks (device-side only): when polarization indicators exceed thresholds, firmware can apply a short recovery action set: hop frequency, pause excitation, or reduce amplitude. If recovery time exceeds a declared maximum, the system flags an electrode health condition instead of silently reporting drifting conductivity.


Evidence fields (algorithm validation and logging):

  • Polarization index (PI): declared metric definition (e.g., PI = |Q|/|I|) and thresholds (warn/action/fault)
  • Recovery time: time for PI to fall below threshold after excitation pause
  • Action log: trigger reason → action taken (hop/pause/reduce) → measured improvement in I/Q
Polarization Mitigation Control Loop (PI → Actions → Recovery) Use I/Q-derived indicators to trigger hop/pause/reduce-amplitude actions and protect measurement integrity. Measurement I, Q drift slope 2–3 freq probe Compute PI PI = |Q|/|I| metric must be declared Decision Warn / Action / Fault Thresholds Recovery timer Actions Hop f_exc Pause Reduce Amp Health Flag Excitation f_exc Amplitude Duty Evidence fields PI definition + thresholds, recovery time after pause, and action logs (trigger → action → I/Q improvement). If recovery exceeds limit, report electrode health instead of drifting conductivity output.
Figure 8. Anti-polarization control loop. A declared polarization index (PI) drives threshold-based actions (hop, pause, reduce amplitude) and logs recovery time. This prevents silent drift and turns electrode behavior into an auditable subsystem.
Cite this figure: Polarization Mitigation Control Loop (PI → Actions) — include PI thresholds, recovery timing, and action logs.

H2-9. Calibration & Temperature Compensation: Turning Raw I/Q into σ or ρ

Calibration is the credibility layer: it converts stable, phase-correct I/Q into conductivity (σ) or resistivity (ρ) with traceable configuration, residual-error evidence, and an explicit confidence flag. A meter is only as reliable as its auditable calibration pipeline and its out-of-cal detection.

Two-point vs multi-point calibration (residuals) Cell constant K lifecycle (estimate, store, drift-track) Temperature compensation model selection Out-of-cal detection + confidence flag

Two-point vs multi-point calibration: two-point calibration can be adequate for a narrow operating range, but it provides limited visibility into curvature and does not produce a full residual map. Multi-point calibration across standards creates an error profile that can be stored and audited. This residual profile becomes the reference for detecting drift, contamination, or configuration changes that invalidate prior calibration.

Cell constant K estimation and storage: K is a system parameter influenced by cell geometry, electrode condition, and assembly variation. K should be stored with a versioned record (timestamp, excitation conditions, temperature reference) and tracked over time. When K drifts or when the cell signature changes (e.g., cable replacement or contamination), the system should downgrade confidence or declare out-of-cal rather than silently reporting shifted conductivity.

Temperature compensation (practical model choices):
  • Linear compensation: suitable for narrow temperature windows and stable solution types.
  • Polynomial / piecewise: used when wider temperature ranges or nonlinearity must be captured.
  • Standards-based mapping: preferred when traceability and cross-build consistency matter.

Out-of-cal detection: calibration should include explicit invalidation triggers. Common triggers include residual error exceeding thresholds across standards, day-scale drift slope rising beyond limits, PI/Q behavior indicating interface dominance, and leakage/cable signature shifts that indicate parallel conduction paths. These triggers feed a confidence flag that is output alongside σ/ρ.


What to measure (audit-grade calibration evidence):

Evidence How to run it What it proves
Residual map across standards × temperature Measure multiple standards at low/mid/high temperature points; log corrected σ (or ρ) vs reference values. Quantifies the usable region and validates the temp model; becomes the stored reference for confidence scoring.
Day-scale drift in a stable standard Hold a stable standard and log I/Q, temperature, final σ/ρ, and PI over hours-to-days. Separates interface aging/contamination/leakage from random noise; provides drift slope thresholds for out-of-cal.
K stability / signature consistency Re-estimate K at defined intervals or after maintenance; compare against stored K record under the same excitation conditions. Detects cell geometry/electrode state changes that invalidate calibration even if short-term readings appear stable.
Calibration Pipeline (I/Q → Z/Y → σ/ρ → Temp → Confidence) Versioned K + residual evidence + drift tracking makes the output auditable. Raw I/Q I, Q Corrections phase / gain Z / Y estimator K mapping σ or ρ Temp comp to Tref Final readout σ / ρ Confidence flag Calibration evidence Standards set ID Residual map (std × temp) Fit params + version K record K value + timestamp f_exc / amplitude Drift tracking Out-of-cal logic Residual thresholds Drift slope / PI Leakage / cable signature Audit rule Always store: calibration set + model version, K record, residual map, drift slope, and confidence flag reason codes. When evidence fails thresholds, output must downgrade confidence or declare out-of-cal.
Figure 9. Calibration pipeline. Raw I/Q becomes σ/ρ through correction, Z/Y estimation, K mapping, and temperature compensation. Stored residual maps, K records, and drift tracking feed a confidence flag and out-of-cal decision.
Cite this figure: Calibration Pipeline (σ/ρ + Confidence) — include residual map, K record versioning, drift slope, and out-of-cal reason codes.

H2-10. Error Budget & Design Validation: What Limits Accuracy (and How to Prove It)

An engineering-grade error budget is not a list of causes—it is a mapping from contributor → expected signature → validating test → pass/fail evidence. This section provides a vertical checklist that enables fast root-cause isolation when σ/ρ becomes unstable or biased.

Interface/polarization (frequency-dependent) Cable C / leakage / contamination (signature shifts) ADC noise + reference drift (amplitude error) Phase mismatch (I↔Q leakage) EMI + aliasing artifacts (mains/switching)

Polarization / interface error: typically worsens at lower excitation frequency and appears as rising Q contribution and phase curvature during sweeps. When interface terms dominate, the system may show stable-looking readings at one frequency but fail across frequency or over time.

Cable capacitance / leakage / contamination: cable length changes primarily affect the frequency-dependent quadrature behavior, while leakage and contamination introduce parallel conduction paths that shift I and drift with humidity. These effects can masquerade as true conductivity change unless signature tests are performed.

ADC noise and reference drift: set the amplitude accuracy and noise floor. Reference drift creates slow bias, while ADC noise integrated over demod ENBW sets the minimum resolvable change. These contributors often look like “random jitter” unless correlated with ENBW and reference telemetry.

Phase mismatch and EMI (common failure patterns):
  • Phase mismatch / jitter: I↔Q leakage; Q changes when configuration changes; “calibration passes but not repeatable.”
  • Mains / switching EMI: coherent ripple or discrete spurs that appear only under certain power states; can fold into the demod band if overloaded.

Validation plan (explicit, signature-driven):

Test What to look for (signature) What it confirms
Sweep f with one standard I/Q vs f shows phase curvature and Q growth at low f (polarization) or spurs/ripple near mains (EMI). Separates interface dominance from EMI/alias artifacts; identifies stable operating window for f_exc.
Swap cable lengths Length-sensitive Q/f behavior and phase shifts indicate cable capacitance dominance; leakage shows as offsets that track humidity. Confirms whether parasitic C or leakage is limiting; supports guarding, routing, and cable constraints.
Inject known RC load Recovered I/Q should match the expected reference; failures indicate phase calibration mismatch or algorithm/config inconsistency. Validates phase calibration, Z/Y estimator, and configuration repeatability.
EMI scenario test Change supply load/state and observe whether I/Q ripple correlates; alias artifacts appear as structured disturbances. Proves immunity to mains/switching pickup and identifies when analog anti-aliasing is insufficient.
Error Signatures Atlas (I/Q Clues) Use signature patterns to pick the right validation test and isolate the limiting contributor. Polarization (low-f worse) Leakage / Contamination Cable C (length sensitive) Phase mismatch / Jitter f f f f Q↑ I stable offset humidity long short I ↔ Q leakage config change → Q jumps phase drift I Q Signatures are simplified patterns; confirm with sweep/RC/cable/EMI tests.
Figure 10. Error signatures atlas. Each panel shows a simplified I/Q pattern that points to a likely limiting contributor. Use these signatures to select the right validation test and to produce auditable root-cause evidence.
Cite this figure: Error Signatures Atlas (Polarization / Leakage / Cable C / Phase) — use it to map observed I/Q behavior to the corresponding validation test.

H2-11. Protection, EMC, and Real-World Cabling: Survive the Field Without Reading Ghost EC

Field robustness must not corrupt high-impedance measurement integrity. Protection and EMC components are only “correct” when they meet two proofs: (1) low-leakage behavior across humidity/contamination, and (2) minimal phase distortion near the excitation band so I/Q remains valid.

ESD at connector without leakage paths Shield + guard routing rules RC/EMI filtering that preserves phase Isolation only when required

1) Connector-side ESD strategy (placement & return path): place ESD parts at the probe connector so discharge current closes locally to chassis/shield ground. Keep the ESD loop short and wide. Avoid placing clamp devices on the high-Z node side of the front-end; that creates humidity-sensitive leakage paths that look like real conductivity.

  • Rule: ESD parts belong on the “connector side” of any series impedance, not inside the guarded high-Z region.
  • Rule: add a small series resistor (or RC) only if the phase impact at f_exc is verified (see section 4).
  • Rule: dedicate a chassis/shield return for ESD; do not force ESD current through analog ground traces near the TIA/high-Z input.

2) Leakage control (the root cause of “ghost EC”): the meter reads “ghost EC” when an unintended parallel conduction path forms at the connector surface, ESD device leakage, PCB contamination, or cable insulation moisture. These paths are often humidity- and cleanliness-dependent, and they can dominate the measurement even when noise looks low.

Leakage minimization checklist:
  • Guard ring: surround the high-Z node and route a guard trace around the connector-side sensitive nets.
  • Keep-clean zone: no flux residue, no solder mask cracks, no “TVS islands” near the high-Z node.
  • Material choices: prefer low-absorption connector housings and avoid porous coatings in the sensitive region.

3) Shielding vs driven guard (different goals): shielding reduces external electric-field pickup; driven guard reduces parasitic current (cable/PCB capacitance and surface leakage) by keeping the guard conductor near the same potential as the high-Z node. Mis-terminating shield can inject mains/common-mode currents and increase I/Q ripple.

  • Shield termination: start with single-end termination to chassis/shield ground at the meter, then validate with the A/B noise test.
  • Driven guard: use when cable length/high humidity makes parasitics dominant; verify guard stability and phase impact.

4) Input RC / EMI filtering without phase damage: any RC pole near the excitation band introduces phase rotation that changes I/Q projection. Filters must be designed and verified so the transfer function is “flat enough” (both amplitude and phase) across the excitation band and demod bandwidth. Over-filtering can reduce EMI but silently break calibration.

Filter placement rule: put EMI filters on the connector side where possible, and keep the high-Z node inside a guarded, minimal-component region. If a filter must touch the high-Z domain, use low-leakage dielectrics (e.g., C0G/NP0) and validate phase.

5) Isolation (only when required): isolation is justified when safety regulations demand it, when large common-mode differences exist between probe and meter, or when ground loops cannot be controlled by shield/return design. Keep scope meter-side: isolation is a boundary to cut common-mode currents, not a full power-supply design topic here.


What to measure (field survivability without ghost EC):

Measurement How to run it What it proves
Connector leakage vs humidity Hold a stable standard (or equivalent resistor), vary humidity/cleanliness state, log I/Q and σ. Measure leakage proxy (offset shift / drift slope). Separates true conductivity change from parallel leakage paths; sets out-of-cal thresholds and confidence downgrade triggers.
Shield A/B noise-floor test With identical setup, toggle shield termination (connected/disconnected) and log I/Q noise floor and mains ripple. Confirms shield termination strategy; identifies ground-loop injection and common-mode coupling issues.
Phase integrity near f_exc Sweep around the excitation band with a known stable load; compare I/Q with and without connector-side RC/EMI network. Verifies that protection/filtering does not distort phase or cause I↔Q leakage that breaks calibration.

Concrete MPN examples (meter-side, low-leakage oriented):

Function MPN examples Why used here (design intent)
Low-cap ESD clamp (connector) TI TPD1E10B06
Nexperia PESD5V0S1UL
Semtech RClamp0502B
Fast transient clamping close to the connector; keep clamp leakage and capacitance low and keep return to chassis/shield short.
Secondary “spark” diverter Bourns CG0603MLC-05E (MLV family example)
Littelfuse 0603L series ESD suppressor family example
Optional first-line surge/ESD energy shunt on the connector edge; avoid placing such parts inside the guarded high-Z region.
Series resistor (ESD current limiting / RF damping) Vishay Dale thin-film TNPW0603 series (value per design)
Yageo thin-film RT0603 series (value per design)
Helps reduce ESD current into the AFE and damps RF; thin-film reduces excess noise and improves stability. Validate phase impact at f_exc.
EMI shunt capacitor (phase-safe dielectric) Murata C0G GRM18/GRM21 C0G series (value per design)
TDK C0G CGA series (value per design)
C0G/NP0 minimizes dielectric absorption and leakage variability; place on connector side if possible; confirm no phase distortion near band.
Ferrite bead (HF noise, not phase-band shaping) Murata BLM18/BLM21 series (impedance per design)
TDK MPZ series (impedance per design)
Targets high-frequency EMI; choose so it does not create a pole/phase rotation near f_exc. Validate with sweep test.
Driven guard buffer (when needed) Analog Devices ADA4530-1 Electrometer-grade input with guard drive capability; used to drive guard traces/cables to reduce parasitic currents in high-Z sensing.
Digital isolation (when required) Analog Devices ADuM141E / ADuM1250
Silicon Labs Si86xx family
Cut ground loops and meet safety constraints for control/communications. Apply only when required; keep isolation boundary clean and auditable.
Shieldable probe connector (examples) Amphenol BNC family (meter-side coax)
TE Connectivity M12 shielded family (industrial probe)
Connector choice impacts shielding continuity, leakage risk, and robustness. Use shielded shells and define chassis termination explicitly.
Connector + Guard + Shield Map (Leakage & Phase Safe) ESD returns to chassis; keep high-Z inside a guarded clean zone; filters must not rotate phase near f_exc. Connector edge High-Z clean zone Shield / Guard routing Probe Connector SIG HI / LO Shield / Chassis ESD TPD / PESD RC C0G High-Z node to TIA / AFE Guard ring KEEP CLEAN no TVS here Leakage Leakage Shield terminate single-end Driven guard ADA4530-1 RC/EMI do not rotate phase near f_exc Evidence to record Leakage vs humidity, shield A/B noise floor, and phase sweep around f_exc with/without connector-side RC/ESD network. Any protection change → re-check I/Q stability and calibration confidence.
Figure 11. Connector + guard + shield implementation map. ESD returns to chassis at the connector edge; high-Z sensing stays inside a guarded clean zone; RC/EMI networks are validated to preserve phase near the excitation band.
Cite this figure: Connector + Guard + Shield Map (Leakage & Phase Safe) — include leakage/humidity evidence and shield A/B noise results.

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

H2-12. FAQs (Evidence-Driven, No Scope Creep)

Each FAQ is a fast triage route: a one-sentence diagnosis, two concrete measurements, one minimal first fix, and a link back to the relevant chapter. The goal is to capture long-tail queries while keeping every answer meter-side and evidence-based.

Short answer (1 sentence) What to measure (2 bullets) First fix (1 bullet) Back-link to a chapter
FAQ Evidence Router Symptom → evidence fields → minimal first fix → link to the right chapter. Symptoms Drift / wobble Long cable unstable Motor / EMI event Saturation / near-zero Probe mismatch Evidence fields Excitation f_exc / Vrms / waveform I/Q + phase Q growth / ENBW ADC / clock Fs / decimation / notch Analog TIA headroom / stability Cabling / leakage length / shield / humidity Calibration K / residual / temp model Minimal first fixes Move f_exc Tighten ENBW Shield A/B Re-check phase Verify K/residual Rule: every FAQ must name at least two evidence fields and one minimal first fix, then link back to a chapter for the full method.
Figure 12. FAQ Evidence Router. Symptoms map to evidence fields (excitation, I/Q, ADC/clock, analog, cabling/leakage, calibration), then to a minimal first fix and the chapter that contains the full procedure.
Cite this figure: FAQ Evidence Router (Symptom → Evidence → First Fix) — use it to keep troubleshooting meter-side and evidence-driven.

Reading drifts upward over minutes—polarization or reference drift?
Short answer

If Q (or a polarization index) grows while reference telemetry stays steady, polarization dominates; if both I and reference drift together, suspect reference/ADC drift.

What to measure
  • Log I, Q over time in a stable standard; watch Q growth and drift slope.
  • Log reference/ADC health proxies (e.g., reference voltage readback, internal temperature) and correlate with I drift.
First fix
  • Increase f_exc slightly and/or enable duty-cycled excitation to reduce net charge while re-checking drift.
Back: H2-3 · H2-7 · H2-8
Stable in lab, unstable with long cable—capacitance or leakage?
Short answer

If changing cable length mainly changes Q and frequency dependence, cable capacitance dominates; if behavior is humidity/touch sensitive, leakage is the likely cause.

What to measure
  • Compare I/Q with short vs long cables at the same f_exc; look for Q/f shifts.
  • Run a humidity/cleanliness A/B test at the connector and observe offset/drift changes.
First fix
  • Enable shield A/B and verify leakage control (guard + keep-clean zone) before changing algorithms.
Back: H2-5 · H2-10 · H2-11
EC changes when nearby motor starts—EMI pickup or aliasing?
Short answer

If the disturbance correlates with motor state and shows discrete ripple/spurs, EMI pickup is likely; if changing Fs/decimation shifts the artifact, suspect aliasing into the demod band.

What to measure
  • Log I/Q ripple and mains components with motor ON/OFF; check repeatability.
  • Change Fs/decimation/notch and see whether the wobble frequency/shape moves.
First fix
  • Adjust notch planning and improve connector-side shielding/returns, then re-check I/Q stability.
Back: H2-7 · H2-11
Quadrature (Q) is large even in standard solution—phase error or interface dominance?
Short answer

If Q can be nulled with a known resistive load but returns with configuration changes, phase alignment is the issue; if Q grows strongly at low f, interface dominance is more likely.

What to measure
  • Inject a known pure-R test load (or stable standard at a proven frequency) and run phase-zero calibration.
  • Sweep f_exc and track Q/I versus frequency to identify low-f interface behavior.
First fix
  • Re-run I/Q phase calibration with coherent reference generation and confirm group delay consistency.
Back: H2-6 · H2-9
Low conductivity reads zero-ish—noise floor or insufficient excitation amplitude?
Short answer

If increasing Vrms increases I with stable Q and improves repeatability, excitation was too small; if I remains buried and scales with ENBW, the noise floor is limiting.

What to measure
  • Step Vrms (within safety limits) and check whether I increases proportionally above the noise floor.
  • Change ENBW (LPF cutoff / averaging) and see how σ/ρ variance scales.
First fix
  • Increase Vrms modestly and/or tighten ENBW while verifying no polarization growth.
Back: H2-4 · H2-5 · H2-10
High conductivity saturates—TIA headroom or ADC range?
Short answer

If the TIA output clips or slews before the ADC rails, it is headroom/stability; if ADC codes hit full-scale with clean analog, the ADC range (or scaling) is the limiter.

What to measure
  • Probe TIA output waveform for clipping/ringing when conductivity is high.
  • Monitor ADC codes for rail hits while keeping excitation constant.
First fix
  • Reduce effective transimpedance (e.g., lower Rf or add a controlled range switch) and re-check phase stability.
Back: H2-5 · H2-7
Different probes disagree—cell constant mismatch or electrode aging?
Short answer

If each probe is internally consistent but offset from others, K mismatch is likely; if the same probe drifts or shows growing Q/PI over time, electrode aging/contamination is more likely.

What to measure
  • Compare stored K records (versioned) and residual maps for each probe in the same standard.
  • Track drift slope and Q/PI over time to detect interface changes.
First fix
  • Re-estimate K with a standard set and store a new version, then verify residual consistency.
Back: H2-2 · H2-9
Temperature compensation makes it worse—wrong model or sensor placement?
Short answer

If the residual error changes shape across temperatures, the model is wrong; if error correlates with thermal lag or gradients, temperature sensing placement/lag is the likely cause.

What to measure
  • Create a residual map (standard × temperature) and compare against the compensation model output.
  • Measure temperature lag by stepping temperature and comparing sensor readout vs stabilization of I/Q.
First fix
  • Temporarily disable compensation for A/B, then switch to a safer model (or re-fit) and re-validate the residual map.
Back: H2-9
After cleaning, readings jump—surface chemistry change or calibration invalid?
Short answer

If Q/PI signature changes after cleaning, the interface changed; if K/residual verification fails, treat it as calibration invalid until re-checked.

What to measure
  • Compare Q/PI and drift slope before vs after cleaning in the same standard.
  • Run a quick residual check against a known standard and compare to stored residual thresholds.
First fix
  • Run a short recovery routine (pause/duty-cycle or f hop) and then re-check K/residual.
Back: H2-8 · H2-9
Mains hum shows up as periodic EC wobble—frequency planning or filtering?
Short answer

If the wobble is locked to 50/60 Hz (or harmonics), frequency planning/notches are the first suspects; if it persists across planning changes, revisit filtering and shielding/returns.

What to measure
  • Measure I/Q ripple amplitude at 50/60 Hz and harmonics during a stable standard test.
  • Change f_exc and ADC notch/decimation settings and check whether the wobble disappears or shifts.
First fix
  • Move f_exc away from mains harmonics and enable/validate a 50/60 Hz notch while confirming phase integrity.
Back: H2-4 · H2-7
Sudden spikes during stirring—bubbles/flow artifacts or poor averaging?
Short answer

If spikes are brief with fast recovery and correlate with agitation events, bubbles/flow artifacts dominate; if variance scales strongly with ENBW, averaging/demod bandwidth is too wide.

What to measure
  • Log time-series I/Q and identify spike duration and recovery time constants.
  • Run an ENBW sweep (LPF cutoff/averaging) and observe how σ variance scales.
First fix
  • Add a simple outlier gate (clip/median) and tighten ENBW, then re-check step response and stability.
Back: H2-6 · H2-10
Why does AC square wave give different results than sine?
Short answer

A square wave contains harmonics; if the analog chain and PSD reference do not reject/handle harmonics consistently, the demod sees a different effective impedance and phase than a pure sine.

What to measure
  • Compare results under sine vs square at the same fundamental f_exc; record changes in I/Q and spurs.
  • Verify analog bandwidth/filters and PSD reference coherence so harmonics do not fold into the demod band.
First fix
  • Use sine for metrology mode, or explicitly define a square-wave protocol (fundamental-only demod + verified filtering) and re-calibrate.
Back: H2-4 · H2-6