I was logging last Thursday and at noticed that Autotap showed Knock Retard without an increase in knock counts.

My PCM program has the Burst mode enable set to 80* C and the ECT was 77* C so it shouldn't have been burst (but it could have been I guess).

It didn't matter what RPM, gear, or anything that I remember.

It wasn't pulling much timing, but it was pulling some.

Even with light changes (say 5-10%) in TPS.

Plus, if I went from 5% TPS to 15% TPS, the retard would come in and stay in for a while, till I backed out of the throttle, yet the knock counter never increased.

Any ideas?

 

I would say it was an error on Autotaps part thinking that timing was in fact getting taken out. It sounds like there was no reason for it to occur and the stable knock count just confirms it. I have never used Autotap but would suggest trying at least Freescan if at all possible (probably not possible, thats why your using AT).

Hal

 

Being that my car is OBDII, Freescan is not available for it.

Autotap is the only option I have at the moment. I'm not going to buy another cable/ software just to test the theory that Autotap is goofing up.


I appreciate your input, for sure! I just can't help but think that Autotap is only printing and logging what the PCM is sending. And so I'm inclined to think that it's actually showing up, not some Autotap ghost. I have two friends that have seen this same thing on their cars, one also has a 1996 car with OBDII (he's running Car Code and not Autotap though), and the other has a 1995 OBDI car and has seen it with Datamaster.

 

Thanks for the feedback as well. I will keep a mental note that this may occur (retard probably not caused by knock).

Hal