This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| actuation:start [2026/01/21 23:20] – created bsamuel | actuation:start [2026/01/21 23:29] (current) – [7. Manual Fallback Mode] bsamuel | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Valves, Pumps & Actuation ====== | ====== Valves, Pumps & Actuation ====== | ||
| - | The **Actuation Layer** defines all AOFS-compliant devices that perform actions on the farm. This includes irrigation pumps, valves, gates, and optionally generator start/stop controls. | + | The **Actuation Layer** defines all AOFS-compliant devices that perform actions on the farm. |
| + | This includes irrigation pumps, valves, gates, and optionally generator start/stop controls. | ||
| All actuators must comply with AOFS **safety, logging, and operational rules**, even if the system operates offline. | All actuators must comply with AOFS **safety, logging, and operational rules**, even if the system operates offline. | ||
| Line 9: | Line 11: | ||
| * Controls water delivery from sources to storage tanks or irrigation manifolds. | * Controls water delivery from sources to storage tanks or irrigation manifolds. | ||
| * Must support: | * Must support: | ||
| - | * Start/stop commands from Field Controller. | + | * Start/stop commands from [[architecture: |
| * Safety interlocks (tank FULL/LOW, low voltage, pressure limits). | * Safety interlocks (tank FULL/LOW, low voltage, pressure limits). | ||
| * Optional energy-aware operation: integrate with [[electrical: | * Optional energy-aware operation: integrate with [[electrical: | ||
| Line 33: | Line 35: | ||
| * **Fail-Safe Operation: | * **Fail-Safe Operation: | ||
| * Hardware and software protections prevent flooding, over-irrigation, | * Hardware and software protections prevent flooding, over-irrigation, | ||
| - | * Actuators must respond to **LOW/FULL tank switches, flow/ | + | * Actuators must respond to [[sensors: |
| * **Energy-Aware Operation (Optional): | * **Energy-Aware Operation (Optional): | ||
| Line 65: | Line 67: | ||
| * Timestamp | * Timestamp | ||
| * Operator ID (if manual) | * Operator ID (if manual) | ||
| - | * Sensor | + | * Relevant sensor |
| * Logs are **synchronized with Farm and HQ Controllers** when connectivity is available. | * Logs are **synchronized with Farm and HQ Controllers** when connectivity is available. | ||
| Line 82: | Line 84: | ||
| * Follow AOFS modular interface rules. | * Follow AOFS modular interface rules. | ||
| - | ===== 6. References ===== | + | ===== 6. Optional Energy-Aware Operation ===== |
| + | |||
| + | * AOFS controllers **may** measure power consumption of pumps, valves, and other actuators while running. | ||
| + | * Controllers **may** estimate battery drain or energy availability for upcoming scheduled irrigation events. | ||
| + | * AOFS supports **event prioritization**: | ||
| + | * Each scheduled irrigation or actuator event can be assigned an **urgency or importance level** by operators. | ||
| + | * If insufficient energy is available: | ||
| + | * Low-priority events can be **delayed or skipped**. | ||
| + | * High-priority events are executed **as soon as sufficient energy is available**. | ||
| + | * Optional alerts notify operators of skipped or delayed events. | ||
| + | * AOFS can provide **proactive scheduling guidance** (optional): | ||
| + | * When the operator attempts to schedule an irrigation or actuator event, the system **may simulate expected energy usage and availability**. | ||
| + | * The controller can then **warn the operator**: "Based on current energy estimates, you will most likely not have enough power for this event." | ||
| + | * Operators may then adjust **priority, timing, or load** before committing the schedule. | ||
| + | * All energy measurements, | ||
| + | * Enables visualization of energy usage and event execution history. | ||
| + | * Helps operators determine if additional batteries, solar panels, or load rescheduling are needed. | ||
| + | * Optional anomaly detection: | ||
| + | * Alerts operators if an actuator consumes more power than expected (e.g., clogged pipe, stuck valve). | ||
| + | |||
| + | ===== 7. Manual Fallback Mode ===== | ||
| + | |||
| + | AOFS supports **manual fallback operation** for farms without fully automated actuators. | ||
| + | |||
| + | * **Purpose: | ||
| + | * Ensure irrigation and critical farm operations can continue when automatic valves or pumps are unavailable. | ||
| + | * Maintain safety, compliance, and event logging even with manual operation. | ||
| + | |||
| + | * **Operation: | ||
| + | * Field Controller generates **step-by-step instructions** for operators: | ||
| + | * Which pump to switch on/ | ||
| + | * Which valve to set to open/closed or partial position. | ||
| + | * Timing recommendations based on **irrigation schedule, soil moisture, tank levels, and weather conditions**. | ||
| + | * Operators must **confirm completion of each step** in the controller interface. | ||
| + | |||
| + | * **Logging & Documentation: | ||
| + | * All manual actions **must be logged**: | ||
| + | * Operator ID | ||
| + | * Action taken (pump/ | ||
| + | * Timestamp | ||
| + | * Relevant sensor readings at the time (tank level, flow, battery voltage, etc.) | ||
| + | * Logs are synchronized with Farm/HQ controllers whenever connectivity is available. | ||
| + | |||
| + | * **Benefits: | ||
| + | * Allows farms to **comply with AOFS even with low-tech equipment**. | ||
| + | * Ensures operators follow optimized schedules and safety procedures. | ||
| + | * Enables full **auditing and analytics** later when automation is introduced. | ||
| + | |||
| + | ===== 8. References ===== | ||
| * [[sensors: | * [[sensors: | ||
| Line 88: | Line 138: | ||
| * [[operations: | * [[operations: | ||
| * [[hydraulics: | * [[hydraulics: | ||
| - | * [[electrical: | + | * [[electrical: |
| + | * [[electrical: | ||