I kind of have an understanding on how this works. 0-20% is the Value. This is my understanding. By adding a Value %, the less the knock sensor’s voltage goes to the ECU. So say you can add as much as 20% resistance to the knock sensor’s voltage to the ECU. Buy doing this the ECU does not pull timing until it surpasses the 20% value added to this.

Am I going in the right direction with this. I would like to have a full understanding.

Eric

 

Related to this, does anyone know if the Xede can monitor actual knock activity or just the knock "map" activity? By that, I mean can it monitor real knock or just the numbers that you plug into the knock map? It would be nice to datalog actual knock activity, although I suppose another option would be to infer this from datalogging the ignition advance.

 

I did look for this but I can't find that option in the Xede tuning software.

Eric

 

Something Shiv said earlier on another thread hinted that you can only read ECU knock activity from the OBD-II port right now?

 

Ok I got to talk with Shiv this weekend about the Knock map in Xede.

20.0 means it's on. Any other value means it's off. Now Shiv explained to me that the built Knock corrections into the Xede firmware are designed to be more sensitive in some areas and less in others to where Shiv has found with tuning to work best with the EVO. Good stuff. I thought that it was a -20% voltage from the knock sensor but I was very wrong.

Eric

 

Correct. The knock adjust feature is internally mapped. 20 means it is one. Anything else means it is off. I did not make the actually mapping user-adjustable since the knock control system is pretty hard to tune without proper tools (namely a load bearing, steady-state dyno and a good set of det-cans). My suggestion is to leave the entire table set to 20 and spend your time tuning boost, fuel and timing.

My 2c,
shiv