Notices
ECU Flash

Electronic det cans and usage

Thread Tools
 
Search this Thread
 
Old Jun 21, 2012 | 10:22 AM
  #1  
ethan169's Avatar
Thread Starter
Evolved Member
iTrader: (3)
 
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
Electronic det cans and usage

Made myself a pair of electronic det-cans today. Hopefully I can once and for all determine if my weird part throttle knock is false or not. As well as some other areas.

They seem to work well but I was curious who else is using det-cans for tuning and where do you usually place the clip or bolt to your engine? Some say block some say right above block on the head. My particular setup has the mic on a large aligator clip. Is there a good spot that anyone has found for this type of mount?

I read somewhere that somebody thought the mic on these cheap devices couldnt pick up the higher frequencies that knock makes. It sounds pretty sensitive and has a broad range of higher frequencies to me. Anybody have any experience with these?

Thanks - Ethan

Reply
Old Jun 21, 2012 | 05:26 PM
  #2  
99EclipseGSX's Avatar
Evolving Member
 
Joined: May 2005
Posts: 100
Likes: 0
From: Santa Monica, CA
Interested to hear this as well. It looks like you tried to upload an image, but it's not displaying correctly for me.

On a similar note, have you logged the raw knock voltage? I believe the channel is called "knock_adc_processed". You can log this, along with RPM, "knock_base" and "knock sum" and NOTHING else, so it logs at a very high sample rate. This may give you an idea if the knocksum you're experiencing is real. Knock_base is the floor, or threshold, that the ECU creates as a result of your knock multiplier settings, and its dynamic adjustment to the threshold based on continuous measurement of noise from the knock sensor. If your knock_adc_processed exceeds knock_base, it is considered to be knock by the ECU and will be reported in knocksum.

Typically, actual knock will be significant spikes above the nominal amount of knock "noise" in the sensor. Continuous "noise" that builds with RPM and crosses the knock_base value may just be that, noise, and nothing else.
Reply
Old Jun 21, 2012 | 09:59 PM
  #3  
stunt2's Avatar
Evolved Member
iTrader: (8)
 
Joined: Nov 2010
Posts: 753
Likes: 1
From: Georgia
as I've been told evoscan's logging speed is slow for that

https://www.evolutionm.net/forums/ec...-knockadc.html
Reply
Old Jun 22, 2012 | 10:17 AM
  #4  
ethan169's Avatar
Thread Starter
Evolved Member
iTrader: (3)
 
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
The image appears for me. Ill try adding it as just an attachment.

I have tried logging just the knock voltage but after a handful of good logs with knock examples and posting a few here i couldn't get any real results. I was basically look for the spikys and what not. Im not really comfortable just say hmmm theres no real spikes so i guess its not real knock...However I was only looking at knock voltage so let me reread your post and the link that was posted to see if I can get a better idea.

Here is a portion of a log I took this morning. It so happens that I had knock voltage checked...Its weird how the knock just appears. It love that 3000-4000 rpm area. It makes the car inconsistent as it doesn't always knock like this. Plus the timing is quite low in these areas. 3°? And the ECU retards it to -1 and dumps fuel down to 10.4 AFR? Seems werid to me. Its been like this for a while though. Id like to nail it.

Ive also tried recording my det-cans while logging but for some reason my computer is recording noise from the car even when the det cans arent plugged in. So I need to sort that out first.

