Thread: TP issue... noticed when map tracing

Got a weird question about my TP load and scaling

All looks good until 5500 rpm and up,tp starts to fall off and unload a few cells to the left at the high rpm (last 3 cells) and yes my Datascan settings are right!

I have done map tracing many times and never noticed any issues with tp/ scaling before. I know if u dont reach the far right column at WOT then you need to lower your tp scales etc.. and vise versa. If you reach the last column to quick then you need to raise your tp scales.

I have sr20 injectors in my ga16de now. the pink ones maxed out! lol

When you upgrade injectors, you probably lowered the K value. When you lower the K value, you shift the whole map. This is why TunerCode advises against this and found a new way to compensate for bigger injectors.

Now what you need to do is lower your TP scales

Vadim,

Ok this is news to me that this is not the route to go. Has always worked great before.

Yes I lowered my K value by doing the formula but then again raised it back up to compensate for the larger maf as per the formula.

I have already lowered my tp scales by using the formula.


For now i will try to lower my tp scales a bit more, or bit by bit till it stays in the last column till redline.

Basically Dave looked at the tune inside out and saw that the K value did a lot more then just deal with injector pulse widths. Only with TunerCode you can avoid touching the K value though.

Back to what you currently have, you can map trace, when doing a map trace with NDS, you should see real time RPM's and TP. Redline the car and see whats the highest TP you went to.

Then make your last column be about 5-10 points above that. So if you had max TP of 72 then make it 80. Nissan ECU's read up and calculate in between values. So if you have your last two columns as 70 and 80, at 72 you will be in the 80 column. Technically it should calculate an in between value too.

More information on that here.