The Complete Guide To APsystems Microinverter Error Codes

APsystems micros stop when the mains voltage or frequency leaves their grid profile limits, which the troubleshooting guide calls AC protection mode against large swings of the utility grid, and resume on their own once the grid settles. It usually hits the whole system on sunny afternoons when street voltage is high; one branch doing it repeatedly points to its cable run or connectors, which an electrician measures.

APsystems' manuals warn that a panel's open-circuit voltage must never exceed the micro's maximum input (60 V on the DS3 and QS1). A panel that breaks that rule, usually an unmatched replacement, will not run properly and can damage the micro. No document found gives this a named event in EMA; an electrician needs to check the panel and micro pairing.

A micro will not start while its panel's voltage is below the operating range, which is normal at dawn, dusk and in heavy shade. APsystems says that if one panel's DC voltage in good sun sits about a third below the others, its junction box has failed and the panel needs replacing; a plug or lead fault looks the same. Either way it is a roof job.

The ECU gateway has lost its link to APsystems' EMA server, so the app stops updating and the system status turns red (EMA's own wording is 'ECU disconnected from internet'). The panels keep producing. On the ECU-R the second light (LED2) goes out when it cannot reach EMA; the cause is nearly always the wifi, a new router or password, the ECU unplugged, or a firewall.

Some micros making much less than the rest. A repeating pattern at the same hour each day is shading from a tree, chimney or aerial and is normal until the obstacle goes. Otherwise APsystems points to micros dropping into AC protection mode, a loose DC or AC connection, or an ECU-C zero export setting. A panel-to-panel spread of about 10 per cent is normal. A protection lockout means the inverter found something it will not run with, so we treat it as a call.

A green flash every 2 seconds means the micro is producing power but has not heard from the ECU for over 60 minutes, so that panel shows NC or no data in the app. Production is not affected. The usual causes are the ECU unplugged or offline, the micro out of Zigbee range, an antenna off, or the micro not linked in the ECU.

A flashing red light means the micro is not producing (on the DS3 and QT2 a slow red flash is not producing, a fast one is not producing or communicating). APsystems' advice is to check the grid voltage and frequency are in range, the breaker and the AC connectors. Every micro red at once is a blackout, a tripped breaker or the grid voltage; one micro red is that unit, a roof job.

A slow green flash under the micro (every 5 seconds on the DS3, QT2 and QT2D; every 10 seconds on the YC600 and QS1) means that micro is producing and talking to the ECU. Nothing is wrong with it; if the app shows a problem for that panel, it is the data path, not the micro.

No light under the micro means no DC input: APsystems' answer is that there is probably no sunshine at that moment, so a dark micro at dawn, dusk or in heavy cloud is normal. In full sun it points to the panel, its plug or lead, or a dead micro, a roof job. A healthy micro shows one quick red then short green blinks when DC is first connected, three on the YC600 and QS1, ten on the DS3 and QT2.

A solid red light means the micro's ground fault detector (GFDI) has found current leaking from the panel's DC wiring to earth. That micro stays off and the ECU keeps reporting the fault until the cause is fixed and the error is cleared through the ECU. APsystems says to contact technical support; the wiring is tested before anything is reset. Only that panel is affected.

A micro that has never shown data while the rest work is usually a registration problem, not a fault: its serial number (UID) was not entered and synced into the ECU, so it has no 'link' in the EMA ECU settings, or the ECU firmware is older than the micro and needs the update it fetches itself once online. A panel never plugged in looks the same. The installer fixes the first two remotely.

A panel marked NC (No Communication) in the EMA module view means its micro has stopped sending data to the ECU, but APsystems says the micro keeps producing. One or a few panels NC is usually Zigbee range or a loose ECU antenna; every panel NC at once is the ECU itself or its internet. If the same panel stays NC after a day or two of sun, that micro or its wiring needs a look on the roof.

Every micro at 0 W while the ECU is still reporting means the micros are seeing no usable AC. APsystems' list is a breaker off or a loose AC connection, the wrong grid profile in the ECU, an ECU-C with zero export switched on while the house uses nothing, or the micros in AC protection mode after a grid swing or overheating, from which they resume on their own. Heat shutdowns point at a failing fan, a blocked vent or a bad installation spot, so we treat them as a call.

One channel or one micro showing 0 W or 2 W while its neighbours produce. APsystems lists a loose or reversed DC connection, a channel with no panel plugged in, a branch breaker off, or a faulty panel: if the panel's DC voltage is a third lower than the others, its junction box has failed and the panel needs replacing. Checking any of that is a roof job. Wiring faults need an electrician, so we treat them as a call.

The micro has stopped because its internal temperature went over the limit (APsystems quotes over 100 degrees C) and it restarts on its own once it cools. The body is its heatsink and can run at 80 degrees normally, so a hot afternoon pause is not damage. A micro that does it most warm days when its neighbours do not is mounted without airflow or is failing, and that is a roof job. Heat shutdowns point at a failing fan, a blocked vent or a bad installation spot, so we treat them as a call.

Grey (No Data) on the EMA dashboard means no production data is reaching the EMA server at all. APsystems calls it a system malfunction that should be investigated: check the ECU connection first, then contact your installer. On a new system a black or grey status can also mean the ECU has never reported, usually because the micros were never registered in it.

Yellow on the EMA status means something needs a look but production has not stopped: communication to some micros was interrupted during the day, a micro is registered but not reporting, or output is low from weak sun or a micro behaving abnormally. The module view shows which panels are affected.

An ECU-C with its zero export function switched on stops every micro producing whenever the house is using no power, so the system shows 0 W on a sunny day while nobody is home. It is a setting, not a fault, and APsystems says the installer can turn it off in the EMA installer account under Remote Control, Meter Zero Export.

The ECU talks to the micros over 2.4 GHz Zigbee, and APsystems says distance, large concrete walls and metal roofs can block or weaken it, so some micros drop out as NC, often at the same time each day. Its answers are to move the ECU closer to the array, make sure both antennas are screwed on and outside any metal box, or fit an antenna extension of up to 10 metres. Production is not affected.