Smart Water Appliance Sensor Front-End Design: TDS, Conductivity Measurement ASIC, Probe, and Mass Production Calibration

Why the Industry Needs Continuous, Interpretable Water Quality Data

The monitoring target of smart water appliances is not a static sample, but a process that constantly changes with flow, temperature, raw water, weather, equipment status, and human operation. Traditional sampling and laboratory analysis are irreplaceable, but they only cover the sampling moment. For household water purifiers, countertop water dispensers, water dispensers, pet water fountains, smart bathrooms, coffee machines, and consumer devices requiring water quality display, the real challenge is what happens between two samplings, how long the change lasts, whether it synchronizes with a process action, and when it warrants triggering a review. The primary value of continuous sensors is to fill these gaps into time series.

The goal of this solution is to embed stable conductivity/TDS measurement capability into mass-produced mainboards within limited cost, space, and power, while ensuring that results from different batches of probes, temperatures, and water samples remain interpretable. Therefore, the project should not start with "which probe to buy," but with the decision problem, allowable response time, data usage, and evidence level. Data for alarms, operational optimization, customer display, and regulatory reporting require different calibration, redundancy, and review procedures. Define the use first to avoid using expensive equipment to generate large amounts of unused data.

Step 1: Transform Monitoring Objectives into Verifiable Engineering Problems

An executable objective should include the object, location, time scale, allowable risk, and subsequent actions. For example, "When key trends in conductivity, TDS, temperature, salinity, and relative changes between multiple water paths deviate from the normal baseline and persist for a certain time, the system issues graded alarms, operators check the process and site conditions, and if necessary, retain reference samples." This statement is more valuable than "real-time water quality monitoring" because it simultaneously constrains points, sampling period, thresholds, review, and responsible persons.

• Trend objectives: Identify baseline, diurnal cycle, seasonal variation, start-up and shutdown processes.
• Event objectives: Capture sudden increases, sudden drops, continuous drift, and unreasonable combinations of parameters.
• Control objectives: Provide inputs for aeration, blowdown, flushing, bypass switching, filter management, or process adjustment.
• Quality objectives: Preserve raw values, status codes, cleaning and calibration records, and manual notes to allow traceability.
• Business objectives: Use continuous evidence to demonstrate the value of the product, process, or service, while clearly defining measurement boundaries.

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

Parameter Combination: Different Measurement Mechanisms Should Explain Each Other, Not Simply Stack

Conductivity measurement may seem simple, but it involves AC or bipolar excitation, electrode polarization, stray capacitance, contact impedance, cell constant, temperature coefficient, and water sample ion composition. The significance of dedicated ASICs is to centralize high-risk analog front-end and digital control, reducing mainboard development effort, but PCB layout, probe structure, and mass production calibration still determine final consistency.

Correspondence with AtomBit Product Capabilities

Single-channel devices suit one measurement point and compact products; BA012, BA022, BA112, etc., multi-channel solutions suit raw water vs. purified water comparison or multi-stage water paths; BAT3U for three-channel scenarios; BA311/BA311L in small packages for space-constrained products; BA121S for low conductivity and higher resolution applications. Final selection must still be checked against the datasheet for range, channels, probe, temperature compensation, interface, package, and calibration process.

The core products covered in this article are BA111, BA121, BA121S, BA012, BA022, BA112, BAT3U, BA311/BA311L, and BA234. Selection must be based on the latest datasheet, target water sample, range, temperature, pressure, material, interface, and installation conditions. Website articles provide engineering logic, not a substitute for item-by-item technical confirmation; for new water bodies or cross-industry applications, AtomBit can cooperate on sample assessment, interface confirmation, trial installation, and model validation.

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

A reliable system typically consists of 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 acquisition; the platform layer is responsible for storage, unit unification, quality marking, and permissions; the analysis layer is responsible for baseline, rate of change, correlation, and event rules; the business layer delivers results to operations, quality, after-sales, or customer interfaces. The absence of any layer may cause a "seemingly online" system to lose its practical value.

RS485/Modbus RTU is suitable for multi-device buses in industrial sites. 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 retries, and communication failures should not be automatically written as zero. Each record should ideally contain device time, platform reception time, quality status, maintenance status, and raw register snapshot to facilitate problem tracking.

Data Frequency Is Not Always Faster

