How to Verify a Missed OpenSprinkler Irrigation Event
A practical evidence checklist for separating a pending event, a missed event, a short runtime, and a controller-program mismatch.
Read field noteGrower Field Notes
Original field guidance on crop steering, measured delivery, plant response, and safe OpenSprinkler automation. Every note is reviewed through a grower’s operating lens.
A practical evidence checklist for separating a pending event, a missed event, a short runtime, and a controller-program mismatch.
Read field noteHow schedule-source proof prevents stale times, flattened runtimes, and incomplete zone programs from reaching a controller.
Read field noteA practical method for converting a timed catch test into the flow value used to calculate cannabis irrigation runtime.
Read field noteA grower-focused explanation of substrate recharge, maintenance irrigation, and the planned dryback window.
Read field noteCrop steering, controller programming, and plant-response measurements solve different parts of the irrigation day. These guides connect the biological target, the measured delivery, and the controller evidence without treating them as one hidden calculation.
See how stage, substrate, flow, and response become visible P1, P2, and P3 events.
Understand the preflight, translation, persistence, and execution checks around controller deployment.
Keep runoff, dryback, VWC, and EC measurements distinct and scoped to the table that produced them.