I did briefly when I first installed it but when I started setting up the software and realized I wanted the IAT in addition to the water temp I re-did the wiring before I actually logged anything. I do remember being unsure of what to use for the frequency during the setup. I guess somehow it stuck in my memory funny... sorry.. my memory has been ****-poor lately and it's embarassing - makes me look like an idiot... which is not the case.

 

Haha...I'm the same way. Then I think about it for awhile and go...oh ****...and correct myself. I don't think anyone cares, since SOME information is better then nothing. You and I aren't currently hacking on it, so it isn't fresh. Hopefully, now that more people are getting the EU, we will collect a better information "database".

My knock sensor culprit theory was from when the first guys with the EU started trying to log knock, maybe even Travis, but I just got the impression that Greddy hadn't worked out most vehicles knock sensors, if any. Then again, if you know the frequency, which John@J&S has posted on the my350z board, you can probably just log freq or counts or whatever like the SAFC does. This isn't really valueable IMO without some kind of background noise algorithm like PLX R500 uses and I decided until someone figured it out, I was leaving it unhooked. I just THINK I remember someone saying they tapped the knock sensor and it caused the factory ECU to think there was knock so it pulled timing. Who knows how they had it setup/wired.

 

Actually, I take that back...looks like John@J&S posts are inconclusive on the frequency, but he said non-resonant.

http://my350z.com/forum/showthread.p...ight=frequency
http://my350z.com/forum/showthread.p...ight=frequency

 

Haha talk about memory but yeah now that you mention it, I think I remember seeing those threads or one of them anyways...

IIRC what I was thinking at the time hooking up the KS to the analog input was that I could at least see the voltage signal on the datalogger to better understand what it was doing. And once I sorted out the error in the manual regarding which pins were input and which were output then I could see the signal nicely. It corresponded to the spec given in the FSM and I did notice that the KS voltage doesn't seem to vary much under normal conditions but under load I did occasionally see a spike of sorts, which could be knock or could be some other vibration. Hard to know though without having the timing display to see if any retardation took place.

Now I never had a chance to do this before but at some point this year I would like to do some runs with the Consult scanner datalogging concurrently with the EU and try to correlate that way to get a feel for what the ECU thinks is knock and compare it to the waveform on the EU. Unlike timing advance I should be able to see that on the scanner since the stock ECU should pull timing if it thinks it's getting knock (and I could always induce that if I had to ).

 

I've read you can simply use a metal object/hammer to bang on the block or a screw driver to bang on the KS to mimick knock. Might be a start.