Why this happens
Modern EV controllers constantly monitor battery voltage, current, temperature, the throttle, brakes and the motor's Hall sensors. When something is out of range they stop or limit the motor and report a code, either as a number on the display or as a pattern of LED flashes. Reading that code turns a vague complaint into a specific starting point.
What you need
Tools
- Smartphone for photos and video
- Torch
- Owner's manual or the manufacturer's app
Materials
- Notebook or a phone note for a fault log
Before you start
- Stop safely before photographing a fault; never handle your phone while riding.
- Do not clear faults by repeatedly power-cycling and riding on; the controller has stopped for a reason.
- Generic online code lists may not match your controller; trust your own manual.
Step by step
- 1
Find where your vehicle reports faults
Check the owner's manual for an error code table. Most scooters show a number or icon on the display; some e-bike and e-rickshaw controllers have a small LED on the controller case that flashes a pattern; connected scooters may show faults in the manufacturer app. Find the method that applies to your vehicle before a fault happens, so you know where to look.
- 2
Capture the code when it appears
When a fault shows, stop safely first. Then photograph the display or record a short video of the LED flashing, because blink codes are easy to miscount. Note the date, battery level, temperature, what you were doing and whether the code cleared by itself. Do not keep power-cycling the vehicle to make the code go away.
- 3
Count blink codes carefully
Blink codes often use long and short flashes, or a group of flashes followed by a pause, repeated. Watch at least three cycles, or count from the video, slowing it down if needed. Write the pattern as numbers, such as four flashes, pause. Check whether your manual counts long flashes as tens and short as units.
- 4
Match the code to the manual
Look the code up in your manual or app. Common categories include undervoltage, overcurrent, over-temperature, throttle fault, brake signal active, Hall sensor fault and communication error between display and controller. Note the meaning and any action the manual recommends. Avoid relying on generic code lists online, because the same number can mean different things on different controllers.
- 5
Do the safe owner checks
Some codes have simple causes you can check: undervoltage means charge the battery with its original charger; brake active means check the levers return fully; throttle fault means check its connector; over-temperature means let the vehicle cool in the shade. Do these checks with the key off and battery disconnected where connectors are involved.
- 6
Keep a fault log
Record every code in one place with date, conditions and what you did. Patterns help: an over-temperature code only on long climbs on hot afternoons is very different from a Hall fault after rain. A log also helps with warranty claims, because it shows the fault is recurring and not caused by misuse.
- 7
Hand over persistent faults
If a code returns after the simple checks, or it relates to the battery, motor phases, controller internals or communication faults, take the vehicle to the authorised service centre. Show them your photos and log. Do not open the controller or battery to look for the fault yourself; that may void warranty and expose you to stored energy.
How to tell it worked
You can name the exact code and its meaning from your manual, you have tried the safe owner checks, and you have a dated fault log with photos to take to the service centre if the fault persists.
Stop and call a technician if
- A battery, overcurrent or short-circuit code appears with heat, smoke or a smell.
- The same code returns after the simple owner checks.
- The vehicle shows a fault while the battery or controller is visibly damaged or wet inside.
Questions
The code disappeared after I restarted. Is it fixed?
Not necessarily. Intermittent faults often clear on restart and return later, so log it and watch for repeats.
Can I clear codes with an app or OBD tool?
Only use the manufacturer's own app or service tools. Clearing a code does not fix its cause, and unofficial tools can change settings you should not touch.