123 Main Street, New York, NY 10001

IVD Electrochem Reader: Potentiostat & Low-Noise ADC Design

← Back to: Medical Electronics

An IVD electrochemical reader becomes repeatable only when the potentiostat/galvanostat control, low-noise current readout, temperature compensation, and calibration work as one closed loop. This page explains how to stabilize WE–RE control and convert micro-current signals into reliable results with clear error budgets and reject/retest gates.

H2-1 · What this page solves

Unstable electrochemical readings are usually caused by a mix of electrode/connector variability, temperature drift, micro-current noise, leakage or bias currents, reference drift, and missing calibration closure.

Key takeaway: Control the electrode potential/current, digitize with a low-noise chain, compensate temperature effects, and close calibration loops to keep chemistry-driven variation within a predictable error budget.

  • Interface variability: electrode contact and strip-lot spread change the raw signal.
  • Temperature drift: reaction kinetics and analog drift shift results across environments.
  • Micro-current integrity: noise, leakage, and bias currents can look like real signal.
  • Reference & calibration: Vref and gain/offset drift require verification and correction.
Figure F1 — IVD electrochem reader signal chain for stable results Block diagram from disposable strip electrodes (WE/RE/CE) into potentiostat AFE with control loop and TIA, then low-noise ADC and MCU/algorithm with calibration and temperature compensation to output a stable result. Disposable strip → AFE control + readout → Low-noise digitization → Compensation → Result (Minimal text, block-level view for design planning) Strip WE RE CE Connector ESD Protection Potentiostat AFE Control loop Bias DAC + RE sense CE drive + compliance TIA readout Micro-current → voltage Range + stability Vref + self-check hooks Low-noise ADC Digitize noise floor Timing Vref MCU / Algo Filtering quality checks Calibration offset / gain Temp comp model / LUT Stable Result F1: Strip → WE/RE/CE → Potentiostat AFE (control + TIA) → ADC → MCU (calibration + temperature compensation) → Result
Figure F1 — A compact “stability chain” view: control the electrochem conditions, digitize with low noise, then correct with temperature + calibration loops.

H2-2 · System architecture: from strip to digital results

A typical reader pipeline is: strip connector and protection → potentiostat + TIA analog front end → ADC digitization → MCU algorithms → calibration and temperature compensation → final reported value.

For multi-test strips or multi-channel designs, channel multiplexing must be treated as part of the measurement chain: switch leakage, charge injection, and settling behavior can directly corrupt micro-current accuracy unless timing and layout are planned at the AFE and sampling level.

Practical rule: treat every block boundary as a measurable error entry point (leakage, noise, drift, or interference), then decide where compensation, verification, and re-check criteria belong.

Figure F2 — Multi-channel front end with sampling risks and optional isolation boundary Diagram showing multiple strip channels feeding an analog MUX into potentiostat/TIA AFE, then ADC and MCU. Risk markers highlight leakage/crosstalk/settling at the MUX and AFE interfaces, with a dashed optional isolation boundary label (system-dependent) for awareness only. Multi-channel architecture (AFE + sampling focus) MUX leakage / crosstalk / settling → AFE integrity → ADC timing → calibration + temperature correction Channels Strip A WE RE Strip B WE RE Strip C WE RE Analog MUX Leakage Charge inj. Settling Timing Potentiostat + TIA Control integrity Micro-current readout noise / drift / leakage ADC + MCU Digitize Calibration Temp comp Optional isolation boundary ! crosstalk leakage F2: Multi-channel view highlights MUX leakage/settling risks; isolation boundary is labeled only (system-dependent).
Figure F2 — Multi-channel front-end planning: treat MUX behavior and settling time as first-class error sources, then place calibration + temperature correction in the data path.

H2-3 · Measurement modes: why potentiostat vs galvanostat

Electrochemical readers mainly operate in two control modes. The correct choice starts by deciding what must be controlled (potential or current) and what must be observed (current or potential) to extract a stable, repeatable signal.

Potentiostat: hold V(WE–RE) and measure I(WE).

Most quantitative electrochem sensing uses a potentiostat because the reaction condition is defined by a controlled electrode potential.

