I can't scale my pte 880's.. help
 

I have been trying for weeks on trying to scale my 880's correctly and getting the latencies right. I have found a thread on a good start latencies but my fuel trims stay at -24 Trim High/Mid/Low.. I have even let it stay at idle for 20 mins.. nothing.. What is next..? Help?!!!

My current Scaling.

Latencys:

3.312
2.184
1.320
0.840
0.672
0.360
0.240


Scaled to 790

I got that a thread to start out with.. But keep getting -24.. Help!!!!:helpme:

you need to scale injectors with a wideband, not going by fuel trims. Only short term fuel trims reset each time you start the car. You need to be driving in order to get proper trim readings, also. And MAF scaling comes into play when reading fuel trims, so your MAF has to be set to match the car perfectly and if you needed 880 injectors I'm going to say that your MAF isn't scaled to read perfectly.

Try these, with Injector scaling: 804

You may also want to rescale the MAF

I did drive for like 20 or 30 mins and the numbers didn't change at all.. it keeps reading -24.. no matte what numbers people give me to plug and play.. it still says -24 for all the trims.. I am so confused and frustrated..

Does the 02 voltage cycle at all?

I haven't checked into that yet.. But what if it does or doesnt?

You need to flash the car to reset the trims, your 02 should fluctuate as the ecu corrects, its a process of the ecu adding/deducting until it settles, cycles every 4 minutes. It's a pain, not difficult just time consuming. Read the how to scale injectors thread, someone has as great flowchart type directional.

well the 880 were there when he got the car. the car was pretty much stock except for the 20g, 880's and a type RS BOV . now the car has a cone filter intake, 3" TBE boost is set to 11 psi (it's untuned)

ok we started today with the scaling and latency table as stated in the first post. we noticed that evoscan was reading -24 in all 3 trims. but we also noticed that the o2 was reading something different. we took a look at the formula in evo scan and saw that the o2 formula had an * in it has the trims did not. i had remembered reading something about that in someones post. so pretty much we made all 4 formulas the same (0.1961*x)-25. after the change we logged the low fuel trim (idle) for about 20 min. and we got down to 8.9. so we adjusted the latency table at the 14v stage to .744 from .672 and we logged again for another 16 mins and the final numbers for now are low 0.188, mid-(-2) high 0.188, and the o2 0.188. next step is to see a log after cruising at 3k rpm (60mph or so). MAF scaling has not been touched yet. the car idles a bit smoother than before. more to come.

can anyone let us know if were on the right track.

Mitsulogger works better for fuel trims.

If the 02 doesn't cycle when the car is at full operating temp you have a bad 02 sensor.

sounds good, I quit when I hit .78 cruise and -.78 idle.

the o2 cycles we just didnt pay close attention to it.

Razor-

Does that hold true about Mitsulogger being better at trims even if you've transferred the correct formula to EvoScan?

Cheers-
E

trims on the '03 don't reset when you flash ... you have to pull the battery cables. That can cause confusion with scaling since the correct scaling will make the car run like poop if the trims are maxed.

EDIT :: I see that you've found an error in the formula. This might still be useful to others though ...

I did notice when I hooked up to the 2nd O2 sensor when were hooking up the widband one of my wires are broke off.. can this play a factor on getting wrong numbers?