SolarEdge GO — Diagnostics & Alerts¶
ACTIVE WORKFLOW
SolarEdge GO diagnostics allow Wadadli Solar technicians to investigate system behavior both remotely (via cloud) and locally (via Bluetooth on-site). Effective use of GO diagnostics reduces unnecessary site visits and ensures technicians arrive prepared when a visit is required.
Diagnostic Strategy Overview¶
ALERT RECEIVED (in GO fleet dashboard)
↓
REMOTE REVIEW — check system status, event log, optimizer map via GO cloud
↓
DECISION POINT:
→ Remote resolve: communication fix, grid fault self-resolved, false positive
→ Schedule visit: hardware fault, arc/ground fault, unresolved production loss
→ Monitor: intermittent issue, low severity, self-recovering
Using GO diagnostics before dispatching a technician means: - Fewer unnecessary site visits - Technicians arrive prepared with specific fault context - Issues that can be resolved remotely are handled without a truck roll
Remote Diagnostics (No Site Visit Required)¶
Remote diagnostics use the inverter's cloud connection — no Bluetooth required.
System Status Check¶
- GO → Sites → select site
- Review real-time status:
- Current production (kW)
- System state (Producing / Error / Standby)
- Active alert summary
- Check Last Communication timestamp — if >6 hours, communication path may be the issue, not the equipment
Remote Event Log Access¶
- GO → Site → Diagnostics → Event Log
- View timestamped events for the past 7, 30, or 90 days
- Look for:
- Fault codes with timestamps
- Whether faults are persistent or cleared
- Whether faults correlate with weather events, time of day, etc.
Remote Optimizer Status¶
- GO → Site → Diagnostics → Module Monitoring
- View the optimizer map — color-coded by status:
- Green: Normal, communicating
- Yellow: Warning or degraded
- Red: Fault
- Gray: Not communicating
- If one optimizer is gray in an otherwise healthy string: isolated hardware issue
- If an entire string is gray: string-level problem (DC wiring, connection, string break)
- If all optimizers are gray but inverter is online: PLC communication issue
Remote vs. Real-Time
Remote optimizer status reflects the last reported data, which may be several minutes old. For real-time status, connect locally via Bluetooth.
Local Diagnostics (Bluetooth On-Site)¶
Local BT diagnostics in GO are functionally equivalent to SetApp diagnostics — the same data, the same screens, now in the GO interface.
Connecting Locally¶
- GO → Site → Connect
- Stand within 10m of inverter
- Bluetooth pairs automatically
- Local mode indicator appears — all data is now real-time
Local Event Log¶
More current than the cloud-synced version. Useful when: - The cloud connection is down (event log still accessible locally) - You need real-time event data, not cached cloud data - Investigating an intermittent fault that hasn't yet synced
String and Optimizer Status (Local)¶
- GO (BT connected) → Module Monitoring
- Real-time per-optimizer voltage, current, and status
- Tap any optimizer for individual detail
- Identify underperforming optimizers by comparing to neighbors on the same string
Power and String Data¶
- GO (BT connected) → Power Control or String Data
- View DC input voltage and current per string
- Compare against expected values:
- Open circuit voltage: approximately (Voc of panel) × (optimizers in string)
- Production current: varies with irradiance — compare string-to-string
Alert Investigation Workflows¶
Arc Fault (AFCI)¶
- Remote check: Confirm system is offline, alert is active
- Pre-visit review: Check event log for frequency — first occurrence or repeated?
- On site: Connect via GO locally, confirm fault state
- Physical inspection: All DC wiring, MC4 connectors, junction boxes
- Resolution: Locate and repair wiring fault → reset via GO → monitor
Never Reset AFCI Without Physical Inspection
Arc faults can cause fires. Do not reset and hope. Find the cause first.
Ground Fault (GFDI)¶
- Remote check confirms system offline
- On site: isolate strings systematically to find the faulted circuit
- Common causes: damaged insulation, rodent damage, water intrusion, cracked module
- Use megohmmeter to measure insulation resistance string by string
- Repair → reset via GO → confirm normal operation
Optimizer Not Reporting¶
- Remote check: single optimizer gray in fleet view
- Check if production is affected — single optimizer offline rarely causes major loss
- Pre-visit: note position in array (row/column from GO module map)
- On site: inspect MC4 connections at that optimizer, check LED state
- If LED off: no power, check string continuity
- If LED red: optimizer fault, replace unit
- After replacement: confirm new unit appears in GO within a few minutes
Communication Failure¶
- Remote check: site shows "no communication" or last data timestamp is hours old
- Is production still happening? (Check last known production before communication dropped)
- Remote investigation:
- Has anything changed at the site? (Client-reported router change, power outage?)
- Is this a single inverter or multi-inverter site? (All offline or just one?)
- Resolution path:
- Wi-Fi: re-enter credentials via GO (BT connected on site)
- Ethernet: check cable, router port
- Cellular: check signal, verify SIM active
- Confirm cloud connection restores in GO fleet view
Over-Temperature Shutdown¶
- Remote check: note time of fault — mid-day peak heat?
- Is this a one-time event or recurring?
- On site: check ventilation clearances, debris on inverter vents, direct sunlight exposure
- Resolution: clear obstructions, improve airflow, add shade cover if needed
- Document ambient temperature conditions in site notes
Remote Inverter Access¶
On inverters with compatible firmware, GO supports remote access features that allow certain diagnostics and limited configuration without a site visit:
- Remote event log refresh
- Remote status polling
- Remote communication settings update (Wi-Fi SSID/password)
- Alert acknowledgment and notes
Feature Availability Varies by Firmware
Not all remote access features are available on all inverter firmware versions. GO will indicate what's available for each site. When remote access is not possible, Bluetooth local connection is required.
Diagnostic Triage Decision Guide¶
| Situation | Remote Diagnosis Sufficient? | Site Visit Needed? |
|---|---|---|
| Communication failure, production was normal before | Often yes — fix remotely | Only if remote fix fails |
| AFCI or GFDI fault | No | Yes — always inspect physically |
| Single optimizer offline | Yes (assess impact) | If hardware replacement confirmed |
| String offline | Partial — identify, but verify on site | Usually yes |
| Grid fault, self-resolved | Yes | No unless recurring |
| Unexplained production decline | Yes (rule out communication) | Yes if real production loss confirmed |
| Over-temperature, first occurrence | Yes | Not urgent, schedule next visit |
| Over-temperature, recurring | Yes (document) | Yes — address root cause |