Galvanostat: force I(WE) and observe V(WE–RE).

Used when a controlled current stimulus is preferred and the voltage response carries the diagnostic feature.

Two-electrode setups mix control and measurement paths, so electrode polarization and series drops are harder to separate. Three-electrode setups (WE/RE/CE) split the control actuator (CE) from the measurement reference (RE), improving stability and repeatability.

  • Current range & resolution: smallest measurable signal and maximum expected current.
  • Compliance: ability to maintain the target condition under worst-case electrode impedance.
  • Potential window: required scan/hold range for the chemistry.
  • Stabilization time: settling after switching channels, steps, or scan updates.
Figure F3 — Potentiostat and galvanostat control loops Two side-by-side loops. Left shows potentiostat mode controlling V(WE-RE) using a DAC and control amplifier driving CE, measuring WE current through a TIA and digitizing with an ADC. Right shows galvanostat mode forcing WE current using a current DAC/source, measuring V(WE-RE) via RE sense and ADC. Labels highlight controlled vs measured quantities. Measurement modes: controlled quantity vs measured quantity Left: Potentiostat (control V) · Right: Galvanostat (control I) Potentiostat CONTROL: V(WE–RE) MEASURE: I(WE) Bias DAC Control Amp Electrode Cell WE RE CE RE Buffer TIA ADC Galvanostat CONTROL: I(WE) MEASURE: V(WE–RE) Current DAC or source Electrode Cell WE RE CE RE Buffer ADC F3: Potentiostat controls V(WE–RE) and measures I(WE); galvanostat controls I(WE) and measures V(WE–RE).
Figure F3 — The mode decision is a “control vs observe” choice: hold electrode potential to read current, or force current to read voltage response.

H2-4 · Potentiostat AFE design: keeping the potential loop stable

A potentiostat is a closed-loop control system. It compares a target potential to the sensed V(WE–RE), then drives CE to correct the cell. Stability and repeatability depend on three practical questions: can the loop hold the target under worst-case impedance (compliance), will it oscillate (stability), and will it recover from faults (robustness).

  • Loop building blocks: bias DAC (setpoint), control amplifier, high-impedance RE buffer, and a CE driver with enough swing/current.
  • Compliance voltage: when electrode/electrolyte impedance rises, the CE driver must still have headroom to maintain the target V(WE–RE); otherwise the loop saturates and the “controlled” condition is lost.
  • Stability & compensation: the cell behaves like a frequency-dependent load (often modeled with R and C). Phase lag can destabilize the loop unless bandwidth and compensation are planned.
  • Protection-aware design: open/short electrodes, plug-in transients, and ESD clamps can shift node impedances; protection must not unintentionally break loop stability.

Common compliance symptom: the CE output rails, V(WE–RE) drifts away from the setpoint, and the measured current no longer represents the intended reaction condition.

Figure F4 — Cell equivalent model and where compensation acts in a potentiostat loop Diagram shows a potentiostat loop with DAC setpoint, control amplifier and CE driver acting on an electrode cell modeled as R||C. Markers indicate compensation locations: RC in amplifier feedback, damping at CE output, and bandwidth limiting at RE buffer. A small note warns that excessive bandwidth can increase noise and instability. Potentiostat loop stability: cell model + compensation points Cell load behaves like R || C → phase lag → compensation + bandwidth planning Setpoint & Control Bias DAC Control Amplifier Error: target − V(WE–RE) Comp RC @ amp feedback CE Driver Swing + current = compliance Damping @ CE output Electrode Cell (model) WE RE CE R C R || C → phase lag RE Buffer BW limit @ RE sense Excess bandwidth → more noise + higher risk of instability (set bandwidth to the chemistry + settling need)
Figure F4 — Model the cell as a frequency-dependent load (R||C). Then place compensation at the amplifier/CE output and limit RE-sense bandwidth to avoid oscillation while meeting settling needs.

H2-5 · Current readout chain: TIA + ADC — How to measure micro-currents precisely and stably

