First Datalog, Some Concerns about Knock
#1
Newbie
Thread Starter
Join Date: Oct 2013
Location: Kansas City
Posts: 24
Likes: 0
Received 0 Likes
on
0 Posts
First Datalog, Some Concerns about Knock
Hey all, I just got done with my first datalog on Evoscan after getting my wideband O2 logging figured out. The log is me idling for a minute or so, driving home from work, and getting a quick WOT pull (3rd gear, starts @ row 2985). During the pull, the timing looks all over the place, and I got pretty significant (peaked at 5 counts) of knock around 6300-7000 RPM. What confuses me here is it doesn't look like the ECU pulled timing to compensate for the knock (I was under the understanding that the IX ECU pulls 1 degree of timing for every 3 counts of knock).
I got knock in areas I was just cruising in as well. The first of these starts @ row 3790, but the more concerning of the two starts at 3949. I was just cruising around 2,500 RPM and got up to a peak of 13 () counts of knock. Here it looks like the ECU tried to pull timing, but it didn't clear the issue right away.
Current mods are K&N Drop-in filter and Buschur TBE (Hallman MBC in signature not yet installed). This car has never been tuned as far as I know. I've read that the timing on the stock tune is overly aggressive and causes knock. The series of knocks around row 3949 lead me to think otherwise, because when the ECU pulled timing the knock didn't clear up right away. Any thoughts?
P.S.: I'm sorry I don't have 2-byte load set up yet. It's on my list of things to figure out in the near future.
I got knock in areas I was just cruising in as well. The first of these starts @ row 3790, but the more concerning of the two starts at 3949. I was just cruising around 2,500 RPM and got up to a peak of 13 () counts of knock. Here it looks like the ECU tried to pull timing, but it didn't clear the issue right away.
Current mods are K&N Drop-in filter and Buschur TBE (Hallman MBC in signature not yet installed). This car has never been tuned as far as I know. I've read that the timing on the stock tune is overly aggressive and causes knock. The series of knocks around row 3949 lead me to think otherwise, because when the ECU pulled timing the knock didn't clear up right away. Any thoughts?
P.S.: I'm sorry I don't have 2-byte load set up yet. It's on my list of things to figure out in the near future.
Last edited by ehall20; Apr 4, 2014 at 06:40 PM.
#3
Evolved Member
iTrader: (10)
First of all, this should be in the EcuFlash section.
Regarding the WOT part, timing was 12° before the knock started at 10/11 after the first 4 count, so yes the ECU did pull timing.
The knock around the 3950 area looks like just noise AKA phantom knock to me, I can't imagine how the engine would have that much real knock under those conditions.
Regarding the WOT part, timing was 12° before the knock started at 10/11 after the first 4 count, so yes the ECU did pull timing.
The knock around the 3950 area looks like just noise AKA phantom knock to me, I can't imagine how the engine would have that much real knock under those conditions.
#7
Evolved Member
iTrader: (10)
The ECU only interpolates between high and low maps when the octane flag is lower than 100. The flag is actually the % of the high octane map that is used in determining what to run. IE if the high octane map has 10° and low octane has 5°, and the octane flag is 80, then it will take 80% of 10 and 20% of 5, AKA 9° as the final value.
The octane flag gets lowered gradually by the ecu when it sees more than 7 counts of knock under boost. It gets raised back up gradually when there is no or very little knock under boost. This is more of a long-term correction that is used for persistent knock.
The ECU also immediately applies a 1° per ~3 knocksum reduction in timing as soon as knock is encountered, which is what we see in the OP's log.
The octane flag gets lowered gradually by the ecu when it sees more than 7 counts of knock under boost. It gets raised back up gradually when there is no or very little knock under boost. This is more of a long-term correction that is used for persistent knock.
The ECU also immediately applies a 1° per ~3 knocksum reduction in timing as soon as knock is encountered, which is what we see in the OP's log.
Thread
Thread Starter
Forum
Replies
Last Post