Deye / Sunsynk F14 Fault (DC Over Current Fault of Hardware)

The F14 fault isn’t actually one I’ve come across all that often in the field, but it’s one of those faults where the description from the user manual doesn’t really tell you much. All it tells you is that the inverter has detected a DC over current fault within the hardware but that doesn’t necessarily mean the inverter itself has failed.

The first thing to understand is that this isn’t really a diagnosis, it’s more of a symptom. Something has caused the inverter to detect an abnormal current on the DC side and it’s shut itself down to protect itself. The difficult part is trying to figure out why.

The most likely culprit naturally would be on the DC bus of the inverter, so we can start by checking, the PV array, the battery system, inverter settings and the inverter itself.

Start by checking the PV array specs, double check your PV string design against the inverter specs. Most installers only look at maximum voltage, but don’t forget to also check the maximum input current per MPPT. If your array is capable of producing more current than the inverter is designed to accept, this is definitely something worth investigating. I’d also spend some time checking every DC connection while you’re there (never hurts, this is something that should be done on a regular basis anyway). Loose MC4 connectors, damaged isolators or overheated terminals can all cause strange DC behavior. I wouldn’t expect a loose connection on its own to cause an F14, but something worthwhile checking.

Next, and what i’ve seen the most, is I’d make sure the inverter is actually allowed to draw the current it’s asking for. For example, a 5kW load on a 48V battery is going to require roughly 100A from the battery. If your battery discharge current has been limited well below that, it’s worth checking whether the inverter is reaching those limits during heavy loads.

I’d also make sure battery communication is healthy. Incorrect CAN settings, firmware mismatches or communication issues can sometimes result in incorrect current limits being applied.

If you’ve ruled out the PV array, battery settings and all the DC wiring checks out, then unfortunately you have to start considering the inverter itself. This could be something like a failed current sensing circuit, a damaged power stage, faulty control board or failed IGBTs or MOSFETs. At that point there’s generally not much more that can be done on site without opening the inverter up, and I’d normally recommend contacting the supplier or repair center in this case.

If I arrived on site with an F14 fault, this would probably be my order of attack:

  1. Check every battery and PV DC connection.
  2. Confirm the PV array hasn’t exceeded the inverter’s design limits.
  3. Check battery charge and discharge current settings.
  4. Confirm BMS communication is working correctly.
  5. Look through the inverter event history to see when the fault occurs (during charging, discharging or high PV production).
  6. Only once everything external has been ruled out would I start suspecting an internal inverter fault.

The F14 fault isn’t one where you can immediately point at a single component and say “that’s the problem”. It’s really just the inverter telling you it’s detected an abnormal DC current condition somewhere in the system. Take your time and work through the DC side methodically. More often than not you’ll find the cause before you ever need to start thinking about replacing the inverter itself.

Leave a Reply

Your email address will not be published. Required fields are marked *