Notices
ECU Flash

Knock control - load vs RPM table found

Old Mar 16, 2011 | 12:25 AM
  #346  
bk_knight's Avatar
Newbie
 
Joined: May 2005
Posts: 1
Likes: 0
From: Singapore
Need Help - Knock Tables and Address for Evo9 JDM 89820002

Dear All, I have be spending hours and hours going thru all the address posted in this forum for my Evo9JDM 89280002 without sucess. Does anyone out there with the knock table address for this ECU. Please help.
Reply
Old Feb 10, 2013 | 08:35 AM
  #347  
kevin8086's Avatar
Newbie
iTrader: (1)
 
Joined: Apr 2008
Posts: 82
Likes: 0
From: Austin TX
So has anyone had to mess with the single and triple noise adder?
Reply
Old Jun 18, 2013 | 06:13 PM
  #348  
Dynotech Tuning's Avatar
Former Sponsor
iTrader: (12)
 
Joined: Jan 2011
Posts: 1,312
Likes: 9
From: Seekonk, MA


Originally Posted by jcsbanks
So it is a full throttle pull from 3000 RPM to 7000 RPM approx (x-axis).

The very spiky tracein blue is the knock voltage if you like. I presume it will be bandpass filtered and rectified. Then a gated integrator of the knock sensor signal for each ignition event.

Yellow is a moving average of the knock voltage. Cyan is a moving average of that. This is then used to calculate knockbase which is in magenta.

The mult, add1 and add2 are looked up by RPM from the tables I posted earlier in this thread.

Knockbase=(mult*knockvar2/8) + Add1 or Add2

Add1 is used before the gain is reduced (at about knockbase 140 or about 4800 RPM on this particular trace), Add2 is used after the gain is reduced.

Testing this for example at 6000 RPM reading the numbers off the graph:
knockbase=(19*40/8)+7=102 which is about what knockbase actually is on the graph at about 6000 RPM.
Has anyone successfully logged these MUT addresses in evoscan??

I tried logging the knock parameters preloaded in evoscan (i.e; knock_var, knock_72,etc) and most don't record anything at all.

-Jamie
Reply
Old Jun 21, 2013 | 02:27 PM
  #349  
burgers22's Avatar
Evolved Member
 
Joined: Jan 2006
Posts: 953
Likes: 2
From: Oxfordshire
Originally Posted by Dynotech Tuning




Has anyone successfully logged these MUT addresses in evoscan??

I tried logging the knock parameters preloaded in evoscan (i.e; knock_var, knock_72,etc) and most don't record anything at all.

-Jamie
I logged in OP2 direct to the SD card, but that logging is way to slow to be any use for analysis, peaks can so easily be missed.
Reply
Old Jun 21, 2013 | 03:23 PM
  #350  
JohnBradley's Avatar
Evolved Member
Shutterbug
Liked
Loved
Community Favorite
iTrader: (30)
 
Joined: Jan 2004
Posts: 11,406
Likes: 78
From: Northwest
Need AEM internal datalogging speed, what is it 1000hz or something? Even 250 would be better.

The best method of those moments that are "hmmm" is use the dyno as the tool. Pull timing and see what it does. No power change - didnt need to be there anyway and most likely real spike without knock. Power drop - timing was probably okay. Timing drop and power increase - stop playing with knock control numbers and trying to crack pistons or pound bearings out.

Using a couple gallons of 110 octane with no changes is another way to determine if the knock was real or not. Same outline as before, no change timing is on. Power drop timing is low (flame front is slower on high octane and power will drop as octane rating is to high for the engine needs) power increase timing was too high and engine was detonating.
Reply
Old Jun 21, 2013 | 03:29 PM
  #351  
Dynotech Tuning's Avatar
Former Sponsor
iTrader: (12)
 
Joined: Jan 2011
Posts: 1,312
Likes: 9
From: Seekonk, MA
I just need to log the knock multiplier, averaged knock curves and single/triple gain adders. I'm all good with the other stuff. DMA logging is pretty good.

So does anyone actually have the answer to my question?

-Jamie
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Hiram6g74
ECU Flash
1
Apr 13, 2017 08:59 PM
S15me2
ECU Flash
9
Dec 8, 2016 08:22 PM
tenney
ECU Flash
1
May 12, 2016 03:29 AM


Thread Tools
Search this Thread

All times are GMT -7. The time now is 11:49 PM.