About: what it does and does not do

What you get

Tools for reading the rides, charges and battery of your Zero

Ride & charging analytics

Every ride and charge on one timeline, with interactive SOC, voltage, temperature and speed charts you can drill into session by session.

Three capacity figures kept apart: the badge on the pack, what a pack like it gives when new, and what yours gives now, estimated from your own charges. Health is graded against the second and withheld until enough qualifying charges exist to mean anything.

Charging insights

Full charge curves, and whether one of your chargers habitually stops short while another finishes. With only one charger it stays quiet, because there is nothing to compare against.

Charging costs

Flat or time-of-use tariffs turned into cost per session, per period, per charger and per kilometre.

Trips & routes

Rides grouped back into the journey you remember taking, with total climb summed over the legs that recorded altitude. The route comes from a recording you made, because the bike has no GPS of its own.

Revocable share links

Publish one trip or a whole bike recap at a link anyone can open without an account. Telemetry, faults, raw log lines and charge stops are off until you switch them on, and a published link can only ever be narrowed.

Fleet dashboard

All your bikes in one view: account-wide stats, costs and battery health, with an AI verdict that is marked stale when new logs arrive.

AI insights

Per-ride and per-trip analysis, a verdict for a window you choose, and a per-bike chat that can quote the official manual for your model. Uploading a log runs one health pass automatically; everything else runs only when you ask.

Battery catalog & setup

Set your actual pack from our catalog of Zero Z-Force batteries. That includes a pack swap your logs cannot show, because many logs carry no pack serial at all.

Telemetry export

CSV, a printable PDF, or everything from one upload as a ZIP. Garmin FIT too, positionless because the bike logs no position. GPX gives you back your own track with the bike's speed, power and temperature written into it.

Tools without an account

Read a .bin as plain text in your own browser with nothing uploaded, work out a range figure, or browse the model and battery catalogs. No sign-up for any of it.

Your units

Metric, imperial or UK, chosen once and followed everywhere on screen. Everything is stored metric and converted for display, so switching changes nothing underneath.

No sign-up needed

Without an account

These need no account, no email address and no upload. There is also a live status page and a changelog you can read before deciding anything.

Decode a log in your browser

Drop in a .bin and read it as plain text, then download the .txt. It runs in your own tab: the file never leaves your computer, and there is nothing for us to store.

Range calculator

Pick a model year, a speed, a load and a gradient and get a range band. The whole setup is kept in the URL, so you can send it to someone else.

Model catalog and comparison

Spec sheets read out of the official manuals, with a long-form owner guide for every model in the catalog and a side-by-side comparison that is kept in the URL.

Battery catalog

The Z-Force packs we have catalogued: capacity, construction, which bikes take each one, and when it was current. Zero has never published the cathode chemistry; the page says so and does not guess one.

Learn

Guides written from Zero’s own manuals and from the log files themselves: fastener torques with the document and page behind each row, the 12 V system, thermal limits, drive-belt tension and the Gen3 record format.

The demo

One click opens a read-only account with two real, anonymised bikes. The account refuses every write and the AI is switched off, so nothing you do there can change anything.

How it works

From upload to insights in minutes

1

Upload

A .bin, a console capture, or a ride you recorded on your phone

2

Parse

Rides, charges and telemetry pulled out, and a file that looks truncated flagged as suspect

3

Match

Deduplicated across overlapping files, rides grouped into trips, and a phone recording matched to the ride its timestamps fit

4

Analyze

Deterministic rules first, then AI on top of them

Supported platform

Built for the Z-Force platform

Every Zero on the Z-Force platform carries two computers, the MBB and the BMS, and the diagnostic logs they write are what this tool reads. The MBB writes a riding snapshot roughly every 51 seconds, so a short event can fall between two samples. How much the two boards record differs by generation: a Gen3 MBB logs no current at all, so anything derived from current is absent there rather than zero. Gen3 decoding is our own reverse engineering, with no documentation from Zero. Neither board records position. The bike has no GPS receiver, so a route exists only where you supplied a recording.

MBB (Main Bike Board)

The bike's main computer. It logs motor and controller temperatures, throttle, speed, odometer and ride events into the MBB .bin file.

BMS (Battery Management System)

The pack's own computer. It logs cell voltages, state of charge, current, pack temperature and charge/balance cycles into the BMS .bin file.

Models we cover

The Z-Force line, all running 28-series “ZF” packs: the modular FX / FXS / FXE, the monolith S / DS / SR / DSR, and the Gen3 SR/F, SR/S and DSR/X. Covered means we decode what these bikes write. Not every model gives up the same amount, and the oldest ones are the least evidenced.

Browse the battery catalog

Out of scope (for now)

