Chinese
Spanish
French
Russian
German
Portuguese
Indonesian
Thai
Vietnamese
Arabic
Direct Answer: Conductivity Is Measured; TDS and Salinity Are Derived
Conductivity is the sensor's direct electrical measurement. TDS and salinity are values derived from conductivity using temperature compensation and a conversion model. Two instruments can therefore report different TDS or salinity from the same water when their conversion factors or scales differ.
For procurement, specify the value that drives the decision. Use conductivity or EC for ion-change trends, RO or process-water checks and irrigation control. Request TDS when the project or customer specification uses dissolved-solids units. Request salinity when seawater, brackish water or salt stress is the decision boundary. Record the conversion setting during commissioning.
Buyer Risk: Comparing Calculated Values Without the Conversion Rule
The main risk is buying by display label alone. A TDS number without its conductivity range, temperature basis and conversion factor cannot be compared reliably with another device. The same applies to salinity scales. Before quotation, provide the water source, expected conductivity, required display unit, temperature variation, installation method and acceptance reference.
For irrigation, aquaculture, RO pretreatment and industrial reuse water, confirm whether the operator needs one primary EC value or several displayed values. Extra calculated outputs are useful only when the team understands how they are produced and how alarms will be interpreted.
Application Scenario and Buyer Decision
The buyer should first define the project boundary: water source, expected range, installation point, output requirement, alarm owner and verification method. For conductivity vs TDS vs salinity, the value is useful only when it explains what the operator should do next.
A strong article and a strong project use the same logic: answer the specific question, explain the measurement boundary, show how the sensor fits the field condition, then describe what proof is needed after startup.
| Conductivity vs tds vs salinity question | Practical answer | Buyer action |
|---|---|---|
| Main decision | conductivity is the measured electrical property, while TDS and salinity are calculated or estimated values based on conductivity, temperature and conversion assumptions | Confirm whether this value changes operation or procurement |
| First data group | conductivity, TDS, salinity | Review these before adding secondary values |
| Field condition | source water intake, irrigation canal, aquaculture pond, RO pretreatment or industrial reuse water line | Choose mounting and maintenance access from the real site |
| Acceptance proof | baseline, output check and cleaning record | Keep evidence for future troubleshooting |
Measurement boundary and selection notes
For conductivity vs TDS vs salinity, the measurement boundary is as important as the sensor name. Buyers should understand what the sensor measures directly, what it estimates, and what still requires laboratory confirmation or site-specific correlation.
The likely project risks include wrong conversion factor, different water matrix, temperature compensation error, confusing calculated values with direct ion testing. These risks should appear in the installation and handover plan, not only in after-sales troubleshooting.
| Ecsal risk | Why it matters | Prevention before ordering |
|---|---|---|
| wrong conversion factor | Can lead to a wrong sensor or wrong interpretation | Define the measurement boundary clearly |
| different water matrix | Can make the same value mean different things at different sites | Ask for water matrix and range information |
| temperature compensation error | Can make readings drift after installation | Plan cleaning and verification from the first month |
| confusing calculated values with direct ion testing | Can create false confidence in the dashboard | Check controller scaling, alarm logic and records |
YexSensor product recommendation
The recommendation below is a soft selection guide. Product choice should still be confirmed with expected range, water matrix, installation drawing, cable length, output requirement and maintenance condition before ordering.
| Product name | Product image | Conductivity vs tds vs salinity role | Best fit for this use |
|---|---|---|---|
| YEX-S1-EC conductivity sensor |  | Measures conductivity as the foundation for salinity, TDS or dissolved-load trend | source change warning, salinity trend, rinse water and reuse water control |
| YEX-S2-MPS-A online multi-parameter self-cleaning probe |  | Combines multiple parameters for compact stations, OEM cabinets and remote points | remote stations, OEM cabinets and multi-parameter field points with limited maintenance access |
Commissioning and handover checks
Commissioning should prove the whole measurement chain. A probe can be correct on the bench but weak in the field if the sample point is wrong, the output is scaled incorrectly or no one owns maintenance.
| Startup proof | Conductivity vs tds vs salinity evidence | Why the buyer needs it |
|---|---|---|
| Installed location | photo and point description | Confirms the value represents the decision |
| First baseline | normal trend after startup | Creates a reference for future alarms |
| Output verification | controller or platform value with unit | Prevents register and scaling errors |
| Maintenance plan | cleaning method and responsible person | Keeps data trusted after handover |
Procurement checklist
Procurement should compare complete packages, not isolated probe prices. A lower unit price may become expensive when cable, mounting, controller, documentation or startup support is missing.
| Purchase item | Common omission | Better requirement |
|---|---|---|
| Sensor and range | parameter name only | State expected normal and maximum values |
| Mechanical scope | no bracket or cleaning access | Confirm holder, cable and retrieval method |
| Data path | no register map or alarm state | Provide Modbus details and dashboard proof |
| Service scope | no spares or verification method | Include maintenance guidance and startup checks |
Engineering boundary for this topic
The engineering boundary for conductivity vs TDS vs salinity should be written in plain project language. The buyer should know what the sensor measures directly, what it estimates from another value, what must be confirmed by laboratory or manual checks, and what operating action will follow an alarm. This boundary prevents a common problem: a correct instrument is installed, but the customer expects it to answer a chemistry or compliance question that belongs to another method.
In the source water intake, irrigation canal, aquaculture pond, RO pretreatment or industrial reuse water line, the boundary should also include the water matrix. Seawater, groundwater, wastewater, aquaculture water and clean process water can behave very differently even when the same parameter name is used. Temperature, suspended solids, color, biofouling, salinity, chemical dosing and flow condition may change how often the probe is cleaned and how the trend should be interpreted.
Installation and data reliability details
Reliable online monitoring depends on the physical point, the electrical signal and the operating record. The probe should sit in representative water, the cable should be protected, the controller should read the right unit, and the operator should know what to do when the value moves. If one part is weak, the dashboard may still look complete while the decision behind it becomes unreliable.
For this application, a practical first-month review should include the first normal baseline, one same-point comparison, one cleaning record and one alarm or simulated-alarm check. This gives the owner evidence that conductivity vs TDS vs salinity is not only installed but usable. The first-month record also helps decide whether the cleaning interval and alarm delay are realistic.
After-sales risk and repeat-order planning
After-sales problems often come from missing details rather than failed electronics. A buyer may reorder the wrong cable length, forget the mounting accessory, replace a probe without checking the controller scaling, or ask for a parameter that was never part of the original decision. A clean handover file reduces these errors.
The repeat-order record should include model, installed point, cable length, output setting, Modbus address if used, spare parts, cleaning tools and the reason the sensor was selected. For conductivity vs TDS vs salinity, this record also helps future buyers understand whether they need the same product, an added parameter or a different verification method.
How to judge whether the recommendation is strong enough
A strong recommendation should be specific enough for an engineer and simple enough for procurement. It should explain the application, the value measured, the product role, the installation condition and the proof required after startup. If the recommendation only lists models, it feels like hard selling. If it only explains theory, it does not help the buyer order the correct package.
For the source water intake, irrigation canal, aquaculture pond, RO pretreatment or industrial reuse water line, the recommended package should therefore connect parameter choice, product selection, data output and maintenance. That is the difference between buying a sensor and buying a monitoring point that can survive real operation.
Before approving the purchase, the buyer should be able to answer five questions: what exact decision does conductivity vs TDS vs salinity support, what range is expected, where will the probe be installed, how will the value reach the controller, and who will maintain the point after startup. If any answer is missing, the project scope is not ready for reliable quotation. The final file should also keep one baseline screenshot and one service note for later comparison, especially before repeat orders and future service.
When calculated values are involved, the conversion assumption should be written into the handover record so later teams do not compare two instruments with different formulas as if one must be wrong.
A final practical note: conductivity vs TDS vs salinity should be easy to explain to a manager who did not attend commissioning. If the team can state what is measured, why it matters, where the probe is installed, how the value is verified and who maintains it, the project is much more likely to keep producing useful data after the first month.
Conductivity Sensor and Integration Options
The YexSensor YEX-S1-EC conductivity sensor is the starting point for EC and compatible calculated-value projects. For high-salinity water, compare the application with the online salinity sensor. Multi-parameter projects can also review the self-cleaning multi-parameter water quality sensor. Use the current product page and manual to confirm the selected model's range and outputs.
For PLC or SCADA projects, define the sensor address plan, register mapping, data type, engineering unit, scaling, communication-fault behavior and maintenance mode before commissioning.
The final handover should identify the selected conductivity range, the TDS or salinity conversion setting where used, and the controller units shown to operators.
Request an EC, TDS or Salinity Recommendation
Send the water source, expected EC or salinity range, required displayed values, temperature range, installation point, cable distance, power supply, Modbus RS485 or controller requirement, quantity and the reference instrument or laboratory method used for acceptance.
For protocol planning, read the RS485 Modbus integration FAQ, then Send Your Project Requirements for model confirmation and a current datasheet.
FAQ
Q1. What is the difference between conductivity, TDS and salinity?
Conductivity is directly measured electrical conductance. TDS and salinity are derived from conductivity through conversion assumptions. Choose the primary value that matches the operating decision and document the conversion rule.
Q2. Why do two meters show different TDS values?
They may use different TDS factors, temperature settings or calibration conditions. Compare raw conductivity first, then verify that both devices use the same factor and temperature basis.
Q3. Can one conductivity sensor output EC and TDS?
Some models provide calculated outputs, but availability and range are model-specific. Confirm the current product page, register map and required units before placing the order.
Q4. When should a dedicated salinity sensor be selected?
Select it when salinity is the required operating value and the expected water matrix fits the model. Seawater, brackish aquaculture and high-salinity industrial water should be disclosed during selection.
Q5. How should irrigation buyers use EC data?
Use EC to trend dissolved-ion loading and support source-water or fertigation decisions, but set crop-specific action limits with the agronomist. The sensor package should match the expected range and sampling point.
Q6. Where should the probe be installed?
Choose a representative point with stable water contact and cleaning access. Avoid trapped air, dead zones, undissolved fertilizer near injection points and deposits that do not represent the delivered irrigation or process water.
Q7. What must be checked in Modbus commissioning?
Verify wiring, address, baud rate, parity, register map, data type, unit, scaling and fault handling. Compare the local reading with the PLC or SCADA value before enabling alarms or control.
Q8. How often should the sensor be cleaned or calibrated?
Set the interval from the water matrix, fouling rate and required confidence. Follow the current model manual and record before-and-after values instead of applying one fixed interval to every site.
Q9. What information is needed for an accurate quotation?
Provide the water source, expected range, required EC/TDS/salinity outputs, temperature, installation, cable, communication, power, quantity and acceptance method. This separates comparable quotations from incomplete ones.
Q10. Should every project display all three values?
No. Display only the values that operators understand and use. A clear primary EC value with a documented conversion is often stronger than several calculated values with no decision rule.
Summary
Conductivity is measured directly, while TDS and salinity depend on conversion assumptions. The fastest way to avoid procurement and commissioning disputes is to define the primary value, expected range, conversion setting, installation point, reference check and Modbus RS485 data path before ordering. Select the final YexSensor model only after matching those inputs to the current official product documentation.