A low-noise TIA with high input impedance, followed by an ADC with accurate sampling, forms the core of precise micro-current measurements. The performance of this readout chain depends on proper TIA selection, handling leakage currents, dynamic range management, and filtering.

TIA Selection: Feedback resistors define the range and noise; capacitors determine bandwidth and stability.

Proper selection of feedback components is crucial for achieving the required accuracy while minimizing noise.

Leakage & Bias Current: Separating the “real current” from “false current.”

Guarding, material choice, and layout principles help mitigate leakage and bias current effects, ensuring accurate measurements.

  • Dynamic Range: Multi-range auto-switching (Rf bank + switch) and transient switching management.
  • Front-end filtering: Power line (50Hz/60Hz) and switching noise enters the signal path; low-pass/digital filter boundaries.
Figure F5 — Multi-range TIA (Rf bank) + ADC sampling point + digital filter position Diagram showing multi-range TIA using Rf bank with switch, ADC sampling points, and digital filter placement for noise suppression. Multi-range TIA, ADC sampling, and digital filtering Rf bank switching and front-end filtering placement for optimal current readout. Multi-range TIA Rf Bank Rf Switch Input Leakage Guard, Materials & Layout ADC Low-pass Filter Digital Filtering ADC Sampling Digital Filter F5: Multi-range TIA (Rf bank) switching, ADC sampling, and filtering placement for optimal micro-current accuracy.
Figure F5 — Multi-range TIA with Rf bank, ADC sampling, and front-end digital filtering designed for low-noise, accurate current readout.

H2-6 · Low-noise ADC choices: ΣΔ vs SAR — How to select the right one

Choosing the correct ADC is essential for ensuring measurement accuracy. ΣΔ ADCs excel at low-frequency noise performance, making them ideal for high-resolution, slow-variable measurements. SAR ADCs offer superior transient capture, making them better suited for applications requiring rapid response or pulse measurements.

ΣΔ ADC: Superior low-frequency noise rejection and anti-50/60Hz noise performance.

Best suited for slow-variable measurements and high-resolution applications.

SAR ADC: Better transient capture and faster sampling speeds.

Ideal for applications requiring quick response times or pulse measurements.

  • Resolution vs Bandwidth: Choose based on measurement speed and signal type.
  • Power consumption vs Speed: SAR ADCs are typically more power-efficient but offer limited bandwidth.
  • Reference noise coupling: External Vref or internal reference choice impacts measurement noise directly.
ADC choice: Sigma-Delta vs SAR for electrochemical readout A decision-style block diagram comparing sigma-delta and SAR ADC paths, highlighting resolution/bandwidth, reference noise coupling, and anti-alias filtering. ADC choice: ΣΔ vs SAR Decide by bandwidth, low-frequency noise, reference scheme, and settling needs Requirements Resolution / ENOB micro-current noise floor Bandwidth scan speed / pulses Power / Cost battery + BOM targets Reference strategy Vref noise → result noise buffer / routing / filtering Key question Is low-freq noise dominant or fast transient capture? ΣΔ ADC path Low-freq noise win 50/60 Hz rejection Best for slow signals settling-driven updates SAR ADC path Fast transient capture scan / pulse / step Needs AA filter front-end RC + layout Reference noise coupling Vref + buffer + RC → ADC codes keep it quiet and stable Rule: match bandwidth to chemistry + settling; do not let Vref noise dominate the reading
Figure F6 — Choose ΣΔ when low-frequency noise / 50–60 Hz rejection dominates; choose SAR when fast steps or scans require transient fidelity and a clean anti-alias path.

H2-7 · Temperature sensing & compensation: A closed loop of algorithm + hardware

Temperature compensation is crucial to ensure accurate measurements in electrochemical sensing. The temperature sensor placement (near reaction area or on the PCB) and the model used for compensation play a critical role in the stability and repeatability of the readings.

Where to measure temperature: Near reaction area vs near PCB (different error sources).

Measurement near the reaction area captures the direct effect of temperature changes on the reaction rate, while PCB-based measurements are more affected by environmental changes and are easier to implement.

Compensation models: Linear coefficients, LUT, and piecewise models.

