Fault & LED reference

The controller reports faults in two places: the dashboard of the on-board web UI (connect to the controller's Wi-Fi and open http://192.168.50.1), which names the exact fault, and the status LED on the board, which tells you whether a fault is active but not which one. When the LED blinks fast, the dashboard is where to look next.

Three protection groups can latch a fault: voltage, current (per motor channel), and short-circuit, plus an overtemperature limit. Each group has its own trip and clear thresholds. The defaults below are what firmware package 0-2-1.9 ships with — every one of them is adjustable in the web UI under Settings, so if your controller has been reconfigured, check your values there.

Voltage protection watches the DC bus. A fault latches only after the voltage stays past the trip threshold for the tolerance time, and clears once it stays back inside the clear threshold — so brief transients don't trip it.

Repeated UV active faults under load with a charged pack usually point at connector or wire resistance rather than the battery itself. Repeated OV active faults while braking mean the battery can't absorb the regen current — check its state of charge and charge-current limit.

Each motor channel (A and B) has three current tiers, from a short spike to a long-term limit. The faster the event, the higher the current it takes to trip.

Hard launches from a standstill draw stall current, which is what usually trips the surge or impulse tier. Before raising any threshold, try slowing the throttle ramp-up in your drive profile — a gentler ramp absorbs most launch transients without losing torque feel. If your motor's locked-rotor current is genuinely above the limits, the controller is undersized for the application.

The short-circuit protector reacts in hardware-time and manages its own recovery. With default settings, a detected short latches within 100 ms and the controller attempts an automatic reset. Up to 5 resets are allowed inside a 3 s window — while that budget lasts, the dashboard shows a warning state. If the budget is exhausted, the controller enters lockout: the motor stays disabled, and a retry is only attempted after the 5 s lockout cooldown.

Repeated short-circuit trips almost always mean damaged motor wiring, a chafed lead, or a failed motor — not a controller setting. Disconnect power and inspect the motor leads before re-powering. Don't keep resetting into a hard short.

The high-temperature fault trips at 80 °C by default. The cooling fan ramps in well before that: it starts at 40 °C, reaches full speed at 70 °C, and switches off again below 35 °C. If you see temperature faults in normal use, check airflow around the board, heatsink mounting, and ambient temperature before raising the threshold.

The dashboard's health panel shows the live state of every protection group using the labels above, and the fault timers panel shows how close each one is to latching or clearing. Faults clear themselves once their clear threshold and timer are satisfied — there is no separate reset button to press for voltage, current, or temperature faults. Short-circuit lockout is the exception: it holds the motor off until its cooldown passes.

All thresholds on this page are the firmware defaults for package 0-2-1.9 and can be tuned in the web UI under Settings. If a fault doesn't make sense for your setup, contact support with the exact label the dashboard shows and what the machine was doing — that label maps directly to the internal fault state, so it tells us most of the story.