####   
 ##  ##  
 ##  ##  
 ##  ##  
  ####   
         

         
         
  #####  
 ##  ##  
 ##  ##  
  #####  
     ##  
 #####   

         
         
  ####   
 ##  ##  
 ######  
 ##      
  #####  
         

  _____ 
 | ____|
 |  _|  
 | |___ 
 |_____|
        

         
         
 ##  ##  
 ##  ##  
 ##  ##  
  ####   
   ##    
         

IMPORTANT: enter the case-INsensitive alphabetic (no numbers) code AND WRITE SOME SHORT summary of changes (below) if you are saving changes. (not required for previewing changes). Wiki-spamming is not tolerated, will be removed, so it does NOT even show up in history. Spammers go away now.


Visit Preferences to set your user name
Summary of change:
Fero's knock logging (Fknock1.log), kd = knock_val - noise_val and kr = knock_val/noise_val. http://www.vems.hu/files/knock/kd.png http://www.vems.hu/files/knock/kr.png The same plots, but plotted by igncount (eg. cylinder): http://www.vems.hu/files/knock/fknock_hist_diff.png http://www.vems.hu/files/knock/fknock_hist_ratio.png The major problem with the logs is the absence of a thrustful indication of whether there are real knocking or just noise. What can we do about that? * Record knock sensor output and primary trigger output in a stereo wave file, such that the knock "music" and primary trigger can be played back on the table (with correct timing wrt. engine phase). * if we assume that the noise is symmetrical around the kv/nv=1.0 that brings us to: anything above 1.3 is real knock. I tested a very simple method in the perl script ''bin/knock_analysis.pl'' for determining if knocking is present in the samples: (kr > k1 && kd > k2 || kd > k3), however without knowledge of when knocking actually occurs, it involves a lot of guessing. Ex, is this a knock? (I think, and a bad one): adv=9.75 rpm=5084 map=149 knock_val=315 noise_val=156 kd=159 kr=2.019 Todo's: * decide which knock detect method to use (and implement) in firmware * get some logs which contains information about whether or not knocking is present in sample N * devise some guidelines for how to setup the configuration
Optional: Add document to category:
Wiki formatting: * is Bullet list ** Bullet list subentry ... '''Bold''', ---- is horizontal ruler, <code> preformatted text... </code> See wiki editing HELP for tables and other formatting tips and tricks.