Various models can be used for compensation, such as linear coefficients, lookup tables (LUT), or piecewise models to adjust for temperature-induced errors in current, reaction rate, and zero-point drift.

  • Temperature & current sampling synchronization: Synchronizing the sampling of temperature and current measurements is critical to avoid errors due to delayed compensation.
Temperature sensing and compensation loop Block diagram showing temperature sensor placement, synchronized sampling, model/LUT compensation, calibration entry, and corrected output. Temperature compensation loop Sensor placement + sync sampling + model/LUT + calibration entry Where to sense Near reaction zone captures chemistry temp Near PCB tracks ambient + board drift Temp sensor I²C / ADC / diode timestamped sample Sync sampling Current sample Temp sample Compensation engine Model / LUT linear / piecewise Calibration entry coeffs + lot params Corrected result compensated code confidence flags Sync temp + current sampling; avoid “compensation delay” that turns into measurement error
Figure F7 — Temperature compensation is a closed loop: sense → time-align → model/LUT → calibrated coefficients → corrected output.

H2-8 · Calibration strategy: Making repeatability scalable for production

Calibration is the key to transforming repeatability into mass-production capability. This chapter outlines the calibration hierarchy, from factory calibration to runtime self-testing, ensuring consistent performance across units.

Factory calibration: Gain, offset, and reference calibration during production.

Ensures each unit has a known baseline performance, adjusting for any systematic variations.

Runtime self-test: Zero-check and known current injection for in-field self-testing.

Self-tests help ensure that the device continues to meet performance standards throughout its operational life.

  • Lot-level calibration: Calibration parameters are linked to the lot code/barcode for traceability.
  • Drift management: Monitoring drift in reference, Rf, and leakage currents over time, with self-test thresholds for periodic checks.
Calibration data flow: factory, lot, runtime self-test Block diagram showing calibration hierarchy from factory calibration to lot adjustments and runtime self-test checks, with NVM storage and algorithm usage. Calibration data flow Factory → Lot → Runtime self-test (data goes into algorithms, not UI flows) Factory Lot Runtime Gain / Offset TIA + ADC chain Reference trim Vref + buffer path Store to NVM CRC / ECC metadata Lot code barcode / ID Lot parameters into algorithm inputs Apply correction gain/offset/curve Zero check baseline validity Known current inject self-test threshold Update flags pass / warn / fail NVM (calibration store) factory coefficients lot + runtime logs Production repeatability = factory baseline + lot correction + runtime self-test gates
Figure F8 — Calibration data enters algorithms through a clear hierarchy: factory coefficients, lot parameters, and runtime self-test flags.

H2-9 · Error budget & robustness: Quantifying the problems ahead

Properly quantifying errors is crucial to design reliable electrochemical measurement systems. This section covers the main error sources, from noise to system-level inaccuracies, and provides strategies to mitigate their impact.

Noise: TIA thermal noise, op-amp voltage/current noise, ADC quantization/reference noise.

Noise directly affects measurement accuracy. To reduce it, select low-noise TIA and op-amps, use high-resolution ADCs, and ensure a stable reference voltage.

System errors: Bias/leakage currents, thermal drift, contact resistance changes, electrode polarization, EMI injection.

These system errors impact measurement precision and reliability. Design countermeasures like shielding, proper grounding, and temperature compensation to address them.

  • Result reliability: Abnormal detection (open/short, out-of-range, instability, temperature out of bounds), and “reject/retest” strategy (criteria only, not medical process).
Error budget map: sources to observables to countermeasures A three-column mapping from error sources to measurable symptoms and engineering countermeasures, including reject/retest criteria. Error budget & robustness map Error sources → observables → countermeasures (with reject/retest rules) Error sources Observables Countermeasures Noise (TIA/op-amp/ADC/Vref) Bias / leakage Thermal drift Contact resistance Electrode polarization Baseline offset Gain error / scale Excess variance Instability / oscillation Out-of-range flags Filter + bandwidth plan Guard + clean layout Temp comp + LUT Contact detect (open/short) Reject / Retest rule Use observables to gate reliability: open/short, instability, temp out-of-bounds → reject or retest
Figure F9 — Error budgeting becomes practical when each error source maps to measurable symptoms and clear countermeasures (plus reject/retest criteria).

