Understand Your Electric Ride
Zero Logs Analyzer reads what your bike actually recorded — the .bin files you pulled off it, a serial-console capture, or a ride you recorded on your phone — and turns them into an estimate of what your pack holds now, ride and charging analytics, charging costs, trips you can keep or publish, and a multi-bike fleet view, with AI on top.
What You Get
A full toolkit for understanding every ride, charge and cell of your Zero Motorcycle
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.
Without an account
Some of this needs no sign-up, no upload and no email address. There is also a live status page and a changelog you can read before deciding anything.
How It Works
From upload to insights in minutes
Upload
A .bin, a console capture, or a ride you recorded on your phone
Parse
Rides, charges and telemetry pulled out — a file that looks truncated is flagged as suspect, not quietly shown as less
Match
Deduplicated across overlapping files, rides grouped into trips, and a phone recording matched to the ride its timestamps fit
Analyze
Deterministic rules first, then AI on top of them
Built for the Z-Force ecosystem
Every Zero on the Z-Force platform carries two computers that write the diagnostic logs we read — the MBB and the BMS. That binary telemetry is the entire reason this tool exists. It is also worth knowing what it is. The MBB writes a riding snapshot roughly every 51 seconds rather than continuously, so a short event can fall between two samples. How much the two boards give up differs by generation: a Gen3 MBB logs no current at all, so anything derived from current is absent there rather than zero, and Gen3 decoding is our own reverse engineering rather than something Zero published. 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 brain. Logs motor and controller temperatures, throttle, speed, odometer and ride events into the MBB .bin file — the story of how you ride.
BMS — Battery Management System
The pack's guardian. Logs cell voltages, state of charge, current, pack temperature and charge/balance cycles into the BMS .bin file — the story of your battery.
Models we cover
The Z-Force line — the modular FX / FXS / FXE, the monolith S / DS / SR / DSR, and the Gen3 SR/F, SR/S and DSR/X — all running 28-series “ZF” packs. Covered means we decode what these bikes write, not that every model gives up the same amount: the oldest ones are the least evidenced.
Browse the battery catalogOut of scope (for now)
Zero's new affordable urban line — the LS1 scooter and the XE / XB — is a different, 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.
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 — though the battery and fleet pages are the heaviest and take a moment on a big account.
Time-Series Optimized
Database optimized for time-series data, enabling fast queries 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 windowed verdict, 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 — we do not strip the VIN out of them.
Security First
Encrypted connections, and nothing published unless 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 — only 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, not quietly shown as less data
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
- A live tracker — it reads logs after the fact, not in real time
- 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 frozen publication — a shared ride with no map can gain one if you attach a recording later
- 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 created by enthusiasts for enthusiasts. While we strive for accuracy, always consult with an authorized Zero Motorcycles dealer for official diagnostics, warranty claims, or safety-related concerns. Use this tool as a supplement to, not a replacement for, professional service.
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.