Zero's new urban line (the LS1 scooter and the XE / XB) is a separate, lower-cost platform with small removable modules and its own electronics. It doesn't produce the MBB/BMS logs this tool parses, and its batteries aren't Z-Force “ZF” packs, so it isn't covered here yet.

Publishing

Sharing, and what stays private

Nothing here is published until you publish it.

What you can publish

A trip or a whole bike recap can go out at a link anyone can open without an account. You choose what it carries: telemetry, a fault summary, raw log lines with the identifiers stripped out of them, charge stops. Route ends can be trimmed so a published map does not start at your front door, and the GPX a reader downloads is built from the same trimmed points, so the file cannot contain a metre the page withholds. Photographs are re-encoded before publishing, so no camera data, timestamp or coordinates survive in the file itself.

What to know before you share

Telemetry, faults, raw log lines and charge stops are all off until you switch them on. A link you have already sent out can be narrowed but never widened, so tightening it does not mean revoking it and losing every reader. Revoking is a hard delete and the address stops working at once, though an image URL already handed out can keep working for up to half an hour. A public rider page carries at most three trips, because a trim radius plus three departure points is enough to work out where you live. A published map never grows either. A ride that had no route when you shared the trip never gains one on the link, and if you later attach a phone recording to a ride or replace its route, the link hides that ride’s route instead of redrawing it (the whole map, if that ride held the trip’s first or last point). To publish the new route, share the trip again.

What we do with your logs

Where they go, what runs on them, and what we do not do

Built to stay usable

Queries are time-bounded and cached so a long history stays workable. The battery and fleet pages are the heaviest and take a moment on a big account.

Time-series storage

The database is optimized for time-series data, so queries stay fast across millions of log entries.

What the AI is given

Your own logs, what you declared about the bike, and any note you wrote on a ride. Deterministic rules run first and, on the verdict for a window you choose, set a ceiling the model cannot argue past. Uploading a log runs one health pass automatically, which spends from your metered monthly allowance and sends that log to the model provider; every other AI feature runs only when you ask. Logs go to the provider as they are, and we do not strip the VIN out of them.

Security

Connections are encrypted, and nothing is public until you publish it. You can see every device signed into your account and sign any one of them out remotely. Deleting a file removes the rides and charges nothing else sourced, and a preview shows exactly what will go before you confirm.

What to expect

What this tool gives you, and where it stops

What you can expect

Interactive charts for every ride and charge
Usable pack capacity and state of health estimated from your own charges, plus cell-balance trends where the logs carry per-cell data
Charging cost breakdowns by tariff, charger and km, only as accurate as the charge energy underneath them
Whether one of your chargers habitually stops short while another finishes (once you have more than one)
A multi-bike fleet dashboard with AI verdicts
Battery pack identification where the log carries a serial, and manual setup for the many that do not
Error-code explanations and anomaly flags
Trips grouped from your rides, with the route if you recorded one
Revocable public links for one trip or a bike recap
A per-bike AI chat that can quote the official manual for your model
CSV, Garmin FIT, PDF and whole-upload ZIP export, plus GPX where you supplied the track
Your units on screen: metric, imperial or UK
A log decoded in your own browser, with nothing uploaded
A file that looks truncated flagged as suspect

What this is not

Official Zero Motorcycles support
A warranty or guarantee of accuracy
A replacement for professional diagnosis
Affiliated with Zero Motorcycles Inc.
A definitive mechanical diagnosis
Advice to modify your motorcycle
A substitute for dealer service
Coverage of the new LS1 / XE / XB platform
Live log reading: a log is read after the fact, once you upload it
A source of GPS: the bike carries no receiver, so no route unless you recorded one
A continuous recording: the MBB writes a riding snapshot roughly every 51 seconds
Documentation from Zero: Gen3 decoding is our own reverse engineering
A state of health from a single charge: the figure is withheld until there is enough evidence
Private from the model provider: an uploaded log is analysed automatically, VIN and all
A complete history: a parked bike overwrites its own buffer, so a log holds what survived

Important disclaimer

Zero Logs Analyzer is a community tool, built by a Zero owner for other owners. We try to be accurate, but for official diagnostics, warranty claims or safety-related concerns, always consult an authorized Zero Motorcycles dealer. Use this tool as a supplement to professional service, not a replacement for it.

Illustration of the author on his Zero FXS

Who built this

This site started with one motorcycle: a Zero FXS that lost a battery module and came back from a summer at the dealership worse than it went in. Reading its logs turned into this tool.

Read the story

Ready to analyze your logs?

Other Zero owners are already reading their own logs here. You can also read what changed in each release before you sign up for anything, or support the project if you already use it.

Create Free Account Read Privacy Policy

Zero Motorcycle diagnostics from your own logs