Joe Perez

iTrader: (8)

Am I the only one who has found it necessary to add some range to the bottom of the VE table? It seems as though nearly every other VE table I've seen posted had 20 kPa as the bottom row.




Don't mind the exact values in the bottom three rows- they were only just created today and are still very rough. But I'm already seeing a massive improvement in mixture stability. Used to be that operating down in this range would drive the gEGO into weird extremes which it would then have to wind out of as soon as I got on the throttle. Lots of tip-in leanness as a result. This way, I can have valid cells all the way to the lowest possible operating value, with the result that gEGO can remain in a fairly neutral position at all times.

"Yes," I can hear you say, "but you're sacrificing resolution at the top end."

True, but it really doesn't matter. Sure this particular car is N/A, but I've left room enough for boost. The upper rows are blacked oput because they're untuned and contain completely bogus data right now, but I could easily re-scale and tune them to accommodate any reasonable amount of boost.

Unlike the region from 15-30 kPa, the rest of the table is pretty damned linear in the MAP axis. You could go all the way from 100 kPa to 250 kPa with only three or four rows and just let the ECU interpolate. Back when we were all using 8x8 tables, it wasn't the top end that was a problem, it was the bottom. (Hell, the old Link ECUs only had six MAP rows.) So I'm not sure why more people are not taking advantage of the extra resolution down in the area where it can do the most good.

NiklasFalk

iTrader: (1)

Just to ask ignorant questions (the autotuning sessions I make is less than scientific to say the least):
Is there any way to analyze the percentage of cell usage while autotuning, to figure out where you would benefit from extra resolution (and then analyze the linearity of the table afterwards)?

Since I don't tune for a DD and don't tune on track (then there is a number of other tings to concentrate on) I feel that i spend very little time in the 40-70 kpa range.
There is the color map for the cell changes in AutoTune, but is there a cell occupancy frequency view?
To really embarrass myself, it was close to two years since I had the MS up and running (the spare engine have been running on a Mazda ECU), so Autotune might have developed a lot.

But there are maybe enough rows available to not care about it.

Have you performed the same analysis on the rpm range?

There is probably more than one statistical method for finding nonlinear data (outliers etc), but I choose to not google it now.

Zaphod

Hi Joe,

you can even extend the VEtable more to your needs be simply using table switching depending on kPa. You use VEtable 1 and Vetable3 then and get 16x32 resolution...

When using Autotune you have to start tuning on both tables, but apart from that it works fine...

damir130

Its not the usage that matters, its the volatitility within a particular cell.

What we used to do was waste an evening running through the entire rev range on a dyno with 100rpm increments and map the VE curve. Youth and free access to dyno time will do that to you.

What you could do is just shift all the rpm setpoints by a certain increment and then autotune again, keeping in mind which area's were adjusted most. You can repeat that a couple of times.

The underlying idea of it all is that there are several VE influencing events going on in an engine. The biggest one is the relationship between rpm, head-flow and cams. Beside that there are several harmonics going on from runners manifolds etc. As the big VE influencer becomes smaller in extent, the harmonics start to have a bigger relative influence. So at lower rpms and VE, a harmonic might cause jumps of up to 50%. At higher VE and RPM, the same harmonic might be just a 0.5% delta to the total VE.

NiklasFalk

iTrader: (1)

As usual I fail in describing my thoughts.
(for me) To be able to figure out where in the table I can find the non linear areas it would help if I could see where in the table I've been (i.e the autotune have some confidence).
If the area is "not linear" it might benefit from "zooming in" and autotune that area some more.

Oh, well a linear table is most probably good enough for me (and when I get the trottles on there the MAP will not be that important anyway).
If it's not I have to figure out it for myself, noone run an engine identical to mine anyway.

DIYAutoTune

This is pretty awesome. I have a different EMS on my rx7, but i still throw a lot of resolution down in the bottom end of the map. Helps out a lot.

Ben

iTrader: (33)

Joe,
Have you seen the idle specific VE table under Startup/Idle > Idle VE Settings?

Also to note, I think we're seeing lower absolute pressure readings with the newer ECU's. Engines are running more efficiently due to the combination of sequential fuel, more precise injection event angle, more precise injection event duration, map sample windowing, and increased spark timing accuracy.

Braineack

iTrader: (62)

I dont see the need for many boosted rows, mine stops at 20kPa, because I dunno, that's where I set it up. But I barely ever pull more than 18-15kPa in the heaviest of vacuum pulls, so there's no fueling going on then.

But I will say, that 20kPa row always seems to be victim of odd VEAL tuning when in cruise, so maybe it would benefit from at least another row below it to help. It's been a while since I lasted tuned, but I remember it always wanting to pull fuel from that row and then leaving me with a lean condition, so I've always used a kPA filter on VEAL to never allow it to tune under 35kPa or something like that.

y8s

iTrader: (8)

y8s has been using the 10kPa table row since before it was cool.



edit:
The reason the idle VE table is insufficient is because it doesn't handle light cruise or coastdown.

Joe Perez

iTrader: (8)

This is exactly the problem I was having.

Again, this.

When you're coasting along with your foot barely on the throttle, you spend a fair amount of time below 20. And for whatever reason, the engine seems to get real non-linear in that range.

curly

iTrader: (25)

Dammit Joe my 12x12 table isn't big enough for these shenanigans.

hustler

iTrader: (6)

This is what made my daily livable in the summer with AC idle stuffs. It did not like to leave the light from a stop.

Braineack

iTrader: (62)

I only need like 2-3 boosted rows. one for my 10psi wastegate, and the other for when im running EBC at 15psi.

quick tony

I have been having the same issues as described and have been thinking of adding more resolution to my VE tables on the low end of MAP. I will be doing this for sure now, and I am interested in any results you find.

Full_Tilt_Boogie

iTrader: (1)

Hondata thinks its important enough to include resolution at high vacuum, even if it may not be used.

Braineack

iTrader: (62)

my romraider presents the tables on that axis, makes me want to cry.

y8s

iTrader: (8)

in tunerstudio on the VEAL tab, did you know you can drag-select groups of cells, right click and lock them from changing?

Leafy

iTrader: (1)

Do your tuning in ecu flash. I only use rom raider now for logging, closed loop maf scaling, and making pretty graphs.

Braineack

iTrader: (62)

that's what I meant; I'm new to it. But I sometimes find myself tilting my head or turning my laptop to one side to read cl fuel and timing tables.

18psi

iTrader: (76)

Was about to say the same thing. But its nicer to use romraider cause its pretty