Free VE Table Corrections — Drop Your MSQ and a Datalog, I'll Do the Rest
Thread Starter
Junior Member
Joined: Apr 2026
Posts: 56
Total Cats: 3
Free VE Table Corrections — Drop Your MSQ and a Datalog, I'll Do the Rest
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.
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.
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.
Reply
0
0
Thread Starter
Junior Member
Joined: Apr 2026
Posts: 56
Total Cats: 3
Hey, got your log. Here's your corrected VE table attached:
Tune was lean across the cruise band; EGO was carrying ~1-4% extra fuel everywhere just to keep up. Now baked into the VE table — should run cleaner with EGO closer to 100% on next log.
This will probably take 2 more passes to dial in. I run conservative corrections on the first pass on purpose — better to creep up on it than overshoot and chase your tail. X3 Pass small change is better than throwing the kitchen sink the first round..... So drive it for a session, log again, send it over, and we'll do another round. Should be tighter every time.
One small change I'd recommend in your tune: go to Fuel Settings → Over-run Fuel cut and find "Delay EGO after fuel return" (near the bottom of that dialog). It's set to 0 — change it to 1 second. What this does is keep your EGO correction quiet for a second after fuel cut ends, while the wideband flushes out. Right now it's reading stale air and over-correcting for a moment every time you come off coast. One second fixes it. Won't change how the car drives, just makes the data cleaner for the next round of corrections.
To use the table: copy and paste it directly into your VE Table 1 in TunerStudio. Burn, drive a 15-20 (more is better) minute log mixing cruise/light boost/some pulls, and send it back when you're ready for round 2.
Let me know how it drives.
Tune was lean across the cruise band; EGO was carrying ~1-4% extra fuel everywhere just to keep up. Now baked into the VE table — should run cleaner with EGO closer to 100% on next log.
This will probably take 2 more passes to dial in. I run conservative corrections on the first pass on purpose — better to creep up on it than overshoot and chase your tail. X3 Pass small change is better than throwing the kitchen sink the first round..... So drive it for a session, log again, send it over, and we'll do another round. Should be tighter every time.
One small change I'd recommend in your tune: go to Fuel Settings → Over-run Fuel cut and find "Delay EGO after fuel return" (near the bottom of that dialog). It's set to 0 — change it to 1 second. What this does is keep your EGO correction quiet for a second after fuel cut ends, while the wideband flushes out. Right now it's reading stale air and over-correcting for a moment every time you come off coast. One second fixes it. Won't change how the car drives, just makes the data cleaner for the next round of corrections.
To use the table: copy and paste it directly into your VE Table 1 in TunerStudio. Burn, drive a 15-20 (more is better) minute log mixing cruise/light boost/some pulls, and send it back when you're ready for round 2.
Let me know how it drives.
Code:
Cell Stat EGO AFR Err Before After Change -------------------------------------------------------------- 6800 x 200 RICH Pulling 0.9% -0.68 88.5 88.2 -0.3 7000 x 200 RICH Pulling 0.9% -0.73 89.4 89.1 -0.3 3700 x 176 RICH Pulling 0.5% -0.59 76.7 76.4 -0.3 4200 x 176 RICH Pulling 0.6% -0.62 79.1 78.8 -0.3 3700 x 130 LEAN Adding 1.3% +0.04 72.1 72.2 +0.1 4700 x 130 LEAN Adding 0.7% +0.04 73.6 73.9 +0.3 3000 x 116 LEAN Adding 2.4% +1.00 66.0 66.2 +0.2 3700 x 116 LEAN Adding 0.7% +0.30 70.0 70.1 +0.1 4200 x 116 LEAN Adding 0.7% -0.02 70.5 70.8 +0.3 4700 x 116 LEAN Adding 1.1% -0.39 71.0 71.3 +0.3 2300 x 100 LEAN Adding 2.5% +0.05 58.9 59.8 +0.9 3000 x 100 LEAN Adding 2.0% +0.86 64.2 65.1 +0.9 3700 x 100 LEAN Adding 1.3% +0.34 68.8 68.9 +0.1 4200 x 100 LEAN Adding 1.1% -0.33 68.4 68.6 +0.2 4700 x 100 RICH -1.71 67.9 67.5 -0.4 1800 x 90 LEAN Adding 3.6% +0.86 55.8 56.3 +0.5 2300 x 90 LEAN Adding 1.6% +0.29 56.6 57.1 +0.5 3000 x 90 LEAN Adding 1.9% +0.49 59.7 60.4 +0.7 3700 x 90 LEAN Adding 1.9% +0.66 64.4 64.5 +0.1 4200 x 90 RICH Pulling 0.5% -1.91 65.1 64.9 -0.2 4700 x 90 RICH -2.43 65.5 64.9 -0.6 900 x 80 LEAN Adding 1.5% +1.22 51.9 52.0 +0.1 1300 x 80 LEAN Adding 0.8% +0.87 53.5 53.8 +0.3 1800 x 80 LEAN Adding 1.4% +0.67 54.7 55.1 +0.4 2300 x 80 LEAN Adding 1.5% +0.15 55.6 55.9 +0.3 3000 x 80 LEAN Adding 2.1% +0.16 58.0 58.3 +0.3 3700 x 80 LEAN Adding 4.0% +0.41 61.3 61.7 +0.4 4200 x 80 LEAN Adding 3.1% -2.42 62.8 63.3 +0.5 900 x 70 RICH Adding 0.6% +1.36 52.6 52.5 -0.1 1300 x 70 LEAN Adding 1.1% +0.61 54.4 54.7 +0.3 1800 x 70 LEAN Adding 1.9% +0.74 54.3 54.5 +0.2 2300 x 70 LEAN Adding 1.2% -0.05 54.3 54.6 +0.3 3000 x 70 LEAN Adding 1.0% +0.16 55.0 55.3 +0.3 3700 x 70 LEAN Adding 3.0% +0.38 56.9 58.1 +1.2 4200 x 70 LEAN Adding 3.0% -3.00 58.8 59.7 +0.9 1800 x 56 LEAN Adding 1.4% +0.23 52.3 52.9 +0.6 2300 x 56 LEAN Adding 1.8% -0.23 52.5 52.7 +0.2 3000 x 56 LEAN Adding 1.6% 0.00 52.3 53.1 +0.8 3700 x 56 LEAN Adding 1.4% -0.01 53.8 54.1 +0.3 4200 x 56 RICH -4.55 54.9 54.1 -0.8 900 x 46 LEAN Adding 0.5% +0.65 48.7 49.0 +0.3 1300 x 46 LEAN Adding 0.7% +0.27 50.1 50.4 +0.3 1800 x 46 LEAN Adding 1.0% +0.03 50.5 50.7 +0.2 2300 x 46 LEAN Adding 1.1% -0.03 50.3 50.6 +0.3 3000 x 46 LEAN Adding 1.1% -0.01 50.1 50.2 +0.1 3700 x 46 LEAN Adding 0.9% -0.95 50.2 50.5 +0.3 4200 x 46 LEAN Adding 1.0% -3.48 51.1 51.3 +0.2 900 x 36 LEAN Adding 0.8% +0.58 46.4 46.7 +0.3 1800 x 36 LEAN Adding 0.7% +0.30 48.4 48.7 +0.3 2300 x 36 LEAN Adding 1.1% -0.08 48.7 48.8 +0.1 3000 x 36 LEAN Adding 0.6% 0.00 47.7 48.0 +0.3 3700 x 36 LEAN Adding 1.9% -0.97 47.7 47.9 +0.2 4200 x 36 LEAN Adding 2.3% -1.55 47.2 47.9 +0.7 900 x 30 RICH Pulling 3.2% +0.44 45.7 45.2 -0.5 1300 x 30 RICH Pulling 1.8% -0.46 46.3 45.9 -0.4 1800 x 30 LEAN Adding 0.7% -0.13 47.4 47.7 +0.3 2300 x 30 LEAN Adding 0.8% -0.24 47.3 47.6 +0.3 3700 x 30 LEAN Adding 1.0% -0.98 44.8 45.1 +0.3 1300 x 20 RICH Pulling 1.7% -0.01 46.7 46.2 -0.5 1800 x 20 LEAN Adding 0.9% +0.51 46.9 47.2 +0.3
Last edited by X-Cam34; Apr 27, 2026 at 01:10 AM.
Reply
0
0
Junior Member
Joined: Mar 2024
Posts: 245
Total Cats: 18
From: Lubbock Tx
Hey, got your log. Here's your corrected VE table attached:
Tune was lean across the cruise band; EGO was carrying ~1-4% extra fuel everywhere just to keep up. Now baked into the VE table — should run cleaner with EGO closer to 100% on next log.
This will probably take 2 more passes to dial in. I run conservative corrections on the first pass on purpose — better to creep up on it than overshoot and chase your tail. X3 Pass small change is better than throwing the kitchen sink the first round..... So drive it for a session, log again, send it over, and we'll do another round. Should be tighter every time.
One small change I'd recommend in your tune: go to Fuel Settings → Over-run Fuel cut and find "Delay EGO after fuel return" (near the bottom of that dialog). It's set to 0 — change it to 1 second. What this does is keep your EGO correction quiet for a second after fuel cut ends, while the wideband flushes out. Right now it's reading stale air and over-correcting for a moment every time you come off coast. One second fixes it. Won't change how the car drives, just makes the data cleaner for the next round of corrections.
To use the table: copy and paste it directly into your VE Table 1 in TunerStudio. Burn, drive a 15-20 (more is better) minute log mixing cruise/light boost/some pulls, and send it back when you're ready for round 2.
Let me know how it drives.
Tune was lean across the cruise band; EGO was carrying ~1-4% extra fuel everywhere just to keep up. Now baked into the VE table — should run cleaner with EGO closer to 100% on next log.
This will probably take 2 more passes to dial in. I run conservative corrections on the first pass on purpose — better to creep up on it than overshoot and chase your tail. X3 Pass small change is better than throwing the kitchen sink the first round..... So drive it for a session, log again, send it over, and we'll do another round. Should be tighter every time.
One small change I'd recommend in your tune: go to Fuel Settings → Over-run Fuel cut and find "Delay EGO after fuel return" (near the bottom of that dialog). It's set to 0 — change it to 1 second. What this does is keep your EGO correction quiet for a second after fuel cut ends, while the wideband flushes out. Right now it's reading stale air and over-correcting for a moment every time you come off coast. One second fixes it. Won't change how the car drives, just makes the data cleaner for the next round of corrections.
To use the table: copy and paste it directly into your VE Table 1 in TunerStudio. Burn, drive a 15-20 (more is better) minute log mixing cruise/light boost/some pulls, and send it back when you're ready for round 2.
Let me know how it drives.
Code:
Cell Stat EGO AFR Err Before After Change -------------------------------------------------------------- 6800 x 200 RICH Pulling 0.9% -0.68 88.5 88.2 -0.3 7000 x 200 RICH Pulling 0.9% -0.73 89.4 89.1 -0.3 3700 x 176 RICH Pulling 0.5% -0.59 76.7 76.4 -0.3 4200 x 176 RICH Pulling 0.6% -0.62 79.1 78.8 -0.3 3700 x 130 LEAN Adding 1.3% +0.04 72.1 72.2 +0.1 4700 x 130 LEAN Adding 0.7% +0.04 73.6 73.9 +0.3 3000 x 116 LEAN Adding 2.4% +1.00 66.0 66.2 +0.2 3700 x 116 LEAN Adding 0.7% +0.30 70.0 70.1 +0.1 4200 x 116 LEAN Adding 0.7% -0.02 70.5 70.8 +0.3 4700 x 116 LEAN Adding 1.1% -0.39 71.0 71.3 +0.3 2300 x 100 LEAN Adding 2.5% +0.05 58.9 59.8 +0.9 3000 x 100 LEAN Adding 2.0% +0.86 64.2 65.1 +0.9 3700 x 100 LEAN Adding 1.3% +0.34 68.8 68.9 +0.1 4200 x 100 LEAN Adding 1.1% -0.33 68.4 68.6 +0.2 4700 x 100 RICH -1.71 67.9 67.5 -0.4 1800 x 90 LEAN Adding 3.6% +0.86 55.8 56.3 +0.5 2300 x 90 LEAN Adding 1.6% +0.29 56.6 57.1 +0.5 3000 x 90 LEAN Adding 1.9% +0.49 59.7 60.4 +0.7 3700 x 90 LEAN Adding 1.9% +0.66 64.4 64.5 +0.1 4200 x 90 RICH Pulling 0.5% -1.91 65.1 64.9 -0.2 4700 x 90 RICH -2.43 65.5 64.9 -0.6 900 x 80 LEAN Adding 1.5% +1.22 51.9 52.0 +0.1 1300 x 80 LEAN Adding 0.8% +0.87 53.5 53.8 +0.3 1800 x 80 LEAN Adding 1.4% +0.67 54.7 55.1 +0.4 2300 x 80 LEAN Adding 1.5% +0.15 55.6 55.9 +0.3 3000 x 80 LEAN Adding 2.1% +0.16 58.0 58.3 +0.3 3700 x 80 LEAN Adding 4.0% +0.41 61.3 61.7 +0.4 4200 x 80 LEAN Adding 3.1% -2.42 62.8 63.3 +0.5 900 x 70 RICH Adding 0.6% +1.36 52.6 52.5 -0.1 1300 x 70 LEAN Adding 1.1% +0.61 54.4 54.7 +0.3 1800 x 70 LEAN Adding 1.9% +0.74 54.3 54.5 +0.2 2300 x 70 LEAN Adding 1.2% -0.05 54.3 54.6 +0.3 3000 x 70 LEAN Adding 1.0% +0.16 55.0 55.3 +0.3 3700 x 70 LEAN Adding 3.0% +0.38 56.9 58.1 +1.2 4200 x 70 LEAN Adding 3.0% -3.00 58.8 59.7 +0.9 1800 x 56 LEAN Adding 1.4% +0.23 52.3 52.9 +0.6 2300 x 56 LEAN Adding 1.8% -0.23 52.5 52.7 +0.2 3000 x 56 LEAN Adding 1.6% 0.00 52.3 53.1 +0.8 3700 x 56 LEAN Adding 1.4% -0.01 53.8 54.1 +0.3 4200 x 56 RICH -4.55 54.9 54.1 -0.8 900 x 46 LEAN Adding 0.5% +0.65 48.7 49.0 +0.3 1300 x 46 LEAN Adding 0.7% +0.27 50.1 50.4 +0.3 1800 x 46 LEAN Adding 1.0% +0.03 50.5 50.7 +0.2 2300 x 46 LEAN Adding 1.1% -0.03 50.3 50.6 +0.3 3000 x 46 LEAN Adding 1.1% -0.01 50.1 50.2 +0.1 3700 x 46 LEAN Adding 0.9% -0.95 50.2 50.5 +0.3 4200 x 46 LEAN Adding 1.0% -3.48 51.1 51.3 +0.2 900 x 36 LEAN Adding 0.8% +0.58 46.4 46.7 +0.3 1800 x 36 LEAN Adding 0.7% +0.30 48.4 48.7 +0.3 2300 x 36 LEAN Adding 1.1% -0.08 48.7 48.8 +0.1 3000 x 36 LEAN Adding 0.6% 0.00 47.7 48.0 +0.3 3700 x 36 LEAN Adding 1.9% -0.97 47.7 47.9 +0.2 4200 x 36 LEAN Adding 2.3% -1.55 47.2 47.9 +0.7 900 x 30 RICH Pulling 3.2% +0.44 45.7 45.2 -0.5 1300 x 30 RICH Pulling 1.8% -0.46 46.3 45.9 -0.4 1800 x 30 LEAN Adding 0.7% -0.13 47.4 47.7 +0.3 2300 x 30 LEAN Adding 0.8% -0.24 47.3 47.6 +0.3 3700 x 30 LEAN Adding 1.0% -0.98 44.8 45.1 +0.3 1300 x 20 RICH Pulling 1.7% -0.01 46.7 46.2 -0.5 1800 x 20 LEAN Adding 0.9% +0.51 46.9 47.2 +0.3
Reply
0
0
Thread Starter
Junior Member
Joined: Apr 2026
Posts: 56
Total Cats: 3
The spool-up zone (MAP 70-100, RPM 2300-4200) was the leanest part of your whole table, and that's where the corrections hit hardest. New table should help with the AFR cuts.
One thing — you mentioned making changes while driving. For the next log, apply the new VE table I sent, set the EGO delay to 1 sec, then don't touch anything else during the drive. I need clean steady data — if you're tweaking mid-log the tool is chasing a moving target and the corrections come out muddy. Just drive it normally for 15-20 minutes mixing cruise, light boost, and a couple pulls, then send the log over.
If you do need to make a change mid-drive, stop the log, make your change, then start a fresh log after. Don't leave the recording running through the change.
One thing — you mentioned making changes while driving. For the next log, apply the new VE table I sent, set the EGO delay to 1 sec, then don't touch anything else during the drive. I need clean steady data — if you're tweaking mid-log the tool is chasing a moving target and the corrections come out muddy. Just drive it normally for 15-20 minutes mixing cruise, light boost, and a couple pulls, then send the log over.
If you do need to make a change mid-drive, stop the log, make your change, then start a fresh log after. Don't leave the recording running through the change.
Reply
0
0
Junior Member
Joined: Mar 2024
Posts: 245
Total Cats: 18
From: Lubbock Tx
The spool-up zone (MAP 70-100, RPM 2300-4200) was the leanest part of your whole table, and that's where the corrections hit hardest. New table should help with the AFR cuts.
One thing — you mentioned making changes while driving. For the next log, apply the new VE table I sent, set the EGO delay to 1 sec, then don't touch anything else during the drive. I need clean steady data — if you're tweaking mid-log the tool is chasing a moving target and the corrections come out muddy. Just drive it normally for 15-20 minutes mixing cruise, light boost, and a couple pulls, then send the log over.
If you do need to make a change mid-drive, stop the log, make your change, then start a fresh log after. Don't leave the recording running through the change.
One thing — you mentioned making changes while driving. For the next log, apply the new VE table I sent, set the EGO delay to 1 sec, then don't touch anything else during the drive. I need clean steady data — if you're tweaking mid-log the tool is chasing a moving target and the corrections come out muddy. Just drive it normally for 15-20 minutes mixing cruise, light boost, and a couple pulls, then send the log over.
If you do need to make a change mid-drive, stop the log, make your change, then start a fresh log after. Don't leave the recording running through the change.
Reply
0
0
Thread Starter
Junior Member
Joined: Apr 2026
Posts: 56
Total Cats: 3
Round 2........ Did this one by hand — your tune is lean dude.... Gave the car the fuel it actually needs. I do not mind if we overshoot a bit rich it is lean that I have issues with
Same protocol — burn it, drive 15-20 min mixing cruise, light boost, and a couple pulls. Don't tweak anything mid-log; if you need to make a change, stop the log, change, then start a fresh one.
Couple questions.......
If you do not mind drop your .msq, I am curious on a couple things now...
Same protocol — burn it, drive 15-20 min mixing cruise, light boost, and a couple pulls. Don't tweak anything mid-log; if you need to make a change, stop the log, change, then start a fresh one.
Couple questions.......
- How did the car run after round 1? Curious what you noticed in normal driving once that table was in — cleaner cruise?, anything feel different?
- What injectors are you running, exactly? Brand, model, flow rating. And what's your dead time set to (Injector Settings → Dead Time, or .... Want to make sure that's dialed in for what you actually have.Code:
injOpen
If you do not mind drop your .msq, I am curious on a couple things now...
Last edited by X-Cam34; Apr 27, 2026 at 10:19 PM.
Reply
0
0
Junior Member
Joined: Mar 2024
Posts: 245
Total Cats: 18
From: Lubbock Tx
Round 2........ Did this one by hand — your tune is lean dude.... Gave the car the fuel it actually needs. I do not mind if we overshoot a bit rich it is lean that I have issues with
Same protocol — burn it, drive 15-20 min mixing cruise, light boost, and a couple pulls. Don't tweak anything mid-log; if you need to make a change, stop the log, change, then start a fresh one.
Couple questions.......
If you do not mind drop your .msq, I am curious on a couple things now...
Same protocol — burn it, drive 15-20 min mixing cruise, light boost, and a couple pulls. Don't tweak anything mid-log; if you need to make a change, stop the log, change, then start a fresh one.
Couple questions.......
- How did the car run after round 1? Curious what you noticed in normal driving once that table was in — cleaner cruise?, anything feel different?
- What injectors are you running, exactly? Brand, model, flow rating. And what's your dead time set to (Injector Settings → Dead Time, or .... Want to make sure that's dialed in for what you actually have.Code:
injOpen
If you do not mind drop your .msq, I am curious on a couple things now...
1. It definitely seemed better, nothing crazy, because anything i had issues with was fixed mostly by ego anyway, but i noticed ego not going as crazy in some spots.
2. Kraken 700cc I got new, theyre bosche iirc, 700cc rated.
this is what I have for deadtimes, these dont come with deadtimes, so I just set it at what seemed to work best. I tried using a deadtime tuner on epicefi but it didnt work as well as i hoped. (most likely user error)
Other important info, i only run e85, so its sitting at about e70 right now, which is why im never super bothered by some lean fueling, obviously hitting afr cut isnt ideal though.
My accel enrich needs to be dialed in way better, ive been putting it off.
My iat sensor is not in the bay, its right after the ic in the charge pipe in front of my tire, so it doesnt heat soak as bad. Im still at work, which is when im getting these logs, so ill try and get another one tonight. Thank you so much.
Reply
0
0
Thread Starter
Junior Member
Joined: Apr 2026
Posts: 56
Total Cats: 3
Ok, good deal, I will check the .msq when I get off work tomorrow, bout to call it a night,,, But you said " It definitely seemed better" so we are headed n the right direction, looking forward to seeing the new log and your thoughts...
Reply
0
0
Junior Member
Joined: Mar 2024
Posts: 245
Total Cats: 18
From: Lubbock Tx
heres this log. Definitely noticed an improvement in ego.
Reply
0
0
Thread Starter
Junior Member
Joined: Apr 2026
Posts: 56
Total Cats: 3
Round 3 ... Same protocol — burn it, drive 15-20 mixed, send the new log when you've got it.
Found some info on your dead time — your Kraken 700cc are EV14 family, and the Finjector EV14-720 spec sheet (closest published data sheet I can verify) shows dead time at your fuel pressure (~60 psi / 4.0 bar) and 14V battery should be 0.815 ms. You've got it set to 1.200 ms. Off by roughly 0.4 ms.Sources:
to
, leave the curve alone.
That said — the dead time error is already baked into the VE table at this point. Your VE values are scaled down to compensate, EGO has converged around it, the engine fuels correctly..... Changing dead time now would lean the engine ~25-30% in the cells where dead time matters most, so the VE table would need to come back up to match. It's worth doing eventually, but doing it right now is your call. If you change it, expect needing another round or two of corrections after to clean it up.
The right procedure when you change dead time:
For this round, just run the new table and log it.
Found some info on your dead time — your Kraken 700cc are EV14 family, and the Finjector EV14-720 spec sheet (closest published data sheet I can verify) shows dead time at your fuel pressure (~60 psi / 4.0 bar) and 14V battery should be 0.815 ms. You've got it set to 1.200 ms. Off by roughly 0.4 ms.Sources:
- https://finjector.com/documents/6463...4-720_Data.pdf
- https://www.miataturbo.net/megasquir...oblems-107726/
Code:
1.200
Code:
0.815
That said — the dead time error is already baked into the VE table at this point. Your VE values are scaled down to compensate, EGO has converged around it, the engine fuels correctly..... Changing dead time now would lean the engine ~25-30% in the cells where dead time matters most, so the VE table would need to come back up to match. It's worth doing eventually, but doing it right now is your call. If you change it, expect needing another round or two of corrections after to clean it up.
The right procedure when you change dead time:
- Bump VE table by ~20% across the board first
- Then change dead time
- Drive carefully, log
- Run correction pass to clean up cell-by-cell residuals
For this round, just run the new table and log it.
Reply
0
0
Thread Starter
Junior Member
Joined: Apr 2026
Posts: 56
Total Cats: 3
Good question. Short version: it's EGO-primary instead of AFR-primary. VE Analyze and Tune Analyze Live treat wideband AFR vs target as the truth signal — mine reads what the ECU's closed-loop EGO trim is actually doing and uses that as ground truth, with AFR as fallback for open-loop conditions. EGO has already absorbed the upstream stuff (wideband bias, baro correction, dead time error, flex fuel) into one clean signal that says how much more or less fuel the engine actually needed. On top of that it's a multi-stage filter chain — fuel cut detection, accel enrichment, post-fuel-cut cooldown, RPMdot/MAPdot transients, off-throttle non-cruise, smart closed-loop detection, EGO/AFR agreement scoring — each filter found and added because it caught something real on a log. Built over 14 months across multiple setups. Defaults to 50% gain per pass so it converges over 2-3 logs without overshooting.
Reply
1
1
Your replies are oddly AI scripted with some of the usual tells. How much of this process is LLM driven, just the replies/user facing part, or are the adjustments to the map as well? Or are those scripted in a different way?
Reply
0
0
A quick scan says "highly likely written by AI". He's (if it is a person) is also quickly realizing the VE table is about 10% of a tune, there are other large issues that usually need to be addressed first.
Reply
0
0
I was noticing that as well, especially the last reply. Sounds very much like AI
Reply
0
0
Junior Member
Joined: Mar 2024
Posts: 245
Total Cats: 18
From: Lubbock Tx
you beat me to it, i was planning on adding a hidden text or prompt to see what would happen, the way its been addressing things has been odd
Reply
0
0
Reply
0
0
