I tried many consult programms but i can't find one that can log or show the knock sensor input. Does someone know a programm which can log the knock sensor?
datascan cable tells u code 34 knock sensnor problem. all u can do is clear it but it will come up again. I am getting the same need to get that fixed soon.
the short answer to your question is 'no' i think you're mixing up functions available with a nistune board vs functions available without. the knock sensor isnt available via consult, hence im 99.34% sure any nistune knock readings will require the nistune ecu daughterboard (aside from knock error code which any consult software will give you). and from memory whatever knock they can read with nistune board/software is currently pretty limited/not supported for all ecu/in testing at the moment. certainly not as simple as powerfc one (but hopefully theyll get it in there for all ecu's eventually)
I understand what you say, but i'm 99% sure that the oem nissans consult reader has this function. i saw it yesterday when i was at the local nissan dealer i saw it. There was a reading for the knock sensor input. So if they can in a stock ecu, we can do it too, right?
was it a consult 1 or consult II unit? and was it on a z32? or a later OBD2 model car? if it was a Z32 or similar consult 1 car, and you werent seeing things, then yes it could be programmed into any consult software. i just had a look with the consult II on a S13 (sr20de) to confirm that i hadnt missed it every other time ive used it, but i couldnt see any knock sensor anywhere. if you're certain it was a Z32 or other consult 1 car and that they could view some knock sensor number, see if u can get back there and tell you the menus/steps to show it
I'm not 100% sure, but I'm pretty sure I saw something knock related when watching the little gauges on the laptop when we took MagicMikes zed for a run after changing the heads last time.
does he have nistune, and were any hallicinogens in the vicinity i really hope there is some way to get knock info out of the ECU (without playing with ecu code like nistune does) because the most ive heard is with a lot of work you can find out the ram variable where the ECU records whether its reading from knock maps or not (which as far as the ECU is concerned, it is either running normal or knock maps, so makes sense they dont provide a user readable value).
Lol, yes he had nistune. And nothing weird in me Mike will probably see this thread in the morning and hopefully confirm/deny my ramblings
That would be knock count Chrispy, I think it goes to 10000 from memory. It just logs one more count each time it knocks. No the nissan consult does not have this function for the z32.
yeah thats what i thought, a non-consult thing that you need the nistune board to get. http://forum.nistune.com/viewtopic.php?t=519
Was just reading that link you posted to the nistune site. Am I reading this correct and thinking the nistune isn't very effective at picking up knock??? If so, that doesn't sit too well with me, one bad batch of fuel and bye bye engine. A bit dramatic maybe, but extremely plausible.
If you read this article it says clearely that there is a knock log. Take a look because i am from Greece and i don't understand everything. http://macmadigan.no-ip.com/kitesystems/Z32CONZULT.pdf
it doesnt show it logging knock - it shows them manually noting down where they think there is knock, based off the ignition timing showing a different value compared to what the maps say should be used at that load point. if u can find the knock value and the steps to get to it with consult, i can try with the ecu i have, or try and grab a Z32 ecu and see if i can find it in there. if they let you, try and get pictures of each consult screen to get to the knock reading (even if its not in english)
if you have the maps you can compare expected ignition timing with actual, that may be what that future use bit there for nistune is about. but im not sure if their knock detection i posted the link to forums for, is using that method, or it is reading from the registers/counters in the ecu that are responsible for reading the knock levels.
