Conductivity & TDS Sensor ASIC Selection Matrix: How to Choose Channels, Range, Resolution, Probe, and Interface

Why This Industry Needs Continuous, Interpretable Water Quality Data

The monitored objects in OEM embedded water quality product development are not static samples but processes that constantly change with flow, temperature, raw materials, weather, equipment status, and human operations. Traditional sampling and laboratory analysis are irreplaceable but cover only the sampling moment. For water purification equipment, instruments, industrial modules, and smart appliances that need to integrate conductivity, TDS, salinity, or temperature measurement on their own control boards, the real challenge is what happens between two samples: how long a change lasts, whether it synchronizes with a process action, and when it warrants verification. The first value of continuous sensors is to fill these gaps into time series.

This approach translates application requirements into nine verifiable selection criteria: number of channels, range, low-end resolution, probe type, temperature compensation, digital interface, package, power consumption, and production calibration. Therefore, the project should not start with "which probe to buy" but with decision-making questions, allowed response time, data purpose, and evidence level. Data for alarms, operational optimization, customer presentation, and regulatory reporting require different calibration, redundancy, and review procedures. Define the purpose first to avoid generating massive unused data with expensive equipment.

Step 1: Define Monitoring Objectives as Verifiable Engineering Problems

An executable objective should include object, location, time scale, acceptable risk, and subsequent actions. For example, "when key trends in conductivity, TDS, temperature, salinity, specific gravity, or other parameters derived from or associated with conductivity and temperature deviate from normal baseline and persist for a certain duration, the system issues graded alarms; operators inspect process and field conditions; and reference samples are taken if necessary." This statement is more valuable than "real-time water quality monitoring" because it constrains point, sampling cycle, threshold, verification, and responsible person.

• Trend objectives: identify baseline, diurnal cycle, seasonal variation, startup and shutdown processes.
• Event objectives: capture sudden increases, decreases, continuous drift, and unreasonable combinations of parameters.
• Control objectives: provide input for aeration, drainage, flushing, bypass switching, filter management, or process adjustment.
• Quality objectives: preserve raw values, status codes, cleaning/calibration records, and manual notes to make data traceable.
• Business objectives: use continuous evidence to demonstrate the value of products, processes, or services, while clearly defining measurement boundaries.

At project initiation, it is recommended to establish a one-page "Measurement Task Sheet": list normal range, minimum meaningful change, expected response time, maximum acceptable missing duration, reference method, maintenance resources, and output recipients. The task sheet is not a one-time document but should be updated after trial operation, seasonal changes, and process modifications.

Parameter Combinations: Different Measurement Mechanisms Should Be Mutually Explanatory, Not Simply Stacked

TDS is not the ASIC directly identifying each dissolved substance; it is an engineering indicator derived from conductivity, temperature, and conversion model. The same conductivity may correspond to different ionic compositions, so the product must clearly indicate purpose, conversion factor, and calibration water sample. If the target is low-end changes in ultrapure water, low-end noise and resolution are often more important than maximum range.

Correspondence with AtomBit Product Capabilities

BA111 and BA121 are suitable for common single-channel products; BA121S emphasizes low conductivity and high resolution; BA012, BA022, BA112 are used for dual-channel or comparative measurement; BAT3U is designed for three-channel water circuits; BA311 and BA311L adopt SOT23-6 small package; BA234 is a single-channel dual-probe interface with NTC compensation and UART output. The model is not "bigger is better" but depends on whether measurement points, range, and system boundaries match.

The core products discussed in this article are the AtomBit BA series water quality sensor interface ASICs and compatible electrode probes. Selection must be based on the latest datasheets, target water sample, range, temperature, pressure, materials, interface, and installation conditions. The website article provides engineering logic and does not replace item-by-item technical confirmation; for new water bodies or cross-industry applications, AtomBit can assist with sample evaluation, interface confirmation, trial installation, and model validation.

System Architecture: From Probe to Actionable Information Requires a Complete Data Chain

A reliable system typically includes five layers: the measurement layer is responsible for stable acquisition of raw signals; the edge layer is responsible for power supply, communication, time synchronization, and status collection; the platform layer is responsible for storage, unit unification, quality labeling, and permissions; the analysis layer is responsible for baselines, rate of change, correlations, and event rules; and the business layer delivers results to operations, quality, after-sales, or customer interfaces. Missing any layer may cause a "seemingly online" system to lose practical value.

RS485/Modbus RTU is suitable for multi-device bus in industrial field. Engineers should unify address, baud rate, parity, register type, data length, byte order, unit, and scaling factor; the master polling should set reasonable timeout and retry; communication failures should not be automatically written as zero. Each record should ideally include device time, platform reception time, quality status, maintenance status, and raw register snapshot to facilitate problem tracking.

Data Frequency: Faster Is Not Always Better

The sampling period should be shorter than the change time of the target event, but also consider sensor response, flow cell replacement, network bandwidth, and storage. Second-level acquisition is suitable for device diagnostics; minute-level averages are commonly used for operation screens; hourly or daily statistics are suitable for management reports. It is recommended to save high-frequency raw data and then generate derived data at different time scales to avoid being unable to review transients after only storing averages.

