VE Table Help

[vc81]

This is the one I'm playing with delco.

vegraph.JPG (88.71 KiB) Viewed 3708 times

[Holden202T]

for starters, get the entire 5600rpm row and copy it to the rpm rows above it, this will scale your graph to a nicer to use one, and you probably want roughly the same fuel there anyways not none!

honestly i have never used the smooth feature, but in this ones case i would be looking at the dips, if all the dips are the ones that were changed then you probably need to lower the ones around them that wern't changed.

alot of it is just getting to know it, if you lower an area and its too lean you'll really know about it, however if you are unsure about a massive dip, put it back up to match the cells around it and then re-test .... the key to getting smooth changes is a BIG log, with lots of hits of every cell then using the histogram average. this will mean if you hit a cell 10 time and one out of 10 is really leaner than the rest, at least the change wont be as severe as its an average of the 10 hits.

another thing i can see in your example, it looks like 3600-4400 or there abouts, 30-60kpa ?!?! its really low compared to everything around it, so either that whole section has been changed and the rpms below that need lowering aswell, or the rpms below and above it are right in which case that whole area needs to be increased.

just out of interest, how have you come to this result, is it from wideband logs or using blms etc ? then plotting on a histogram ?

[antus]

Yep, holden202t's advice is good. Also the logs get less accurate the more spikey the tables get as the logged data is logged against a cell but the ecu might be interpolating between two very different values right next to each other. Thus the result that ends up on the center of the cell can be affected a lot by the cell next to it. As holden202t said, you need to look at it logically, work out whats meant to be changed and whats been missed and smooth it out. I would do it by hand, but if a tool gets the result, great. Once its smooth, take another log and the results should be less spikey as the table was smoother to begin with. And repeat untill the wideband is good and the table is smooth.

[vc81]

Thanks for your advice antus and holden202t. The previous screenshot is from a standard vn v6 ve table that I changed on purpose to make it leaner. I done this to try and educate myself by doing some wideband datalogs and going through the process to get it back to standard again. This screenshot is where I'm at now. I think it's an improvement.

[vlad01]

very good!

[Holden202T]

that's looking a lot better.... however the end of the table (left) is not quite what I meant .....

so this is a standard $12P V6 tune, straight out of the zip file, as you can see it has the same drop off above 7200rpm.

ve table before-graph.jpg (202.46 KiB) Viewed 3675 times

ve table before.jpg (204.85 KiB) Viewed 3675 times

so I got the 7200rpm row and copied it to all the rows above, and as you can see below you get a much better scaled graph view to work with.

ve table after-graph.jpg (234.63 KiB) Viewed 3675 times

ve table after.jpg (211.95 KiB) Viewed 3675 times

it may never go to that rpm but if nothing else it much the 3D view look better and it can only mean the engine is rich that high in the revs if you do take it that far!

[delcowizzid]

yeah filling the table with higher values sure does make the table look nicer and makes it easier to use.and make sure you tune above the rev limiter rpm level by at least 1 row or you end up chasing your tail wondering why it dies before hitting the limiter LOL

[Holden202T]

i've found usually if you copy across like above you end up getting rich in that area as torque is dropping off well before there so making it like above will be plenty usually, you could even go a few rows back and use those numbers if you wanted to be really safe.

that said i normally do all my tuning and then copy over the last row to all the ones above it anyways to keep it nice and neat

[vc81]

I'm tuning from logs and I feel like I'm chasing my tail. I am doing smooth throttle applications but I still keep getting heaps of spikes on the 3D map. I smooth it then do another log and it is all spikey again. I'm really struggling to move any further forward. Should I have AE & DE and BLM's turned off? I already have lean cruise & closed loop turned off.
Thanks,
vc81

[vlad01]

yes blm needs to be off, that will be trying to "correct" the afr trims which in turn give you false wb data log.

i don't know about AE or DE though?