LogEntrySecondsTPSRPMTimingAdvKnockSumKnockVoltageLoad1BJDMMAPWideBandAF
118.7029313.72549022218.752300.46815.6-9.6632515.3615
118.8124213.72549022093.752200.42916.8-9.8567214.7588
118.917613.725490221252200.682516.8-10.0501914.7588
119.0272813.72549022093.752200.58516.8-9.6632514.3766
119.1424416.86274512062.52200.487518-9.2763113.9062
119.2493819.215686272062.52300.70222.8-8.695913.9062
119.3595819.607843142093.752600.526525.2-8.5024315.1851
119.4693620.784313732062.53000.42928.8-8.3089620.3007
119.5765121.568627452031.253100.50731.2-7.3416120.3007
119.6863523.529411762062.53000.916538.4-6.5677331.5756
119.7962723.921568632093.753000.565540.8-5.6003830.2085
119.9032829.411764712093.752900.682557.6-3.0852730.2085
120.0133831.764705882156.252500.81968.4-2.1179217.5518
120.1233431.7647058821252400.799569.6-1.9244514.2884
120.2302833.333333332187.52400.74173.2-1.3440414.2884
120.3406536.0784313722502000.70279.2-0.7636315.1557
120.4503436.470588242281.251810.70280.4-0.7636314.7294
120.5605936.86274512343.751501.618584-0.3766914.7294
120.6692838.8235294123751400.838588.8-0.1832214.5971
120.7793541.568627452437.51000.4485960.3971914.4648
120.8893941.960784312468.75801.306599.60.7841314.4648
120.9992447.450980392531.25600.702106.81.5580114.553
121.1092747.450980392593.75400.7215110.42.1384214.5824
121.2163547.450980392656.25500.4875115.22.7188314.5824
121.326347.058823532687.5401.0531203.1057714.0679
121.4363547.058823532812.5401.4821263.8796512.7302
121.5435746.27450982843.75300.87751324.2665912.7302
121.6533646.27450982968.75301.053139.25.2339412.4215
121.763646.27450983000300.9945146.46.0078211.9217
121.8704146.27450983125301.482153.66.9751711.9217
121.9802446.27450983187.5301.3065163.28.1359911.7012
122.0902446.666666673312.5300.9165171.69.2968111.5101
122.1972746.666666673375301.053183.610.651111.5101
122.3075547.450980393562.5342.1645194.412.1988611.319
122.4173547.843137253625071.833213.615.1009111.0544
122.5242954.117647063812.5072.028247.218.389911.0544
122.6422656.470588243968.75-171.911271.221.0984810.584
122.7582658.431372554093.75-160.8385267.622.6462410.4076
122.8642572.941176474343.75060.663274.823.6135910.4076
122.9743976.078431374531.25151.0725268.824.19410.4811
123.081576.078431374687.5150.819265.222.6462410.4811
123.1913757.254901964875141.287236.418.9703110.9809
123.3012434.901960784937.5530.468100.80.5906611.0397
123.4085714.117647064718.753700.74126.4-8.5024311.0397
123.5182714.117647064531.253801.28721.6-10.0501910.0401
123.6285514.117647064312.53801.228518-10.4371311.1132
123.7353714.117647064093.753800.54614.4-10.630611.1132
Attached Thumbnails Electronic det cans and usage-photo-2-2-.jpg  
Reply
Old Jun 22, 2012 | 10:34 AM
  #5  
03whitegsr's Avatar
Evolved Member
iTrader: (8)
 
Joined: Nov 2006
Posts: 4,001
Likes: 17
From: Utah
Does it not respond to timing advance changes?

I'd actually try increaseing the timing at the low RPM/load areas that get pased through while the turbo is spooling up.

I could be wrong, but my theory is the ECU is only looking at the knock sensor for a small window of time. If you start retarding the timing too far, you start getting more of the ignition noise in that window and it can lead to false knock detection. I was running a decent amount more timing at that load and RPM range and if I dropped it any lower, I got all kinds of "knock."
Reply
Old Jun 22, 2012 | 12:19 PM
  #6  
ethan169's Avatar
Thread Starter
Evolved Member
iTrader: (3)
 
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
I havent really tried giving it more timing but was pondering that too. The car does feel quite sluggish down low and gets worse when it actually get "knock" and retards even more.

I am looking into the DMA live map and it might make making changes here and there easier on the fly. The only thing that sucks is they done have my ROM ID patchable. So I am looking into switching to 95630706 ROM ID.

Thanks for your input
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Live4Redline
ECU Flash
6
Jul 17, 2024 07:09 AM
Toxin
ECU Flash
13
Jul 4, 2015 07:29 AM
stunt2
ECU Flash
19
May 28, 2013 08:51 PM
strawe510
EvoM New Member / FAQs / EvoM Rules
4
Aug 2, 2010 01:53 PM
jid2
ECU Flash
13
Jan 22, 2009 06:56 PM




All times are GMT -7. The time now is 11:14 AM.