rob wrote:Hi all,
Here is my first attempt at what will eventually end up on my FAQ for how my knock light works. Let me know if you see anything missing, incorrect, or just plain confusing.
-Rob
Rob,
Here are my edits/suggestions. Feel free to use all, some, or none of them as see fit
Robtune Knock Light behavior
My custom knock light code is triggered off of a specific software flag in the
Subaru knock detection algorithm. This flag is triggered only when the
Engine Control Unit (ECU
) has determined it believes that actual engine knock has occurred. At this point the ECU has a few options
on how to handle the knock. It could do nothing, change the
Long
Term
Knock
Correction
(LTKC), drop the
Ignition Advance Multiplier (IAM
), and/or immediately retard ignition timing. It is also important to note that a side effect of my knock code is that when there is a real
Check Engine Light (CEL
) error, the CEL will flash very fast to the point it almost looks dim. If you see this, you need to
review your CEL codes and fix
the identified issues. With the CEL flashing like this you will get no knock indication.
Now the question is, what to do if you see knock activity. It is always
a good safe practice to immediately let off the gas when you see knock activity and
(removed the word plain) imperative to prevent engine damage if you see more than a couple flickers at a time.
These are the logical steps that I suggest for tracking down the source of the knock light activity
: (I moved this sentance out of the previous paragraph)
1) It is important to understand that occasional and brief knock activity should be considered normal. The ECU will continually try to reach maximum ignition timing. It will either max out all possible positive adjustment or hit some areas of knock that will affect the LTKC map (localized correction) or the IAM (global correction). This will be more obvious with lower octane or a motor with higher knock tendencies.
2) To determine if you are having real knock issues, you have to judge
whether you are not having "occasional and brief" knock activity. Obviously this isn't always easy to figure out. I suggest looking for patterns of when you see the knock activity (the occasional part) and how long the knock activity lasts (the brief part). If you can reproduce the knocking at the same load/RPM consistently over a couple tanks of gas then I would not count it as "occasional". If you get more than a few knock light blips in a row, then I would not count them as "brief".
3) If you think you have real knock issue
(removed comma & then) the first step is
to separate false knock from genuine engine knock by characterizing
(removed the word under) which conditions you are seeing the activity. That will lead
you to understand the best course for correction. Now we need to talk about false knock. My knock code is triggered after all the Subaru hardware and software filtering, but even with that
(removed comma) false knock gets through. False knock is most typically due to mechanical vibration,
a faulty or loose knock sensor
, or bad sensor wiring (shielding or grounding). If you see knocking in low load situations (free rev, or low load)
(removed comma & then) you can almost guarantee it is false knock. Also
, if you see consistent knocking at the same RPM even after continuously turning the boost eventually
down to WG level, that is also a good indication of false knock. I have also recommend
ed running the current tank empty and putting in 1/4 tank of race gas. If the knock activity continues (again after systematically turning down the boost) then you are seeing false knock.
4)
After you have eliminat
ed false knock
(removed comma & then) I would say there is a
real knock issue to track down
as soon as possible. There are many many things that can cause real knock issues. Although
(removed comma) this is not an exhaustive list
(removed comma) here are the most common ones I have seen
:
• Lean
Air Fuel Ratios (AFR
’s
): There are also many many reasons why this can happen. In terms of troubleshooting a
knock issue
(removed comma) identifying a lean condition is the first step. You will need a good
Wide Band (WB
) oxygen (O2
) setup with logging capability.
•
Mass Air Flow (MAF
) sensor issues: The ECU depends on the MAF
sensor to determine engine load. If the value seen by the ECU is incorrect, then it could be applying ignition advance values from the wrong part of the map.
• High
Compression Ratio (CR): My tune is based on a factory
8:1 CR. Anything higher either from the wrong motor (late model ej20G motors) or based on component choices during an engine build
and all bets are off.
• Excess Carbon Deposits: Another issue is excessive carbon deposits in the combustion chamber
which can lead to hot spots where the air-fuel mixture can ignite prematurely.
• Fuel issues: My tune is based on 92 octane. There is enough adjustability to run on 91, but
again below that
and all bets are off.
It is
also possible to get low quality fuel
; in this case
(removed comma) knock light activity should change with the change in fuel type or source.
• Ignition issues: Incorrect or failing plugs and a failing ignition system can also cause knock issues.
• Poor intercooling: Basic Ver1/2 WRX intercoolering should be enough.
• The tune: Given the number of hours run on my current tune by both myself and
(removed my) hundreds of customers
(removed comma) I feel ok saying the ignition maps should be considered
the lowest likelihood for causing knock issues. It is
also possible for something to go wrong with burning the chip, either human error or some kind of data corruption.