The sampling period should be shorter than the change time of the target event, but sensor response, flow cell displacement, network bandwidth, and storage must also be considered. Second-level acquisition is suitable for equipment diagnostics, minute-level averages are often used for operation screens, and 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, avoiding the inability to review transients after only saving averages.

Point Location and Installation: Representativeness Is Often More Important Than Nominal Accuracy

Measurement points inside consumer products should avoid bubble accumulation, strong temperature gradients from heaters, motor and switching power supply noise, and also ensure long-term cleanliness for users. Flow channel design, probe insertion depth, and thermal coupling of the temperature sensor must be verified together with the algorithm.

Submersion 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 representative samples, stable flow, bubble removal, and supporting structures for shutoff, bypass, drain, and flush. High pressure, high temperature, corrosive, or food-contact scenarios also require separate confirmation of seals, materials, and hygienic requirements.

• Survey actual minimum and maximum water levels, flow, temperature, pressure, and pollutant loads.
• Compare candidate points with portable instruments or sampling to confirm spatial representativeness.
• Check for bubbles, sedimentation, floating matter, sunlight, vibration, electromagnetic interference, and maintenance safety.
• Record installation depth, orientation, flow cell volume, pipe length, and photos, and include in site files.
• During commissioning, simultaneously retain reference samples to verify points and response time before finalizing the design.

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

Quality control of continuous sensors cannot be reduced to a single calibration date. Each maintenance should first record the stable value before cleaning and on-site status, then complete cleaning and record the value after cleaning, and finally verify with reference solution, portable reference instrument, or representative sample. The three sets of data can distinguish between contamination effects, 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 should ensure that the sample corresponds in time and space to the sensor reading, and record sampling, preservation, transport, method, and uncertainty. For spectral surrogate parameters, the normal range, low values, high values, and typical anomalies of the target water body should be covered; model evaluation should not only look at the correlation coefficient but also observe residuals, low-value bias, high-value saturation, seasonal stability, and cross-point applicability. When the water matrix changes significantly, revalidation should be performed.

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

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

A single fixed threshold is susceptible to seasonal, recipe, raw water, and operating condition changes. More robust rules can combine absolute threshold, relative baseline, rate of change, duration, consistency among multiple parameters, and equipment status. For example, if turbidity suddenly rises but flow, UV254, and organic trends do not respond, it 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-test, when to retain a sample, when to escalate, and when to close. Unvalidated automatic control should have upper and lower limits, hysteresis, minimum run time, interlocks, and manual override to prevent sensor transient anomalies from directly driving critical equipment.

Common Failure Modes and Prevention Methods

• Selecting a chip only by maximum range while ignoring low-end resolution
• Treating the cell constant as a fixed theoretical value without batch verification
• Temperature compensation sensor placed too far from the water sample, causing dynamic error
• DC bias and polarization of electrodes causing long-term drift
• Prototype calibration valid but mass production tooling, standard solutions, and version management out of control

The common characteristic of these issues is that the device itself may not be damaged, but the data has lost representativeness or interpretability. Prevention strategies should cover on-site structure, communication, algorithms, personnel, and documentation, without attributing all problems to "recalibration." When an anomaly occurs, first check the status code, raw signal, adjacent parameters, maintenance records, and on-site events, then decide on cleaning, verification, remodeling, or component replacement.

How to Calculate Total Cost of Ownership and Project Benefits

Shorten the analog front-end development cycle, increase platform reuse rate between different SKUs, and support filter management, remote diagnostics, and differentiated water quality display through multi-channel and digital interfaces.

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

Do not rush to promise large-scale savings during the pilot phase. First, select a point with a clear pain point and the ability to obtain reference samples, run a cycle covering typical operating conditions, and statistically measure data availability, maintenance time, number of events detected, false alarm rate, and relationship with the reference method. Only after forming a verifiable pilot report can large-scale replication have a reliable basis.

Phased Implementation Roadmap

1. Requirements definition: Determine business problem, parameters, candidate points, data usage, reference method, and responsible personnel.
2. Sample and interface assessment: Verify water sample range, environmental conditions, power supply, communication, materials, and mainboard interface.
3. Small-scale pilot: Establish installation files, baseline, maintenance schedule, reference samples, and quality flags.
4. Model and alarm validation: Check error, residuals, seasonal stability, and alarm handling effectiveness using independent data.
5. Scale deployment: Replicate verified structure, address plan, parameter table, operation and maintenance forms, and spare parts strategy.
6. Continuous improvement: Review data availability, maintenance cost, event value, and model version monthly or quarterly.

