VE Table Tuning — I Need 2 Things From You.
I've built a tool that analyzes your MegaSquirt datalog and tells you exactly what your VE table should be — cell by cell, with confidence ratings and full diagnostics.
Step 1: Extract your tune info (30 seconds)
Go here: MSQ VE Extractor
Drop your .msq file on the page. That's it. It pulls everything I need automatically:
Click Download Summary and upload that .txt file to your post.
Your tune never leaves your computer. The tool runs 100% in your browser — nothing gets uploaded to any server. Open the page, drop the file, done.
Step 2: Upload a datalog
Record a datalog in TunerStudio while driving. Export it as .csv from MegaLogViewer (File → Export → CSV). Upload the .csv to your post.
What to log:
Requirements:
That's it. Two files:
No screenshots. No copy-paste from TunerStudio tables. No guessing what your breakpoints are.
What you get back:
A corrected VE table you can paste directly into TunerStudio, plus a full diagnostic report showing:
The tool filters out fuel cut frames, accel enrichment, post-fuel-cut wideband lag, transient data, warmup enrichment, and sensor glitches before calculating anything. What's left is clean steady-state data that actually represents your engine's fueling needs.
Results are real. On a 306ci SBF (X303 cam, MegaSquirt PNP2) I tuned with this tool, three log-and-correct passes reduced the average wideband offset from +0.23 AFR to +0.06 AFR — a 74% reduction in fueling error across the entire table. GOOD cells nearly doubled each pass. The tune converges.
Scope — read this:
I am correcting your VE table only. I'm not adjusting AFR targets, timing, idle, boost, injector sizing, or anything else. If your AFR targets are wrong, that's on you. This tool makes your engine hit whatever targets you already have set. That's it.
Questions about the process — ask away.
Questions about spark tables or why your car won't start — not here.
I've built a tool that analyzes your MegaSquirt datalog and tells you exactly what your VE table should be — cell by cell, with confidence ratings and full diagnostics.
Step 1: Extract your tune info (30 seconds)
Go here: MSQ VE Extractor
Drop your .msq file on the page. That's it. It pulls everything I need automatically:
- VE table (flipped and formatted, ready to analyze)
- RPM and MAP breakpoints
- Injector dead time and battery voltage correction
- EGO authority and closed-loop settings
- DFCO settings
- Accel enrichment configuration
- Warmup enrichment curve
- Rev limiter settings
Click Download Summary and upload that .txt file to your post.
Your tune never leaves your computer. The tool runs 100% in your browser — nothing gets uploaded to any server. Open the page, drop the file, done.
Step 2: Upload a datalog
Record a datalog in TunerStudio while driving. Export it as .csv from MegaLogViewer (File → Export → CSV). Upload the .csv to your post.
What to log:
- Idle for 30-60 seconds (warmed up, 160°F+ coolant)
- Normal city driving with moderate acceleration
- Highway cruise at a few different speeds
- A few WOT pulls if you're comfortable (2nd or 3rd gear, safe location)
- Some deceleration / coast down
Requirements:
- Engine fully warmed up before logging (CLT 160°F+)
- Wideband O2 required — narrowband will not work
- 10-15 minutes of driving is plenty, longer is better
- More driving conditions = better cell coverage = better results
That's it. Two files:
- The .txt summary from the MSQ Extractor
- Your datalog exported as .csv
No screenshots. No copy-paste from TunerStudio tables. No guessing what your breakpoints are.
What you get back:
A corrected VE table you can paste directly into TunerStudio, plus a full diagnostic report showing:
- Every cell that was corrected and by how much
- Whether the correction was EGO-driven (primary) or AFR-based (fallback)
- Confidence level per cell based on sample count and data quality
- Cells that need more driving data for better coverage
- EGO clamp report — cells where your EGO authority ceiling is limiting corrections
The tool filters out fuel cut frames, accel enrichment, post-fuel-cut wideband lag, transient data, warmup enrichment, and sensor glitches before calculating anything. What's left is clean steady-state data that actually represents your engine's fueling needs.
Results are real. On a 306ci SBF (X303 cam, MegaSquirt PNP2) I tuned with this tool, three log-and-correct passes reduced the average wideband offset from +0.23 AFR to +0.06 AFR — a 74% reduction in fueling error across the entire table. GOOD cells nearly doubled each pass. The tune converges.
Scope — read this:
I am correcting your VE table only. I'm not adjusting AFR targets, timing, idle, boost, injector sizing, or anything else. If your AFR targets are wrong, that's on you. This tool makes your engine hit whatever targets you already have set. That's it.
Questions about the process — ask away.
Questions about spark tables or why your car won't start — not here.
