Home / Support
Help & service

How can we help?

Search the knowledge base, browse guides, or talk to the engineers who built your controller.

⌘K
Frequently asked

Answers, straight up

The questions our support inbox sees most. If yours isn't here, the form below reaches a firmware engineer — not a ticket bot.

01The web UI won't load — what address do I use?

Join the controller's Wi-Fi access point (default PW-AP-1, password SpeedControl) and browse to http://192.168.50.1 — or type http://pw.setup, which resolves to the same address. The config UI is served locally from the controller, not the internet, so your phone or laptop must stay on the controller's network; if it warns about “no internet connection”, stay connected anyway.

If you've changed the access point name or password in Settings, use your values. More in the documentation hub.

02A flash was interrupted halfway. Is the board bricked?

No. The browser flasher writes only the application and web-interface partitions — it never touches the bootloader region and never erases the whole chip. An interrupted write leaves the bootloader intact, so reconnect over USB and flash again. An incomplete application image simply won't boot, and the motor stays off until a good image is flashed.

03An overcurrent fault trips on every hard launch.

That's the protection doing its job — launching from a standstill draws stall current, which is what trips the surge or impulse tier. By default each channel allows 100 A continuous, 150 A surge for 2 s, and 200 A impulse. Before raising any threshold, try slowing the throttle ramp-up in your drive profile — a gentler ramp absorbs most launch transients without losing torque feel. The tiers and defaults are in the fault reference; if the motor's locked-rotor current is genuinely above those limits, the controller is undersized for the application.

04Do I need to stay connected to Wi-Fi while driving?

No. The access point is for configuration and diagnostics only — the control loop, limits, and protections run entirely on-board, so connecting or disconnecting a phone or laptop has no effect on throttle, braking, or safety behavior. The status LED shows the difference: solid means no device is connected, a slow blink means one is (see the fault & LED reference).

05Does updating firmware erase my configuration?

No — configuration lives in its own storage partition, which neither update path touches. The browser flasher writes only the application and web-interface images and never erases the chip; OTA updates from the web UI behave the same. OTA requires the controller's access point password and a matching pair of application and web-interface images from the same release package — the upload is rejected if the versions don't match.

06Which motors and voltages are supported?

The DRV1100 series drives brushed DC motors; brushless (BLDC/FOC) motors are not supported. Out of the box the protections default to a 16 V undervoltage trip, an 86 V overvoltage trip, and 100 A continuous per channel (150 A surge, 200 A impulse) — all adjustable in the web UI (see the fault reference). The hard electrical limits for your board revision are in the datasheet.

Contact

Talk to an engineer

Sales & volume orders

OEM pricing, custom firmware profiles, and pre-configured fleet batches for ride-on and automation builders.

sales@jara.tech
On the underside of the board, or in the web UI under Device.
Diagnostic data is only shared if you attach it.