At each stage, retain "exit conditions": if the point is not representative, the target change is less than the system uncertainty, maintenance resources are insufficient, or the data has no clear user, modify the plan rather than continue stacking equipment. For new industries not pre-covered by AtomBit, the customer's process knowledge combined with our sensing, interface, and engineering verification capabilities can jointly define new application boundaries.

Procurement and Technical Review Checklist

• Whether the target water body, parameters, range, temperature, pressure, material, and expected response time are documented in writing.
• Whether the sensor, probe, cable, cleaning device, flow cell, bracket, gateway, and power supply form a complete BOM.
• Whether the communication protocol, registers, byte order, address, baud rate, status codes, and abnormal values are integrated and tested.
• Whether the calibration solution, reference instrument, laboratory method, sampling plan, and acceptance criteria are clearly defined.
• Whether automatic cleaning, manual maintenance, spare parts, training, remote support, and data responsibility are assigned.
• Whether all promotions, alarms, and reports accurately describe the boundaries of trend, surrogate, screening, and compliance results.

Engineering Appendix: A Review Method from a Single Reading to a Trusted Conclusion

When reviewing a segment of data, first check completeness: whether time is continuous, whether the device clock has jumped, whether communication failures are written as zero, and whether maintenance periods are correctly flagged. Second, check physical reasonableness: whether temperature and range are reasonable, whether the rate of change is plausible, and whether related parameters exhibit completely identical or opposite anomalies. Third, check on-site evidence: whether pump, valve, aeration, feeding, rainfall, discharge, cleaning, and sampling records correspond to the curve.

Fourth, compare. First compare with the historical baseline of the same device, then with adjacent points, other measurement mechanisms, and reference samples. Comparison must unify time, units, temperature conditions, and sampling location. A discrepancy between two methods does not automatically indicate an online sensor error; it may stem from sample inconsistency, preservation changes, laboratory uncertainty, or different measurement objects of the two methods; the discrepancy itself is also important information for understanding the water body.

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

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

Conclusion: Technology Platform Fixed, Application Value Defined Jointly by Site Problems

BA111, BA121, BA121S, BA012, BA022, BA112, BAT3U, BA311/BA311L, and BA234 provide integrable and verifiable sensing and interface capabilities; the ultimate value comes from the customer's industry process understanding, correct points, reference methods, data quality, and clear actions. Typical applications are only part of what has been verified. For new water bodies, equipment, or business models, AtomBit can collaborate on samples, selection, interfaces, trial installation, calibration, data interpretation, and mass production to help partners turn unknown applications into deliverable solutions.

References and Further Reading

• AtomBit BA Series Sensor Interface ASIC Datasheets and Selection Documentation
• AtomBit TFE Series Electrode and Digital Probe Documentation
• USGS Materials on Conductivity, TDS Surrogate Relationships, and Temperature Conditions

This article is a summary of engineering application methods, compiled from public agency guides and AtomBit product documentation. Specific projects should comply with local regulations, industry standards, and safety requirements; conclusions involving compliance, health, or trade release should be confirmed by qualified laboratories and responsible authorities.

Supplementary Note: Project Documentation and Long-Term Maintenance Mechanism

It is recommended that each project establish equipment lists, site descriptions, wiring diagrams, register tables, calibration records, reference sample records, maintenance records, alarm handling records, and version change records. Documents should be associated with equipment serial numbers and point identifiers to avoid knowledge loss after personnel changes. When platform modifications are made to ranges, coefficients, thresholds, and models, the modifier, reason, time, and impact scope must be recorded, and rollback capability must be retained.

Long-term operation should also set indicators such as data availability, maintenance hours, verification pass rate, communication success rate, alarm confirmation time, and effective event ratio. Indicators are not for blame but to discover systemic issues: if a site's maintenance hours are consistently high, installation structure may need adjustment; if false alarms concentrate during rainy periods, seasonal baselines should be improved; if reference sample coverage is insufficient long-term, sampling resources should be rearranged.