Qualify an OEM conductivity probe replacement against a named skid, cable assembly and controller build. Release it as an interchangeable spare only when a technician can install it under the approved service procedure and recover the same measurement and fault response. A unit that needs different scaling or wiring belongs on a revision-specific retrofit list.

Why a plausible reading can hide a substitution error
Two probes can carry the same family name and still require different connections or controller settings. A technician may see a plausible number immediately after replacement even if the scale, temperature basis or register interpretation has changed. In a fleet, that error can propagate when the same spare is issued to a second site. Define the unit of approval as a probe and host combination.
Which specifications matter for OEM conductivity probe replacement?
Mechanical resemblance and a common digital interface leave several compatibility questions open. The host must interpret the supplied registers, scaling, units and temperature basis correctly. The sensing assembly must also provide the needed performance at the process working points. Qualify the complete combination rather than assigning interchangeability from a product-family name.
| Parameter | YEX-S1-EC Modbus configuration | Engineering and purchase implication |
|---|---|---|
| Principle | Two-electrode conductive measurement | Use the same reference solution for the original assembly and the candidate. Record each result against the reference as well as against the other probe. |
| Range | 0–5000 µS/cm | Include the lowest control point in the bench test. Agreement near the top of the range leaves the low-end duty unqualified. |
| Temperature treatment | Automatic compensation | Match the reference temperature and compensation settings to the skid baseline before interpreting a difference as probe drift. |
| Output / supply | RS485 Modbus RTU / 12–24 V DC | Use the proposed cable and production PLC build. Check register interpretation, units and the alarm shown after disconnection. |
| Protection / mounting | IP68 / immersion, NPT 3/4 | Compare insertion depth, sealing detail and removal clearance with the installed drawing. Thread size alone leaves all three unresolved. |
These model-specific values come from the YEX-S1-EC Modbus configuration official product page. Review the delivered configuration and its documents against the proposed installation.

Conductivity sensor compatibility: direct spare or retrofit?
| Option | What it provides | What to specify |
|---|---|---|
| Exact revision spare | Known mechanical and electrical configuration | Keep its approved bill of materials and controller revision with the stores code. Recheck settings at issue. |
| Proposed substitute | Supply continuity when the approved part changes | Require a drawing comparison, revision-specific communications document and a witnessed bench test before adding it to the interchange list. |
| Separate spare families | Sites with different hosts, ranges or process connections | Label the allowed skid serial numbers. The extra stock line may cost less than repeated field adaptations. |
Keep one spare code only for combinations that have passed the required fit, measurement and host tests. Treat a substitute as a qualification task. Separate spare families where a controller or connection change needs different settings, and identify any approved retrofit explicitly in the interchange schedule.
Related reading: Modbus records and skid handover.

Skid revisions that change conductivity probe compatibility
The same skid frame uses two PLC generations
A candidate verified on the newer host may need a software or parameter change on the older one. Bench-test both revisions before expanding the spare list. If a retrofit is required, issue the instructions and acceptance test as a controlled package instead of shipping the sensor under the original interchange code.
A supplier changes the cable or connector assembly
The sensing model may be unchanged while pin assignment, shielding or service access differs. Compare the delivered drawings and test the complete cable with the production host. Record the new assembly identifier and keep any excluded skid variants visible on the order and picking documentation.
Separate measurement error from host error
Use two standards that exercise different parts of the intended duty, including the low decision region. Preserve the raw host response and displayed value together. A consistent factor between reference and display points first to units or scaling. An offset that matters disproportionately at the low point warrants a fresh standard, clean vessel and repeat measurement before attributing it to firmware. Where the error plus reference uncertainty consumes the skid tolerance, exclude that service from the spare approval even if the upper test point passes.
Test conductivity scaling and replacement fault behavior
Test the operating region the skid actually uses. Agreement near one convenient point does not establish performance near a much lower baseline, and a readable Modbus response does not prove correct scaling. Use suitable standards under their stated reference conditions and capture the host-displayed values. The acceptance difference must be justified for the instruments and the process requirement rather than borrowed from an unrelated installation.
Retain an explicit configuration record: sensor and cable identifiers, host project revision, relevant settings and the reference method. Add the observed response to disconnect and restart. These records allow a service partner to identify which earlier qualification applies after a supplier revision. Where a change affects an untested function, keep that skid family outside the interchange approval until the affected checks are complete.
Release the combination on a production host
Fit the supplied assembly to a representative skid and reproduce the service change with the installed cable route. Check the seal, insertion position and ability to remove the probe without disturbing adjacent pipework. From the production display, witness a low operating point, a normal point, a disconnect and a cold restart. Save the host build and settings with the results. If recovery requires an undocumented address or scale change, quarantine that combination until the service instruction and compatibility list carry the same revision.

