Segway Max Error Codes
This page recreates the legacy Segway Max error-code reference for fleet technicians. Use it when a Segway Ninebot Max or Max-family rental scooter displays an error code on the dashboard or reports one through Segway tooling.
Safety first
Do not redeploy a scooter with brake, throttle, controller, battery, motor, or lock errors until the fault is resolved and the vehicle passes a test ride.
Quick Reference
| Code | Meaning | Field action |
|---|---|---|
| 10 | Display and controller communication abnormality | Reset. Reseat the dashboard connector. Update firmware. Replace LCD, then controller if needed. |
| 11 | Motor A-phase current sampling abnormality | Inspect motor phase wiring for frays, pinches, cuts, or loose connectors. Replace controller, then motor if needed. |
| 12 | Motor B-phase current sampling abnormality | Same as code 11: inspect phase wiring, then controller, then motor. |
| 13 | Motor C-phase current sampling abnormality | Same as code 11: inspect phase wiring, then controller, then motor. |
| 14 | Throttle Hall sensor abnormality | Inspect throttle movement and wiring. Replace throttle if it does not return cleanly or the sensor is faulty. |
| 15 | Left brake Hall sensor abnormality | Check whether the left brake was held during startup. Inspect brake magnets and wiring. Replace the brake handle if needed. |
| 16 | Right brake Hall sensor abnormality | Same as code 15, but for the right brake handle. |
| 18 | Motor Hall sensor abnormality | Inspect the motor Hall connector and 5-pin wiring. Replace controller, then motor if needed. |
| 19 | Abnormal battery voltage | Charge the battery and inspect charger LED behavior. Replace battery or controller if voltage remains abnormal. |
| 21 | BMS communication error | Check the 4-pin battery communication connector. Charge for several hours. Test with known-good controller and battery. |
| 22 | Wrong BMS password | Usually rental firmware or STLink provisioning mismatch. Refresh serial/provisioning in Segway tooling or replace controller/battery. |
| 23 | BMS default serial number | Change the BMS serial number in Segway tooling. Replace battery, then controller if needed. |
| 24 | System voltage detection abnormality | Check for battery upgrades, overcharge, or mismatched firmware. Run down/charge battery, then replace battery or controller if needed. |
| 26 | Flash save error | Reset, update firmware, then replace controller if unresolved. |
| 27 | Controller password error | Usually rental firmware/provisioning mismatch. Refresh serial/provisioning in Segway tooling or replace controller. |
| 31 | Program jump error | Reset. If it returns, replace controller. |
| 32 | IoT heartbeat timeout | Inspect IoT connection and harness. Reseat cable. Replace IoT, then controller if needed. |
| 35 | Controller default serial number | Change controller serial number in Segway tooling. Replace controller, then battery if needed. |
| 37 | Charging base or charging cable failure | Reset. Inspect wiring from controller to battery. Replace affected wiring/component, then controller or battery if needed. |
| 39 | Battery temperature sensor abnormality | Check battery temperature in Segway Launcher. Warm/cool battery if needed. Restart. Replace battery if persistent. |
| 40 | Controller temperature sensor abnormality | Let controller cool. Inspect controller wiring. Replace controller if persistent. |
| 41 | Motor temperature abnormality | Let motor cool. Inspect motor wiring. Replace motor if persistent. |
| 45 | Retail/rental firmware mismatch | Confirm firmware path. Reflash to the correct rental-compatible firmware. |
| 50 | Temperature sensor or rental firmware setup problem | Reset. If firmware-related, update IoT, battery, and controller firmware. |
| 51 | LCD/controller firmware mismatch | Update LCD firmware, then controller firmware. Replace LCD, then controller if needed. |
| 52 | E-lock/controller firmware mismatch | Confirm matching firmware versions. Replace controller, then e-lock if needed. |
| 54 | E-lock and controller communication failure | Inspect e-lock/controller wiring. Replace damaged wiring, controller, then e-lock if needed. |
| 55 | Battery cover sensor failure | Reopen and fully close the battery cover. Replace the battery lock if persistent. |
Detailed Notes
Codes 10-13: Display and Motor Phase Communication
Code 10 points to display-controller communication. Start with a reset and dashboard connector reseat before replacing hardware.
Codes 11, 12, and 13 point to motor phase current sampling. Inspect motor phase wiring carefully for cuts, pinches, damaged insulation, or loose connectors. If wiring looks good, test with a known-good controller before replacing the motor.
Codes 14-16: Throttle and Brake Hall Sensors
Code 14 is a throttle Hall sensor issue. Make sure the throttle physically returns to neutral and is not blocked by grip damage or debris.
Codes 15 and 16 are left/right brake Hall sensor issues. They can be triggered if the brake is held while the scooter boots. If the error persists, inspect the brake handle magnets, wiring, and connector.
Codes 18-24: Motor, Battery, and BMS
Code 18 is a motor Hall sensor issue. Inspect the 5-pin Hall connector before replacing parts.
Code 19 usually means the battery voltage is below the expected range. Charge first. If charger LED behavior indicates no charge acceptance, test with a known-good battery.
Code 21 means the controller cannot communicate with the BMS. Reseat the battery communication connector and test with known-good battery/controller hardware.
Codes 22, 23, and 24 usually involve provisioning, serial, battery, or firmware mismatch. Use Segway tooling before replacing hardware.
Codes 26-35: Firmware, Program, IoT, and Serial Issues
Codes 26, 27, 31, and 35 are usually controller firmware/provisioning issues. Reset and firmware update come before controller replacement.
Code 32 means the scooter cannot detect the IoT module. Inspect the IoT harness, reseat the cable, and replace the IoT module before replacing the controller.
Codes 37-55: Charging, Temperature, Firmware Match, and Locks
Code 37 points to charging base/cable failure. Inspect wiring before replacing expensive parts.
Codes 39-41 are temperature-sensor or overheating paths. Let the component return to normal temperature and inspect sensor wiring.
Codes 51 and 52 are firmware-match issues between paired components. Confirm matching firmware before replacing hardware.
Code 54 means e-lock/controller communication failure. Inspect the e-lock harness first.
Code 55 means the battery cover is not fully closed or the cover sensor/lock is faulty.