Worthless reject member
From what I'm reading, you were right on the money here. It's pulling timing early in a run in anticipation of a knock so that it doesn't actually get any, kinda like "flinching". I was just going to ignore it but seeing as how it's not real knock, I figure why not play around with it and see what it does. So I've shifted the base vs cylairdelta over a couple columns, and pulled 10% out of the mult vs rpm table, see what if any differences that shows.it started to pull timing when dyn air went up. it sounds kinda like burst knock. so the ECM might be anticipating knock because of the sudden change in airflow. so it pulls timing.
that is weird. i've never noticed kr after flashing. the ls2 doesn't have THAT much compression. 10.9:1 is nothing these days.I'm really starting to wonder about some of the shit I see on hpt. I read a post where a guy said the ls2 has such high compression that it's on the ragged edge of knock off the factory floor. The someone else said that for some unknown reason the scanner picks up knock within 15 minutes of a new flash, so wait 15 minutes before trying to log kr. I know I'm in no position to call bs, but I started logging bs and was getting a few degrees of bs retard from these posts.
I might try to take a little more timing out at some point to see if I'm still getting any kr, but I think my next step is to visually inspect any areas where contact may be occurring. Like the header and steering rack for instance.
That's it I'm leaving the site.sounds like you're on top of this stuff then.