PRIVATE RIDER BETA · REQUEST ACCESS
Turbo Levo only · tuning preview

Plan a tuning profile. Nothing changes on the bike.

OpenLevo Tune is the Turbo Levo profile workspace inside Bikes → Tune. Adjust Assist and Peak power for Eco, Trail, and Turbo, then review the exact before-and-after values. In the current beta, profiles stay local and bike writes are disabled. Tuning for Bosch Smart System bikes is not available in this workspace.

How tuning preview works

From a ride idea to a reviewed profile.

Think of a profile as a reusable recipe for how you want the three familiar ride modes to feel. Tune keeps the recipe, its controls, and the exact proposed changes in one place.

1. Choose a starting profile

Begin with a local profile such as Factory feel, Lunch laps, or All-day epic—or create your own. Profiles let you prepare different intentions without treating one setup as right for every ride.

2. Shape each ride mode

Assist describes how much support the mode is intended to provide. Peak power sets its planned upper limit. Tune shows both controls for Eco, Trail, and Turbo, for six documented values in total.

3. Review the exact difference

Before anything could be applied, Tune lists every previous and requested value side by side. Nothing changes merely because you moved a slider, and the current preview cannot write to the bike.

Tune the ride in full view.

Choose a local profile and adjust only the six documented values: Assist and Peak power for Eco, Trail, and Turbo.

The editor — Bikes → Tune. Local profiles—Factory feel, Lunch laps, All-day epic, or one you create—with per-mode Assist and Peak power sliders.

The honest apply state. The diff is useful now. The write button is replaced by “Awaiting hardware validation.”

Verify what the bike accepted.

Before and requested values stay explicit. When physical-bike validation opens the gate, every changed value must be read back and reported as verified, mismatched, or unavailable.

The hardware gate stays honest.

Preview is useful without pretending sample values came from a bike. Writes remain unavailable until the complete stopped-bike, confirmation, write, and read-back path passes physical validation.

OpenLevo Tune's safety contract

Six documented values only Assist and peak power for Eco, Trail, and Turbo. Smart-mode variants and every undocumented parameter are excluded from the writable set.
Never while moving A future apply requires measured speed to equal zero. With the hardware gate closed, no confirmation can be presented and no write can execute.
Verified by read-back A Bluetooth "write succeeded" is not proof the motor took the value. Each changed value is read back; mismatch, retry failure, or unavailable verification is reported without claiming success.
Factory baseline, hardware-gated Only a measured, gate-open bike configuration can become the factory baseline. Preview sample values can never be saved as one.
Every change on the record When tuning is enabled, each write must log what changed, when, before and after values, and whether read-back verified it.
No speed unlock. Ever. The one control other apps whisper about is the one OpenLevo will never have. Read why — it's a settled decision, tested against in every release.