Skip to content

SolarEdge System Architecture

Understanding why SolarEdge works the way it does makes troubleshooting and diagnostics vastly more intuitive. Do not skip this section.


Traditional String Inverter vs. SolarEdge

Traditional String Inverter

Panel A → ─────┐
Panel B → ─────┤→ String → Inverter (one MPPT for the whole string)
Panel C → ─────┘
Panel D (shaded) → ─┘

If Panel D is shaded or underperforming, the entire string is dragged down to that panel's operating point. The inverter can only track one maximum power point for the whole string.

SolarEdge Optimized Architecture

Panel A → [Optimizer A] ─┐
Panel B → [Optimizer B] ─┤→ Optimized DC string → SolarEdge Inverter
Panel C → [Optimizer C] ─┤
Panel D → [Optimizer D] ─┘
(each optimizes independently)

Every panel runs at its own maximum power point. Panel D being shaded only affects Panel D. The string continues to produce at full potential from Panels A, B, and C.


Fixed-Voltage String Architecture

SolarEdge optimizers output a fixed, regulated voltage to the string. Unlike traditional strings where voltage varies with temperature and irradiance, a SolarEdge string maintains a constant target voltage set by the inverter.

This simplifies the inverter design and allows: - Better performance over wide temperature ranges - Accurate per-optimizer monitoring - SafeDC shutdown capability


Monitoring Architecture

Optimizers → (RS485 or wireless) → Inverter → (Ethernet/Wi-Fi/Cellular) → SolarEdge Cloud
                                                                   Monitoring Dashboard

Each optimizer reports its data to the inverter, which aggregates and sends it upstream. If the communication path from the inverter to the cloud is broken, you lose monitoring data but not production.

If the RS485 chain from optimizers to inverter is broken, you lose per-module visibility but often maintain system production (the string still generates).


SafeDC Architecture

SolarEdge's SafeDC is a regulatory requirement in many jurisdictions (especially rapid shutdown compliance):

  1. AC grid drops / main AC disconnect opened
  2. Inverter detects loss of AC
  3. Inverter sends shutdown command via the DC bus to all optimizers
  4. Each optimizer reduces output to ~1V DC
  5. Total string voltage: (number of optimizers) × ~1V = effectively safe

This is why SolarEdge is widely used in code-compliant installations requiring rapid shutdown. The rapid shutdown command propagates through the existing DC wiring — no separate communication wire required.


Communication on the DC String

Optimizers communicate with each other and with the inverter using power line communication (PLC) — signals embedded in the DC power wiring itself. This means:

  • No separate communication cable between optimizers
  • A break in the DC string breaks communication downstream of that break
  • A failed optimizer may appear as "not communicating" even if the string itself still produces power

Key System Boundaries

Boundary What It Separates Why It Matters
Panel → Optimizer Module DC vs. optimized DC Optimizer failure here = module data lost
Optimizer → Inverter (DC string) Optimized DC vs. inverter conversion String fault here = section offline
Inverter → Grid (AC) DC/AC conversion boundary SafeDC activates here
Inverter → Cloud Local system vs. monitoring Cloud loss ≠ production loss