MIGHTYMOUSE

iTrader: (59)

slick: he probably did turn your knock sensors off, if i turn mine off, i loose the 4* of retard bringing my total up to 30 as well. but that is not proper (since i have a ton invested in the motor)

i want it to work properly, i've tried 3 files now, all still do the same thing, hoping mine is in the sensor or circuitry, checkign that out tomorrow.

SIKLS1

Did a bit of R&D on the weekend with LS1EDIT, and if you tune it the wrong way the whole lot will produce codes, P0325 P0327 P0332, i put back in the stock tune as beforehand no more problem.
So check at what you have alter before this started.

Predator

MM, I'm not sure about this, but my thinking is that the ks codes only go off if your LS1 Edit settings are somehow incorrect. In my case, I didn't change the rev limiter settings EVERYWHERE. Just taking a wild guess here, but as you said: "changing the maf frequency table by TOO MUCH."

MIGHTYMOUSE

iTrader: (59)

ill upload another totally stock file when i get home, but i recall trying this already and it did not work for me.

Predator

MM, I hope it works for you. Let me know what happened, if you feel like posting.

MIGHTYMOUSE

iTrader: (59)

i couldnt find anything out of place on the tunes, the stock one didnt work any better from what i can tell.. but i had to do some mandatory stuff to it like gear recalibration/code removal etc. so i may have over looked or reproduced teh problem.

Predator

SIKLS1, I can't thank you enough mate! You helped me BIG time. I recently swapped out both knock sensors, and the harness, and after awhile I started getting P0327 and P0332. It never occurred to me that changes I had made in LS1 Edit was causing those codes. After reading your message, I remembered that I didn't start getting the codes until I changed my rev limiter settings (I upped the "rev by gear" to 6400 and changed the intial settings on the folder, only). I set everything back to stock and now the ks codes are gone. Again, thanks so much!

Best Regards!

Predator

I'm not going to mess with it, but I think you have to change the rev parameters EVERYWHERE, not just "by gear" as I did.

MIGHTYMOUSE

iTrader: (59)

so if say i changed the maf freq table by too much.. it would throw the 332 knock code? hmm

so how amd i supposed to tune with the thing if it sets off these when i move it too far from stock?

Predator

MM, I'm almost 100% positive that removing codes wouldn't cause those ks codes, and it seems gear changes wouldn't either unless there is a change that doesn't make sense to the computer. My situation made sense because I clearly didn't change the rev limiter everywhere possible.

Just curious, do you have the stock pulley?

Predator

It's back to the drawing board for me: P0327 and P0332 came back <img border="0" title="" alt="[Sad]" src="gr_sad.gif" /> .

MIGHTYMOUSE

iTrader: (59)

ah, sorry to hear it, but feel better knowing im not the only one.

im considering a gm pcm reflash and relearn, like $75 bux.. what are you thinking?

Predator

MM, I'm thinking about pulling off my intake, AGAIN, and rechecking all the connections. I didn't torque my knock sensors, just went by feel. Also, the old wiring harness was routed along the side of the valley, and I didn't do that when I reinstalled the new harness. Maybe my intake is pressing against the harness causing low voltage. It's funny that sometimes the light doesn't come on and sometimes it does; also, after I clear the SES light it won't come on again until I turn the car off and restart it. I know there's an explanation, I just can't find it. You got any more ideas <img border="0" title="" alt="[Embarrassed]" src="gr_emb.gif" /> ?

Predator

Oh yeah, misery loves company <img border="0" title="" alt="[Razz]" src="gr_tounge.gif" /> .

Predator

I've also thought about just turning off the rear knock sensor (P0332). P0327 isn't on the list in LS1 Edit, just P0325 and P0332.

slick98ta

</font><blockquote><font size="1" face="Verdana, Helvetica, sans-serif">quote:</font><hr /><font size="2" face="Verdana, Helvetica, sans-serif">Originally posted by Predator:
<strong>It's funny that sometimes the light doesn't come on and sometimes it does; also, after I clear the SES light it won't come on again until I turn the car off and restart it. I know there's an explanation, I just can't find it. You got any more ideas <img border="0" title="" alt="[Embarrassed]" src="gr_emb.gif" /> ?</strong></font><hr /></blockquote><font size="2" face="Verdana, Helvetica, sans-serif">Thats what mine was doing also.I could clear the code and it would be fine for the rest of the day for driving.I still say its programming though,I just don't see how me or others could never have a SES light problem before programming with the KS codes and soon as mine gets programmed I set those codes like crazy.
One other thing that's weird to me.Ed Wright is doing my programming and he said he "WIDEN" the range for the Knock Sensor senitivity and now I don't get and SES lights and I have no KR but..
My car won't shift,its an A4 and shift points are set at 6500 and its shifting at 6800!!And he didn't touch anything else.He says its my car is whats wrong.I have another pcm here that a friend is letting me use and ED Wright programmed that also,and his shift points are at 6000 and it shifts right on 6000 everytime.Ed has my pcm right now and called this morning about the shifting weird and he said he didn't mess with that,so i told him to just put the shift points down to 6200 to see what it does.This is more of a headache than its worth.I'll let you know how it goes.

BTW: With the knock sensors,if your taking the intake back off try putting Teflon tape around the threads of the sensors.I never did it to mine but heard it reduces the sensitivity of them.Worth a shot <img border="0" title="" alt="[Smile]" src="gr_stretch.gif" />

Later
Mark

Predator

Mark, I've never used Ed Wright, and I started getting P0332, only, before I ever had LS1 Edit. When I checked my rear ks it was filled with water and the valley was caked with white corrosion. So it made sense that the computer would throw that code because it corresponded with what I found under the intake. I changed both knock sensors, and the harness, and I even RTV'd around the KS rubber boots as in the GM TSB. I thought I was had solved my problem. Then out of nowhere, a couple days later I started getting P0327 and P0332 and I couldn't believe it. I had deleted egr and air codes before disconnecting my battery and pulling my intake to replace nock sensor. I was so careful about everything,I couldn't imagine that my new knock sensors and harness were at fault. The only thing I didn't so was torque the sensors but I knew I didn't over or under tighten them. Is it possible that a flaw in LS1 Edit is causing these codes? I know it's tough to say.

Yes, please let me know how your situation turns out. I like your tip about the teflon tape. Anyway, hang in there. We should be able to solve this if we keep working on it. Good luck, and thanks.

MIGHTYMOUSE

iTrader: (59)

i think it is a flaw in the programming. there is no other explanation.

im going to swap a freinds 98 computer into mine and see if the code shows up again.

if i get a complete reflash and it doesn not go away, i will be asking for that money back from somebody.

i never had a problem with 332 until i edited the first time. now i throw a 332 code approximately one ever 10 minutes.

just my op. but the teflon tape, while it could coushion the sensors, will also mess up their conductivity to the block, its electrical connection is the threads

<small>[ July 26, 2002, 02:33 PM: Message edited by: MIGHTYMOUSE ]</small>

slick98ta

MIGHTYMOUSE,
Thats about the only thing you can do is swap out the pcm.I did that and my codes went away so i knew it wasn't my car.

As far as the Teflon tape thing goes,I understand what your saying.It was just something I heard.I haven't tried it but figured it could be worth a shot.

Predator

MM, how come not everyone is throwing those codes after editing? It seems like just a few people scattered here and there.

You know it's ironic too, because my car is running so friggin' good, and I'm so in love with the beast, and these codes don't make sense, whatsoever. I've always found the pcm to be right about everything--but not this time. At least that's what I think <img border="0" title="" alt="[Big Grin]" src="gr_grin.gif" /> .