VESC · electronics and software

Wiring and config done properly

The electronics side of an Onewheel build is where most problems start and where they are cheapest to avoid. Controllers wired neatly, looms made to fit, limits set to your hardware, and faults diagnosed with instruments rather than guesswork.

Talk about your build

Who does the work

A day job in electronics, applied to boards

I work as a Principal Electronics Engineer and run the Electronics department at an Engineering firm. The habits that come with that (correct conductor sizing, production level terminations that survive vibration, and a focus on quality of work) are the same habits that make a board reliable and last the distance.

In practice that means a custom loom built for your chassis rather than bodged to length, a controller configured around your pack and wiring rather than left at defaults, and a written record of what was changed so nothing is a mystery six months later.

What we do

Whole builds, single jobs, or a look at something that is not behaving.

Custom looms

Built to the length your chassis actually needs rather than coiled up in the box. Routed clear of rail edges and heat, with connectors chosen for the vibration a board sees rather than what came in the kit.

Controller config

Motor detection run properly, current and voltage limits set to your pack rather than left at defaults, and float package tuned around how you ride. Config files backed up and handed over so you can go back to a known state.

Fault finding

Intermittent cutouts, phantom faults, sensor errors, bad batteries and looms that have chafed. Logs read and measurements taken before anything gets swapped, so you are not buying parts on a guess.

Firmware and updates

Firmware brought up to a version that suits your hardware, with settings backed up first. Rollback plan agreed before we start.