Bad Timing

[2GeNTSi]

Time, RPM, Timing, TPS, O2 1 Bank 1, O2 Trim 1 Bank 1

07:12.11, 2288.0, 28.0, 20.83, 0.86, 16.41
07:12.51, 2360.0, 26.0, 24.75, 0.24, 14.84
07:13.33, 2524.0, 26.0, 24.75, 0.72, 11.72
07:15.82, 3336.0, 22.0, 67.58, 0.96, 0.0
07:16.19, 3516.0, 8.0, 84.48, 0.96, 0.0
07:16.57, 3696.0, 8.0, 96.27, 0.96, 0.0
07:16.92, 3860.0, 9.0, 97.05, 0.96, 0.0
07:18.07, 4332.0, 9.0, 97.05, 0.96, 0.0
07:18.45, 4480.0, 9.0, 97.05, 0.96, 0.0
07:19.64, 3264.0, 30.0, 18.07, 0.04, -5.47

I know this isn't a good log first of all but the timing will look like that regardless if I went all the way to redline. I'm surprised the o2's aren't at 1v, because while I had my downpipe off, it was getting that quite often at WOT. I'm not sure what the problem is but apparently I'm getting half the timing I'm supposed to be getting.

I attached a graph of this section just to show you how large a dip in timing that is.

 

[rowlex]

you need to provide more of a log. one all the way to redline. however that is what a 2G is suppose to do, from cruise at 28* once WOT and boost hits it drops timing to 10*ish and then slowly moves up. O2 sensor at 1.0v means its running rich, but thats how my 2g likes it too.

 

[2GeNTSi]

I'm aware of that but from entire gear pulls that I've done before, there hasn't been much of a difference. I would post it but my PDA always would freeze, so I would end up losing the log. I had a few good ones and they all looked similar, timing would maybe peak at 11 once I hit redline.

 

[rowlex]

I'm aware of that but from entire gear pulls that I've done before, there hasn't been much of a difference. I would post it but my PDA always would freeze, so I would end up losing the log. I had a few good ones and they all looked similar, timing would maybe peak at 11 once I hit redline.

Well thats very interesting then. Im pretty stumped. Did you check for boost leaks? My car is pretty much the same, i get a max of 11-12* timing running 21psi on a 60-1, although I've pulled timing back a LOT in order to rid myself of knock. Maybe it's knocking for some reason? Does it pull pretty smoothly or buck at all?

 

[2GeNTSi]

That's the thing, there's no hesistation or bucking whatsoever. I don't understand it myself. I've done a boost leak not too long ago, the only one I couldn't fix was the leak at the tb (apparently it's the o-rings that need to be replaced).

Sometimes it actually does advance properly, but most of the time it retards timing. Once I get a job, I think the next thing I'll get will be DSMLink.

 

[spyderturbo007]

I would post it but my PDA always would freeze, so I would end up losing the log.

Sounds like your pocketlogger communication settings are too fast for the ECU to keep up. Rerun the byte timing test, or turn both parameters up (inter-byte delay and inter-packet delay, if I remember correctly).

 

[2GeNTSi]

The settings are the ones I'm using from the test. The PDA wouldn't freeze while I'm using it but sometimes when I turn it on, it'll just lock-up and the only thing I could do is reset it and erase all my data.

 

[spyderturbo007]

Have you tried doing a hard reset and then reloading all the information? When doing this you have to make sure that you remove all the information from the C:/Palm/hotsync/username folder. Where username is the name that you gave the palm. That might not be the exact path, but it's close.

Anyway, if one of your files is corrupt, everytime you hotsync you are just reloading the corrupt information from the PC.

Might also what to post a thread here about the lockup:

www.pocketlogger.com/forum/

 

[truwarrior]

Worst log ever, u should get atleast 15 at redline

 

[spyderturbo007]

Worst log ever, u should get atleast 15 at redline

That was an extremely helpful post, thank you truwarrior.

Um, how do you know what timing he had at redline????

The log stops at 4400.