ign phasing / knock tooth correlation ?
ign phasing / knock tooth correlation ?
UPDATE: after talking with a few folks at AEM and seeing a few logs where I got a knock tooth 4 reading, which should not exist for the evo, AEM told me that the code for knock tooth was never completed and knock tooth should not be used to gauge which cylinder is knocking. They said this is true for all ems versions. Cylinder trims do work and the info provided here is correct for coil to cylinder mapping.
O.K.
So I delted everything I posted here yesterday because I think I have figured this out. I would like some of the Pro's out there to confirm that I am correct or point out where I am wrong.
the 30-1313 is configured for 4 ign teeth per cycle (720 degrees) and 4 fuel teeth per cycle. This is the bit that was confusing the heck out of me. The crank sensor is a 4 blade sensor so I'm not sure why AEM is using 4 teeth per cycle instead of 8 but they sure seem to be. As a reult the following info seems to be correct:
ign-tooth 0 tdc cyl #1 coil 2
ign-tooth 1 tdc cyl #3 coil 1
ign-tooth 2 tdc cyl #4 coil 7
ign-tooth 3 tdc cyl #2 coil 6
inj-tooth 1 tdc #1
inj-tooth 2 tdc #2
inj-tooth 3 tdc #3
inj-tooth 4 tdc #4
If the above is correct I believe the knock #1 tooth to cylinder correlation is as follows:
Knock #1 tooth 0 - Cyl #1
Knock #1 tooth 1 - Cyl #3
Knock #1 tooth 2 - Cyl #4
Knock #1 tooth 3 - Cyl #2
So if both the above are correct the coil to cylinder correlation would be:
Coil #1 - Cyl #3
Coil #2 - Cyl #1
Coil #6 - Cyl #2
Coil #7 - Cyl #4
The Injectors are setup as you would expect, injector #1 - Cyl #1 etc.
Can anyone confirm the above info or point out where it is wrong?
For those wondering what the purpose of all this is.... I wanted to be able to trim the ignition and fuel for each cylinder so I had to figure out what coil trim affects what cylinder.
O.K.
So I delted everything I posted here yesterday because I think I have figured this out. I would like some of the Pro's out there to confirm that I am correct or point out where I am wrong.
the 30-1313 is configured for 4 ign teeth per cycle (720 degrees) and 4 fuel teeth per cycle. This is the bit that was confusing the heck out of me. The crank sensor is a 4 blade sensor so I'm not sure why AEM is using 4 teeth per cycle instead of 8 but they sure seem to be. As a reult the following info seems to be correct:
ign-tooth 0 tdc cyl #1 coil 2
ign-tooth 1 tdc cyl #3 coil 1
ign-tooth 2 tdc cyl #4 coil 7
ign-tooth 3 tdc cyl #2 coil 6
inj-tooth 1 tdc #1
inj-tooth 2 tdc #2
inj-tooth 3 tdc #3
inj-tooth 4 tdc #4
If the above is correct I believe the knock #1 tooth to cylinder correlation is as follows:
Knock #1 tooth 0 - Cyl #1
Knock #1 tooth 1 - Cyl #3
Knock #1 tooth 2 - Cyl #4
Knock #1 tooth 3 - Cyl #2
So if both the above are correct the coil to cylinder correlation would be:
Coil #1 - Cyl #3
Coil #2 - Cyl #1
Coil #6 - Cyl #2
Coil #7 - Cyl #4
The Injectors are setup as you would expect, injector #1 - Cyl #1 etc.
Can anyone confirm the above info or point out where it is wrong?
For those wondering what the purpose of all this is.... I wanted to be able to trim the ignition and fuel for each cylinder so I had to figure out what coil trim affects what cylinder.
Last edited by Mad_SB; Feb 22, 2008 at 12:13 PM.
Just called AEM and had them read over this post (cross posted to AEM forum) and they said the information is correct in terms of the coil to cylinder and knock tooth to cylinder.
I should also not that this info only applies to stock ignition setup. Coil on plug users need not pay attention.
I should also not that this info only applies to stock ignition setup. Coil on plug users need not pay attention.
can you list the values that you have within your ignition/adv. ign /ign phasing-option?
my file reads:
ign tooth #01 = 1.03
ign tooth #02 = 0.03
ign tooth #03 = 0.00
ign tooth #04 = 0.00
ign tooth #05 = 0.00
ign tooth #06 = 3.03
ign tooth #07 = 2.03
ign tooth #08 = 0.00
ign tooth #09 = 0.00
ign tooth #10 = 0.00
being our firing order is 1,3,4,2
it would seem that:
Ign t2 = cyl 1 coil 2
Ign t1 = cyl 3 coil 1
Ign t7 = cyl 4 coil 7
Ign t6 = cyl 2 coil 6
Knock tooth # = coil number..... i know we dont have 7 coils, coil number is in reference to the coil assignment pin-out for aem... my file is configured off an old base file from aem start-up stuff.....
i havent confirmed this, but it is how i read it....
i too want to apply ign trims to a knocky hole as well....i am on 91 octane
my file reads:
ign tooth #01 = 1.03
ign tooth #02 = 0.03
ign tooth #03 = 0.00
ign tooth #04 = 0.00
ign tooth #05 = 0.00
ign tooth #06 = 3.03
ign tooth #07 = 2.03
ign tooth #08 = 0.00
ign tooth #09 = 0.00
ign tooth #10 = 0.00
being our firing order is 1,3,4,2
it would seem that:
Ign t2 = cyl 1 coil 2
Ign t1 = cyl 3 coil 1
Ign t7 = cyl 4 coil 7
Ign t6 = cyl 2 coil 6
Knock tooth # = coil number..... i know we dont have 7 coils, coil number is in reference to the coil assignment pin-out for aem... my file is configured off an old base file from aem start-up stuff.....
i havent confirmed this, but it is how i read it....
i too want to apply ign trims to a knocky hole as well....i am on 91 octane
My table matches yours, only time it will change is if you have to "sync" the timing.
What I posted above is correct according to AEM:
Coil #1 - Cyl #3
Coil #2 - Cyl #1
Coil #6 - Cyl #2
Coil #7 - Cyl #4
Knock tooth code was never completed and should not be used for reference on any AEM EMS per AEM. If you can figure out the cyl that is unhappy the coil to cylinder assignment I listed is correct. coil6 and coil7 are virtual coils for the second firing of 1 and 2.
What I posted above is correct according to AEM:
Coil #1 - Cyl #3
Coil #2 - Cyl #1
Coil #6 - Cyl #2
Coil #7 - Cyl #4
Knock tooth code was never completed and should not be used for reference on any AEM EMS per AEM. If you can figure out the cyl that is unhappy the coil to cylinder assignment I listed is correct. coil6 and coil7 are virtual coils for the second firing of 1 and 2.
if your numbers are right, then i wonder how my numbers are wwrong, as i spoke to a aem rep about the config of my files & he said my stuff is correct too?
your coil to cyl. ref is different than mine & you say that our ign tooth config's are the same?
i reduced my knk sensor tbl to articifally think it was knocking to see the behavior of knock tooth #1, i never saw a knock tooth #4.
what i did see, was if what was considered knk, the knk tooth # changed & held that number till the next knock event...
your coil to cyl. ref is different than mine & you say that our ign tooth config's are the same?
i reduced my knk sensor tbl to articifally think it was knocking to see the behavior of knock tooth #1, i never saw a knock tooth #4.
what i did see, was if what was considered knk, the knk tooth # changed & held that number till the next knock event...
Our coil to cylinder mapping match each other, just listed differently.
I have seen knock tooth 0,1,2,3,4 in my logs to date. I agree that 0 normally means no knock event detected since power on of the ecu. I have seen tooth 2 hold during an event then drop back to 1 after the timing and fuel are restored. I have also seen tooth 1 during an event and hold well after timing and fuel are restored, in fact it will always show 1 after an event and until another event that show a different tooth.
Since AEM told us both we are correct, someone must be wrong. It was not until I emailed the guy that does EMS training that I was told the knock tooth code was never completed and knock tooth should not be used. This was news to him as well.
I think AEM has the table labeled wrong as the left column "ignition tooth" is not the ignition tooth but the ignition coil number and the right column is the tooth count from the crank sensor, well almost, since aem is only counting 4 teeth for one full cycle when the sensor would show 8 (4 blade wheel).
So,
I would say we are correct on the coil to cylinder mappings and that knock tooth is meaningless until AEM either fixes the code or provides a full explanation of the knock tooth function.
I do think it would make sense for knock tooth to = igntooth +1 so that 0 would be no event, but again, I was told the code was never completed so it should not be used at all.
I have seen knock tooth 0,1,2,3,4 in my logs to date. I agree that 0 normally means no knock event detected since power on of the ecu. I have seen tooth 2 hold during an event then drop back to 1 after the timing and fuel are restored. I have also seen tooth 1 during an event and hold well after timing and fuel are restored, in fact it will always show 1 after an event and until another event that show a different tooth.
Since AEM told us both we are correct, someone must be wrong. It was not until I emailed the guy that does EMS training that I was told the knock tooth code was never completed and knock tooth should not be used. This was news to him as well.
I think AEM has the table labeled wrong as the left column "ignition tooth" is not the ignition tooth but the ignition coil number and the right column is the tooth count from the crank sensor, well almost, since aem is only counting 4 teeth for one full cycle when the sensor would show 8 (4 blade wheel).
So,
I would say we are correct on the coil to cylinder mappings and that knock tooth is meaningless until AEM either fixes the code or provides a full explanation of the knock tooth function.
I do think it would make sense for knock tooth to = igntooth +1 so that 0 would be no event, but again, I was told the code was never completed so it should not be used at all.
Last edited by Mad_SB; Feb 26, 2008 at 07:48 AM.
sorry for not reading the stuff you had written...i just looked @ the order & not so much what was written!!
regarding knock tooth, i was told by a software guy there, it was a while ago, that knock tooth holds onto / displays the last coil that knocked....
funny thing is, he never mentioned the software wasnt completed while he was telling about the functionality....if there was someone there that would know, i am pretty certain it would be this guy....??
i need to give him a call.
regarding knock tooth, i was told by a software guy there, it was a while ago, that knock tooth holds onto / displays the last coil that knocked....
funny thing is, he never mentioned the software wasnt completed while he was telling about the functionality....if there was someone there that would know, i am pretty certain it would be this guy....??
i need to give him a call.
Trending Topics
sorry for not reading the stuff you had written...i just looked @ the order & not so much what was written!!
regarding knock tooth, i was told by a software guy there, it was a while ago, that knock tooth holds onto / displays the last coil that knocked....
funny thing is, he never mentioned the software wasnt completed while he was telling about the functionality....if there was someone there that would know, i am pretty certain it would be this guy....??
i need to give him a call.
regarding knock tooth, i was told by a software guy there, it was a while ago, that knock tooth holds onto / displays the last coil that knocked....
funny thing is, he never mentioned the software wasnt completed while he was telling about the functionality....if there was someone there that would know, i am pretty certain it would be this guy....??
i need to give him a call.
Please do give him a call man. I'll pm you the name of the guy I talked With, he is the one that does the EMS training, when I reached out to him, he talked to dev and came back and said the code was never completed.
Lets try to get some closure on this so we can do a sticky with all the relevant info.
i was told to log ignition firing location 1-4 & also to log knk tooth. this way, you can see exactly where or which coil experienced knock based off of degree angle...i havent done this, but i plan to give it a try.
Thread
Thread Starter
Forum
Replies
Last Post
Tw3NTy0n3
04-06 Ralliart Engine/Drivetrain
0
May 21, 2016 11:24 PM
KevOVIII
Evo Engine / Turbo / Drivetrain
18
Nov 10, 2005 08:05 AM
Johnboy1065
Evo Engine / Turbo / Drivetrain
22
Sep 17, 2005 12:36 PM
93civEJ1
Evo Engine / Turbo / Drivetrain
17
Sep 7, 2004 12:54 PM




