FarDriver beeping? Count the beeps.
First check for the auto-learn pattern. Otherwise, count the repeating short beeps between pauses and match the number below.
Auto-learn: two short beeps, one long beep
What it means: A repeating short, short, long pattern means the controller is in self-learning mode. It is not numbered fault code 2 followed by fault code 1.
What to do: Keep the vehicle secured with the drive wheel fully off the ground and the area clear because the motor may rotate forward and backward. Complete the auto-learn routine, or cancel self-learning if you entered it unintentionally. The repeating prompt sound stops when self-learning finishes or is canceled.
Motor Hall fault
What it means: The controller is not receiving a valid Hall signal from the motor.
Could be: A loose Hall plug, damaged signal wire, backed-out connector pin, or failed motor Hall sensor.
Throttle fault
What it means: The throttle signal is not at an acceptable value.
Could be: The throttle is not returning to zero, the signal is outside its configured range, the connector or wiring is damaged, or the throttle itself has failed. FarDriver notes that this code may briefly appear during startup and clear after self-check.
Current-protection restart
What it means: The controller restarted after a current-protection event.
Could be: A one-off current spike or a recurring overcurrent event under load. FarDriver’s table calls this an “abnormal protection alarm” and does not identify the exact cause from the beep alone.
Phase-current overcurrent
What it means: Motor phase current crossed the controller’s protection threshold.
Could be: A stalled or heavily loaded motor, a phase-wiring problem, or motor/current-control parameters that do not match the setup.
Voltage fault
What it means: The voltage measured by the controller is outside its allowed range.
Could be: Pack voltage outside the controller’s permitted range, the wrong controller/battery voltage combination, or a poor main power connection affecting the reading.
Anti-theft alarm signal
What it means: This slot is associated with the anti-theft or alarm input.
Could be: An active alarm input, anti-theft wiring, or an OEM-specific use of that signal. The older FarDriver manual marks the detailed description as reserved, so confirm the live fault name on your version.
Motor-temperature fault
What it means: The reported motor temperature is outside the controller’s usable range.
Could be: An actually hot motor, a disconnected or damaged temperature wire, the wrong sensor type selected, or an implausible sensor reading.
Controller-temperature fault
What it means: The controller’s reported temperature is outside its usable range.
Could be: Heavy load, poor cooling or ventilation, extreme ambient temperature, or an internal temperature-sensing fault.
Phase-current overflow
What it means: The controller detected an abnormal phase-current overflow condition.
Could be: A phase-current event or mismatched motor-control parameters. FarDriver’s beep table does not narrow this code to one component.
Phase-current zero-point fault
What it means: The phase-current measurement does not return to its expected zero point.
Could be: An internal current-sensing, calibration, or controller hardware problem. FarDriver classifies this as an internal controller alarm.
Phase short or motor fault
What it means: The controller sees a short in the motor phase circuit or a motor fault.
Could be: Damaged phase-wire insulation, a shorted phase connector, or a shorted motor winding.
Line-current zero-point fault
What it means: The battery/line-current measurement does not return to its expected zero point.
Could be: An internal line-current sensor, calibration, or controller hardware problem. FarDriver also classifies this as an internal controller alarm.
Upper-bridge MOSFET fault
What it means: FarDriver identifies damage in the controller’s upper power bridge.
Could be: A failed high-side MOSFET or related internal power-stage damage.
Lower-bridge MOSFET fault
What it means: FarDriver identifies damage in the controller’s lower power bridge.
Could be: A failed low-side MOSFET or related internal power-stage damage.
Peak line-current protection
What it means: Hardware overcurrent protection was triggered by a peak current event.
Could be: An actual current spike, a motor/controller mismatch, or incorrect motor-control parameters. FarDriver’s parameter notes specifically connect bad AN, LM, PID, and excessive weak-field settings with MOE/OVER protection.
Sources: FarDriver controller manual ↗ · firmware and parameter notes ↗