Need some help with burst knock
TP % RPM lb/min MAF Hz ADV KR IAT °C ECT °C CYLAIR g/cyl 47.8 2950 20.55 8512 17 0 34 81 0.79 47.8 2945 20.55 8502 17 0 34 81 0.79 47.8 2962 21.03 8543 17 0 34 81 0.81 51.4 2953 23.73 8807 13 0 35 81 0.91 57.6 2782 23.08 8841 2 0 35 81 0.94 57.3 2893 23.36 8892 6.5 1.3 35 81 0.92 57.3 2966 24.43 8979 7 1.2 35 81 0.93 57.3 2923 23.57 8974 5.5 1.1 35 81 0.91 57.3 2918 23.78 8911 6 1.1 35 81 0.92 57.3 2952 24.43 8958 8 1.1 35 81 0.94
What would cause burst knock like this? Is there a PID in EFI that will show burst knock?
I did some searching on Burst knock, but came up with next to nothing ... The onlyh thing I got from searching is that it is anticipated knock which may or may not be true.
No clanking .. no KR to speak of in that snippet. The only place I see that timing could be pulled in my program is Burst Knock and it's roughly 14 degrees max, which is about what I saw. The converter is relatively new, only about 3-4000 miles on it. FWIW ... there's only about 12 on the truck all together.
Just so we're on the same page ... I changed my sig some, I think you were reading the mods on my old truck. Just in case your not up with the truck parts the RADIX is a MagnaCharger blower.
Trending Topics
The Best V8 Stories One Small Block at Time
I see the timing drops but no KR for a few frames and only ~1*KR at that point... Yes, I think I saw somewhere that maybe burst KR does not show up on KR logs. Another way to test if its burst KR would be to drastically increase the values in the Airflow to Enable Burst KR table. Maybe 300% or more... with a SC you're getting a lot more air than the stock tune was set up for. Good luck with the tuning...
I did get some logs with misfire data in there, but it's on my laptop and I'm gonna let it charge up some before I get back on it. I will get those up later on.
I did get enough info from it to tell the only time I'm getting any considerable misfire counts is at idle, more in Park.
Something I did notice that was a little strange is that in one of these instances, the o2's are reading .3xx and the injector duty cycle goes from 55+ down to 30'ish. Keep in mind this is at 65% throttle with PE coming in at 40.
Something tells me I have more problems than what I'm hoping it is. The o2 dropping down so low and timing running where it should be while it's that low is kind of worrysome. Would anyone like to volunteer to check out my EFI log? I can get you the EFI or a CSV log.
I will email you once I get back on my laptop.
You're not hitting COT (Cat Over Temp), are you??
I don't think my truck is set up to pull timing when that kicks in, but I hear that it will throw the O2's and injector readings off.
threshold and it also changes timing based on where
you move, on the CylAir-based timing map. I would
add the Dynamic Cylinder Air PID to your logging
and then look at your spark table step by step,
if you see you are on the spark value the table
says then that's that; if you are retarded to some
degree then look at the delta CylAir (make a
column with stepwise difference) and see if this
looks like a burst knock event trigger. I haven't
yet gotten the definition of what the HPTuners
burst knock delta threshold has as its timebase
but you should be able to pick out any big jump
anyhow.
To me it looks like you did get a burst knock
pullback applied, it was a bit over-the-top,
but once it started to release it exposed a
pin condition (which was its purpose for
coming on, to cover that up).
MAP transients expose the quality of your
speed-density tune, the MAF is too slow to
give accurate dynamic readings and you
probably want to see MAP, and work on VE
table at the MAP & RPM to get a little more
dynamic enrichment (effectively) by making
sure your SD tune is fat enough to party.
That's my guess.


