Display, throttle and error codes: reading your e-scooter dashboard
The display, the throttle lever and the brake levers are the only channel the e-scooter has for talking to the rider. When a triangle blinks with code “E2” or “14”, the Google query usually flies off without context and without the official manual at hand. This section is about how the user-facing interface works on popular families (Xiaomi, Ninebot, the EY3 ecosystem of Dualtron / Kaabo / Currus, Apollo, Inmotion), how the three throttle types and cruise control behave, and which actually-meaningful error codes each vendor surfaces. It complements the technical section Controllers, BMS, power electronics, which describes what happens “below the display”.
Display types
Xiaomi M365 / M365 Pro / 4-series: four-digit LCD
The base M365 (2017) has a single-symbol 7-segment block that shows only battery level (one of four bars) and the current mode. The M365 PRO (2019) and the later Mi Electric Scooter Pro 2 / 3 / 4 / 4 Pro carry a four-digit LCD with much richer readouts: speed (big numeral), battery percentage, mode glyph (Eco / D / S), icons for headlight, Bluetooth, lock and brake events, and a single “!” mark for error codes.
A Xiaomi-ecosystem quirk: the error code is a two-digit number (10, 11, 14, 21, 24…) — but on the old M365 without LCD digits, it is delivered as a series of blinks / audible beeps: long = first digit, short = second. “Two long + six short = error 26” (Electrazoom). On LCD models the number is printed directly in the speed field.
Mi Home / Xiaomi Home app (iOS, Android) pairs over Bluetooth and gives three things: (1) deeper error readout with a text description instead of just a digit; (2) Cruise Control toggle (off by default); (3) KERS calibration, regen strength regulator, tire-diameter calibration (Xiaomi Mi support; ScooterHacking).
Segway-Ninebot ES / Max G30 / GT-series: LCD with ER codes
Ninebot uses its own LCD chip with a field for two-digit ER codes (no “E” prefix — just the number). Structurally this is the same format as Xiaomi, but the controller logic differs: Ninebot’s controller groups errors into 10-x (communication), 11-13 (motor phase currents A/B/C), 14-15 (input peripherals — throttle and brake), 16 (motor temperature), 18-19 (controller and supply), 21-24 (battery, BMS, hall sensors), 26-27 (controller firmware and hardware) (EScooterHut; Levy Electric).
The Segway-Ninebot app provides the same trio: textual decoding of the code, Cruise Control toggle, KERS-strength selection and unit choice (km/h / mph).
EY3 LCD on Dualtron / Kaabo / Currus / Speedway
EY3 (sometimes labelled “Color EY3” — there is a colour OLED revision) is a standalone Minimotors product, Mi-independent, fitted in Dualtron (every model), Kaabo (Mantis, Wolf), Currus NF / Panther, Speedway 5 and other high-power decks (Rider Guide). It is a trigger-throttle module with an integrated screen and three buttons (Power, Mode, Gear).
EY3 simultaneously shows speed, ODO / TRIP, battery voltage (V, not %), current draw (A), mode (1/2/3), p-settings (programmable parameters P0–PD: max-power, torque, KERS, wheel inches, auto-off timeout). A long Mode press (3–5 s) opens the p-settings menu; the Gear button cycles values (Rider Guide; Wee-Bot).
EY3 error codes are single-digit (1–6), described below.
Apollo TFT / IPX LCD
Apollo Scooters use their own design: a monochrome LCD on City / Air, a full-colour TFT on Phantom / Pro / Ghost. The Apollo format is prefix E + digit (E1, E2, E3, E4, E5, E7). It is not the “Xiaomi-style” long/short blink — the code is printed directly in the message field. Apollo has its own app with firmware and an error log (Apollo Support).
Inmotion: E01–E16 with prefix
Inmotion (S1, RS, Climber, Air, Air Pro) surfaces faults as a three-character “E0x” code numbered 01–16, covering controller, motor, battery, brake, throttle, display, overheat and fall-detection (Inmotion Zendesk; Green220).
Three throttle types: trigger, thumb, twist
The accelerator type directly affects long-ride fatigue, control off-road, and compatibility with winter gloves.
| Type | How it works | Brands | Pros | Cons |
|---|---|---|---|---|
| Trigger / Finger (lever) | Spring-loaded lever-trigger under the index finger on the front of the handlebar | Apollo, Minimotors / Dualtron, Kaabo, Currus, Nami | Most precise control; stable over bumps (vertical hits don’t transfer); EY3 module already includes the display | Index-finger fatigue on long rides; worse compatibility with thick winter gloves |
| Thumb / Paddle (paddle under the thumb) | Flat paddle on the top of the right grip, pressed down by the thumb | Xiaomi M365 / Pro / 4-series, Ninebot ES / Max G30 / GT, NIU, many entry-level | Less finger fatigue; better with gloves; ergonomic for riders with arthritis / carpal tunnel | More sensitive to vertical hits (a pothole makes the thumb push harder involuntarily); less precise |
| Twist / Full-twist (rotating grip) | Twist the whole right grip toward you, motorcycle-style | EMOVE Cruiser, some Wolf King GT models, Speedway | Familiar to motorcyclists; intuitive by feel | Tougher for beginners (hard to hold a steady speed); strains the wrist on long rides; can accidentally rotate when switching hands |
Aggregated from Apollo Scooters; Rider Guide; Varla Scooters.
Throttle-module IP rating. Apollo notes that roughly 53% of thumb-throttle models carry a declared IP rating versus ~20% of trigger-throttle models (Apollo Scooters) — this is because thumb-throttle units more often ship on entry-level decks where IP54 certification is a competitive selling point. Higher-end trigger decks often compensate with a separate controller IP rating (see IP protection).
Cruise control: activation condition, exit, limits
Cruise control is a function that locks the throttle in the position the rider held it for N seconds at a stable speed, then the scooter keeps going on its own without pressing the accelerator.
Typical activation mechanic (aggregated from Nanrobot; Levy Electric; CitizenSide):
- Accelerate to the desired speed.
- Hold the throttle steady for 5–8 seconds (firmware-dependent: Xiaomi — 5 s, Ninebot — 6 s, EY3 / Apollo — 5 s).
- A beep sounds and/or a dedicated icon appears on the display (on EY3 — code “1” with a triangle).
- You can release the throttle — the scooter keeps the speed.
Exit from cruise control — three ways, any one of them disables the function immediately:
- Press any brake lever (front or rear) — the main and safest exit.
- Press the throttle again and release — some firmwares treat this as “overwrite the speed”, others as “exit”.
- Power / Mode button (on some models, not universal).
Cruise is off by default on Xiaomi M365 / Pro / 4-series and Ninebot Max G30 / GT — and must be deliberately enabled in the Mi Home / Segway-Ninebot app (Xiaomi Mi support; Levy Electric). EY3 / Apollo / Inmotion ship with cruise active out of the box.
Safety limits (Levy Electric; Gyroor): don’t use in traffic, on wet surfaces, on steep descents (a fixed speed becomes uncontrollable downhill), or with thick gloves — brake reaction lags. If cruise engages accidentally (this is the most common complaint on Xiaomi), it’s easy to disable in the app settings.
Speed modes / Eco-Standard-Sport
Most modern decks offer three modes tied to a power and max-speed limit:
- Eco / mode 1: as a rule, limits to roughly half the available power and on the order of 15 km/h, aggressive KERS. Purpose — maximum range (Levy Electric estimates the eco-mode gain at roughly +30%), gentle riding in the rain.
- Standard / D / mode 2: an intermediate power level, on the order of 20–25 km/h (on 250 W EU models capped at 20 exactly). The default urban mode.
- Sport / S / mode 3: full power and max-speed, bounded by the market’s regulatory cap: 25 km/h in the EU under EN 17128, likewise 25 km/h (15.5 mph) in the UK rental trials (UK DfT), and tens of km/h higher where no cap applies. Often with a more aggressive acceleration curve.
Switching — a short press of Mode / Power. On EY3, the Gear button (the current mode shows as “1”, “2” or “3” next to the speed).
Eco doesn’t lock the motor on a hill. If Eco is on but the deck struggles on a climb, the controller still delivers the power needed to maintain speed, up to the cap. This isn’t a bug — it’s by design (Rider Guide).
Error codes: Xiaomi M365 / M365 Pro / 4-series
Codes above 9 are two-digit. If an old M365 without LCD digits transmits the code via blinks, count: long blink = tens, short = ones. On LCD models the code is printed directly.
| Code | Meaning | Most likely cause | Action |
|---|---|---|---|
| 10 | Bluetooth (BLE) communication error | BLE module isn’t answering the controller | Spin: off–on; if it persists — replace the BLE board |
| 11 | Calibration / power MOSFET error | Current calibration or power switch | Try re-flashing firmware; otherwise the controller goes for replacement |
| 12 | Current-sensor calibration | Current sensor drifted | Re-flash; recalibrate |
| 13 | Calibration / MOSFET | Same as 11 | Same |
| 14 | Throttle / brake input error | Throttle or brake sensor isn’t at zero at startup | Release throttle and brake at power-on; check throttle cable |
| 15 | Throttle / brake error | Same | Same |
| 18 | Motor Hall sensor error | One of the three motor hall sensors isn’t answering | Inspect the motor plug; otherwise — replace the motor |
| 21 | BMS communication error | Cable between battery and controller | Power down, reseat the battery |
| 22 | Bad BMS serial / password | Incompatible or non-original battery | Try the original battery |
| 23 | BMS abnormal | Same plus deep discharge / overcurrent | Charge fully; if it persists — BMS for diagnostics |
| 24 | Wrong supply voltage | Voltage outside expected range (aged battery, shock) | Measure cells; battery or BMS for replacement |
| 26 | Controller memory error | Firmware corrupted | Re-flash via Mi Home or custom tool |
| 27 | Controller password mismatch | Like 26 | Same |
| 28 | MOSFET error | Power switch is failing | Replace controller |
| 29 | ESC wrong serial / not activated | Controller not activated by the Mi system | Mi Home → re-pair |
| 31 | Program error | Firmware | Re-flash |
| 35 | Wrong scooter serial | Part mismatch | Check serials in Mi Home |
| 36 | Battery temp sensor / overheating | Battery is hot | Let it cool ≥1 hour |
| 39 | Scooter temp abnormal | Motor overheated | Let it cool; reduce load |
| 40 | Main controller temp sensor / overheating | The controller under the heat-sink is hot | Same plus check the thermal paste |
Sources: Electrazoom; Electric Scooters London; Fallman.tech; XiaomiTime.
Error codes: Segway-Ninebot Max G30 / ES / GT
| Code | Meaning | Most likely cause | Action |
|---|---|---|---|
| 10 | Dashboard communication error | Loose / water-damaged harness in the stem | Inspect stem harness, reseat |
| 11 | Motor phase A current abnormal | Short in phase A, damaged controller or motor wire | Inspect MOSFETs; motor cable |
| 12 | Motor phase B current abnormal | Same for phase B | Same |
| 13 | Motor phase C current abnormal | Same for phase C | Often — controller replacement |
| 14 | Throttle abnormality | Throttle damaged / pinched cable | Inspect throttle cable; replace if damaged |
| 15 | Brake sensor fault | Brake lever sensor drifted / over-tensioned cable | Loosen the cable; make sure the lever returns to zero |
| 16 | Motor temperature abnormal | Long climb, overload | Let it cool before restart |
| 18 | Controller fault | Overheat, water, short | Controller replacement |
| 19 | Battery voltage abnormal | Loose battery cable; deep discharge | Check the cable BEFORE assuming a dead battery |
| 21 | Battery communication error | Like 19 + BMS protection trigger | Inspect the cable |
| 23 | BMS communication error | Corrosion, poor contact | Clean the connectors |
| 24 | Motor Hall sensor fault | Motor wiring damaged / water ingress | Sometimes — motor replacement |
| 26 | Firmware / flash memory abnormal | Interrupted firmware update | Power-cycle; re-flash |
| 27 | Controller hardware abnormal | Burnt component, overheat | Controller replacement |
Sources: EScooterHut; Levy Electric; Kickmotion.
Error codes: EY3 (Dualtron / Kaabo / Currus / Speedway)
EY3 displays a “!” triangle with a single-digit code above the battery indicator. Not every “code” is a real error: 1 and 3 are status signals.
| Code | Meaning | Nature | Action |
|---|---|---|---|
| 1 | Cruise control engaged | Not an error — informer | Brake to exit |
| 2 | System error | Internal controller fault | Power-cycle; otherwise — service |
| 3 | Brake levers activated | Not an error — the sensor reports a pressed brake | Release the levers; if it persists — check the cable isn’t over-tightened |
| 4 | Motor / Hall sensor error | Motor cable or hall sensor | Inspect the motor plug; replace if damaged |
| 5 | Throttle (accelerator) error | Throttle or the EY3 module itself | Make sure the throttle returns to zero; check the EY3 → controller plug |
| 6 | Controller communication error | Between the EY3 and the controller | Unplug-replug; verify the 5-pin cable is intact |
Sources: Rider Guide; Apollo Support.
Error codes: Apollo Scooters
Apollo (City, Air, Phantom, Pro, Ghost) uses its own numbering E1–E7. Codes 1–3 often trigger after removing and refitting the handlebar on foldable models — the harness in the stem can splay or get pinched.
| Code | Meaning | Most likely cause | Action |
|---|---|---|---|
| E1 | Brake sensor circuit | Damaged / pinched brake sensor cable (often after folding or a fall) | Inspect brake-sensor connections |
| E2 | Throttle sensor circuit | Damaged throttle cable | Inspect the throttle cable |
| E3 | Handlebar ↔ controller communication | Connection between the bar block and the controller lost | Try power-cycle; check the stem harness |
| E4 | Motor power loss | Connection drops during acceleration / after an impact | Motor cable; controller for diagnostics |
| E5 | Battery / power issue | Deep discharge or BMS undervoltage protection | Charge; check the BMS |
| E7 | Motor hall sensor | One of the motor hall sensors isn’t answering | Sometimes — motor replacement |
Source: Apollo Support — error codes and the detail pages for E1, E3, E7 (Apollo Scooters).
Error codes: Inmotion (S1, RS, Climber, Air, Air Pro)
| Code | Meaning | Cause / context |
|---|---|---|
| E01 | Controller failure | Internal controller fault |
| E02 | Motor failure | Motor, cable, hall sensor |
| E04 | Low battery | Battery flat |
| E05 | Battery overvoltage | Regen on a fully-charged battery during a long descent |
| E06 | Brake handle fault | Brake-lever sensor |
| E07 | Accelerator handle failure | Throttle |
| E09 | Display not receiving data from controller | Stem-display cable |
| E10 | Controller not receiving data from meter | Same channel, opposite direction |
| E11 | Motherboard overheating | Long climb |
| E12 | Motor overheating | Long climb / excessive load |
| E15 | Display hardware failure | The LCD itself |
| E16 | Fall detection triggered | The scooter has fallen; motor auto-locks |
Quirk: errors 5, 6, 7, 11 and 12 can self-restart after a sufficient pause (usually hours) — this is a cool-down reset. Sources: Inmotion Zendesk; Green220.
On-the-go diagnostics: what a symptom means
Not every problem prints a code. Some sit in the behavior. Basic symptom-to-cause mapping that holds across platforms:
| Symptom | What it could be | What to check first |
|---|---|---|
| Throttle doesn’t respond but the display is alive | Throttle sensor, throttle cable, or brake-pull (the controller locks the throttle while the brake is pulled) | Are the brake levers at zero at power-on? |
| Reverse / brake lever reads “pressed” all the time | Brake cable over-tensioned or sensor drifted | Let the lever return fully; loosen the cable |
| Sudden brief jerks on the move | Motor hall sensors (one of three drops out) | Loosen and reseat the motor plug; code 18 (Xiaomi) / 24 (Ninebot) / 4 (EY3) |
| Sporadic reboots during acceleration | BMS overcurrent protection (battery aging) | Avoid Sport mode; measure cells under load |
| Speed “drips” down after 5–10 min | Motor or controller overheat | Let it cool; often — poor airflow under the deck |
| Cruise engaged accidentally on a downhill | The throttle was steady for 5–8 s (the typical condition) | Disable cruise in the app |
| The scooter won’t power on with the Power button | Battery flat or blocked by low-voltage cut-off | Charge; on a BMS cut you need to “push” voltage from the charger |
| BLE pairing won’t go through | BLE module or firmware conflict | Mi Home → forget device → re-pair; occasionally a firmware rollback |
Reset procedures: a safe soft-reset
There is no “hard reset” (as in a phone’s hold-button) on most scooters. Available methods:
- Power-cycle (off, wait 30 s, on) — fixes most transient errors (10, 21, 23 on Ninebot; 10, 21 on Xiaomi; 6 on EY3).
- Hold Power + Mode for 3–5 s (Xiaomi) — switches the unit km/h ↔ mph; does not reset errors. Don’t confuse.
- Mi Home / Segway-Ninebot app → settings → reset KERS / restore defaults — zeroes KERS calibration and wheel-diameter.
- Re-flash firmware via ScooterHacking Utility / Xiaomi CFW Builder (ScooterHacking) — only when confident, voids the warranty.
What not to do: don’t disconnect the battery “under load” (while riding or with the controller on) — this can blow a MOSFET. Don’t “guess” by jumpering two connector pins that “look wrong” — every vendor wires their connectors differently.
When to take it to service
Self-diagnosis is safe while the scooter isn’t moving. When the symptom appears on the move (jerks at speed, falling into full-throttle without input, brake doesn’t bite, smoke / burning smell, hot controller-to-the-touch after a few minutes), it is a stop-condition, not a “we’ll look later”. Same for any code tied to MOSFET (Xiaomi 11, 13, 28), Motor Phase (Ninebot 11–13), Controller (Apollo E3/E4, EY3 6, Inmotion E01).
Before going in: write down the code and the circumstances (speed, hill, temperature, rain — was there any beforehand), photograph the display with the code. This shortens diagnostics because the mechanic doesn’t have to start with a full pre-screen.
Summary table: where to look first
| Platform | Display numbering | App for full opcode | Default cruise | The most-feared code that isn’t actually a fault |
|---|---|---|---|---|
| Xiaomi M365 / Pro / 4 | 10–40 two-digit | Mi Home / Xiaomi Home | Off | 14 / 15 (throttle or brake not at zero at power-on) |
| Ninebot ES / Max G30 / GT | 10–27 no prefix | Segway-Ninebot | Off | 10 (BLE / dashboard re-sync) |
| Dualtron / Kaabo / Currus (EY3) | 1–6 single-digit | (No official one — Bluetooth tools are 3rd-party) | On | 1 (cruise engaged — informer) and 3 (brake pressed) |
| Apollo City / Air / Phantom / Pro / Ghost | E1–E7 | Apollo App | On | E1 (brake sensor after folding) |
| Inmotion S1 / RS / Climber / Air | E01–E16 | InMotion | On | E05 (overvoltage when braking on a full battery) |
For a deeper dive into the electronic architecture behind these codes — see Controllers, BMS, power electronics, and for brake lever sensors and fail-safes — Electric scooter brakes.
Related topics
If display, throttle and error codes surfaced a specific question or symptom, here are sister articles with §-section pointers to where that topic is discussed in more depth:
- Display & HMI engineering §1–§4 — the engineering side of what a rider sees in §1–§5 of this article: TFT vs LCD, contrast ratio for sunlight, ECE R10 EMC requirements for transflective displays, IP rating of OLED films.
- Handgrip, lever and throttle engineering §2–§5 — exactly how a hall sensor in a trigger / thumb / twist throttle converts travel into a mV signal (
0.8–4.2 Vtypical, fail-safe on out-of-range), §3 covers detent kinematics, §4 the controller-side pull-up/pull-down, §5 explains how “throttle not at zero at power-on” (Xiaomi 14/15, Ninebot 14, Apollo E2) is detected at the ADC level. - Controllers, BMS, power electronics §1–§3 — what happens “below the display”: MOSFET bridge, BMS UART protocol, IoT stack. Explains most of the 11/13/21/26/27 from §6–§9 of this article at the hardware level.
- Motor & controller engineering §5–§6 — Park/Clarke transforms, SVPWM, IGBT/MOSFET driver stages. Explains the Ninebot 11/12/13 “motor phase A/B/C abnormal” and the Xiaomi 28 “MOSFET error” from §6–§7 of this article.
- Electrical protection & overcurrent engineering §1–§4 — IEC 60364-4-43 overcurrent + IEC 61643 surge protection. Context for Xiaomi 24 “wrong supply voltage”, Ninebot 19 “battery voltage abnormal”, Inmotion E05 “battery overvoltage” from §6–§9 of this article.
- Functional safety engineering §3–§5 — IEC 61508 SIL levels, ISO 26262 ASIL decomposition, brake-pull lock-out, fall-detection (Inmotion E16) as a safety function. Explains why some codes are “not an error, just a state” (EY3 1/3 from §7 of this article).
- Software & firmware engineering §2–§4 — UART/CAN bus between display-controller-BMS, OTA flash contract, firmware integrity (CRC32 + signature). Explains Xiaomi 26/27/31, Ninebot 26, Apollo E3, EY3 6 from §6–§9 + §11 (re-flash). Also:
ScooterHacking Utilityas a community tool reverse-engineered from these very protocols. - Cybersecurity engineering §2–§5 — Bluetooth pairing (Mi Home / Segway-Ninebot), authentication moments, anti-tampering. Explains Xiaomi 22 “bad BMS serial / password” and 29 “ESC not activated” — Xiaomi uses a challenge-response handshake between controller, BMS and Mi Home as an anti-theft / anti-counterfeit vector.
- Privacy & data protection engineering §1–§3 — GDPR Art. 25 (privacy-by-design) for telemetry from Mi Home / Segway-Ninebot / Apollo App. Also: the error log (Apollo App, Inmotion app) sent from the device to the cloud.
- Human factors & ergonomics engineering §3–§5 — ISO 9241-110 (interaction principles) + Fitts’ Law for placement of Power/Mode/Gear buttons. Argues why the twist throttle (§3 of this article) scores lowest on precision in Steering Reversal Rate (SRR) tests.
- Anti-theft, locks, GPS, parking §2–§4 — lock mode (Mi Home) + GPS tracker that leave the display in a low-power state. Some codes (Xiaomi 10 “BLE communication error”, Ninebot 10 “dashboard communication error”) often appear after exiting a stay-on-locked state.
- Repair & reparability engineering §2–§5 — EN 45554:2020 reparability score, ECC marking, parts availability. Argues §10–§12 of this article: why some “codes” mean “replace the controller” (closed unit, no socketed MOSFET) vs “socketed BLE board on M365 Pro replaceable in 5 min”.
- Verification & validation engineering §3–§5 — V-model + UL 2272 + IEC 60068 (vibration, shock, IP). Explains why error codes between models in the same family (Xiaomi M365 vs Pro vs 4) are different enum tables: the V&V plan runs at the per-SKU level, and the code table is part of release acceptance.
- EMC / EMI engineering §2–§4 — CISPR 25 + IEC 61000-4 for BLE in the dense 2.4 GHz urban environment. Explains why Xiaomi 10 / Ninebot 10 sporadically trigger in Wi-Fi-saturated downtowns — the pairing signal collides with 802.11n channel 6.
- Pre-ride safety check §2–§4 — startup checklist that includes display self-test + cruise-engagement check + brake-pull verification. Also: how to read the summary table (§12 of this article) in the field.
- Segway-Ninebot history §3–§5 — how the Ninebot-ESC protocol (the basis of the 10–27 error table in §7 of this article) became the de-facto standard after the 2015 Segway acquisition.
Sources
Consolidated source list, grouped by the §-sections of this article. All sources are English-first (where there is a choice) or the manufacturer’s own language; numbering follows the order in which they appear across §-sections.
§1–§5 Displays — Xiaomi, Ninebot, EY3, Apollo, Inmotion
- Electrazoom. “Xiaomi M365 and M365 Pro Electric Scooter Error Codes Explained.” — the original description of the blink encoding (long = tens, short = ones).
- Xiaomi Mi Global Support. “How to enable / disable Cruise Control on Mi Electric Scooter.” KA-07527. — the official contract for Mi Home → Settings → Cruise Control toggle.
- ScooterHacking.org Wiki. “Guide for Mi generator.” — the most complete community documentation of DRV-controller parameters (system voltage, current control, KERS, brake lever, BLE display, cruise control delay).
- ScooterHacking.org Wiki. “Mi Electric Scooter — protocol reverse-engineering.” — UART protocol between the DRV ESC and the BLE chip (XOR-CRC, packet framing) — the basis of Xiaomi 10/26/27.
- EScooterHut. “Ninebot Max G30 Error Codes.” — the full 10–27 table with level fields (input peripherals, motor phase, BMS, controller).
- Levy Electric Support. “Segway Max Error Codes.” — a fleet-operator diagnostic doc; verified across 250+ devices, hence field-validated.
- Kickmotion. “Ninebot G30 Max Electric Scooter Error Code List.” — UK-distributor sweep with extra field notes (brake harness, water ingress).
- Rider Guide. “EY3 LCD Throttle.” — the fullest public reference on the Minimotors EY3 (button mapping, p-settings P0–PD, error codes 1–6, OEM distribution Dualtron / Kaabo / Currus / Speedway).
- Wee-Bot Dualtron LCD Guide. — French-language EY3 deep-dive, English toggle on-site, p-settings table with measurements.
- Apollo Scooters Support. “Error Codes.” — the official E1–E7 sweep with per-code deep-dive pages (E1: 2613303, E3: 2888232, E7: 2888800).
- Apollo Scooters Support. “E1 Error Code.” — brake sensor circuit, post-fold harness pinch.
- Apollo Scooters Support. “E3 Error Code.” — handlebar ↔ controller comms loss.
- Apollo Scooters Support. “E7 Error Code.” — motor hall sensor diagnostic.
- Inmotion Service Centre Zendesk. “Error codes for Scooters.” — the official E01–E16 sweep, context for self-restarting codes (5/6/7/11/12).
- Green220. “Understanding Your Inmotion Electric Scooter.” — operator sweep, extra field notes on fall-detection (E16) and motherboard overheating (E11).
- Fallman.tech. “Xiaomi M365 Error Codes.” — repair-shop notebook, useful on rare codes (29, 31, 35).
- Electric Scooters London. “Xiaomi M365 and M365 Pro Electric Scooter Error Codes.” — UK service-shop sweep, annotations with frequency stats.
- XiaomiTime. “Xiaomi Ninebot Electric Scooter Error Code List.” — cross-family Xiaomi + Ninebot roll-up with a note on shared MOSFET-error semantics.
§6 Throttle types — trigger / thumb / twist
- Apollo Scooters Blog. “Comparing Different Throttles for Electric Scooters: Trigger, Thumb or Twist.” — source of the “~53% thumb vs ~20% trigger have an IP rating” statistic.
- Rider Guide. “Throttles.” — comparative review with an ergonomic focus.
- Varla Scooters. “Choosing the Right Electric Scooter Throttle: Thumb vs Trigger.” — brand perspective, data from an internal user survey.
- Allegro Microsystems. A1324/A1325/A1326 Low Noise Linear Hall Effect Sensor ICs. Datasheet AN296127. — a typical throttle-module hall sensor, mV/G transfer function, fail-safe out-of-range detection (
<0.5 V/>4.5 V). - SAE International. J1939 — Recommended Practice for Serial Control and Communications Heavy Duty Vehicle Network. — protocol base for CAN throttles (Apollo Pro+, NAMI), though the e-scooter market more often uses a simpler UART.
- ISO 26262-1:2018. Road vehicles — Functional safety — Part 1: Vocabulary. — the ASIL classification framework that auto OEMs apply to throttle redundancy; the e-scooter market is still on pre-ASIL self-certification.
§7 Cruise control — activation / exit / safety limits
- Levy Electric. “What is Cruise Control on an Electric Scooter.” — fleet-operator perspective, frequency stats for accidental-engagement complaints.
- Levy Electric. “How to Turn Off Cruise Control on an Electric Scooter.” — the Mi Home / Segway-Ninebot toggle procedure.
- Levy Electric. “Understanding Cruise Control on Electric Scooters.” — safety-limit checklist (traffic / wet / descent / gloves).
- Nanrobot. “E-scooter Guide: What is the Cruise Control on Electric Scooters.” — the manufacturer-side activation contract.
- CitizenSide. “How To Use Cruise Control On An Electric Scooter.” — step-by-step with video references.
- Gyroor. “What Does Cruise Control Do on Electric Scooter: A Complete Guide.” — additionally covers kid-scooter cruise-disabling firmware (3-mph cap).
- SAE International. J2399 — Adaptive Cruise Control (ACC) Operating Characteristics and User Interface. — auto-industry recommended practice; the e-scooter market copies the activation pattern (steady throttle window), the exit pattern (brake-pull cancel) and HMI-indicator standards from ACC.
§8 Speed modes / Eco-Standard-Sport — power and speed mapping
- CEN/CENELEC. EN 17128:2020. Light motorized vehicles for the transportation of persons and goods and related facilities and not subject to type-approval for on-road use — Personal light electric vehicles (PLEV) — Requirements and test methods. — the principal EU PLEV-class standard, specifies max 25 km/h, motor cut-off above this speed, the mode-switching contract.
- Verordnung über die Teilnahme von Elektrokleinstfahrzeugen am Straßenverkehr (eKFV). 2019-06-15, Germany. — the German type-approval framework that de facto triggers the “Eco/Standard/Sport” architecture in EU models (20 km/h hard cap, no Sport).
- UNECE Regulation No. 10 (R10). Uniform provisions concerning the approval of vehicles with regard to electromagnetic compatibility. — EMC requirements for the controller-display-BLE link.
- UNECE Regulation No. 79 (R79). Uniform provisions concerning the approval of vehicles with regard to steering equipment. — steering + speed-control reference standard that the ACC/cruise-control body cites.
- UL 2272:2022. Standard for Electrical Systems for Personal E-Mobility Devices. — US-side counterpart to EN 17128, covering the power-mode logic for NRTL-certified devices. 36a. Levy Electric. “Understanding the Eco Mode on Electric Scooters.” — source of the eco-mode gain estimate (~+30% range from running the motor in a more efficient power band). 36b. UK Department for Transport. “E-scooter trials: guidance for users.” — source of the 25 km/h (15.5 mph) cap for UK rental-trial devices.
§9–§11 Error codes — root-cause hardware tie-back
- Texas Instruments. DRV8316C 60-V Three-Phase Smart Gate Driver with Adjustable Slew Rate and Current Sense Amplifiers. SLLSF85B. — a typical gate-driver IC, on the DRV family of Xiaomi M365/Pro/4; fault flags (
OCP,OTW,OTSD,UVLO) → Xiaomi 11/13/28/40. - Infineon Technologies. 6EDL04N06PT Driver IC for MOSFETs / IGBT. — Ninebot Max G30 gate driver; field-fault patterns map to Ninebot 11/12/13.
- Bosch Engineering GmbH. “Brake System for Two-Wheelers and Light Electric Vehicles.” — the eABS lever sensor (Hall-effect) triggers at 0.8–2.2 mm of lever displacement; Apollo E1 / Ninebot 15 / Inmotion E06 trigger on out-of-range.
- Bluetooth SIG. Core Specification 5.3. — the baseband reference for Mi Home / Segway-Ninebot / Apollo App pairing; pairing-failure modes explain Xiaomi 10 and Ninebot 10.
- IEC 60068-2-78:2012. Environmental testing — Part 2-78: Tests — Test Cab: Damp heat, steady state. — the humidity-cycling reference behind the
loose / water-damaged harnessfailure modes (Ninebot 10/24). - IEC 61508-2:2010. Functional safety of electrical/electronic/programmable electronic safety-related systems — Part 2: Requirements for electrical/electronic/programmable electronic safety-related systems. — the framework for fault detection (FMEA) and fault-reaction time (FRT); auto-restart (Inmotion 5/6/7/11/12) is FRT with a recovery class.
- Microchip Technology. AVR Watchdog Timer Operation. AN1023. — WDT-reset mechanics that explain the “firmware / flash memory abnormal” code classes (Xiaomi 26/31, Ninebot 26).
- NXP Semiconductors. S32K1 Microcontroller for Automotive General Purpose. RM. — controller base for newer platforms (Apollo Pro+, Nami); fault-bit definitions → Apollo E3/E4 mapping.
§12 On-the-go diagnostics + reset + service
- SAE International. J2012_201612 — Diagnostic Trouble Code Definitions. — the auto-industry DTC framework; e-scooter vendors emulate its structure (system letter + 4-digit number) in Mi Home / Apollo App / InMotion app logs, though the display keeps the short form.
- IEEE 11073-10101:2019. Health informatics — Personal health device communication — Part 10101: Nomenclature. — reference for the event-log nomenclature adapted by Mi Home / Inmotion app telemetry.
- ISO 9241-210:2019. Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems. — the basis of error-message design (clarity, recovery path, single-attempt rule); explains the difference between Apollo “E2: Throttle sensor circuit” (descriptive) and Xiaomi “14” (numeric only).
- ISO/IEC 25010:2011. Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models. — the reliability sub-axis (maturity, availability, fault tolerance, recoverability); the reference for the self-restart pattern (Inmotion 5/6/7/11/12).
- Bosch Automotive Handbook, 11th ed. (2022). ISBN 978-1-119-91190-6. Wiley. — Chapter “Electrical and electronic systems for vehicles”: gate-driver fault modes (UVLO, OCP, DTC), Hall-sensor failure semantics. The reference textbook for §6 and §11 diagnostics.
- Mohan, N., Undeland, T., Robbins, W. Power Electronics: Converters, Applications, and Design, 3rd ed. (2003). ISBN 978-0-471-22693-2. Wiley. — Chapters 21–22: MOSFET reliability, thermal modeling, derating curves. The reference textbook for understanding Xiaomi 28 / 40 root causes.
- ECE Regulation No. 78, Rev.3 (2023). Uniform provisions concerning the approval of vehicles of categories L1, L2, L3, L4 and L5 with regard to braking. — brake-lever fail-safe specs for category L1e; the basis of Apollo E1 / Ninebot 15 / Inmotion E06.