H2-10 · IC & block checklist: Dimensions for IC selection

This section defines the key dimensions for selecting integrated circuits (ICs) and blocks in potentiostat/AFE designs, covering aspects like noise, drift, and power supply ranges. Each component is essential for ensuring system stability and accuracy.

Potentiostat/AFE: Input bias, output swing, noise, drift, and power supply range.

Proper selection ensures that the potentiostat or AFE performs optimally within the designed voltage range and meets noise performance standards.

ADC: Resolution, ENOB at low frequency, reference scheme, sampling rate.

Choosing the right ADC ensures accurate measurement by selecting the appropriate resolution, low-frequency performance, and sampling speed.

  • Reference: Noise, drift, and load capability.
  • DAC: Monotonicity, noise, output range/buffering.
  • Analog switch/MUX: Leakage, charge injection, Ron flatness.
  • Temp sensor: Accuracy, location, interface.
  • NVM: Calibration data reliability (ECC/write life).
  • Power: Low-noise LDO/power filtering (AFE power supply cleanliness only, not isolation).
IC & block checklist for IVD electrochemical readers Checklist-style block diagram for key IC blocks (AFE, ADC, reference, DAC, mux, temp, NVM, power) with example part numbers. IC & block checklist (examples) Pick by bias/noise/drift/leakage; examples are for sourcing reference, not a mandate Potentiostat / AFE bias • swing • drift Examples ADuCM355 AD5940 LMP91000 ADC ENOB@LF • rate • Vref Examples ADS124S08 AD7124-4 ADS8860 (SAR) Reference noise • drift • load Examples ADR4550 REF5050 MAX6126 DAC mono • noise • range Examples AD5686R DAC8562 Analog MUX leak • inj • Ron flat Examples ADG1208 TMUX1108 Temp sensor accuracy • placement Examples TMP117 MAX31875 NVM ECC/CRC • endurance Examples FM24CL64B (FRAM) AT24C64 (EEPROM) Power (AFE) low noise LDO Examples TPS7A49 ADP7118 Checklist first, part numbers second: bias/leak/noise/drift must match the electrochem range and calibration plan
Figure F10 — IC & block checklist with example part numbers for quick sourcing reference (final selection should follow the defined electrical requirements and calibration strategy).

Request a Quote

Accepted Formats

pdf, csv, xls, xlsx, zip

Attachment

Drag & drop files here or use the button below.

H2-11 · FAQs – IVD Electrochem Reader

These FAQs focus on potentiostat/galvanostat measurement, low-noise readout, temperature compensation, calibration, and robustness gates for repeatable IVD electrochemical results.

