> ## 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. # Quiz — Troubleshooting: 10 Questions with Answers > 10 multiple-choice questions on troubleshooting: one-restart rule, power-off sequence, BMS comm faults, grid protection consent, and backup overload fixes. Ten questions from the [Troubleshooting](/troubleshooting/not-starting) group. Work through all ten before scrolling to the key. Suggested pass mark: **8 / 10**. Each miss points to a source page — re-read it, not the whole group. ## Questions **1.** The correct restart discipline when a fault code appears on either platform is: * A. One restart; if the fault persists, stop and escalate to Kent service * B. Restart repeatedly until the code clears or 30 minutes have passed * C. Never restart — escalate immediately without any restart attempt * D. Three restarts, ten minutes apart, then escalate *** **2.** The correct power-off sequence before any service work is: * A. Turn off the grid AC breaker first, then the battery * B. Turn off the battery switch first, then the grid AC — the exact reverse of power-on * C. Turn off the PV DC switch first, always * D. Any order is acceptable once the display is dark *** **3.** A Kent M1 showing E400–E402 or a Kent G3 showing "CAN Fail" with SOC missing — the first check is: * A. Check the battery cells for physical damage * B. Check the BMS communication cable — label, continuity, pinout, and RJ45 seating — before touching any setting * C. Update the inverter firmware * D. Check the grid code setting *** **4.** Kent G3 "BatName-FAIL" means: * A. The battery pack is empty — recharge before commissioning * B. The BMS fuse has blown * C. The battery selection in the HMI is wrong — correct it after the comm cable is confirmed good * D. The inverter firmware needs updating *** **5.** Kent M1 E303 (AFCI) fault behaviour is: * A. Permanent lockout — a service call is always required to clear it * B. Clears only after a full battery reset and 24-hour wait * C. Auto-recovers; if it occurs 5 times in one day it auto-clears — check the AFCI CT connection if the code repeats * D. A cosmetic fault that can be ignored *** **6.** Grid protection points — voltage and frequency trip thresholds — should be changed: * A. By the installer to match the nearest available grid code * B. By the customer from the display if tripping seems too frequent * C. Automatically by the meter when grid conditions change * D. Only per the Kent-issued parameter sheet for the specific DISCOM — never improvised or estimated *** **7.** A backup circuit that trips the backup output breaker under load is best resolved by: * A. Widening the backup breaker's trip setting * B. Moving the overloaded load to the grid-only panel — backup overload means something too big is on the essential panel * C. Increasing the inverter's rated power via a setting * D. Replacing the backup breaker with a higher-rated type *** **8.** Kent M1 fault code E100 means: * A. PV string overvoltage * B. Battery undervoltage — check the pack SOC * C. No AC connection — restore the AC path: upstream breaker, terminations, cable * D. Fan failure *** **9.** Kent M1 E303 (AFCI) occurs up to 5 times per day without intervention. Before diagnosing further, you should check: * A. The PV string Voc against the 500 V limit * B. The AFCI CT connection and installation at the PV input * C. The battery SOC level * D. The grid frequency setting *** **10.** An internal fault code — Kent M1 E600–E602 or Kent G3 INI-FAULT / DSP-B-FAULT — that survives one restart is: * A. A site wiring problem — check terminations before escalating * B. Fixed by a factory reset from the advanced menu * C. Fixed by swapping the BMS communication cable * D. A Kent service case — stop all work, do not open the unit *** ## Answer key | Q | Answer | Why | | -- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | **A** | One restart is the maximum field step. If the fault survives a single restart, the job is an escalation — not more cycling. Repeated restarts obscure fault data. | | 2 | **B** | Power-off is the reverse of power-on: battery off first, then grid AC. This sequence protects the inverter from back-feeding and protects the battery from an uncontrolled disconnect. | | 3 | **B** | A BMS comm fault is almost always a cable problem. Check the crossover cable label, continuity, pinout, and RJ45 seating before touching any setting or firmware. | | 4 | **C** | BatName-FAIL means the battery selection in the HMI does not match the connected pack. Correct the selection to PYLON\_LV (for Kent Lithium Battery) after confirming the comm cable is good. | | 5 | **C** | E303 auto-recovers and clears itself after 5 occurrences in a day. If it repeats, investigate the AFCI CT connection at the PV input — it is not a hard fault requiring a service call by itself. | | 6 | **D** | Grid protection points are utility-consent settings. Use only the Kent-issued parameter sheet for the site's specific DISCOM. Improvised changes risk grid disconnection or regulatory violation. | | 7 | **B** | Backup overload means something too large is on the essential panel. The fix is to move that load to grid-only — not to widen the trip point or upsize the breaker. | | 8 | **C** | E100 is "No AC Connection." Check the upstream AC breaker, the AC wiring terminations, and the cable path before looking elsewhere. | | 9 | **B** | When E303 repeats, check the AFCI CT connection and installation at the PV input. A loose or incorrectly installed AFCI CT is the most common cause of repeat E303 events. | | 10 | **D** | Internal fault codes that survive a restart are Kent service cases. Do not open the unit, do not attempt a factory reset — escalate with the fault code, time, and one restart record. | ## Related pages * [Inverter Not Starting](/troubleshooting/not-starting) * [Comm Fault](/troubleshooting/comm-fault) * [Backup Not Working](/troubleshooting/backup-not-working) * [When to Escalate](/troubleshooting/when-to-escalate)