Question regarding map column values

[creizlein]

Excuse me if this is a dumb question but would like to read some opinion on this as I haven't found much on this topic on the forum.
I am curious to know how are you suppose to tune the columns on the fuel map, As I am having the problem that, the base map jdm-p30 I started to use has a col10 Load Index of 1044mBar, and my care barely reaches ~1020 on WOT, so when I am doing data-logging I cannot get the last column to be filled.

I do not believe I have any air leaks that prevents this nor that the map sensor is faulty, as I seen the same behavior on other cars as well, but mine when vtec is off and rpm is 2k-5k reads about 1020-1030mBar and when vtec is on and rpm is higher it drops to 1010mBar , always above 1k but that difference makes the data-logging to not record results for that column?

So my question is if I should change the load index to 1000mBar to be safe and ensure it always get recorded, but then the col9 will read 987mBar which makes me think if 13mbar difference between the two columns is redundant? should i change it to be 960-1000mBar ?

What is the best way to sort them out?

[crluver123]

leave it as is. you will rarely fill the entire 10th column. if you lower the load value for column 10, anytime the map sensor reads higher than that value the ecu will freak out and send all sorts of bogus signals which can often cause pretty hefty damage to your engine.
just tune the 9th and 10th columns at the same time. or tune just the 9th column, and make the 10th column have the exact same shape but a little higher so it looks like a smooth flow from 8th 9th 10th when viewed in 3d

[creizlein]

Ok, thank you very much for your reply, that does make sense. Except for the part that the ecu would freak out :)
I was targeting the col9 and 10 to 12.8/.9 AFR and i will try to aim col8 to 13.5/.6 and make it as smooth as possible. but in my case I found that there is always a big jump for the WOT columns.

[crluver123]

one thing you'll notice while datalogging is the recorded lamba will usually only fill cells for map values it can actually reach, instead of values it is closest to. meaning for example if you have columns with 900mbar 950, and 1000, if actual map is 990, it will record into the 950 column, not the 1000 column. and if actual map is 910, it will record in the 900 column. or if map is 945 it will record in the 900 column still.
so just be careful of that when going over everything.

asfor the ecu freaking out if you exceed the value that is in column 10, expand your map to show boost values. look at the map in 3d, highlight column 11. it will most likely be way higher or way lower than column 10. this goes for both fuel and ignition. if you exceed the value for column 10, it will start pulling data from column 11, which could be very bad if not set up correctly

[creizlein]

Ah. I see. That does clarify a lot. Thanks for the explanation.
Dumb question tho. But wouldn't it be a good idea to use the 3 extra columns of the boost table and modify their load index then as well ? To have something like 900/940/980 and 1020/1040/1060+ on the boost tables despite I am N/A ?

I assume it's a terrible idea since didn't see much ppl doing it but now that you mention it will go read values from the boost table when value I exceeds col10 I wonder why not use them ?

[Spunkster]

You do not need to do this as it interpolates between the columns and NA tuning does not need higher resolution.

[creizlein]

Fair enough, thanks for the help.