Tunelyzer
Get notified
Native Holley datalog analysis

TUNELYZER

Native datalog analysis for Holley® EFI V6 and Terminator X V3. Reads .dl and .dlz files directly — open the app, get the answer. Built for tuners who want speed.

Status
Available now
Platform
Windows 10 / 11
Price
$99 launch · $129 after
Pull · Session 03
TQ
HP
PEAK · 6,820 RPM 2K 4K 6K 8K RPM
Why Tunelyzer

Datalog analysis, simplified.

Tunelyzer is built around three things — getting your runs in fast, knowing what they tell you at a glance, and catching trouble before it catches you. Every pass, every time.

01

Open the app — your run is right there

Tunelyzer reads your datalog folder. Open the profile after a pull and your latest log is already loaded — or every new log since last time, your call. Native parsing of .dl and .dlz files means no round-trip through another tool, no waiting.

Versus: hunt the file → open the viewer → wait while it renders. Every time.
02

Race-day-grade workflow

Walk back from the round, open the laptop. Latest pass already loaded — DA, weather, and tune name auto-filled. Warning rules already ran on it. Two glances and you know if the tune held.

Versus: between rounds, pen, paper, and guessing which round was which.
03

Red, yellow, or green — at a glance

Set warning rules once — "AFR under 12.5 in boost", "oil pressure below 40 over 4,000 RPM" — and every future log gets a status badge. Green means clean. Red means something needs your attention. No more checking each channel manually after every pass.

Versus: scrolling every log hoping you spot the lean spike before it spots you.
See it in action

The main window.

A real Holley pull loaded — tabs across the top, multi-axis plot on the left, live stats panel in the middle, channel picker on the right. Quick stats sit underneath. Everything you need on one screen.

Tunelyzer main window — V6 datalog loaded
Tunelyzer · main window · V6 datalog loaded
What's inside

Built for the way you tune. Every part of it.

Every feature here exists because something about the stock viewer made the job harder than it needed to be.

Tunelyzer log selector showing new and previously-loaded .dl and .dlz files with V6 and TX badges
Pass to plot

Open a profile — your runs are right there.