Write a release decision that stores can apply
A useful interchange schedule has a row for each approved combination. Suppose the same probe threads into two skid generations but the older controller interprets its value in different units. The newer generation can receive a direct spare once it passes the agreed tests. The older one requires a separate kit if its software must change. Putting both under an unrestricted stores code shifts that decision to a technician during an outage, when the firmware baseline may be difficult to establish.
Keep one tested assembly available as a comparison during first installation. If the bench result passes but the field value changes with pump operation, repeat the comparison on the same collected water and inspect the installed sensing position for trapped gas or intermittent wetting. Compare the host diagnostic record at the time of the excursion with the reference instrument result. A communication dropout and an actual change in sample conductivity require different repairs. Retain the original part and controller settings until the skid has demonstrated normal operation after restart.
RFQ scope for skid spare parts
The RFQ schedule links installed skid serial ranges to sensor revision, process connection, cable drawing and PLC build. Price a direct spare and any retrofit kit separately, including commissioning time and the required software baseline. The release document identifies the tested combinations, excluded duties, approved reference method and the person who can extend the list. A connector or firmware change triggers review of the affected rows.
Project inputs for a configuration review
Include these project inputs when requesting the YEX-S1-EC Modbus configuration.
- Installed skid serial ranges, approved sensor and cable revisions
- Actual working range, temperature reference and controller software
- Mechanical drawing, bench method, fault tests and proposed change-control terms
Frequently asked questions
Q1. Does a common RS485 interface establish OEM conductivity probe replacement compatibility?
A1. No. It establishes neither a common register map nor identical measurement behavior. Verify address settings, register meanings, data format, units and temperature basis against the delivered revision’s documents. Test the candidate with the actual controller software and cable assembly. Purchasing should approve the probe-and-host combination, with supported skid serial numbers recorded, so a communications label cannot become an undocumented substitute-parts policy.
Q2. Why can two conductivity probes disagree while both appear functional?
A2. Check that they measure the same water using the same units and temperature reference before suspecting a hardware fault. Different scaling, compensation or stale host data can create plausible but unequal readings. Compare against a suitable standard under its specified conditions, then repeat a paired process check. Store the results with the probe and controller revisions so the fleet’s interchange decision is reproducible.
Q3. How should the controller behave when a replacement probe is disconnected?
A3. Demonstrate the actual behavior during a bench or site test. A zero, a frozen value and a communication alarm carry different meanings, and the host may retain the last successful reading. Define how freshness and faults appear on the display and affect control. Require the controls supplier to record the tested behavior and the deliberate procedure for restoring the channel after a replacement.
Q4. When can several skid generations share one spare part number?
A4. They can share an approved spare when mechanical fit, measurement performance and host interpretation have been demonstrated for every supported configuration. Frame similarity and a common sensor family name are insufficient. Make a matrix of skid serial ranges, controller versions and approved sensor assemblies. Use a separate stock code or a documented retrofit where one generation needs different settings, fittings or acceptance work.
Q5. Does a matching upper range prove suitability for a low-EC duty?
A5. The YEX-S1-EC Modbus configuration is published as 0–5000 µS/cm, but the upper limit alone cannot establish the uncertainty required near a low operating baseline. Specify the lowest working value, significant change and acceptance method for each skid family. Ask for evidence at those points. A replacement that communicates correctly can still be unsuitable for the measurement decision the machine must make.
Q6. Can an adapter make a different sensor revision interchangeable?
A6. An adapter can resolve a defined mechanical mismatch, but it introduces its own wetted parts, seals, clearances and service requirements. Check chemical exposure and the sensing position as well as thread fit. Repeat the relevant commissioning checks with the full assembly. Include the adapter drawing and part number in the approved spare configuration so a field technician does not assemble an untested combination from individually familiar components.
Q7. Who should approve a proposed substitute when the original part is unavailable?
A7. Assign an engineering owner to approve the affected configurations and evidence before purchasing releases the substitution. The review should identify supported hosts, required settings or hardware changes and the installation acceptance procedure. A distributor can then quote the substitute against that defined scope. Keep supply continuity and technical approval as separately documented decisions so urgency does not erase the limits of the tested combination.
Q8. What records and change controls should the service partner receive?
A8. Supply the approved part, sensor and cable revisions, supported skid serial ranges, controller version, bench results and field checklist. Identify excluded configurations before shipment. Repeat the affected qualification checks when the sensing assembly, cable, firmware, host logic or installation changes, recording why earlier evidence still applies or needs replacement. Agree supplier change notification and document control so purchasing and stores can keep each substitute within the tested compatibility boundary.
Summary
Release the YEX-S1-EC as a common spare only for the skid revisions on which the complete probe, cable and PLC combination passes. List the low working point, temperature basis, disconnect response and cold-start result on the release sheet. If one skid needs rewiring or a software change, assign that combination a retrofit kit and a service procedure. Purchasing can then order by skid serial range and approved bill of materials.






