What do you mean it is not true. It is DSMers that wrote the software for pocketloger. Here is the link

http://www.pocketlogger.com/index.ph...knock&type=dsm

Here is what it says:

Knock:

Range: 0 to 43
The knock sum scale is given to represent the signal from the knock sensor to the ECU. The ECU then calculates the amount of detonation present. The higher the knock sum the more the ECU retards timing to get rid of the knock.
With a knock sum of:
3 or below, the ECU will advance timing.
Between 3 and 7, the ECU leaves timing alone.
Higher than 7, the ECU will begin retarding timing. Higher knock = higher retard, with the possiblity of seeing less than 4deg total advance at the maximum knock sum of 43.
One important note to remember is the knock sensor can detect "false" knock and retard timing. This is most commonly caused from the noisy lifters but anything it can audibly pick up could cause this.

 

how come my OBD-II pocketlogger doesn't support knock sensor voltage?

 

I think because it is logging thru the obd2 port, so it is getting reading from ecu.

 

yeah, but shouldn't knock sensor voltage be a parameter viewed by the ECU and obd-2 port?

 

nj1266,

Did anyone ever tell you that you are a pretty stubborn guy?

Listen for once and learn something from someone that knows. I am a 'DSMer'. And most of what I have learned about the DSM ECU has come from personal experience with years of using DSMLink and from the creators of DSMLink themselves. If you have never heard of it, the guys the created DSMLink have basically perfected for the DSM ECU what ECUFlash and EvoScan are just scratching the surface on for the Evo ECU.

DSMLink allows you to tune as well as log everything (knock retard, mass airflow, etc, etc) from the stock ECU. They have even created their own code that can be written to volatile memory so that the ECU doesn't have to be flashed for every change. I don't want to write a book about it....go to their site to learn more....you won't be able to get into their forums, but you can learn some from their site.

Anyway, I can show you hundreds of logs that show the amount of knock retard that you get from the amount of knock counts. Actually, most people on the DSMLink boards don't even log knock counts, because knock retard is what the important value is (note the number of threads in this forums about how much knock retard there is for different number of counts, etc).

The guys at DSMLink have disassembled pretty much the entire ECU, if not the entire ECU already. And they have posted the formula for knock counts and knock retard and it is in the client.

So, when I tell you how the DSM ECU works, why do you always try to find someone that says otherwise. You think the people who wrote a pocketlogger knows more about the ECU than the people who have disassembled the entire ECU and wrote an open source program to control it? Give me a break.

Once and for all, the DSM ECU pulls approximately .35* of timing for every 1 count of knock. The only reason I say approximately is because the exact forumla was fractional and I don't want to waste my time looking it up for someone who doesn't even want to listen.


Eric

 

Ain't that the damn truth.

 

 

Eric,

I do not know you from a hole in the wall. Sorry, but the guys who wrote the pocket logger for the DSM are also DSMers. I trust them more than I trust you.

If you think they are wrong, them e-mail them and have them correct that info on their website. Please post their e-mail response to you and share it with us.

 

Dude,

You don't have to know him or trust what ANYONE says,

Do some logs of your own and figure it out on your own, It is not hard to tell how much timing the ecu is pulling if you have good logs and a copy of your rom in front of you.

 

nj1266,

You don't have to believe me....I'm not forcing anything on you. I'm just telling your the truth. Take is as you may.

But, if you put your thinking cap on her for a second and think logically, you can come to the conclusion that I am correct, without even knowing me.

The guys that wrote the pocket logger basically had the ability to log timing and knock counts. That's all they had to determine how much timing was being retarded by the stock ECU. The pocketlogger is just a logger....it doesn't display timing maps or anything like that in the ECU. So, these guys were even worse off than we are now with the Evo ECU. We can do what they did and have the advantage of looking at the stock timing maps. Even so, we can't completely say when and how much timing is being pulled, until we get a definitive load formula and do map tracing. I hope to be able to do this for the Evo ECU soon, once we can log mass airflow.

But, this has already been done, and more, with DSMLink for the DSM ECU. There is no guessing here. The pocketlogger guys took a shot, and came up with what they though was going on. I commend them for the efforts. But, the DSMLink guys disassembled the ECU (like is happending now with the Evo ECU) and told us EXACTLY what is going on. And, to top it off, we can log it for proof.

It's really quite straightforward...I don't know why you have such a hard time understanding. I know you don't have access to the DSMLink forums, so you have to trust what I say, but just research DSMLink a bit, if you don't believe me.


Eric

 

Somebody give nj1266 a DSMlink forums account so he can go do homework for like a month.

 

And please disable his IP access on evom for the month he is studying.

 

 

Fortunately, the DSMLink forum is a private forum. That's why I like it so much....people there know what's going on and they don't have to deal with a bunch of bull crap from people who like to spew any and all misinformation that they find on the net.

I love this forum for the people who take time out of their day to post useful and valid information. A lot of people on this board post their logs, test, post again, test some more, etc. That's great stuff and that's how we learn. It's just difficult to weed through all the crap, though, when anyone with an account can post whatever they want without any personal experience behind it.

Eric

 

Couldn't have said it better.