Open a profile and Tunelyzer lists every log in its datalog folder, newest first. Pick the one you want, or flip the auto-import flag and every new pass loads automatically. Keep a profile per scenario — race day, driveway tuning, customer cars — each with its own folder, channels, warnings, and tabs. .dlz and .dl files are treated the same — no separate unzip step, no waiting, no extra clicks.

  • Auto-import flag loads every new log when you open the profile
  • Or pick individually — every log in the folder is one click from open
  • Bulk-import filters by ECU family (V6 profile won't pull TX logs)
  • Profiles export to .tnzprof — share a vetted setup with another tuner
  • Copied a log to a new folder or renamed it? Tunelyzer recognizes it by content and re-uses the old import — no duplicates

Versus: the long way — open the viewer, find the file, wait for it to render. Every time.

Tunelyzer Configure Info Card dialog showing the field list with options to add, rename, reorder, hide, and delete fields
Log Info card

Custom fields, arranged how you like.

Track, fuel, ET, 60-ft, tune notes, knock zero, pulse modifier — every log carries fields you define. Add a field, rename it, change its type, hide it, delete it. Reorder by drag. The card is yours. Tune name auto-populates from the .dlz on import so you never type it.

  • Field types: text, numbers, dates, dropdowns
  • Defaults that auto-populate ("Fuel Type = 93" if that's your usual)
  • Mark a field tune-shared — edit on one log, every sibling with the same tune name picks it up
  • Auto-open the card on every import (one toggle in Preferences)

Versus: a single fixed notes field per log. Hope you remember what you ran last week.

Tunelyzer Current Weather dialog showing live density altitude for the user's location
Racer's killer field

Density altitude — now and on every pass you've ever recorded.

Click Current Weather for your live DA right now — handy when you're at the track and trying to decide what tune to load. The same source auto-fills temperature, humidity, barometric pressure, and DA on every log you import, looked up from the date and location of the run. Already have a year of .dlz files? Import them and Tunelyzer pulls historical weather on every one. Your archive becomes searchable by DA in one go.

  • Live DA on demand — no separate weather app at the track
  • Historical fetch on import — old .dlz files get the weather they ran in
  • Falls back to IP location if Track and Location are blank
  • Combines with the searchable archive next: "every E85 pass at 2,000+ ft DA"

Versus: type the DA in by hand from whatever weather app you trust. Every pass, every time.

Tunelyzer Search Logs dialog filtering by fuel type with a live 2-of-7 match count
Find any pass, instantly

Every E85 pass with DA over 2,000 ft.

Click the search icon next to the Log Info button and the Search logs dialog opens. Fill any fields you care about — Tune, Fuel Type, Tune Changes, Notes — plus min/max ranges on Air Temp, Humidity, Barometer, Wind, and Density Altitude. Results update live as you type, with a match counter at the bottom ("2 of 7 logs match"). Double-click any result, or hit Open, and you're in that log.

  • Text fields are case-insensitive substring — type e85 to match anything containing it
  • Numeric fields take min/max ranges — 1500…2500 ft DA gives you every altitude-y pass
  • Profile-scoped — searches stay inside the active car's logs
  • Combines freely: Fuel = e85 + DA min 2000 + Notes contains colder plugs in a single search

Versus: scroll a flat list, hope the filename is descriptive enough to find what you're after.

Tunelyzer stats panel showing the warnings strip and Quick Stats dashboard side by side
Stats panel

Green or red, peak or low — the two-second pass check.

The stats panel pins the two things you want first after a pass. Warning rules fire green or red against conditions you've set ("AFR below 12.5 in boost", "oil pressure under 40 over 4,000 RPM"). Right next door, Quick Stats shows the headline numbers — peak RPM, max boost, lowest AFR, min oil pressure — updated as you pan and zoom. Two seconds and you know if the pass went well.

  • Warnings: critical (red) or warning (yellow) severity; plain-talk rule wizard — no boolean logic
  • Click a red warning to jump straight to the worst sample in the run
  • Quick Stats: any channel + aggregation (max, min, average, first, last, count-above-threshold)
  • Both work on math channels — pin peak Horsepower or warn on AFR Error
  • Rules export to .tnzwarn — share with another tuner; per-profile so each car has its own set

Versus: read every curve and scroll every log, every pass, every time.

Tunelyzer comparing two runs with overlay showing before-and-after tune change
Before / after

See what your tune change actually did.

Lay last week's pass on top of today's. Pick overlay (dashed lines, same plot) for matched scales, or split (pane underneath, shared X-axis) when the curves are too crowded to read on one. Line up at launch uses your profile's auto-zero trigger — one click and both runs start from the same instant. Time-shift manually if you need finer alignment.

  • Works on math channels too — overlay Horsepower-A vs Horsepower-B the same way
  • Synced cursor across both runs as you scrub
  • Auto-zero alignment for drag passes (zero out at launch input)

Versus: two windows side by side, eyeballing the difference by hand.

Tunelyzer math channel editor showing a Horsepower formula built from RPM and Torque
Build your own channels

Horsepower, Slip, AFR Error — any number you can write a formula for.

Wrap a channel name in brackets and use the usual math: Horsepower = [RPM] * [Torque Estimate] / 5252. Once saved, your math channel works like a real one — plot it, stat it, warn against it. Math channels can reference other math channels, so you can stack simple formulas into fancy ones. Hit Test to run it on the open log before you save so you can sanity-check the numbers.

  • Built-ins included: Horsepower, Torque, Converter Slip, AFR Error
  • Functions: abs, min, max, sqrt, log, clamp
  • Export to .tnzmath files — share a custom formula with another tuner

Versus: no built-in way to compute it. Eyeball peak values, run the math in your head, or skip it.

Tunelyzer plot tabs strip showing 60 Foot, Suspension, Boost, Fueling, and Retards tabs
Built for the way you look at logs

One tab per question. Multiple panes per tab.

A 60 Foot tab zoomed to launch. A Suspension tab with the shock and ride-height channels. A Boost tab with RPM, TPS, MAP, and knock stacked in their own panes — shared time axis, synced cursor. Drop a note ("traction loss at 0.8s") in one tab and it shows in all of them. The note follows the moment in the run, not the view.

  • Tabs save with the profile — open the car next month and your views are back the way you left them
  • Right-click a tab to rename, clone, split, or remove
  • Split-pane: stack 2–4 panes inside one tab for a complex view

Versus: one view, switched between channels by hand, every time you reopen.

Compatibility

Works with what you already run.

Tunelyzer reads native Holley `.dl` and `.dlz` files from the V6 and Terminator X V3 ECU families. Designed to run on the laptops you already use at the track or in the shop — including older hardware.

Holley EFI V6
HP · Dominator · NA HP
Terminator X V3
Terminator X · Terminator X Max
Windows 10 / 11
x64 · 1809 or later
Older shop laptops
Pre-AVX2 CPUs supported
.dl and .dlz formats
Native — no Holley install needed
User-named I/O channels
Custom inputs read with their tune names
What you get

No subscription. No telemetry. No surprises.

30-day refund

No questions, no forms. Just email me directly.

Free v1.x updates

Every fix and feature in this major version is yours. Buy once, own this version.

Single-machine license

One activation per license. Changing shop laptops? Email me and I'll move it. Free.

Runs offline

One activation ping on first launch. After that, no telemetry, no analytics, no usage tracking.

Pricing

One price. Own it.

Introductory price: $99. Regular price $129 once the introductory window closes. One-time payment, single machine, no subscription. 30-day refund if it's not for you.

Introductory price
$99 $129
USD · one-time payment · regular price $129
[email protected]

Online ordering opens shortly.
Email [email protected] — click the button if you have a mail app set up, or copy the address — and you'll get a note the day sales go live.

Questions

Things people ask before buying.

Which ECUs does Tunelyzer support today?

Holley EFI V6 (Dominator family) and Terminator X V3 datalogs (.dl and .dlz). Sniper support is on the roadmap — email me your files if you'd like it prioritized.

Will Windows warn me when I install it?

Probably yes today. Tunelyzer isn't yet code-signed, so SmartScreen may show "Windows protected your PC" on first run — click More info → Run anyway. A signed build is coming; the same license activates either version.

Can I install on more than one computer?

One license = one machine at a time. If you change shop laptops, email me and I'll move the activation. No charge.

How do updates work?

All v1.x updates are free for life — emailed to license holders. v2.0, if it ever happens, will be a paid upgrade with a meaningful discount for existing customers.

What's the refund policy?

30 days, no questions asked. Just email [email protected] and you'll have your money back the same day.

Does Tunelyzer phone home?

License activation needs an internet connection once on first launch to verify your key. After that, the app runs offline. No telemetry, no analytics, no usage tracking.

Mac or Linux version?

Windows 10 / 11 only at launch. The Holley tuning world is overwhelmingly Windows, but if enough demand shows up, Mac and Linux could follow. Email me if a port matters to you.

I'm just starting to tune — is this for me?

If you open Holley datalogs and want a faster, clearer view of them, yes. If you don't yet collect logs, get familiar with the standard tooling first and come back later.