Knock counts = 0

[wheels87k5]

I've been researching and reading a lot about chip tuning. And I've come to the conclusion that trying to dig up all the information on how to tune your own chips, and actually understand it, causes mass amounts of brain farts. I mean, come on. I see where a tutorial was started, on different sites, to help get a better understanding but it really isn't. So if anyone has a link to "How to tune your own chips for older farts" please let me know.

Anyway, from what I am able to comprehend, I was able to burn a couple of chips to see which .bin and .xdf I could work with. I already have an ECM that has been soldered with the G2 for quick replacement of the chip. And I've been data logging to see where the tune needs to take place.

One thing I have noticed on all the logs is that the KNOCK count is 0 and the BLMs were around 135-138. I have checked timing and it is set at 0. Fuel pressure was at 13 so I bumped it to 14.5 That moved the BLMs down to around 127.

Engine light comes on when you're cruising and you floor it to gain some speed (WOT). Some research says it could be header noise. But 0 count? Shouldn't there be some number besides 0?

My concern is if the knock sensor is bad. What is the best way to test it?

 

[dyeager535]

Check out the service manuals in my signature. Read up on whatever knock sensor code(s) there are, pretty sure there is a diagnostic done on startup, but it's been awhile since I looked.

 

[wheels87k5]

I remember that diagnostic sheet.....I'll find it and go from there. I think I looked at it before but it's been awhile also. Thanks

 

[sreidmx]

you can check if its working by tapping on the block with a hammer (yes you can see it retard the timing with a light).

 

[wheels87k5]

OK...found the solution. Come on here. Start a thread. It's working. Can't beat that

I'm not sure what to think. I started k5.....started data logging......booom.....1 knock count. Got under truck, hit block a few times.....still 1 knock count. Go under and hit few more times, now have 5 knock counts. Maybe when I touched the wire with the hammer it could have made it work. Possibly the wire or connection. I'll wait till it cools off to check it further.

 

[dyeager535]

OK...found the solution. Come on here. Start a thread. It's working. Can't beat that

I'm not sure what to think. I started k5.....started data logging......booom.....1 knock count. Got under truck, hit block a few times.....still 1 knock count. Go under and hit few more times, now have 5 knock counts. Maybe when I touched the wire with the hammer it could have made it work. Possibly the wire or connection. I'll wait till it cools off to check it further.

Those knock sensor connectors sometimes go bad, they see a fair bit of heat.

 

[bp71k5]

I used to almost always get a knock count by stomping on the gas. The count would increase right as it would go into PE mode and I'd get a code 43 on the ECM followed by much slower feeling motor. I suspect it was doing the ESC test and failing, then pulling a bunch of timing.

I've modified the tune to not do the ESC test and it's been fine since. I've also heavily modified the tune to make sure it's not knocking. You'll almost always get a few knock counts when you first start the engine. At least that's what I've read everywhere.

 

[wheels87k5]

I ran 7 different chip set ups and data logged each one to see how much change there would be. I used my stock ACSU and ASDU from another ECM. Loaded each with a different .xdl. All of the logs had 0 knock count so I thought there might be something wrong. The last data logs before this testing/learning session always had knock counts. I still haven't worked on it since the other day. Working on getting a water softener installed in the house.

Did you modify the tune by turning off the ESC flag? I am just now getting into tuning chips and from what I've read you can set it so that you don't get a CEL but I don't think it makes it any better. The light doesn't come on but a problem still exists.

It's going to take some time to research and learn more about tuning. There's a lot to soak in and I'm not getting any younger. So this is a good time to teach an older dog new tricks. I use the Burn2 to build my chips. If I can figure that out then I should be ok until the first aneurysm.

Thanks for the input.

 

[dyeager535]

I think I'm the king of having weird problems, but I've had two issues with chip burning that drove me crazy. Well, three. Wait, four.

One was a corrupted tunerpro rt install. The ONLY issue exhibited were difficulties burning chips. Sometimes worked, often not. Acted like the chips were bad.

Second was a corrupted bin. Everything was set properly, but deceleration fuel cutoff wasn't happening, and it made deceleration horrible, enough that I used my brakes instead of clutch. Started with a fresh copy of the bin, problem gone.

Third was a connector issue. Lock on one of the MAF wire terminals at the ECM had failed, and led to an intermittent error code.

Fourth was a mechanical problem. Fuel pump hose split as I was roughing in my tune, and changes to the bin weren't having the expected results.

Making sure everything you can is mechanically good before worrying about the tune is a necessity. Things like the connector issue are very hard to find, found that by blind luck, but should have been part of my procedure prior to running the GM flowchart.

 

[bp71k5]

Did you modify the tune by turning off the ESC flag? I am just now getting into tuning chips and from what I've read you can set it so that you don't get a CEL but I don't think it makes it any better. The light doesn't come on but a problem still exists.

That just turns the light off as you found. There's a patch in tunerpro that marks that test as done and passed. It's called "ESC done" and is grouped with highway mode into a single patch you can apply in tunerpro. Just make sure your knock sensor actually is working and get your timing in order. I'm not sure why that test is there. I don't want to purposely cause the engine to knock just to test the sensor.

 

[sreidmx]

you can test the Knock sensor to verify its bad or good. I believe there is a resistance value that tells you what is good or bad. Mine had the wire roasted on it but it still was working.. I have since replaced it. If I run my hypertech chip and advance the timing I get all kinds of knock counts so I know its working. I also know that chip adds too much timing for normal fuel and the heat out here.

 

[wheels87k5]

I've got a new GM knock sensor and connector w/tail arriving Thursday. There is a you tube video that shows how to test the sensor. I'll be done with the water softener install by tonight so I can work on the k5 tomorrow. Do some data logging and see it the knock counts return.

 

[bp71k5]

I've got a new GM knock sensor and connector w/tail arriving Thursday. There is a you tube video that shows how to test the sensor. I'll be done with the water softener install by tonight so I can work on the k5 tomorrow. Do some data logging and see it the knock counts return.

Make sure to torque the sensor down correctly. They are supposed to get too sensitive if they are too tight. The torque rating isn't very high and I didn't know it was a big deal when I installed mine.