TorqueGirl / Data tools / V3

Power, recorded.
Now make sense of it.

OBD2 LOG ANALYZER

THE SIGNAL IS THE STORY.

Understand your log. Inspect a moment. Follow the relationship between sensors.

Recorded data and transparent observations. No automated diagnosis.
01 / IMPORT

Every drive tells a story.

Bring your recorded data. Explore what the sensors actually saw.

CSV / TSV · up to 25 MiB, 250,000 records, 2 million cells · comma, semicolon or tab

◉ Your log stays in memory in this browser. Only mapping templates and notebook notes you explicitly save persist locally. Raw logs and the analysis session are never saved or restored. Nothing is uploaded. Leaving or reloading clears the logs; returning starts a new analysis.

Start with a file or demo. The demo lets you practice without a vehicle log.

How to use this analyzer
  1. Choose a file or demo. Keep your original export as a backup.
  2. Check delimiter, time and PID mapping. Confirm column separation, elapsed duration, signal identity, bank and units against your source.
  3. Accept with Analyze log. Apply corrections with Update preview first.
  4. Inspect data quality. Review rejected rows, missing values, gaps and sample spacing before interpreting shapes.
  5. Select useful signals. Start with two or three that answer your question, plus operating context.
  6. Inspect the timeline. Tap or drag a chart, use its arrow keys, or move Log position. What happened here shows readings and their source times.
  7. Select a region or driving phase. Zoom for a closer view; choose Phase region A below for region statistics and Inspect this phase in Run A.
  8. Optional: compare Run B. Review its mapping and quality, select regions, then check the operating-condition match before What changed.
  9. Optional: explore relationships. Choose signals and a pairing tolerance for the selected phase. Correlation alone cannot establish a cause.
  10. Record an observation and next test. Use the local notebook below: capture evidence, review it, then save intentionally. Include the region, signals, units, conditions, timing limits and an alternative explanation.

Find patterns first. Diagnose second. Leaving or reloading clears the in-memory logs; returning starts a new analysis.

02 / UNDERSTAND

Trust the timeline.

See missing samples, recording gaps and uncertain units before reading a chart.

03 / INSPECT

What happened here?

Tap a moment to see synchronized readings, their source times and how old they are.

04 / EXPLORE

Follow the relationships.

Replay real elapsed time. Compare RPM, throttle and the signals your file contains.

07 / OBSERVATION + RETEST NOTEBOOK

Keep the observation. Plan the retest.

Find patterns first. Diagnose second. Record what the data supports, another possible explanation and a safe next test. Every field is optional; no vehicle details are required.

Browser-local notes only, on this origin in this browser. Nothing is sent over the network. Raw logs, source rows, traces and the analysis session are never saved or restored. Browser data clearing or private browsing may lose notes. JSON backups are user-controlled local files and may contain private identifiers or observations; store and share them carefully. Share Tool shares only the public tool URL.

Checking browser storage…

New observation

No unsaved changes.

Capture current analysis (optional)

Choose signals in Build your view above. Phase capture includes those Run A signals and matching Run B signals (up to 16 combined), current phase statistics and the current comparison if available. Timeline capture includes the visible Run A time bounds and signals, without phase statistics. Review run labels; filenames are not copied automatically.

Analyze a log to capture evidence, or write a manual note below.

Observation details - all optional
Selected region (optional, elapsed seconds)
Selected signals (optional, maximum 16)

Saved observations (0)

At most 100 records and 512,000 UTF-8 bytes per notebook; each record at most 24,000 bytes. Backups contain notes and compact evidence only.

Import a notebook backup

Validation and preview happen before any write. Merge keeps local versions of conflicting IDs. Replacement removes saved notes only after confirmation. Your current form is kept.

Replace saved notebook?

0 saved notes will be removed. This cannot be undone without your own backup. Your current form stays in memory.

Data first. Context always.

Use a CSV or TSV with one header row and one row per sample. Time (s), Time (ms), ISO date/time and HH:MM:SS are supported. Put units in parentheses or brackets. Exporter recognition is based on header conventions; it does not validate a scanner, app or every export variant. Proprietary recordings are not supported.

New here? Follow the first-use guide above, or open the local observation notebook to record a question and next test without a log. Save notes explicitly and download a backup; raw logs and sessions are never saved or restored.

Need a usable file? How to record and export OBD2 logs

How to analyze OBD2 live data and logsScanner versus code reader

What an OBD2 scanner tells youUnderstanding diagnostic codes