Change-log reading for successful living.

 

Is there any way to make TunerStudio produce a difference report after a VEALive session?

What I'd like is a table with the same X/Y scaling as the VE table, but with the cells showing me the amount of change (positive or negative) that were done in each cell over the course of that particular session. It already has the data (you can see it by hovering over each cell in the VE table) but I can't seem to find a way to export it all as a single chunk.

 

You can make a spreadsheet to do it in about 5 minutes.

 

By first doing an export of the VE table prior to tuning, and then doing another export afterwards, and then merging then together into a single spreadsheet and creating a third table to represent the difference between them.

Yeah, I get that. I was just hoping for a one-button solution that I could use while still sitting in the car before hitting "burn" and shutting the engine off, so I could, at a glance, get a quick idea of what VEAL accomplished on that trip and whether any of it jumps out at me as being particularly odd.

 

Exporting? I was just gonna say copy paste. Unless Tuner studio and MLV are some of those unreasonable programs that dont lets you copy and/or paste within them.

 

joe are you using incorporate AFR?

 

What would I copy from? At present, there is no single screen which displays the difference.

Or did you mean copy and paste the VE table twice, as opposed to exporting it twice? Because that would mean I'd have to do copy-and-paste operations into a spreadsheet while balancing my laptop at a really odd angle between my stomach and the steering wheel and struggling to read the display while in full sunlight. And that would be less non-annoying than doing two exports.

 

Welcome to tuning without an auto tune feature?

 

Which answer would be most likely to make you say "Oh, good" and not ask me about it again?

 

Haha.

Yeah, that would kind of be a step backwards to the days before TunerStudio, when we used MLV to do it all.

Tunerstudio clearly has the information I want already in memory, and it shows it to me one cell at a time when I hover. I was hoping maybe there was some function I had overlooked to make it dump all this data into a table in one easy step.

 

i dunno.

I'm going to suggest using it. I play on retuning with it.

 

Go ask Phil at Msextra - shouldn't be too hard for him to implement.

 

Unless you plan on changing your AFR targets frequently, I don't really see the point to it. I'd have to completely rebuild my VE table from scratch in order to turn it on, and I don't feel like wasting time to do that, since my AFR targets are what they are. Once I have the VE table really dialed in, my plan is to remove the wideband altogether and run on the narrowband only. (This is an emissions thing. A narrowband sensor gives me the greatest precision in seeking stoich- no possibility of drift or miscalibration.)

 

Hey Joe,

I just opened a thread at msextra.com about the total change table:

Megasquirt MSEXTRA / MS3EFI • VEAL total change table possible? (View topic)

 

Good call, that would be handy.

 

but it's easier to just chat with the developers directly

 

For those of you only going down to 20kPa, what does your bottom line look like. I'm still chasing this issue of an annoying bog at low load while cruising. I've tried retuning my ve table, smoothing timing, adjusting/verifying overrun settings, etc. and nothing has seemed to fix it yet. I'm on the mspnp though, which doesn't drop below 20kPa...

 

what do you mean by "bog"? sounds like you need to tune enrichments.
the only time you'll be below 20kPa is engine braking.

 

I've got another thread in engine performance, so I'll try not to sideline discussion here too much. Played with enrichments a lot, but afrs trend to 12 and below while cruising or partial throttle with 15 or less inhg vacuum, and the engine gives a chug. Then it may recover and be perfectly fine for miles, then another partial throttle engine chug comes along.

Relevancy to this thread is perhaps the bottom line should be significantly leaner? I'm kind of at a loss chasing it down.

 

Couple of things:

1. You can fill in the MAP and RPM values for your table if you don't like the MSPNP defaults. You're not stuck with what you start with.

2. When tuning that area, it's important to turn off Overrun Cutoff. If you don't, then both VEA and VEAL will recognize the Overrun Cutoff and not bother making VE adjustments.