Map editing

[Steve @ VersaTune]

What's your IAT? Is it below 20C? There is an IAT req load modifier that applies only to the req load used for the DBW lookup. It starts to reduce the req load used for the DBW lookup at IAT 20C and below.
0.8% reduction at 20C
2.5% reduction at 10C
5.3% reduction at 0C

The reduction is in the req load used for the DBW lookup, not the dbw itself. You need to find your req load based on gear, app, baro, accel/decel mutliplier, etc. then apply the IAT modifier then take that req load and lookup the DBW.

You may actually be targeting a DBW below 80 after all the modifiers are applied.

[skiptownmcat]

Yeah, temps have been anywhere between 8-12 C, I'll check it out.

[skiptownmcat]

Where is this table located? In the meantime, I'm going to make the upper end of the DBW throttle table 86 and see if that makes a difference.
Just looking at the log, throttle starts to shut at 1.95 load which is well into the 80 range in my DBW table.

[skiptownmcat]

Reduced the load target in the 2250-3000 range so peak load is at 3.5k and increased DBW to 86 from 80 it seems to have done the trick, I'm now over boosting in the peak range (mid 20's) though so I'll have to drop it back and take away some on the BCS base table. Even though I'm targeting less, third gear feels so much better. I'll take some logs tomorrow once the map has settled properly.

[Steve @ VersaTune]

Where is this table located? In the meantime, I'm going to make the upper end of the DBW throttle table 86 and see if that makes a difference.
Just looking at the log, throttle starts to shut at 1.95 load which is well into the 80 range in my DBW table.

That table is not exposed in VT at this time. I can add it easily.

Try raising the DBW values for lower load points rather than setting values >80 in higher load.

Don't confuse absolute load with requested load. You may be seeing 1.95 but targeting 1.8.

[skiptownmcat]

I set the req load and baro load tables high and them just used the gear tables for targeting, my DBW throttle was definitely set to 80 in those load/app areas. I think it must be some sort of logic that tries to "smooth" the transition from one cell to the next. As I said, reducing the load and peaking at 3.5k seems to have sorted the problem.

[Steve @ VersaTune]

The modifiers that are applied after the table lookups reduce the requested load from the lookup value. For instance, at 0c IAT, a 2.0 load setting in the gear table will result in a 1.9 req load used to lookup the DBW. There are other modifiers than IAT that could result in the req load being even lower.

[skiptownmcat]

In my DBW table, the 80 range extends down as far as 1.688 req load in the ranges I was getting the closure. I was trying to target 2.05, I can't imagine I would be losing over 15% at a temp of 12C?


See, I had changed the 80 to 86 in the pic.

[javigti]

Steve

I performed a calibration of the MAF but it still gives a 30% STFT at high voltages. Is it normal or STFT should be on the + -5% across the voltage range?

(The LTFT is 6% )

thanks

[skiptownmcat]

New logs, it's still happening but it's less severe. I must be on the right track