Rider, route, and motion
Phone GPS and motion sensors, optional Apple Watch measurements, ride timing, and derived jump events follow the rider across both supported bike systems.
Telemetry becomes useful when its source stays visible. This guide explains every signal available in OpenLevo Studio, what it can reveal, and why a missing value is sometimes the most honest answer.
The Telemetry template: speed, rider and motor power, cadence, and battery in one monospace feed, a route card, and a ticker carrying heart rate, elevation, and ride events—each value tagged with where it came from.
Real footage, sample data: first-person trail footage edited and exported by OpenLevo Video Studio with sample telemetry. The footage was not used to infer or recover measurements.
Speed, cadence, rider and motor power, battery percentage, and odometer can be shared across supported systems. Energy in watt-hours, temperatures, bike range, assist modes, and detailed status are bike-specific and appear only when reported. OpenLevo never manufactures a missing channel.
Phone GPS and motion sensors, optional Apple Watch measurements, ride timing, and derived jump events follow the rider across both supported bike systems.
Turbo Levo can add controller, energy, thermal, ownership, security, and supported tuning context when its controller and firmware expose them.
Smart System supplies its published live channels for speed, cadence, rider and motor power, battery, odometer, and system status. OpenLevo does not write Bosch settings.
The rider-power channel reported by the bike: useful for seeing where you worked, not a complete measure of physiological load.
Private by default. Unavailable when the bike does not report it.Your share of combined rider and motor power at that moment. It shows the partnership without judging the effort.
Private by default. Requires both rider- and motor-power channels.Crank revolutions per minute. Pair it with power to see how a climb was ridden, not simply how fast the bike moved.
Unavailable when cadence is not reported.Measured heart rate from an allowed health source, synchronized to the film only when the rider chooses to include it.
Private by default. Never inferred from the footage.Bike-reported speed where the channel is available, kept distinct from phone GPS speed.
Units follow the project setting.The bike’s reported motor-power channel, revealing when assistance builds, settles, or responds to rider input.
The exact channel depends on bike support.Battery state of charge reported by the bike—a familiar percentage for the arc of the ride.
A stale stream is marked stale rather than frozen.Remaining energy in watt-hours when the bike exposes that channel. It is not fabricated from battery percentage.
May be unavailable on some bike and firmware combinations.The reported mode state—such as Eco, Trail, Turbo, eMTB, Tour+, or another recognized mode—giving context to power and battery changes.
Shown only when a recognized mode is reported.The motor's own reported temperature — the story of a long climb told in heat, journaled for the whole ride.
Unavailable when the bike does not report it.Measured pack temperature. It feeds the range model directly — a cold battery honestly costs range.
Unavailable when the bike does not report it.The bike's own short and long range estimates, shown as their own rows and never blended into OpenLevo's model.
Availability varies by controller and firmware.Lifetime distance the bike has actually rolled — the figure that drives Garage totals and service intervals.
GPS totals stay labeled "ridden with OpenLevo."Altitude from the recorded phone route. It can reveal the profile of a climb, with normal GPS variation.
Precise route use is opt-in for export.Change in GPS elevation over ground distance. It is useful as a trend and can be noisy over short intervals.
Derived from accepted route fixes; smoothing may be applied.Distance accumulated from accepted phone GPS fixes, synchronized to the point shown in the film.
Units follow the project setting.The synchronized ride clock at the playhead, connecting a video moment to its place in the recorded ride.
Calculated from project and ride timing.Energy per distance as the ride actually burned it — the number that turns battery percent anxiety into arithmetic.
Journaled when the bike reports it.OpenLevo carries the source and state of telemetry through import, preview, and export. That protects the meaning of the ride.
Bike, phone GPS, Watch GPS and barometer, chosen health measurements, and imported recorders like a Garmin remain distinguishable from calculated values — each labeled with its source.
If a stream drops, the editor can mark it stale instead of holding the last number as though it were current.
Unsupported or absent channels remain unavailable. OpenLevo does not infer telemetry from video pixels.
Precise route, heart rate, and rider power require explicit inclusion. Studio edits and source files stay local.