Point Selection and Installation: Representativeness Is Usually More Important Than Nominal Accuracy

Selection review should simultaneously bring water sample range, temperature range, flow channel materials, probe drawings, main control voltage, interface resources, EMC environment, target BOM, and production cycle time. Simply handing the chip manual to the hardware engineer without involvement of water path and algorithm usually postpones problems to the final product testing stage.

Immersion installation should keep the sensing surface continuously submerged, avoid direct impact and cable stress, and reserve space for lifting, cleaning, and replacement. Flow-through installation should ensure sample representativeness, stable flow, and bubble exhaust, with matching shut-off, bypass, drain, and flushing structures. High-pressure, high-temperature, corrosive, or food-contact scenarios also require individual confirmation of sealing, materials, and hygienic requirements.

• Survey actual minimum and maximum water level, flow, temperature, pressure, and pollutant load.
• Use portable instrument or sampling to compare candidate points and confirm spatial representativeness.
• Check for bubbles, deposits, floating objects, sunlight, vibration, electromagnetic interference, and maintenance safety.
• Record installation depth, orientation, flow cell volume, pipeline length, and photos; include in site archive.
• During trial operation, simultaneously retain reference samples to verify point and response time before finalizing design.

Calibration, Validation, and Data Quality: Establish a "Pre-Cleaning → Post-Cleaning → Post-Verification" Evidence Chain

Quality control for continuous sensors cannot be reduced to a single calibration date. Each maintenance should first record the stable value before cleaning and field status, then complete cleaning and record the value after cleaning, and finally verify using reference solution, portable reference instrument, or representative sample. These three sets of data can distinguish the effects of fouling, calibration drift, and actual water body changes. If only the final normal value is retained, the basis for judging whether historical data can be used is lost.

Laboratory comparisons must ensure that samples correspond in time and space to sensor readings, and record sampling, preservation, transport, method, and uncertainty. For spectral proxy quantities, cover the normal, low, high, and typical anomaly ranges of the target water body; model evaluation should not only look at correlation coefficient but also examine residuals, low-end bias, high-end saturation, seasonal stability, and cross-point applicability. If water matrix changes significantly, re-validate.

Data platforms should use quality flags rather than simply deleting anomalies. It is recommended to at least distinguish: valid, under maintenance, cleaning recovery, under calibration, communication failure, out of range, suspected bubble, suspected fouling, and pending review. Customer-facing charts can hide invalid segments, but internal databases must retain raw values, reasons, and handling records.

Alarm Design: Threshold, Rate of Change, Duration, and Parameter Correlation Are All Indispensable

A single fixed threshold is easily affected by seasonal, recipe, raw water, and operating condition changes. A more robust rule can combine absolute threshold, relative baseline, rate of change, duration, consistency of multiple parameters, and equipment status. For example, a sudden increase in turbidity without response in flow, UV254, and organic trends may be bubbles or local particles; if multiple related parameters change synchronously and persist, it is more worthy of triggering sample retention and manual inspection.

Alarms must be bound to a handling procedure: who receives, how long to confirm, which status to check first, whether to re-measure, when to retain sample, when to escalate, and when to close. Unvalidated automatic control should set upper/lower limits, hysteresis, minimum run time, interlock, and manual override to prevent transient sensor anomalies from directly driving critical equipment.

Common Failure Modes and Prevention Strategies

• Insufficient number of channels leading to later addition of external analog switches
• Ignoring noise, leakage, and board cleanliness for low-conductivity water
• Mismatch between probe and front-end range resulting in saturation or insufficient sensitivity
• UART protocol, supply voltage, and main control startup sequence not verified in advance
• Calibration coefficients without serial number, batch, and firmware version traceability

The common characteristic of these issues is that the equipment itself may not be damaged, but the data has lost representativeness or interpretability. Prevention strategies should cover field structure, communication, algorithms, personnel, and documentation, rather than attributing all problems to "recalibration." When anomalies occur, first check status codes, raw signals, adjacent parameters, maintenance records, and field events before deciding to clean, calibrate, remodel, or replace components.

How to Calculate Total Cost of Ownership and Project Benefits

Enable product managers, hardware, structure, algorithm, and manufacturing teams to use the same selection table early in the project, reducing repeated board revisions and improving reuse efficiency across product families.

The cost model should at least include sensor and accessories, installation structure, power supply and communication, platform, reference samples, consumables, labor, inspection travel, downtime, spare parts, and data review. Benefits can be measured by anomaly lead time, reduced manual sampling, avoided downtime or quality loss, chemical and energy optimization, reduction of false alarms, and customer service efficiency. For reagent-free solutions, also perform a full lifecycle comparison with traditional methods including reagent procurement, storage, waste liquid, and pump/valve maintenance.

Do not rush to promise large savings during the pilot phase. First select a point with a clear pain point and accessible reference samples, run a cycle covering typical conditions, and statistically analyze data availability, maintenance time, number of event discoveries, false alarm rate, and relationship with reference methods. Only after forming a verifiable pilot report can scaling have a reliable basis.

Phased Implementation Roadmap

