Key Takeaways:
- Valley and AgSense do not publish a single exhaustive public alarm code list — alerts are reported as descriptive text categories rather than numeric codes, making understanding alert class more useful than memorizing specific codes
- AgSense 365 converts Valley ICON panel alarm states into push notifications and email alerts with descriptive text — the alert message identifies the alarm category, the timestamp, and on Machine Diagnostics-equipped systems, the specific tower location
- The five main AgSense alert categories — safety stop, stuck pivot, power/pressure fault, end-of-field stop, and configuration alert — each have a distinct response protocol ranging from immediate technician dispatch to simple remote restart
- A stuck pivot alert requires field inspection before restart — never remotely restart a pivot that reported stuck without confirming no physical obstruction or structural problem caused the stop
- Machine Diagnostics alerts on ICON7 and ICON10 systems provide tower-level hardware information that narrows the fault location before field dispatch — reading the full alert detail before calling a technician saves time and informs what parts to bring
Valley ICON panels do not communicate through a numbered fault code list — they report alarm conditions as descriptive text states that AgSense 365 converts into push notifications and email alerts delivered to your smartphone. Understanding what each alert category means, what condition triggered it, and what the correct response is determines whether you restart remotely in two minutes, dispatch a technician immediately, or make an informed decision about whether the situation is urgent enough to interrupt a night’s sleep. This guide covers the complete AgSense 365 alert taxonomy for commercial soybean pivot operations, with response protocols for each category.
How AgSense 365 Reports Valley ICON Alarms
When a Valley ICON panel detects a fault condition or alarm state, it reports that state to the AgSense 365 platform through the cellular or BaseStation3 Wi-Fi connection. AgSense translates the panel state into a human-readable push notification and email alert that identifies: the alert type (safety stop, stuck, power issue, etc.), the time the alert was generated, the pivot name or ID, and on Machine Diagnostics-equipped systems, any tower-level hardware data associated with the alarm.
The alert arrives within 1–3 minutes of the panel detecting the fault condition on cellular-connected systems — faster on BaseStation3 Wi-Fi-connected systems with reliable local internet. Alert delivery speed is cellular-dependent; in low-signal areas, alerts may be delayed or require a manual status refresh in the app. Confirm your pivot’s cellular connectivity and alert delivery reliability before the irrigation season begins — a system that delivers alerts unreliably provides false security rather than the operational protection remote monitoring is intended to deliver.
The Five Main AgSense Alert Categories and Response Protocols
| Alert Category | What Triggered It | Immediate Action | Remote Restart Appropriate? | Technician Required? |
|---|---|---|---|---|
| Safety Stop | Safety circuit interrupted — cable fault, connector fault, or end-tower switch activation | Read full alert detail including Machine Diagnostics data; check event log for preceding events | Only after identifying and resolving the fault cause — never blindly | If cable break or component fault confirmed |
| Stuck Pivot | Pivot arm stopped moving without a panel-initiated stop command — mechanical obstruction, drive fault, or alignment issue | Do not restart remotely — drive to field and inspect before any restart attempt | No — field inspection required first | If mechanical cause confirmed (gearbox, motor, tire) |
| Power / Pressure Fault | Electrical supply problem or low-pressure water supply condition detected | Check pump station status; verify utility supply; confirm pressure switch condition | After confirming supply issue resolved — not before | If pump fault or utility problem confirmed |
| End-of-Field Stop | Pivot reached programmed stop-in-slot position — normal operation | Verify position matches expected stop; reverse direction or adjust stop-in-slot setting | Yes — remote direction reversal or restart is the normal response | No |
| Configuration / Programming Alert | Panel setting conflict, GPS position anomaly, or programming parameter out of range | Review panel settings in AgSense app; check GPS position for unexpected location | After confirming no physical problem underlies the configuration alert | If GPS or panel hardware fault suspected |
Safety Stop Alerts: The Most Common and Most Variable
Safety stop alerts are the most frequent AgSense alert category on commercial soybean pivot operations and the most variable in their implications — ranging from a simple end-tower switch reset to a serious cable fault requiring technician service. The alert text alone does not distinguish between these scenarios; the event log and Machine Diagnostics data are what provide the diagnostic information needed to select the right response.
Reading the Event Log Before Responding
The AgSense 365 event log records the sequence of panel states leading to any alert — available in the app under the pivot’s event history. Reading the event log chronologically before any response decision is the single highest-value action after receiving a safety stop alert. A log showing “water pressure normal → motor running → safety stop” points to a spontaneous safety circuit event. A log showing “pressure drop → motor stop → safety stop” indicates a water supply problem that cascaded into a safety stop — a fundamentally different diagnostic picture that points to the pump station rather than the pivot arm.
Machine Diagnostics Data in Safety Stop Alerts
On ICON7 and ICON10 systems with Machine Diagnostics enabled, safety stop alerts include tower-level hardware data — tire pressure readings and drive unit status at each tower at the time of the stop. A safety stop alert accompanied by a low tire pressure reading at tower 5 tells you immediately which tower to inspect and what you are likely to find when you get there — a flat drive tire that caused tower misalignment and triggered the safety shutdown. Without Machine Diagnostics, the same safety stop alert requires a full arm walk to locate the problem. The diagnostic time savings from Machine Diagnostics on a large commercial pivot — a 130-acre quarter-section pivot has 7–9 towers to inspect manually — is meaningful at 2 AM in July.
Stuck Pivot Alerts: Never Restart Remotely
A stuck pivot alert — indicating the pivot arm stopped moving without a panel-initiated stop command — is the alert category that most clearly requires field inspection before any restart attempt. The conditions that cause a stuck pivot alert range from a soft spot in the field where a tower tire sank and lost traction, to a mechanical obstruction in the pivot’s path, to a gearbox or drive unit failure that stopped a specific tower from moving. Remotely restarting a pivot that stopped for any of these reasons without field inspection risks worsening the underlying condition — a pivot running with one non-functional tower will rapidly misalign to the point of structural damage.
The correct response to every stuck pivot alert is the same: do not restart remotely, drive to the field, and identify the cause of the stop before attempting any restart. This is the one alert category where the remote monitoring platform’s most valuable function is getting you the alert quickly so you can reach the field faster — not enabling a remote restart that bypasses the inspection requirement.
Power and Pressure Alerts: Check the Supply System First
Power and pressure alerts on AgSense are among the most frequently misdiagnosed — because the pivot panel reporting a power or pressure fault has stopped correctly in response to a problem that originated outside the pivot system itself. Dispatching a pivot technician to a pivot that stopped because a utility pole fuse blew or because a pump motor tripped on thermal overload is a wasted service call that delays the correct response by hours.
For any power or pressure alert, check external supply systems before assuming pivot component failure. If your pump station has a remote monitoring device — many commercial pump installations include cellular monitoring through systems like Crop Link or standalone pump monitors — check pump station status in parallel with the pivot app. A pump status showing “motor trip” alongside a pivot pressure alert confirms the sequence: pump problem caused pressure loss, pivot stopped correctly. Call a pump contractor, not a pivot dealer.
For the complete electrical fault diagnosis protocol applicable when power issues are confirmed to be within the pivot system itself, see our center pivot electrical fault diagnosis guide. For the full Valley ICON panel buying guide including Machine Diagnostics specification, see our Valley ICON buying guide.
Setting Up AgSense 365 for Optimal Alert Management
AgSense 365 alert configuration determines which conditions generate notifications and how urgently you receive them. Default alert settings on newly commissioned systems may not match your operational management style or risk tolerance — reviewing and customizing alert settings at the beginning of each irrigation season is a worthwhile investment of 20–30 minutes.
- Enable push notifications for all fault categories — not just safety stops. Power alerts, pressure alerts, and stuck pivot alerts received as push notifications allow faster response than email-only delivery
- Set end-of-field stop alerts to your preference — some operators want an alert every time a pivot reaches a stop-in-slot position; others find this creates alert fatigue and prefer to disable end-of-field alerts while keeping fault alerts active
- Verify alert delivery on your specific cellular carrier and location — send a test alert from the app and time the delivery to your phone before the irrigation season starts
- Share alert access with a second operator or trusted neighbor — AgSense 365 supports multiple users on the same pivot; distributing alert responsibility reduces the risk of an undetected overnight shutdown when the primary operator is unavailable
For the full remote monitoring setup guide including BaseStation3 installation for multi-pivot farms, see our Valley ICON remote monitoring guide. For guidance on interpreting alerts from older pivots with AgSense Field Commander retrofit rather than native ICON panels, see our GPS and telemetry retrofit guide.
For more guides on Irrigation Controllers, visit the Aguafox irrigation controllers for soybean farms hub.
Valley ICON Alarm Codes FAQs
Where can I find the complete Valley ICON alarm code list?
Valley and AgSense do not publish a single exhaustive public alarm code list with numeric codes. ICON panel alerts are reported as descriptive text categories — safety stop, stuck, power fault, pressure fault, end-of-field stop — rather than numeric codes. The ICON panel operator manual for your specific panel generation (ICON7, ICON10, ICON5, ICONX, or ICON+) contains the most complete reference for panel alarm states and their meanings. Your authorized Valley dealer can provide the correct operator manual for your panel. Detailed alarm interpretation for your specific installation is also available through Valley’s AgSense support line.
What does a Valley ICON safety stop alert mean?
A Valley ICON safety stop alert indicates the pivot’s safety circuit detected an open or interrupted condition and halted the system. The safety circuit runs continuously through every tower — a cable fault, loose connector, tripped end-tower switch, or physical damage to any element of the circuit produces a safety stop alert. The correct response is to read the event log in AgSense for the event sequence leading to the stop, review any Machine Diagnostics tower data included with the alert, identify the fault cause, and resolve it before restarting. Never clear and restart a safety stop alert without identifying the underlying cause.
What does a stuck pivot alert mean on AgSense 365?
A stuck pivot alert indicates the pivot arm stopped moving without a panel-initiated stop command — meaning no end-of-field stop, safety stop, or operator-initiated stop caused the halt. Common causes include mechanical obstruction in the pivot path, a drive tire flat or stuck in soft soil, a gearbox or motor fault stopping a specific tower, or a severe alignment problem. Do not attempt remote restart on a stuck pivot alert — drive to the field and inspect the full arm before any restart attempt. Restarting a pivot stopped due to a mechanical drive fault risks worsening structural damage or tower misalignment.
Can AgSense 365 tell me which tower caused a safety stop?
On Valley ICON7 and ICON10 systems with Machine Diagnostics hardware enabled, yes — safety stop alerts include tower-level hardware data that can narrow the fault location to a specific tower. On systems without Machine Diagnostics, safety stop alerts identify the event type and timestamp but do not pinpoint the tower location — a full arm walk is required to locate the fault. Machine Diagnostics hardware is available as an addition to ICON7/10 panel configurations — confirm with your Valley dealer whether your specific installation includes it and what the incremental cost is if not.
Valley ICON Alarm Codes: Citations
- Valley Irrigation — AgSense 365 Remote Monitoring: Alert Categories, Push Notification Configuration, Machine Diagnostics Integration, and Event Log Access for Commercial Center Pivot Operations
- Valley Irrigation — ICON Panel Family: Safety Circuit Design, Alarm State Reporting, Machine Diagnostics Tower-Level Monitoring, and Fault Response Protocols
- University of Nebraska-Lincoln CropWatch — Center Pivot Remote Monitoring: Alarm Response Protocols, Fault Diagnosis Sequence, and Safe Restart Procedures for Commercial Irrigators
- Clemson University Agricultural Safety — Center Pivot Safety Circuit Operation: When to Reset, When to Inspect, and When to Call a Technician After an Alarm Event






Leave a Reply