SolarEdge Troubleshooting Guide¶

EXPANDING

This guide covers the most common SolarEdge field faults encountered in Wadadli Solar operations. Each entry documents the finding, diagnosis path, and confirmed resolution where available.

Troubleshooting Approach¶

1. REMOTE REVIEW via SolarEdge GO (before arriving on site)
   - Check GO fleet dashboard for active alerts
   - Review event log and optimizer status remotely
   - Determine if site visit is actually required

2. ARRIVE → document physical state of inverter LEDs and display

3. CONNECT via SolarEdge GO (Bluetooth)
   - Real-time status
   - Event log (last 7 days minimum)
   - String and optimizer status
   (Use SetApp if GO cannot connect on a legacy system)

4. IDENTIFY the boundary
   - Is this an inverter issue?
   - Is this a string/optimizer issue?
   - Is this a communication issue?
   - Is this a grid issue?

5. CONFIRM with physical measurements before replacing hardware

Fault Categories¶

Inverter FaultsOptimizer FaultsCommunication Faults

Grid Voltage Out of Range¶

Symptoms: Inverter offline, grid fault LED, "Grid Voltage High" or "Grid Voltage Low" in event log

Diagnosis: - Check actual grid voltage at AC output with meter - SolarEdge default operating range: ~211–244V (120V systems) or per country code - Persistent fault = utility issue or wiring problem

Resolution: Wait for utility to normalize (if utility issue). If wiring problem: check AC connections.

Isolation Fault (GFDI)¶

Symptoms: GFDI fault in event log, red fault LED, system offline

Diagnosis: - Isolation faults indicate a path between PV wiring and ground - Causes: damaged module, degraded wiring insulation, water intrusion, rodent damage - Requires systematic isolation of strings to find the faulted circuit

Resolution: Inspect wiring and modules methodically. Do not repeatedly reset and ignore.

Arc Fault (AFCI)¶

Symptoms: AFCI fault, system offline, no production

Diagnosis: - AFCI triggers when the inverter detects high-frequency noise patterns consistent with arcing - Common causes: loose or damaged MC4 connectors, damaged wiring, poor crimp connections

Action: Full inspection of all DC wiring and connectors before reset. Locate and repair the arc source.

Do Not Bypass AFCI

Arc faults can cause fires. Do not disable or repeatedly override AFCI without identifying and correcting the root cause.

Over-Temperature Shutdown¶

Symptoms: Inverter shuts down during high production periods (hot summer afternoons)

Diagnosis: - Check ventilation clearances (typically 25cm from all sides, check spec sheet) - Check ambient temperature in inverter location - Check that ventilation slots are clear

Resolution: Improve airflow. Add shade cover if in direct sunlight (without blocking ventilation).

Single Optimizer Not Reporting¶

Symptoms: One module shows "not communicating" in monitoring; gray on map

Diagnosis: 1. Check if the optimizer is the last in a daisy-chain — a break before it will take it offline 2. Inspect MC4 connections at that optimizer 3. Check optimizer LED (visible from below panel) 4. Swap with a known-good optimizer to confirm hardware vs. wiring

Resolution: Replace optimizer if confirmed failed.

String Offline (Multiple Optimizers)¶

Symptoms: Entire string showing offline or zero production

Diagnosis: 1. Check DC disconnect for that string 2. Verify string is wired to correct combiner input 3. Measure open-circuit voltage on the string at the combiner or inverter input 4. If voltage is zero: string is physically disconnected or all panels are covered 5. If voltage is present: inverter or combiner input issue

No Monitoring Data¶

Symptoms: Site shows "offline" in monitoring portal, last data is hours or days old

Diagnosis: 1. Is the inverter still producing? (Check display or SolarEdge GO via Bluetooth) 2. If producing: communication issue only — not urgent for power, but needs resolution 3. Check Wi-Fi credentials (has client changed router/password?) 4. Check RS485 wiring if applicable 5. Check cellular kit connection if applicable

Resolution: Restore communication path per Communication Systems.

Field Decision: Replace vs. Troubleshoot¶

Scenario	Decision
Single optimizer failed, hardware confirmed	Replace
Single optimizer, unclear cause	Verify connections first
Inverter with persistent fault after reset	Escalate to SolarEdge support
Arc fault, cause found	Repair cause, reset, monitor
Arc fault, cause not found	Do not restart — escalate
Communication only issue	Fix comms, no hardware replacement

Escalation to SolarEdge Support¶

When to call SolarEdge tech support: - Persistent faults that field troubleshooting cannot resolve - Inverter hardware failure (not optimizer) - Warranty replacement authorization - Firmware upgrade issues

Have ready: Inverter serial number (from nameplate or SolarEdge GO), site ID in GO fleet view, event log export from GO.