> ## Documentation Index > Fetch the complete documentation index at: https://learning.kent.co.in/llms.txt > Use this file to discover all available pages before exploring further. # Fault Codes > Every Kent G3 status and alarm message — what the display means, the first response, and which flow continues the job. export const Escalate = () =>

Escalate to Kent New Energy service only — through your registered Kent partner channel or the Kent service desk details on your work order. Do not contact any third-party or component-manufacturer support line for a Kent-branded system: tickets outside the Kent channel are not tracked, not covered, and can void warranty handling.

; export const Applicability = ({labels}) =>
Applies to: {labels.map(l => {l})}
; export const SITE_NAME = "Kent New Energy Knowledge Base"; **Read the message, don't guess it.** Record the exact string from the HMI (including any `10xx DATA:000x` code) before touching anything, then take the first response below. Where a row says *Continue in*, that flow — not this table — finishes the job. **For trained/authorized installers only.** Any restart follows the official sequence, and any cover-off work follows [Isolation & Shutdown](/safety/isolation-and-shutdown) — including the 5-minute discharge wait. **The one-restart rule.** For an alarm message: power off in the correct order, **wait 5 minutes, restart once**. If the same alarm returns, collect the evidence and escalate — repeated power-cycling destroys the diagnostic trail and fixes nothing. ## Status messages These describe an operating state, not a fault — most need no action at all. | Message | What it describes | First response | Continue in | | ----------------- | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------------------------------------------- | | **Off** | Control device to shutdown | Turn the device on in the ON/OFF Setting | [Not Starting](/g3/troubleshooting/not-starting) | | **LmtByEPM** | Output is under external control | Confirm an external EPM/meter is limiting against reverse current; confirm any third-party control; confirm the power-control setting; verify the export settings and meter readings | [Zero Export Failing](/g3/troubleshooting/zero-export-failing) | | **LmtByDRM** | DRM function ON | No action needed | — | | **LmtByTemp** | Over-temperature power limit | No action needed — normal operation | — | | **LmtByFreq** | Frequency power limit | No action needed — normal operation | — | | **LmtByVg** | Volt-Watt mode active | Triggered by local safety regulation when grid voltage runs high — generally no action; disabling it sits behind partner-gated settings, so escalate rather than adjust | [Grid Fault](/g3/troubleshooting/grid-fault) | | **LmtByVar** | Volt-Var mode active | Same as LmtByVg — regulation-driven, generally no action; the disable path is partner-gated | [Grid Fault](/g3/troubleshooting/grid-fault) | | **LmtByUnFr** | Under-frequency limit | No action needed | — | | **Standby** | Bypass run | No action needed | — | | **StandbySynoch** | Off-grid → on-grid transition | No action needed | — | | **GridToLoad** | Grid supplying the load | No action needed | — | ## Alarm messages — grid & AC | Message | What it means | First response | Continue in | | ---------------------------------- | ------------------------------------------ | --------------------------------------------------------------------------------------------- | ------------------------------------------------ | | **Surge Alarm** | On-site grid surge | Grid-side fault — one restart; persists → Kent service | [Grid Fault](/g3/troubleshooting/grid-fault) | | **OV-G-V01 / OV-G-V04** | Grid voltage above the upper range | Confirm whether the grid is abnormal; confirm the AC cable is properly connected; one restart | [Grid Fault](/g3/troubleshooting/grid-fault) | | **UN-G-V01 / UN-G-V02** | Grid voltage below the lower range | Same grid + AC-cable + one-restart sequence | [Grid Fault](/g3/troubleshooting/grid-fault) | | **OV-G-F01 / OV-G-F02** | Grid frequency above the upper range | Same grid + AC-cable + one-restart sequence | [Grid Fault](/g3/troubleshooting/grid-fault) | | **UN-G-F01 / UN-G-F02** | Grid frequency below the lower range | Same grid + AC-cable + one-restart sequence | [Grid Fault](/g3/troubleshooting/grid-fault) | | **G-PHASE** | Unbalanced grid voltage | Same grid + AC-cable + one-restart sequence | [Grid Fault](/g3/troubleshooting/grid-fault) | | **G-F-GLU** | Grid voltage/frequency fluctuation | Same grid + AC-cable + one-restart sequence | [Grid Fault](/g3/troubleshooting/grid-fault) | | **NO-Grid** | No grid | Restore the AC path — breaker, terminations, cable | [Not Starting](/g3/troubleshooting/not-starting) | | **OV-G-V02 / OV-G-V03** | Grid transient overvoltage | One restart; confirm whether it continues | [Grid Fault](/g3/troubleshooting/grid-fault) | | **OV-G-V05** | Grid voltage RMS instantaneous overvoltage | One restart; confirm whether it continues | [Grid Fault](/g3/troubleshooting/grid-fault) | | **IGFOL-F** | Grid current tracking failure | One restart; confirm whether it continues | [Grid Fault](/g3/troubleshooting/grid-fault) | | **OV-G-I** `(1018 DATA:0000)` | A-phase RMS overcurrent | Confirm the grid; confirm the AC cable connection; one restart | [Grid Fault](/g3/troubleshooting/grid-fault) | | **GRID-INTF.** `(1030 DATA:0000)` | AC hardware overcurrent (abc phase) | One restart; confirm whether it continues | [Grid Fault](/g3/troubleshooting/grid-fault) | | **DCInj-FAULT** `(1037 DATA:0000)` | DC component of current over limit | Confirm the grid; confirm the AC cable connection; one restart | [Grid Fault](/g3/troubleshooting/grid-fault) | | **GRID-INTF02** `(1046 DATA:0000)` | Power grid disturbance 02 | Confirm whether the grid is seriously distorted; check the AC cable is reliably connected | [Grid Fault](/g3/troubleshooting/grid-fault) | ## Alarm messages — battery | Message | What it means | First response | Continue in | | -------------------------------------------- | ------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | | **NO-Battery** | Battery not connected | Verify battery voltage is within standards on the information page; measure battery voltage at the plug | [Comm Fault](/g3/troubleshooting/comm-fault) | | **BatName-FAIL** | Wrong battery brand selection | Confirm the battery model selection matches the actual pack | [Comm Fault](/g3/troubleshooting/comm-fault) | | **CAN Fail** | Inverter–battery communication failure | Check cable condition; confirm the cable sits in the CAN port at both battery and inverter; confirm it is the right (pairing-specific) cable | [Comm Fault](/g3/troubleshooting/comm-fault) | | **OV-Vbatt** | Battery overvoltage detected | Verify battery voltage is within standards; measure at the inverter connection point; battery-side follow-up is a battery-service case | [Battery Not Charging](/g3/troubleshooting/battery-not-charging) | | **UN-Vbatt** | Battery undervoltage detected | One restart; persists → Kent service | [Battery Not Charging](/g3/troubleshooting/battery-not-charging) | | **OV-Vbatt-H / OV-BUS-H** `(1051 DATA:0000)` | Battery overvoltage hardware failure / VBUS | Check whether the battery circuit breaker is tripping; check whether the battery is damaged | [When to Escalate](/troubleshooting/when-to-escalate) | ## Alarm messages — backup | Message | What it means | First response | Continue in | | ------------------------------ | ------------------------ | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | | **OV-Vbackup** | Inverting overvoltage | Check the backup port wiring; one restart | [Backup Not Working](/g3/troubleshooting/backup-not-working) | | **Over-Load** | Load overload fault | Backup load power (or an inductive load's start-up power) too large — remove some backup load or the inductive load | [Backup Not Working](/g3/troubleshooting/backup-not-working) | | **OV-ILLC** `(1052 DATA:0000)` | LLC hardware overcurrent | Check whether the backup load is overloaded; one restart | [Backup Not Working](/g3/troubleshooting/backup-not-working) | ## Alarm messages — PV & leakage | Message | What it means | First response | Continue in | | ------------------------------------------ | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- | | **OV-DC01** `(1020 DATA:0001)` | DC 1 input overvoltage | Check whether the PV voltage is abnormal; one restart | [Not Starting](/g3/troubleshooting/not-starting) | | **OV-DC02** `(1020 DATA:0002)` | DC 2 input overvoltage | Check whether the PV voltage is abnormal; one restart | [Not Starting](/g3/troubleshooting/not-starting) | | **PV ISO-PRO01** `(1033 DATA:0001)` | PV negative ground fault | Check the strings for insulation problems; check the PV cable for damage | [Nuisance Tripping](/g3/troubleshooting/nuisance-tripping) | | **PV ISO-PRO02** `(1033 DATA:0002)` | PV positive ground fault | Check the strings for insulation problems; check the PV cable for damage | [Nuisance Tripping](/g3/troubleshooting/nuisance-tripping) | | **ILeak-PRO01–04** `(1034 DATA:0001–0004)` | Leakage current failure (30/60/150 mA classes) | Check current leakage to ground; verify the grounding; verify all wires are sound and not leaking to ground | [Nuisance Tripping](/g3/troubleshooting/nuisance-tripping) | | **ILeak\_Check** `(1039 DATA:0000)` | Leakage current sensor failure | One restart; persists → Kent service | [When to Escalate](/troubleshooting/when-to-escalate) | | **AFCI-Check** `(1040 DATA:0000)` | AFCI self-test failure | One restart; persists → Kent service | [Not Starting](/g3/troubleshooting/not-starting) | | **ARC-FAULT** `(1041 DATA:0000)` | AFCI failure (arc detected) | Verify PV connections are tight; further arc-fault adjustment sits behind partner-gated settings — escalate rather than adjust | [Not Starting](/g3/troubleshooting/not-starting) | ## Alarm messages — internal & hardware | Message | What it means | First response | Continue in | | ------------------------------------ | --------------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | **Fan Alarm** | Fan alarm | Check whether the internal fan is working correctly or jammed | [When to Escalate](/troubleshooting/when-to-escalate) | | **OV-BUS** `(1021 DATA:0000)` | DC bus overvoltage | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **UN-BUS01** `(1023 DATA:0001)` | DC bus undervoltage | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **UNB-BUS** `(1022 DATA:0000)` | DC bus unbalanced voltage | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **UN-BUS02** `(1023 DATA:0002)` | Abnormal DC bus voltage detection | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **DC-INTF.** `(1027 DATA:0000)` | DC hardware overcurrent (1–4) | Check the DC wires are connected correctly with no loose connection | [When to Escalate](/troubleshooting/when-to-escalate) | | **OV-DCA-I** `(1025 DATA:0000)` | DC 1 average overcurrent | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **OV-DCB-I** `(1026 DATA:0000)` | DC 2 average overcurrent | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **IGBT-OV-I** `(1048 DATA:0000)` | IGBT overcurrent | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **OV-TEM** `(1032 DATA:0000)` | Module over-temperature | Check the surroundings for poor heat dissipation; confirm the installation meets the requirements | [When to Escalate](/troubleshooting/when-to-escalate) | | **RelayChk-FAIL** `(1035 DATA:0000)` | Relay failure | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **UN-TEM** `(103A DATA:0000)` | Low-temperature protection | Check the working-environment temperature; one restart | [When to Escalate](/troubleshooting/when-to-escalate) | | **12Power-FAULT** `(1038 DATA:0000)` | 12 V undervoltage failure | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **INI-FAULT** `(1031 DATA:0000)` | AD zero drift overlink | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | | **DSP-B-FAULT** `(1036 DATA:0000)` | Master–slave DSP communication abnormal | One restart; persists → escalate | [When to Escalate](/troubleshooting/when-to-escalate) | ## Before you call Kent service Have ready: the unit's **serial number**, the **installation date**, the **exact message** (with any `10xx DATA` code) and a **photo of the screen**, a description of the problem with pictures, and the **PV array configuration** (panel count and capacity, number of strings). The Kent service contact and case checklist are on [When to Escalate](/troubleshooting/when-to-escalate). ## Related pages * [Not Starting](/g3/troubleshooting/not-starting) * [When to Escalate](/troubleshooting/when-to-escalate)