Skip to main content
Skip table of contents

Watermark Troubleshooting

Watermark sensors can experience problems where the readings suddenly jump up to 200 cbar (kPa) and flatline, as shown in this screen capture:

image-20240422-050041.png

2 already very dry watermark sensors flatline at 200 cbar, Basil, Bakersfield, CA

This can be caused by three reasons:

  1. Watermark sensors losing good contact with the soil

  2. Water has corroded the connection in the scotchlok 

  3. Bad connection between the wildeye and the watermark

Watermark sensors losing good contact with the soil

Watermarks can lose contact from the soil more easily than water content sensors which use electric fields instead of direct contact, to detect water (water content sensors can still experience air gaps, but that is usually due to poor installation or rocks during installation, once they are settled air gaps are rare).

Soil contact loss is particularly noticeable in tree crops during large gaps in irrigation, or as in this example some short-term crops like basil when the ground is left to dry prior to harvest.

Once the watermark sensor loses contact, in most cases it will need to be re-installed.

If there is any doubt about the sensor working correctly, confirm that the sensor is working prior to re-installation by dipping it into water, as shown in this screenshot:

image-20240422-050122.png

2 watermark sensors removed and dipped in water, Basil, Bakersfield, CA

Water has corroded the connection in the scotchlok

If the scotchlok's experience flooding in which they are submerged under water for a duration of time, the wires can corrode which prevents electrical contact. The easiest way to remedy this is by cutting back the wire and attaching a new scotchlok connector.

Bad connection between the wildeye and the watermark

Check the connection at the end of the wildeye or expander to check that there is a watermark. If the wildeye is not attached to a watermark sensor the wildeye will report this as 200 kPa. 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.