Well, simple i guess. I see knock counts that start continually go all the way up to 60,000+/- and then drop...then climb back to the 60k+ mark, for infinity. I don't have the knock sensor even plugged in. I'm running the latest .xdf's for Tunerpro RT, an Ostrich 2.0, Moates G1 adapter without the zif (Ostrich cable plugged directly into Ostrich). This was happening with my 749 ECM (for sale now) so I switched out to my 730. The 730 does it as well so I'm not sure its ECM related...help?

 

The value should only be counting up to 255 so there is a math conversion applied to the reading in the ads file that you don't need. Without the KS connected it will do that. Put a 3.9k resistor (or a KS) on the wire to ground if you want to stop the counts.

 

He's running code based on $58. my experience has been, this is pretty normal. Bruce and I went back and forth for a while on the knock code for $58/$60. You can tell when you get real knock, vs false knock based on the retard - but the counts increase all the time. I'd see 5,000 counts burst. This is with datamaster, tunerpro, and my snapon scanner.

-- Joe

 

FWIW, the counts would cycle infinitely from 0-65k+ all the time the ECM would be pulling up to my max retard degrees. I realy could see where / when real knock was occuring. I'm starting to look at plugs now. All looked normal so far so that's good I guess.....

 

Exhaust leak? Loud blower? Idler banging around?

I never saw any retard to speak of, with the false knock.

-- Joe

 

Actually I did just find a pinhold leak in my ypipe last night. I'm talkign REAL small pinhole but none the less a leak. Blower belt isn't on right now. New front suspenction components all the way around the car.