This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| electrical:start [2026/01/21 22:27] – bsamuel | electrical:start [2026/01/22 15:22] (current) – [4. Implementation Guidelines] bsamuel | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Electrical & Power Control Interfaces ====== | ====== Electrical & Power Control Interfaces ====== | ||
| + | AOFS defines the electrical and power control architecture to **safely operate pumps, valves, and irrigation loads** under any power source. | ||
| + | It is designed to **ensure fail-safe operation, energy efficiency, and compliance with AOFS standards**, | ||
| + | ===== 1. Core Power Principles ===== | ||
| + | * AOFS is **power-source agnostic**: it works with grid, generator, solar, or hybrid systems. | ||
| + | * Controllers must enforce **fail-safe operation** for irrigation and actuation regardless of the power source. | ||
| + | * Systems must support **safe shutdowns** in case of power anomalies or failures. | ||
| + | * AOFS may track **energy consumption of pumps and actuators** to support optional logging, reporting, and operator awareness. **Recommended for off-grid or weak-grid farms, but not required** for farms with stable grid power. | ||
| - | ===== Solar & Power Integration ===== | + | ===== 2. Optional |
| + | AOFS supports optional solar monitoring for farms that want to optimize energy usage: | ||
| - | AOFS is designed to operate with any existing power infrastructure: | + | * **Level 1 – Minimal Monitoring (Recommended for off-grid / weak-grid farms)** |
| + | | ||
| + | | ||
| + | * Fully optional for farms with stable grid or generator power. | ||
| - | AOFS defines | + | |
| + | * Controllers can read solar generation metrics from panels/ | ||
| + | * Enables dynamic irrigation scheduling based on energy availability. | ||
| + | * Supports advanced PUE analytics and reporting. | ||
| + | * Completely optional — AOFS compliance does **not depend** on it. | ||
| - | * **Level 1 (Recommended / Minimal Monitoring)** | + | ===== 3. Optional Energy-Aware Operation ===== |
| - | * Field Controllers may monitor battery voltage and current to enforce fail-safes and manage irrigation loads. | + | |
| - | * Useful for off-grid or weak-grid farms to improve reliability. | + | |
| - | * **Not required** if the farm has a reliable main power supply. | + | |
| - | * **Level 2 (Optional / Integrated Monitoring)** | + | * AOFS controllers |
| - | * Controllers can read solar generation metrics via standard protocols (e.g., Modbus, MQTT, RS485). | + | * Controllers |
| - | * Enables dynamic | + | * AOFS supports **event prioritization**: |
| - | * Fully optional: | + | * 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 | ||
| + | * 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. | ||
| + | * AOFS can provide **real-time anomaly detection** (optional): | ||
| + | * If an event starts drawing **more power than usual**, the controller | ||
| + | * Examples include: | ||
| + | * Clogged pipes increasing pump load. | ||
| + | * Valves partially stuck or leaking. | ||
| + | * Unexpected actuator malfunction. | ||
| + | * Provides actionable insight so operators can **investigate, | ||
| + | * All energy measurements, | ||
| + | * Enables visualization of energy | ||
| + | * Helps operators determine if **additional batteries, solar panels, or load rescheduling** are needed. | ||
| - | **Guidelines:** | + | |
| - | * AOFS compliance does **not require any specific power monitoring**. | + | ===== 4. Optional Generator Integration ===== |
| - | * Optional monitoring modules | + | |
| - | * All modules, regardless of power source, must support safe fail-safe operation | + | AOFS supports optional generator-based backup to supplement energy supply for irrigation and other actuator events. |
| + | |||
| + | | ||
| + | * If a compatible generator with remote start/stop interface is available, the system **may automatically start** it when energy is insufficient for scheduled events. | ||
| + | * Remote interfaces can include: relay, Modbus, CAN, or other compatible protocols. | ||
| + | | ||
| + | * Prevent start during maintenance. | ||
| + | * Prevent overload or dry-run conditions. | ||
| + | * All starts/ | ||
| + | |||
| + | * **Manual Alert Generator Start (Optional)** | ||
| + | * If a generator exists but cannot be automatically started, AOFS can **alert operators** when battery or energy is insufficient. | ||
| + | * Example alert: " | ||
| + | * Operators can then **manually start** the generator. | ||
| + | * The system continues to monitor energy availability and advise operators on priority and schedule adjustments. | ||
| + | |||
| + | * **Integration with Event Prioritization** | ||
| + | * Both automatic and manual generator options respect **event urgency**. | ||
| + | * Low-priority irrigation can be delayed, while high-priority events trigger generator use. | ||
| + | * Energy logs and operator actions are **recorded** to support farm management decisions and future optimization. | ||
| + | |||
| + | * **Optional Analytics** | ||
| + | * Tracks generator runtime, energy supplied, and efficiency. | ||
| + | * Helps farm managers decide if **additional batteries, solar panels, or load rescheduling** are needed. | ||
| + | |||
| + | |||
| + | ===== 5. Implementation Guidelines ===== | ||
| + | * AOFS compliance does **not require any specific power source, | ||
| + | * Optional monitoring modules | ||
| + | * All controllers and modules, regardless of power source, | ||