Advertisement
Collecting High Quality Soil Data--Tips
1. Observe maps in SoilViewer as data
is being collected. High quality data
has good pass-to-pass repeatability
and soil zones have distinct, natural
shapes that follow known field soil
properties. Poor data is jumpy or
streaky, and maps don't appear like
soil's natural continuum.
2. Observe any warnings that appear in
the Warning Box.
3. Observe the depth sensor readings
for proper depth and for iScan
stability. If depth is inconsistent
check airbag pressure and coulter
settings.
4. Make sure EC values read -1 on
headlands or whenever implement is
raised. This code ensures data is
only logged when the iScan is
engaged in the soil. If data points
are evident when implement is
raised, some EC troubleshooting is
needed.
Data Quality Troubleshooting: EC
If there are positive EC values appearing when implement is raised (should be -1), or if the EC values are
extremely erratic, conduct Service Procedure #4. If the EC readings for the most part are acceptable but are
noisier than desired:
1.
Check depth and down pressure settings covered previously in this section. Make sure all soil engaging
components are in consistent contact with moist soil.
2.
Perform Signal tests
at least once a week during mapping season
every 40 hours of mapping
after extended periods of non-use
after replacing or repairing electrode components or wiring
whenever readings are questionable
Data Quality Troubleshooting: Optical
1. Inspect window for possible breakage or soil buildup
2. Check angle of implement: is system running level?
3. Verify optical module is firmly pressing into moist soil at a 1.5-3" (3-6 cm) depth.
4. Check plant residue buildup around iScan runners; remove if necessary and consider lowering front
coulter
Figure 7
5-3
Pub# OM22-iScan EC-OM
Various system
warnings will
appear here
Advertisement
