Fronius status codes: a comprehensive guide (100 to 1000 series) and what to do in each case

Fronius inverters (Primo, Symo, Eco, GEN24, Tauro) display a status code on the display, on the web interface and on Fronius Solar.web when they detect anything out of the ordinary. Most of these are alerts that resolve themselves; others indicate a problem with the installation (grid, solar array, cabling); and a few require intervention by the technical support team. This guide organises them by series and tells you what to check in each case.

How codes are organised

  • 100 Series: grid parameters (voltage and frequency). Almost always external to the inverter.
  • 300 Series: power stage and solar array (DC voltage, temperature, overcurrent).
  • 400 Series: hardware and internal communications. They usually require technical support.
  • 500 Series: system: insulation, strings, communication with peripheral devices, power limitations.
  • 600–700 Series: internal components (memory, clock, cards). They rarely affect production.
  • 1000+ Series: messages from the Solar.web platform and Datamanager (connectivity).

100 Series: electricity network

CodeMeaningWhat to do
102Mains voltage too highCommon in rural areas or areas with a high concentration of solar panels. Check the voltage at the connection point and the cross-sectional area of the AC cable leading to the distribution board. If it regularly exceeds 253 V, notify the distribution company.
103Mains voltage too lowVoltage drops on the line or an undersized AC cable.
104Unstable mains voltageIt usually accompanies 102/103.
105Mains frequency too highCheck the country/standard configured for the network (Spain: RD 244 / UNE 217002).
106Frequency too lowDitto. When using a generator, the frequency is often outside the tolerance range.
107Signal outside the permitted range / no signalThe inverter is not detecting the mains supply or is out of range. Check the inverter’s AC circuit breaker and ensure that all three phases are present (Symo).
108Detection of island operationThe inverter believes it is supplying an isolated grid. This may occur on very weak grids; if it happens repeatedly, please contact support.

All the codes in this series are auto-reset: the inverter only reconnects once the grid has stabilised. They are only a problem if they occur on a daily basis and affect output.

300 Series: power amplifier and solar array

CodeMeaningWhat to do
301AC overcurrentIt resets automatically. If the problem persists, check the network.
302DC overcurrentCheck the solar array: there are more panels connected in parallel than the MPPT can handle.
303 / 304DC/AC module overtemperatureInsufficient ventilation or direct sunlight on the inverter. Clean the vents and ensure the distances specified in the manual are observed.
305No power is supplied even though the relay is closedRestart the inverter. If the problem persists, contact SAT.
306Insufficient PV power (LOW PV OUTPUT)Normal at dawn, dusk and when there are thick clouds.
307Insufficient DC voltage (LOW PV VOLTAGE)Normal at the start and end of the day. In direct sunlight, this indicates a disconnected string, a blown fuse or a Voc below the MPPT minimum. See My Fronius isn’t working.
308Intermediate circuit voltage too highAutomatic restart. If the problem persists, contact SAT.
309 / 313Input voltage too high at MPPT1 / MPPT2There are more panels in the string than the inverter can handle (maximum 1,000 V for the Primo/Symo models, 600 V for the GEN24 model, depending on the model). Correct the string before the equipment is damaged.
314 / 315Calibration error / current sensorSAT.
325Overheating in the connection areaAC/DC terminals are not tightened properly or are of insufficient cross-section. Check whilst the equipment is switched off.
326 / 327Fan failureClean the fan; if it does not turn, replace it (this is a common spare part for the Primo/Symo models).

400 Series: hardware and internal communication

These codes indicate a fault between the power stage and the inverter control unit. The first step is always to full reset (AC and DC switched off for 5 minutes). If the error code reappears, you must raise a ticket with the SAT.

CodeMeaning
401No communication with the power stage
406 / 407Faulty temperature sensor
408A direct current injection has been detected in the grid
412Fixed voltage mode instead of MPP (check the setting in the menu – this is not a fault)
415Safety shutdown via optional card or Datamanager
416No communication between the power stage and the control stage
417 / 419Hardware identification conflict (common after replacing a power amplifier stage)
420No communication with the Hybrid Manager (GEN24 with battery)
425No communication with the power stage
431 / 436 / 438Software incompatibility: update the firmware (see how to update)
443Low or asymmetrical intermediate circuit voltage
447 / 475Insulation fault in the solar array (see 502)
448Neutral not connected (Symo three-phase): check terminal N
457Network relay stuck or neutral-to-earth voltage too high
463Reversed AC polarity: check L and N
474Faulty RCMU sensor
476Driver supply voltage too low
480 / 481Functional incompatibility: firmware
482Set-up interrupted: repeat the initial wizard
489Persistent overvoltage in the intermediate circuit

500 Series: system

CodeMeaningWhat to do
502Insulation fault in the panelsMoisture in MC4 connectors, stripped cable or a panel with a ground fault. This mainly occurs in the morning when there is dew and disappears once it dries out. If the problem persists, the insulation resistance of each string must be measured.
509No injections in the last 24 hoursThe inverter has not been generating power for a day: the DC disconnector is open, the fuses have blown, there is snow, or the inverter is in standby mode.
515No communication with the filterRestart; if the problem persists, contact SAT.
516No communication with the storage unitGEN24 with battery: check the communication cable connected to the battery and its power supply.
517Temperature-dependent deratingThe inverter reduces power output to protect itself. Improve ventilation.
518Internal ruling by the DSPSAT.
520No communication with the power stageSAT.
522 / 523Low DC voltage in string 1 / string 2One string is producing less than the other: shadow, blown fuse, loose connector or damaged panel. Compare the curves for each MPPT on Solar.web.
558 / 559 / 564Functional incompatibilityUpdate the firmware.
560Power reduction due to over-frequencyRegulatory requirement: the inverter reduces power output when the grid frequency rises above 50.2 Hz.
566Arc detector deactivatedFor information purposes only (models with AFCI).
567Power reduction due to mains voltageThe inverter cuts out to prevent the mains voltage from rising any further. If this happens regularly, check the AC wiring or ask your electricity supplier to adjust the transformer.
568No communication with the smart meterCheck the Modbus RTU cable, the terminating resistor and the meter’s address. See Smart Meter and feed-in 0.

600–700 Series: internal information

Codes such as 601 (CAN bus full), 701–704 (start-up information), 705–716 (memory and clock) or 721–728 (data log) are for information purposes only. If they appear in isolation, no action is required. If error codes 705/706 (memory error) recur after a reset, the inverter must be checked.

1000 Series: Solar.web and connectivity

  • 1030: Solar.web has lost communication with the inverter. This is not a fault with the inverter: it is due to a WiFi/LAN issue, the Data Manager or a power cut. See Solar.web offline.
  • 1055 / 1056: Messages from the Fronius Smart Meter (no data / values outside the range).
  • 1070+: Battery management alerts on the GEN24 Plus (SOC, temperature, charging limits).

What to do before contacting technical support

  1. 1. Make a note of the exact code and the time it appears (Solar.web → Messages).
  2. 2. Restart the inverter: switch off the AC circuit breaker, then the DC isolator; wait 5 minutes and switch them back on in reverse order (DC first, then AC).
  3. 3. Check that the firmware is up to date.
  4. 4. Check the mains voltage and the condition of the solar array (fuses, connectors, shading).
  5. 5. If the error code reappears, create a support ticket including the serial number, model, error code and a screenshot from Solar.web.

FV Componentes is Fronius authorised technical service centre (Fronius System Partner). If the problem persists after carrying out these checks, please open a ticket at Technical support with the serial number and a screenshot of Solar.web, and we’ll diagnose it.

Share this post:

Other blog entries