⚠️ Error 30 — Communication Error
What it means: A communication/connection fault between the display and the controller — they have lost their conversation. This is the code we see most, and it is very often a simple connector issue or a known bad display batch, so work through it before assuming the worst.
How to fix it:
- Reseat every connection. Power down, then unplug and replug all connections on the kit — the entire main wiring harness (display, throttle, brake levers), the motor leads, the battery, and the speed sensor. Inspect closely for bent pins and align the arrows on each Higo plug. This resolves the majority of Error 30 cases.
- Check for pinched or over-tight cables. Make sure no cable — especially the ones coming out of the controller — is being pinched, stretched taut, or pulled partway out of its connector by tight routing.
- Suspect the display (especially a C965). There was a known bad batch of C965 displays (around 2016) with internal cable breaks that mimic a controller failure and throw Error 30. If you can, swap in a known-good compatible display — this is the fastest way to confirm, and it fixes a large share of stubborn Error 30s. (Any UART-protocol BBS display works; CAN-protocol displays do not.)
- Check the 5V rail at the throttle. A dead 5V supply — often from water intrusion in the throttle or a failed sensor dragging the rail down — can cause Error 30. If you have a multimeter, check for ~5V at the throttle connector; no 5V points to a short somewhere on that rail.
- Open the controller and reseat internal plugs. Loosen the controller from the motor core, unplug and replug all internal controller plugs, and check for silicone interference or a plug that isn't fully seated.
- Contact support. If none of the above clears Error 30, open a support ticket and we will help you isolate the display versus the controller by swapping components.