Dragino Soil Moisture Correction: Validate the Range Around Your Irrigation Trigger
A soil moisture dashboard can display a plausible percentage after a correction has been applied, yet still provide weak evidence for an irrigation trigger. The practical question is whether that trigger lies within a range you have checked against an independent reference. Before using corrected readings operationally, test the calculation at its breakpoints, record where it extrapolates, and validate separate measurements near the intended decision point.
Original ProSense engineering illustration. Equipment and plotted relationships are conceptual, not a live installation or software screenshot.
Key takeaways
Validate independent reference measurements around the decision range. Passing through correction points proves the arithmetic there, not irrigation suitability or accuracy outside the checked range.
Confirm the model and the quantity first
Dragino’s SE01-LB/LS manual describes an FDR soil sensor reporting moisture, temperature and conductivity. Its moisture specification uses volumetric percent, V/V %. A soil water tension reading in kPa is a different quantity; do not substitute it directly as the reference percentage.
Check the label on the supplied unit. SE01-LB and the older LSE01 are separate model names. The current SE01-LB/LS FAQ links to a correction document originally titled for LSE01, supporting its use as a platform-side calculation reference. That shared link does not establish firmware or payload-decoder interchangeability.
The ProSense Dragino soil sensor listing includes this SE01-LB photograph alongside LSE01 model text. Confirm the exact model and probe before ordering or commissioning; use the documentation matching the delivered label.
Understand what the three-point correction does
In Dragino’s soil correction PDF, three pairs link the sensor’s reported moisture X to reference moisture Y. Between adjacent pairs, Y is interpolated along a straight segment. Below the lowest sensor point A1, the formula scales X by A2/A1. At or above the highest sensor point C1, it applies the offset C2−C1. Moisture results above 100 are capped at 100.
Those outer branches are extrapolation rules, not additional observations. The upper branch does not continue the slope of the final internal segment. Consequently, a smooth-looking trend above your highest calibration point does not demonstrate that the correction remains accurate there. Keep the measured range visible in the commissioning record.
Choose ordered, distinct sensor values for the three pairs. Identical adjacent X values make a segment denominator zero. A zero lowest point also makes the lower scaling branch undefined if software evaluates it. Reject malformed inputs and test the actual implementation rather than assuming every calculation engine handles unused branches identically.
Original workflow diagram summarising the checks in this guide. It does not establish a device specification or a customer test result.
Worked example: a breakpoint changes the slope
Consider hypothetical moisture pairs, all in volumetric percent: sensor 10 maps to reference 12; sensor 30 maps to reference 36; sensor 50 maps to reference 56. These invented numbers illustrate calculation checks only. They are not calibration values for your soil or recommended irrigation thresholds.
At X=40, the middle-to-upper segment gives Y=(40−30)×(56−36)/(50−30)+36=46. At X=50, the upper branch gives Y=50+56−50=56. At X=60 it gives 66. Extending the preceding segment happens to give the same answer here because its slope is one; that coincidence disappears with different reference pairs.
For example, changing only the final reference value to 60 makes that segment’s slope 1.2. At X=60, extending the segment would give 72, while the documented outer branch gives 70. Both calculations can look reasonable on a graph. Only one follows that branch rule, and neither supplies evidence of actual accuracy outside the measured range.
Validate the decision range before handover
Record the sensor and probe identity, soil or growing medium, measurement units, reference method, paired readings and conditions. Keep the original reported values alongside corrected values so another technician can reproduce the calculation.
Test all three calibration inputs, values just below and above each breakpoint, and values outside the measured range. Compare the platform output with an independently checked calculation. Include invalid inputs and missing readings in the test plan.
Collect additional paired observations that were not used to construct the curve, particularly around the proposed irrigation trigger. Agree on an acceptable difference with the application owner before reviewing the results.
Label readings outside the validated range. Decide who investigates them and how operational decisions proceed while the measurement is uncertain. Avoid silently treating extrapolated data as fully validated.
Save the calculation version, its effective date and the validation results. Repeat relevant checks after changing the probe, medium, reference method or correction logic.
Common mistakes and practical limits
Do not adjust a curve merely to make two different locations agree. First establish whether the measurements represent comparable material and conditions. Likewise, passing through the three construction points proves the arithmetic at those points, not performance everywhere between them.
Dragino also publishes a linear calibration guide that stresses checking linearity. Do not replace a piecewise curve with a single line solely because it is easier to configure. If independent checks show a systematic mismatch, investigate the measurement and reference before adding further correction.
Finally, moisture correction does not establish a crop’s irrigation requirement. Have the responsible agronomist or application specialist confirm the decision criteria. For a useful technical enquiry, provide the model label, existing calculation, paired observations and the range in which decisions must be dependable.
Diagnostic comparison
Observation | Next check |
Trigger lies outside measured pairs | Obtain independent evidence near the decision range. |
Curve passes construction points | Test independent points, breakpoints and outer branches. |
Sensor model is uncertain | Resolve label and matching documentation before selection. |
Recommended equipment / related solutions
Review the instrument or gateway discussed in this article. Confirm the exact supplied model and relevant configuration before ordering.
Discuss selection and application scope with ProSense technical services.
Send the model and diagnostic evidence through ProSense Instruments technical enquiries.
Need help with your application?
ProSense Instruments - discuss sensors and instrumentation. ProSense Solutions - discuss monitoring and automation projects. ProSight Software - discuss software requirements; device integration must be confirmed for your application.
Instrument enquiries: sales@prosenseinstruments.com.au | 1800 560 854. Project enquiries: sales@prosense.com.au. Software enquiries: info@prosightsoftware.com.
Comments