The "VCM scanner" as well as the "NGK_WB"? The former is the file that contains the custom PIDs.

It works for me, obviously

 

I had the same deal with my 00 PCM, could play with timing, afr, new knock sensors and race gas all day, it still threw a fair amount of random kr all the time. I swapped to an 02 PCM and it cleared up 100%. To me, $200 is cheaper than a new engine because your PCM can't tell you true knock from false knock. Also, I tried an 02 OS with the 00 PCM, didn't help at all.

 

Was there any other difference besides the 02 just works better? I guess I know what I will try next if the plugs dont work...

 

I have a 01 PCM and have zero knock... There's ways around it. I have an idea of what it is but won't e able to see the log until this afternoon

 

Im very hesitant to touch the knock sensor sensitivity since I did that last time...

 

My 01 pcm's operating system gave me an erratic false knock at the weirdest times. I loaded an 02 12212156 os into my 411 pcm and the erratic knock issue stopped. This is with efilive though so I'm not sure if you can easily do tis with HPTuners

 

Im pretty sure I would have to license whatever file I want to write to my pcm with hptuners. That means im still out the $200 with my same physical pcm. I found a few salvage yards nearby that should have an 02 pcm. If the plugs dont work, that will be next stop.

 

Use notepad to open vcmscanner cfg and you'll see the PID's he's using.

 

If I remember right, the 01+ pcms had a better processor or some type of physical improvement. Been awhile since I dealt with it, but I'm pretty sure it was more then just the operating system.

 

Its no theory, the 99 PCMs are horrible about false knock and the 00-01s are a litte better but the 02s seem to work fine. Same thing with the 98 fbody PCMs, its a well documented issue. Just an FYI, Id hate to see you keep chasing your tail over a relatively simple issue.