Join the waitlistJoin
Life Lever Moto

What do you want lifelever to help with?

Not sure? Start with your own AISee all levers

More coming: finance, work, parenting.

Moto

How Moto reads a bike

How the bike side of Life Lever Moto reads your motorcycle, from the diagnostic port to your own AI assistant, step by step.

The diagnostic port

Most vehicles built in the last few decades have a diagnostic port. On cars it is a standard 16-pin socket under the dash. The standard behind it is a common diagnostic channel, and it lets you ask the engine computer (the ECU) a few questions.

What the standard asks

What is your rpm? What is your coolant temperature? Do you have stored fault codes? What is your VIN?

Motorcycles are less tidy

Some have a standard 16-pin socket. Some, like the KTM we use, have their own small plug and need a cable. And not every bike answers the standard questions.

The data connector

A small data connector plugs into the port and translates between the bike and your phone. The one we use speaks Bluetooth LE. It talks to the bike on one side and to your phone over Bluetooth on the other. Each bike gets its own connector, so there is nothing to carry or swap.

Bluetooth LE, and why not the other kind

There are two kinds of Bluetooth, and the difference matters on an iPhone.

Bluetooth LE

Works. Low energy. Open to apps, so an app can talk to a data connector directly.

Bluetooth Classic

Will not work. On iOS it needs a special Apple certification on the accessory, so an app cannot talk to a Classic data connector at all.

That is why we use a Bluetooth LE data connector, and why a Classic one will not work with Moto.

Bikes speak different languages

There are two broad cases.

Bikes that answer

You ask for rpm and it replies. The Triumph Sprint ST answers this way, over an older wire called K-line that needs a slow handshake to start. We read live values, codes and more.

Bikes that talk all the time

The KTM 300 XC-W answers almost nothing on the standard channel, and live data gets an empty reply. But its engine computer continuously broadcasts its own data on the bike's internal network, whether anyone asks or not. We listen and decode.

On the KTM we do not ask, and we do not send anything that changes the bike. Reading the broadcast means working out what each byte means, and we check each signal against reality before we trust it. For example, we recorded the exhaust on a phone and checked the rpm against its pulse rate: a one-cylinder two-stroke fires once a revolution, and the two agreed to within a few percent.

The bikes pages list the signals we read on each bike.

Bike profiles

What a bike says and how to read it lives in a profile, one per bike. Adding a bike does not mean changing the app. If your bike has no profile, the app tries the standard way, names the bike from its VIN if it can, and tries the closest profile while it checks the values live.

The engine computer is read-only

Passive and read-only

What you decide in Moto changes the app, never the bike. The Moto app reads data and codes. It does not unlock secured ECU functions: it never attempts the seed and key security access that guards them, and it never writes to the engine computer to change tuning or maps.

Clearing codes is gated

The app shows a clear-codes button only when the bike's profile allows it, today the Triumph Sprint ST 955i, and you confirm each tap. It then reads the codes again to show what is left.

What gets recorded

When you press Record, the app keeps:

The GPS track

One point a second, each with its accuracy.

Engine data

From each bike connected during the ride.

Motion

The phone's motion data: lean angle and g forces.

Battery and codes

Battery voltage and any fault codes read.

On request, a GPX

The whole ride as a GPX file.

Recording starts and stops only when you say so. Engine stops and lost Bluetooth links inside a ride are gaps in the data, not the end of the ride.

From a ride to one record in your lifelever

  1. The bike reports its data through the diagnostic port.
  2. The data connector passes it over Bluetooth LE to your iPhone.
  3. The app records the ride: GPS, engine data, lean and g, battery.
  4. You save the ride, and it goes up in the background, if you are signed in, to your own file in the cloud.
  5. Your lifelever stores it as one ride, linked to the bike it came from, beside your sleep, workouts and money.
  6. Your own AI assistant, the one you already use, reads your file when you ask it something, and answers from your own record.

See the app for what it looks like in your hand, and the bikes for what each one gives.

Ride with Moto

Your ride and your bike, in one app.

Moto is in private beta, free while it lasts, then $5.99 a month with every lifelever app included. Beta riders get the exact tested parts list with their invite.

Join the waitlist