Upon connecting the AutoProm to the ALDL connector and starting the engine, the knock count will be around 0-4. But after the initial connection, the knock counts do not update or change, they just stay at that number during the entire datalog. Is this a problem with TunerPro or with my knock sensor, the knock sensor is brand new, and i don't see any noticable wiring problems. What could be wrong?

 

Maybe nothing. Are you sure you're getting any knocks?

 

Yes, i am getting audible knocks, so the knock sensor should be at least picking those up. And I know they are knocks because after retarding the timing they went away. But i did not have any knock counts before and i don't have any now. Another problem, maybe this is related, but when i was tuning in open loop to get my AFR even closer, my BLM's would remain at whatever they were when i connected to the ecm. In closed loop they update fine, but in open loop they held constant. I know they are supposed to do that in PE. but i didn't think so in open loop.

 

Make sure the ADS is reading byte 43 for that. (8 bit, calc = "X", factor 1...)
Other than that the sensor may be shot or not picking up on the 383 ??

 

Its on my friends mostly stock 87 GTA, and the sensor is brand new. It is on channel 43 and the factors are correct as well, so i have no idea what could be wrong.

 

I wonder if the ESC module is bad . I dont know just throwing that out there, I never had that problem. They didn't sell you a knock sensor for a 730 ECM TPI did they?

 

Any chance the memcal he's using is for the wrong size motor? Or wrong style BIN? An 87 is a MAF based BIN, so make sure the memcal being used is for a MAF car and for the right engine size. Makes a difference.

 

His car is an 87, and it originally had a 32b mask, the bin we are running now is a 6e mask. We are running a modified ARAP bin with AUJN spark tables for now, until we can tune the spark once the knock sensor is working. I am not 100% sure on the memcal, but i am assuming that it is the original memcal for an 87 350 Automatic.

Another concern that i have is that even if the knock sensor is not functioning, why don't the knock counts go to zero. for whatever reason when i connect the ecm the knock counts show up as a number less than 5, usually 1 or 0, then they remain at that number thru the entire datalogging session and do not go down to zero with no knocking or to any other number when an audible knock is heard.

 

The couple of knock counts at the beginning are the ECM testing the knock sensor. It intentionally causes a couple of knocks at startup to make sure the knock sensor is working and sets the SES light if nothing is recorded. At least that's what happens on $8d, you always get a couple of knocks at startup.

I'm not an expert on the MAF based stuff, so I'll have to defer to others more knowledgeable to give definitive suggestions in that area. However, be absolutely sure you have compatible knock module (it's on the memcal on the 7730, not sure on yours), knock sensor, and BIN file. I suspect your problem is in this area. I once put a MAF based memcal in my 7730 speed density set up and got the opposite of what you're seeing - my knock counts cycled all the way to 255 and rolled over to zero and started ramping up to 255 again - and it would cycle thru 255 knock counts in 3 or 4 seconds. The frequency "listened for" by the KS varies by engine size as well, different part numbers for the 305 vs. the 350. Just highlights the differences you can run into...

Good Luck, and hope this helps at least a little bit.


- Vern

 

Just to verify the sensor, it should be 3.9K ohm resistance for the 350 sensor. Maybe he has teflon tape or something on the threads that are not allowing proper contact with the block.