Documentation

Troubleshooting

Find your symptom, work down the list. Most problems on this page resolve without tools — and nothing here requires reinstalling firmware unless explicitly stated.

110085
On this page

Start here

Two things tell you most of what's going on before you touch anything:

  • The status LED.Steady means no Wi-Fi station is connected and no fault is active; slow blink means at least one station has joined the controller's Wi-Fi; fast blink means a fault is active. The LED does not report whether motor output is enabled. If it never lights, verify input power and the ON connection. The full table is in the fault & LED reference.
  • The Dashboard page. If you can reach the web app, the Dashboard shows the live throttle input, the active direction, the motor current, and any active fault in real time — start there rather than guessing.

If you haven't set the controller up yet, follow the quickstart first — several "problems" are just steps that haven't happened yet.

Can't reach the web app

The controller hosts its own Wi-Fi access point and serves the web app from it. Connect your phone or laptop to the controller's network, then browse to http://192.168.50.1 (default password SpeedControl). If it won't come up:

  • Give it a few seconds after power-on — the access point comes up a little way into boot. If the status LED is off, the board has no power: check the supply wiring first.
  • Use the IP address directly — http://192.168.50.1 — and make sure it's http://, not https://. Some browsers force the secure scheme; the controller serves plain HTTP on its own network.
  • Confirm you're still on the controller's network. Phones quietly fall back to mobile data or another Wi-Fi network when one has no internet — turn mobile data off for a moment, or tell the phone to stay connected.
  • If the page loads but looks broken (often right after a firmware update), force-refresh (Ctrl/Cmd+Shift+R) or open a private-browsing window to bypass cached assets.

Power's on but the motor won't move

The controller needs both a throttle command and a chosen direction before it will drive the motor. Open the Dashboard page and check, in order:

  • The controller is enabled.The ON pin has to be tied to B- for the controller to run — if it's left open, the output stays disabled even with the battery connected.
  • A throttle input is arriving.Watch the live throttle reading on the Dashboard while you press the pedal or move the transmitter. The throttle input (T) expects 0–3.3 V; if the Dashboard reading doesn't move, the problem is on the input wiring or calibration, not the motor.
  • A direction is indicated. The controller will not drive the motor until a direction tells it which way to turn. Confirm a direction shows on the Dashboard — select it with the input you assigned to forward/reverse, or set it on the Direction page.

The motor runs the wrong way

  • Swap the motor leads. Reverse the polarity of the motor connection — swap the two wires at the MOTOR OUTPUT terminals — and the motor turns the other way.
  • Or fix it in software.Check the direction on the Diagnostics page; if it's backwards, change the active direction on the Direction page in the web app.

It runs for a few seconds, then shuts off

A short run followed by a shutdown is almost always a protection doing its job. Check the Dashboard for the active fault, then work through these on the Protection page:

  • Low-voltage threshold set too high. If the undervoltage cutoff is above what your pack actually holds under load, the controller trips as soon as the voltage sags. Review the battery profile and its derived undervoltage trip and clear thresholds. The default trip delay is 30 seconds and the default clear time is 2 seconds.
  • A staged current threshold is qualifying. Watch measured current and the active stage on Dashboard or Diagnostic. The default continuous, surge, and impulse thresholds are 100 A, 200 A, and 300 A; they are protection trips, not the normal current command. Set normal current authority with Max drive current on the Essential page.
  • Something else is faulted. The Dashboard names the active fault — start with whatever it reports rather than guessing.

RST recovery and full erase

RST recovery and a full erase have different scopes:

  • Restore account and developer defaults with RST. Connect RST to 3.3 V while powering the controller on. This restores the default Wi-Fi name and password, developer settings, primary board role, and extension default. Motor, battery, direction, and protection settings are preserved; this is not a full factory reset.
  • Full erase over USB. For a complete wipe, connect the USB-C port (programming only, and un-powered) to a computer, open the web flasher, choose the full-erase option, and flash the current release. This clears the entire flash — settings and firmware — and reinstalls from scratch.

After RST recovery, reconnect to PW-AP-1 at http://192.168.50.1 using password SpeedControl. After a full erase, follow the quickstart to set it up again.