Representative Sensors, Calibration and Data-Quality Verification
Technician II troubleshooting starts by asking whether the data deserve to drive a decision. Placement, shielding, crop plane, response time, calibration history, maintenance history and agreement with independent measurements all affect whether a sensor represents the condition under investigation.
Learning objectives
- LO-LH-TECH2-002-01
- LO-LH-TECH2-002-06
Key vocabulary
How well a measurement describes the location, crop zone or process condition relevant to the decision.
Temporary comparison of sensors at the same location to determine whether disagreement follows the instrument or the environment.
A documented reason a value may be unreliable, incomplete, unrepresentative or unsuitable for a specific decision.
Placement is part of the measurement
Wall, return-air and canopy sensors can describe different microenvironments. Record exact position, height, shielding and crop context before treating disagreement as instrument failure.
Use comparison before conclusion
Colocated comparison with a verified instrument helps distinguish a spatial gradient from sensor bias or drift. A comparison should use enough stabilization time and the same exposure conditions.
Preserve questionable data instead of hiding it
If a sensor is suspected, flag the value, record why, preserve the original data and document the comparison or calibration evidence. Do not change setpoints or records merely to make the dashboard look normal.
Worked examples
- A wall sensor and canopy probe disagree; moving a verified reference beside each sensor shows the difference follows location, supporting a real spatial gradient.
- A probe remains offset from a verified reference when colocated, so the reading is flagged and the instrument is routed through the authorized calibration/maintenance process.
Common mistakes
- Calling every disagreement a calibration failure.
- Comparing sensors in different locations and treating the comparison as a calibration test.
- Deleting or overwriting data after deciding a sensor is suspect.
Practical application
Create a sensor-verification record including device ID, exact location, comparison instrument, stabilization period, paired readings, calibration status, data-quality disposition and escalation decision.
Lesson summary
Reliable troubleshooting starts by verifying that sensor data are representative, comparable and documented well enough to support the decision being made.