Notices
ECU Flash

Knock control - ignition retard

Thread Tools
 
Search this Thread
 
Old Dec 5, 2008, 04:45 PM
  #1  
Evolved Member
Thread Starter
 
jcsbanks's Avatar
 
Join Date: May 2006
Location: UK
Posts: 2,399
Likes: 0
Received 5 Likes on 4 Posts
Knock control - ignition retard

The ignition value we can log with MUT4 is shifted left 8 times and then divided by 90 (decimal). 231 minus the result is stored as a value that is later prepared for ignition.

Knocksum is added to this value.

Therefore, we have knocksum*90/256 = 0.35 degrees of ignition retard per knocksum as people suspected. I can't see any other funny business.

The offset suggests that the spark firing is scheduled from 61 degrees BTDC. Notice when you log the MUT 06 with the engine off you get 61 degrees BTDC timing. All starting to hang together

Last edited by jcsbanks; Dec 5, 2008 at 04:55 PM.
Old Dec 5, 2008, 09:13 PM
  #2  
EvoM Guru
iTrader: (6)
 
Ted B's Avatar
 
Join Date: Aug 2004
Location: Birmingham, AL
Posts: 6,334
Received 59 Likes on 45 Posts
So exactly what type of event triggers the low octane fuel and ignition tables?
Old Dec 6, 2008, 03:14 AM
  #3  
Evolved Member
Thread Starter
 
jcsbanks's Avatar
 
Join Date: May 2006
Location: UK
Posts: 2,399
Likes: 0
Received 5 Likes on 4 Posts
Octane value interpolates between high and low. Subject to the coolant temperature being warmed up, load being sufficient and no faults, the octane value will increase when the knock sum is 0-3, stay the same at 4-5, decrease when 6 or higher.

So knock sum of >=6 starts you moving towards low octane.
Old Dec 6, 2008, 02:06 PM
  #4  
Evolved Member
 
Mattjin's Avatar
 
Join Date: Apr 2008
Location: Sydney, Australia
Posts: 604
Likes: 0
Received 0 Likes on 0 Posts
I have noticed when a scan device is plugged in and the car not started you also get 61 degrees. Same on my permanent mounted Blitz R-VIT display.

FYI, from memory the actually crank trigger event is at 76* based on what almost all of the aftermarket ECU's use as their reference point for it. So they may be allowing 15* in which to allow time for timing calculations.

The big question is, does the system actually retard the timing in 0.35* chunks? I have always assumed it did. And is timing itself in the same increment. i.e. does the ecu interpolate between the 1* map resolution?



So from what the latest discoveries are saying, we all should be re-evaluating the term "knock sum" and change it to "knock retard" and use the correct timing values.

Last edited by Mattjin; Dec 6, 2008 at 02:10 PM.
Old Dec 6, 2008, 02:49 PM
  #5  
Evolved Member
Thread Starter
 
jcsbanks's Avatar
 
Join Date: May 2006
Location: UK
Posts: 2,399
Likes: 0
Received 5 Likes on 4 Posts
The calculation and lookup from the maps is to 1 degree accuracy. It gets multiplied up before the knocksum is added. So we only get the higher accuracy towards the end of the calculations. Depending on how near the final reported timing is to rounding to the next degree, this would explain why people feel that 1 degree being pulled is inconsistent between knocksums of 1,2,3.

There is a cam angle sensor pulse for every cylinder event (ie twice per engine rotation). Interrupts or compare match timers on the rising and falling edges coordinate the spark, fuel and knock measurement events. More digging to do obviously.
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
richardjh
09+ Ralliart Engine/Turbo/Drivetrain
156
Apr 30, 2012 05:32 AM
mrfred
ECU Flash
44
Dec 11, 2011 06:01 PM
jcsbanks
ECU Flash
64
Sep 19, 2009 01:34 PM
jcsbanks
ECU Flash
24
Dec 10, 2008 01:50 PM
jcsbanks
ECU Flash
9
May 18, 2007 03:34 PM



Quick Reply: Knock control - ignition retard



All times are GMT -7. The time now is 10:02 PM.