1) Where is the real boundary between potentiostat and galvanostat?
Choose a potentiostat when the requirement is a controlled WE–RE potential and the measured quantity is current (typical strip readers). Choose a galvanostat when the requirement is a forced current and the observed quantity is potential, often to probe impedance-like behavior or controlled polarization steps. The practical boundary is set by what must be “held constant,” plus settling time and compliance headroom under cell impedance changes.
2) When is a 2-electrode setup acceptable, and when is 3-electrode required?
A 2-electrode setup can be acceptable when repeatability requirements are modest and electrode polarization/lead resistance are stable enough that control and sensing can share the same path. A 3-electrode setup is preferred when the WE–RE control voltage must stay accurate while current varies, because RE sensing is separated from CE drive. If cell impedance and polarization drift noticeably across samples, 3-electrode control usually improves stability and reduces “mystery” offsets.
3) Why is zero calibration often more important than using a higher-resolution ADC?
If baseline offset is dominated by leakage, input bias, contamination, or contact effects, a higher-resolution ADC only measures the wrong baseline more precisely. Zero calibration removes the largest systematic component first, so the remaining noise floor is what the ADC must resolve. A good rule is: when offset drift over temperature/time is comparable to the signal of interest, prioritize zero checks and self-test gating before increasing ADC bits.
4) How can multi-range Rf switching avoid transient misreads?
Treat range switching as a transient event: charge injection, op-amp recovery, and digital filters can create short “ghost” peaks. Use a blanking window after each switch, then require stability (variance/settling) before accepting data. If possible, confirm with two consecutive samples (or two filter frames) within a tolerance band. Also ensure the MUX/switch leakage and Ron do not create a false baseline in the most sensitive range.
5) Should temperature compensation be applied to current or to the final concentration?
Compensate at the layer where temperature creates the dominant error. If temperature mainly shifts the electrochemical reaction rate or sensor chemistry, compensation often belongs closer to the final conversion model (result domain). If temperature mainly shifts the electrical chain (Rf drift, bias/leakage, reference drift), compensation belongs earlier (current/code domain). In practice, systems frequently use both: early correction for electrical drift plus a final model/LUT for chemistry behavior.
6) How does reference noise become reading noise, and what is the most ignored path?
ADC codes are scaled by Vref, so any Vref noise inside the measurement bandwidth directly modulates the output code. The most ignored path is the “reference distribution chain”: reference buffer load steps, routing pickup, and inadequate RC filtering near the ADC reference pins. Treat Vref like an analog signal: isolate it from digital return currents, use a stable buffer where needed, and filter for the bandwidth actually required by the chemistry and settling time.
7) ΣΔ vs SAR: what is the decisive difference in electrochemical readers?
ΣΔ ADCs are often decisive when low-frequency noise, 50/60 Hz rejection, and high effective resolution at slow update rates dominate. SAR ADCs become decisive when fast steps, scans, or pulse capture require true transient fidelity and predictable latency. The trade is not just “bits,” but bandwidth planning: SAR needs a clean anti-alias path and careful front-end filtering, while ΣΔ relies on digital filtering and can introduce settling delay that must match the measurement timing.
8) If the control loop is stable but readings still “jump,” what should be checked first?
First check baseline drift mechanisms: leakage/bias currents (including contamination and humidity effects) and contact resistance changes at the strip connector. Next check reference noise coupling and supply cleanliness for the AFE/ADC reference network. Finally check whether range switching or sampling timing is creating non-settled data acceptance. A stable loop prevents oscillation, but it does not guarantee low noise or repeatability if the baseline and reference paths are not controlled.
9) What are the observable symptoms of insufficient compliance voltage?
When compliance is insufficient, the CE driver saturates and the system can no longer hold the target WE–RE potential, producing systematic current error or clipped/railed control signals. Common observables include a control output near its rail, a persistent WE–RE error that does not settle, and reading changes that strongly correlate with cell impedance variation. Distinguish compliance issues from algorithm issues by monitoring the control output headroom and the residual control error during the settling window.
10) Which criteria should trigger “reject” or “retest” for open/short or poor contact?
Use criteria that are tied to observables: out-of-range current or potential, unstable variance that fails a settling criterion, open/short detection signatures, and temperature out-of-bounds for the compensation model. After range switching or insertion events, require a defined stabilization window before accepting data. If any gate fails, reject the reading or retest with a controlled sequence rather than outputting a “plausible” value that is actually driven by contact artifacts.
11) In multi-channel readers, how can sampling-level crosstalk and memory effects be reduced?
Reduce crosstalk by controlling MUX charge injection and residual charge: include discharge/settling time after each channel switch, and avoid immediately sampling the next channel at the most sensitive range. Use a predictable switching order and require channel-specific stabilization criteria. Keep high-impedance nodes guarded and clean to prevent leakage-based “memory.” At the sampling layer, the goal is simple: do not accept data until the new channel has fully settled.
12) When must calibration data be invalidated and rebuilt (factory/lot/runtime)?
Invalidate calibration when self-test gates indicate the baseline has moved beyond allowed limits, when known-current checks fail, or when drift patterns suggest leakage/contamination has changed the effective offset. Lot data must be treated as versioned parameters: if the lot code does not match the expected parameter set, apply the correct lot mapping or reject the run. A robust system prefers conservative gating—flagging “needs retest” rather than silently using stale coefficients that can systematically bias results.