1. Requirements Definition: Determine business problem, parameters, candidate points, data purpose, reference method, and responsible person.
2. Sample and Interface Assessment: Verify water sample range, environmental conditions, power supply, communication, materials, and main control interface.
3. Small-Scale Pilot: Establish installation archive, baseline, maintenance cycle, reference samples, and quality flags.
4. Model and Alarm Validation: Check error, residual, seasonal stability, and alarm handling effectiveness using independent data.
5. Scale Deployment: Replicate validated structure, address planning, parameter tables, O&M forms, and spare parts strategy.
6. Continuous Improvement: Monthly or quarterly review data availability, maintenance costs, event value, and model version.

At each stage, retain "exit criteria": if the point is not representative, the target change is less than system uncertainty, maintenance resources are insufficient, or data has no clear user, modify the plan instead of continuing to add equipment. For new industries not previously covered by AtomBit, the customer's process knowledge combined with our sensing, interface, and engineering validation capabilities can define new application boundaries.

Procurement and Technical Review Checklist

• Are target water body, parameters, range, temperature, pressure, materials, and expected response time confirmed in writing?
• Do sensors, probes, cables, cleaning devices, flow cells, brackets, gateways, and power supplies form a complete BOM?
• Are communication protocol, registers, byte order, address, baud rate, status codes, and anomaly values integrated and tested?
• Are calibration solutions, reference instruments, laboratory methods, sampling plan, and acceptance criteria clearly defined?
• Is division of labor for automatic cleaning, manual maintenance, spare parts, training, remote support, and data responsibility established?
• Do all promotions, alarms, and reports accurately state the boundaries of trends, proxy quantities, screening, and compliance results?

Engineering Appendix: Review Method from a Single Reading to a Trustworthy Conclusion

When reviewing a data segment, first check completeness: whether time is continuous, device clock jumps, communication failures are written as zero, and maintenance periods are correctly flagged. Second, check physical plausibility: whether temperature and range are reasonable, change speed is possible, and related parameters show identical or completely opposite anomalies. Third, check field evidence: whether pump, valve, aeration, feeding, rainfall, discharge, cleaning, and sampling records correspond to the curve.

Fourth is comparison. First compare with historical baseline of the same device, then with adjacent points, other measurement mechanisms, and reference samples. When comparing, time, unit, temperature condition, and sampling location must be unified. Inconsistency between two methods does not automatically indicate that the online sensor is wrong; it may come from sample inconsistency, preservation changes, laboratory uncertainty, or different measurement objects of the two methods; the difference itself is also important information for understanding the water body.

Fifth, form a conclusion level. Conclusions can be classified into "trend changes with normal equipment status," "suspicious events requiring field verification," "water quality changes confirmed by reference samples," and "invalid data affected by fouling or drift." This classification is more suitable for continuous monitoring than simple pass/fail and allows operations, engineering, and management personnel to communicate based on the same evidence.

For cross-industry new applications, it is recommended to establish a joint validation sample library: each sample stores time, point, operating condition, sensor raw and output, laboratory result, and remarks. The library is not only used for one-time calibration but also for regression testing of firmware, model, and hardware version upgrades. As customers accumulate data, technical capability can continuously expand to new water bodies and decision problems based on fixed sensing principles.

Conclusion: Technology Platform Fixed, Application Value Defined by Field Problems

The AtomBit BA series water quality sensor interface ASICs and compatible electrode probes provide integrable and verifiable sensing and interface capabilities; the ultimate value comes from the customer's understanding of industry processes, correct point selection, reference methods, data quality, and clear actions. Typical applications are only a part of what has been validated. For new water bodies, equipment, or business models, AtomBit can collaborate from sample, selection, interface, trial installation, calibration, data interpretation to mass production, helping partners turn unknown applications into deliverable solutions.

References and Further Reading

• AtomBit BA Series ASIC Chinese Datasheet and Product Selection Documentation
• AtomBit Compatible Electrode, NTC Probe, and Digital Probe Documentation
• USGS Technical Information on Specific Conductance, TDS, and Water Ionic Composition

This article summarizes engineering application methods, compiled from public institutional guidelines and AtomBit product documentation. Specific projects must comply with local regulations, industry standards, and safety requirements; conclusions involving compliance, health, or trade release should be confirmed by qualified laboratories and responsible agencies.

Supplementary Note: Project Documentation and Long-term Maintenance Mechanism

It is recommended that each project establish equipment list, site description, wiring diagram, register table, calibration records, reference sample records, maintenance records, alarm handling records, and version change records. Documentation should be associated with equipment serial numbers and point IDs to prevent knowledge loss after personnel changes. When modifying range, coefficients, thresholds, and models on the platform, record modifier, reason, time, and impact scope, and retain rollback capability.

For long-term operation, also set indicators such as data availability, maintenance man-hours, calibration pass rate, communication success rate, alarm acknowledgment time, and effective event ratio. Indicators are not for blame but to identify systemic issues: if maintenance hours at a site are persistently high, installation structure may need adjustment; if false alarms are concentrated in rainy season, seasonal baseline should be improved; if reference sample coverage is persistently insufficient, reallocate sampling resources.