My CSV

[LukeD]

Ever since I put in my UD pulley I've had this surging at high rpms. I finally recorded it and thought maybe someone could shed some light on what is going on. I've been thinking I may need a case learn but until I try that (until 1.1.9E comes out) I've logged my runs. The problem shows up I believe somewhere around frames 939-980. I goosed it onto the freeway and then kept on it till the hesitation. It dosn't always show up at the same speed and seems to not do it as much at night when it's colder. Any ideas? Thanks. If you want to read the file, just download it and rename the extension to csv.

Edit: Weird. When looking at it, it seems normal and there is a vaccum (negative boost) and then all of a sudden when the surging happens it goes to 0 boost and then even slightly into the positive with 0.441 and numbers like that (0.XXX). Weird things are happening with my EGR valve numbers too so I don't know.

[tejohnson]

Honestly, you do not need to be scanning the boost parameter, but replace it with MAP (kPa). The other critical item that is missing is TPS% (would help me to understand what you are telling the car to do at the time).

I would be curious to see if those misfires clear up in the lower RPMs after you do a CASE. Check your plugs (the electrodes and grounding straps, color, etc), wires, and coil packs in the short term. I have no way of telling where you are pulling your spark values from, so it would be nice to get rid of total misfires, and the 1-2, and 2-3 shift times, and replace them with IAT and MAF(Hz). You are getting a few degrees of KR, but your spark advance is fairly low (~2° KR with ~20° commanded). I am under the assumption that this is a scan while your car is relatively cooler (since your tranny temps are only almost 100°F). I may be willling to bet torque managemment is holding you back (look at how traction% climbs after the KR). Can you get a new scan based on the request above?

[LukeD]

Sure, I'll get all that tonight, thanks. I forgot to mention too, I'm running my stock PCM (It was doing this back when I had DHP 1.5 too though) cause for some reason my PT isn't showing support for my car. I've been waiting on Charles for a couple weeks now to get back to me on why it's not showing support for my car when their records show they did add support for it. I guess he's busy trying to get 1.1.9E out (hopefully by tonight too).

[LukeD]

Ok here's my new log. Same txt to csv deal as before. This time I used the DHP 1.5 file and did a case learn first. Problem still happens. Do you think it could be clogged injectors?

edit: link should be fixed

[xonelith]

link no worky

[LukeD]

thanks link fixed

[xonelith]

Well, I'm not sure I can figure out why you are surging ( I was too, but somehow I fixed it...lol) I'd be concerned with the misfires though. Are you throwing a code?

You might wanna start scanning LTFT, STFT and ECT, they can help get your fueling correct (I like gear, but many don't use it). Scanning the TQ might help in determining if TM is kicking in with regard to your KR.

Why are you scanning boost?

Based on your o2's at WOT, it looks like you are running rich (980 or so). Generally for an NA car, you should be around 890-920. How old is your O2 sensor? Might need replacing. However, narrowband is not accurate, so it is hard to tell, just a ballpark.

If you are running rich, you may have fouled plugs. Did you check your plugs? I would replace them then rescan. Might clear up alot of your problems.

Todd knows alot more than I do on this stuff as I'm still new, so wait on his answer:)

[LukeD]

Thanks for the input. This weekend I'll try some new plugs, these ones I have are about a year old but you never know, especially cause I made the mistake of bosch platnium 4s and later read on here those cause problems. I'll go back to copper next time.

Boost I ment to take off the list but forgot.

My o2 sensor is as old as the car so that might be a problem. I know for sure the problem happens (the surging) more when it's warmer, the misfires I think are all the time. I'm throwing the "multiple misfire" code but no light because of it. It's only when I scan for it. I'll do another run tomorrow without the Pro-M maf. I know it doesn't have to do with the surging cause I've tried that before but maybe it will lean me out to go back to my stock maf. Thanks for the input.