Community Tephra Tweaking
You can copy the definition files from the "auto lancer" rom that has the tephra stuff in it. With those tables and scalings you can see that the stock settings are multiplier 18, and gain is 3 and 5....the knock thresholds are 50 half of the way up the rpm range, and 40 up the final part. There are also "filter maps" that are in the lancer rom, and I think that might be the way to stabalize the knock sensor....but I can't see the filter map for the evo roms, so not sure.
Well, if I can get an evo knock sensor for cheap, like 10-20 bucks, I will check to see if that is something feasible. I know its not necessary at all, but you never know. I agree with the filter maps. I guess they just don't worry about defining that in the evo rom as its meant for an evo knock sensor, not a lancer.
just so everyone knows, i sent 03lances a copy of my most recent log...ill figure how to post my maps through my phone soon.
03lances if you notice from bout 50 load at 2k rpm i start seeing that massive knock...i checked my afrs and im at about 12. i also changed the thresehold to the stock lancer settings.
oh yea if anyone has the stock 5spd lancer rom, can you send one my way @sawulknoz@gmail.com
03lances if you notice from bout 50 load at 2k rpm i start seeing that massive knock...i checked my afrs and im at about 12. i also changed the thresehold to the stock lancer settings.
oh yea if anyone has the stock 5spd lancer rom, can you send one my way @sawulknoz@gmail.com

. I am going to go ahead and call this false as it goes extremely high for just a couple samples then drops to 0 BUT. I need to check out your rom for sure as something is off here. This timing is strange and way too low everywhere. Cross referencing some of my logs show my timing at like 18 at the same rpm/tps (not referencing load since dont think you have the evo maf) as yours having like -1 no knock. Not good
I have put the knock sensor filter maps into my 81870017 def file, the stock lancer "knock filter" maps. I dont see how this can hurt the car as to im still using a stock lancer knock sensor and stock lancer knock settings, so im hoping this will solve the problem of the crazy know we get just crusing as what not. Im goin to flash it to the car, take some logs and let you guys know if it made any difference
Yo sawulknoz can you send me a copy of your rom? Are you using a modified version of the one I sent you? Looks like your running forced open loop still. Your timing is wayyyy to retarded man I see -5 with no knock and only 1/4 throttle
. I am going to go ahead and call this false as it goes extremely high for just a couple samples then drops to 0 BUT. I need to check out your rom for sure as something is off here. This timing is strange and way too low everywhere. Cross referencing some of my logs show my timing at like 18 at the same rpm/tps (not referencing load since dont think you have the evo maf) as yours having like -1 no knock. Not good
. I am going to go ahead and call this false as it goes extremely high for just a couple samples then drops to 0 BUT. I need to check out your rom for sure as something is off here. This timing is strange and way too low everywhere. Cross referencing some of my logs show my timing at like 18 at the same rpm/tps (not referencing load since dont think you have the evo maf) as yours having like -1 no knock. Not good
ok so my main thing is idle...
its driving me nuts, so I figured don't touch the latency and look at other issues, is there a leak thats making me rich, is my filter dirty. Then I will look into the rom if there is nothing else.
03lance when you did your latency did you just use the stock lancer rom latencies, did you use the subaru latency? im not sure where to start from and when and where to increase and decrease latency. Help me get an understanding so I can go about this idle issue.
I found out a formula to help you scale your injectors I found this off an evo x site but im putting it into my words and using my injectors as the value
We assume the OEM injectors are 275cc, and the scalar value is 232. We want to use 880cc injectors. So we plug in 880 for X in the following equation.
NEW INJ SCALAR VALUE=(X*232)/275
742.4=(880*232)/275
I have my cruise ltft at .69
edit** if you can get the exact number just round it, Im using 750 as my scaling
its driving me nuts, so I figured don't touch the latency and look at other issues, is there a leak thats making me rich, is my filter dirty. Then I will look into the rom if there is nothing else.03lance when you did your latency did you just use the stock lancer rom latencies, did you use the subaru latency? im not sure where to start from and when and where to increase and decrease latency. Help me get an understanding so I can go about this idle issue.
I found out a formula to help you scale your injectors I found this off an evo x site but im putting it into my words and using my injectors as the value
We assume the OEM injectors are 275cc, and the scalar value is 232. We want to use 880cc injectors. So we plug in 880 for X in the following equation.
NEW INJ SCALAR VALUE=(X*232)/275
742.4=(880*232)/275
I have my cruise ltft at .69
edit** if you can get the exact number just round it, Im using 750 as my scaling
I have put the knock sensor filter maps into my 81870017 def file, the stock lancer "knock filter" maps. I dont see how this can hurt the car as to im still using a stock lancer knock sensor and stock lancer knock settings, so im hoping this will solve the problem of the crazy know we get just crusing as what not. Im goin to flash it to the car, take some logs and let you guys know if it made any difference
ok so my main thing is idle...
its driving me nuts, so I figured don't touch the latency and look at other issues, is there a leak thats making me rich, is my filter dirty. Then I will look into the rom if there is nothing else.
03lance when you did your latency did you just use the stock lancer rom latencies, did you use the subaru latency? im not sure where to start from and when and where to increase and decrease latency. Help me get an understanding so I can go about this idle issue.
I found out a formula to help you scale your injectors I found this off an evo x site but im putting it into my words and using my injectors as the value
We assume the OEM injectors are 275cc, and the scalar value is 232. We want to use 880cc injectors. So we plug in 880 for X in the following equation.
NEW INJ SCALAR VALUE=(X*232)/275
742.4=(880*232)/275
To simplify, I know the 232/275 is used for informational purposes to show how the value was obtained, but if that's confusing, multiply the known max (like 440 for 440cc injectors) by .8435, and you'll get 371. This is basically that "rule of thumb" that says take 15% off the top, ie .8435 + .15 =(almost) 1
I have my cruise ltft at .69
edit** if you can get the exact number just round it, Im using 750 as my scaling
its driving me nuts, so I figured don't touch the latency and look at other issues, is there a leak thats making me rich, is my filter dirty. Then I will look into the rom if there is nothing else.03lance when you did your latency did you just use the stock lancer rom latencies, did you use the subaru latency? im not sure where to start from and when and where to increase and decrease latency. Help me get an understanding so I can go about this idle issue.
I found out a formula to help you scale your injectors I found this off an evo x site but im putting it into my words and using my injectors as the value
We assume the OEM injectors are 275cc, and the scalar value is 232. We want to use 880cc injectors. So we plug in 880 for X in the following equation.
NEW INJ SCALAR VALUE=(X*232)/275
742.4=(880*232)/275
To simplify, I know the 232/275 is used for informational purposes to show how the value was obtained, but if that's confusing, multiply the known max (like 440 for 440cc injectors) by .8435, and you'll get 371. This is basically that "rule of thumb" that says take 15% off the top, ie .8435 + .15 =(almost) 1
I have my cruise ltft at .69
edit** if you can get the exact number just round it, Im using 750 as my scaling
Injector Latency for decapitated wrx injectors
V 6.5 9.0 11.5 14.0 16.5
mS 4.02 2.14 1.42 1.14 0.60
From another site (it will vary a tiny bit depending on the application, maf scaling, and of course the fuel pressure)
740 cc 3656 2002-2003 WRX OEM Modified 2.79, 1.49, 0.98, 0.68, 0.38
Stockers are
WRX 2.79, 1.49, 0.98, 0.68, 0.38
V 6.5 9.0 11.5 14.0 16.5
mS 4.02 2.14 1.42 1.14 0.60
From another site (it will vary a tiny bit depending on the application, maf scaling, and of course the fuel pressure)
740 cc 3656 2002-2003 WRX OEM Modified 2.79, 1.49, 0.98, 0.68, 0.38
Stockers are
WRX 2.79, 1.49, 0.98, 0.68, 0.38
voltage OEM Modified
6.5 ----- 2.79 -- 4.02
9.0 ----- 1.49 -- 2.14
11.5 ---- .98 --- 1.42
14.0 ---- .68 --- 1.14
16.5 ---- .38 --- .60
Also found this:
WRX 440cc Latencies
10v-1.25ms
11v-1.01ms
12v-0.87ms
13v-0.74ms
14v-0.62ms
15v-0.53ms
and this:
420 cc 6442 2002-2003 WRX 2.79, 1.49, 0.98, 0.68, 0.38
800 cc 3380 2002-2003 WRX OEM Modified 2.79, 1.49, 0.98, 0.68, 0.38
850 cc 3180 2002-2003 WRX OEM Modified 2.79, 1.49, 0.98, 0.68, 0.38
But then someone says "Your OE modded latencies are definitely not right. I'm around: 3.6 2.4 1.48 1.12 .88"
So maybe they don't need to be modified....perhaps the squirt stays the same no matter how big the tip is (must...not...say...that's........)
Basically, 1 person says use scaling of 740 and stock latencies, and another says use basically stock latencies * 1.5....more or less. Still, common sense would tells us that latencies are used to tell the ecu how long the injector needs to stay open for the amount it's trying to squirt....so modified injectors do need different latencies than oem ones I'm thinking. What are you using right now? and your fuel trims are "okay"? I'm thinking if you are having idle issues, it may just be a bi-product of having such a big injector (that's what she said).
Last edited by HornstarBU; Nov 22, 2010 at 08:03 AM.
Mine didnt ether, but i copied them from a stock lancer ROM's XML and put them into my current tephra v7 ROM's XML and it seems to be working, highway crusing at 65-70 MPH, 15.3 AFR 37 timing advanced with the ocasional one count every now and then, which is normal and a safe number for any combustion engine. alot better than the 18+ counts i was getting crusing, they were false knock it seems anyway. Also in boost i still have some work to do, but it seems more accurate, instead of the 10+ counts of knock i got when taking off from idle its only 4 or so. i just need to work on the fuel part now, still to lean in boost!
My latencies are as follows
4.69v---3.144
7.03v---2.112
9.38v---1.200
11.72v---0.744
14.06v---0.600
16.41v---0.480
18.68v---0.360
There are plenty of people who say they cannot get a good idle using the 440's they claim its the bigger injectors. I do not have this issue my car idles just like stock. Those modded 880's though idk thats a hell of a jump from our stock setup and as Hornstar stated it may or may not be able to get a perfect smooth idle because of it.
Sawulkn> got the rom going to check it over now.
4.69v---3.144
7.03v---2.112
9.38v---1.200
11.72v---0.744
14.06v---0.600
16.41v---0.480
18.68v---0.360
There are plenty of people who say they cannot get a good idle using the 440's they claim its the bigger injectors. I do not have this issue my car idles just like stock. Those modded 880's though idk thats a hell of a jump from our stock setup and as Hornstar stated it may or may not be able to get a perfect smooth idle because of it.
Sawulkn> got the rom going to check it over now.
Mine didnt ether, but i copied them from a stock lancer ROM's XML and put them into my current tephra v7 ROM's XML and it seems to be working, highway crusing at 65-70 MPH, 15.3 AFR 37 timing advanced with the ocasional one count every now and then, which is normal and a safe number for any combustion engine. alot better than the 18+ counts i was getting crusing, they were false knock it seems anyway. Also in boost i still have some work to do, but it seems more accurate, instead of the 10+ counts of knock i got when taking off from idle its only 4 or so. i just need to work on the fuel part now, still to lean in boost!
If I try to put them in the Tephra rom, I see nearly jibberish, although it is somewhat close to what you'd expect to see in a few of the tables. I'm thinking that means that while the data I am looking at may be a table of somewhat similar size and data, it's not necessarily any knock data. I think what we need to do is find people with Evo's who have defined the "Knock Sensor Filter Map", and not just the "Knock Load". The other odd thing is that I read in some spots people saying that a few years back, it was discovered that the "knock sensor filter maps" aren't actually knock related at all....and they recommend they be re-named, so I'm not sure exactly what the deal is here.
You would think either there is a map that shows a multiplier used on a per RPM basis (a 1D table) and the values would be calculated by some formula using load to determine what the threshold is before something is considered knock, or a predefined table that basically has that data in it (a 2D table)....but I wouldn't expect to see both. So, in the lancer rom, I can copy Mitsu.kids auto tephra rom stuff in, and see the knock thresholds in a 1D table, but also as he says the 2D tables (and I confirmed) still show up there as well.
I'm thinking....perhaps the evo's are missing the table that might straighten us out. Oh, side note, the value in the base lancer rom for 4000 rpm and up is 255, which I am guessing means "maximum sensitivity, no "reduction for noise at low rpm", so I doubt that much "up top" knock is phantom...only the low stuff, specifically at 2250-2500 rpm
Also, check https://www.evolutionm.net/forums/en...detection.html that post. The first post has a link to an xls spreadsheet with graphs of each filter map....they are no where near the same as the stock lancer ones. Not sure why there are a lot of them, or how we would compare them to ours....but I'm betting number 1 is the most important, and it sure as heck doesn't match.
Last edited by HornstarBU; Nov 22, 2010 at 09:25 AM.
What you said confuses me. I added the "Knock Sensor Filter Map 1..2..3..etc" to your xml, and the values are identical to the stock lancer rom. The reason you can paste the filter maps in, is because you have a lancer rom.
If I try to put them in the Tephra rom, I see nearly jibberish, although it is somewhat close to what you'd expect to see in a few of the tables. I'm thinking that means that while the data I am looking at may be a table of somewhat similar size and data, it's not necessarily any knock data. I think what we need to do is find people with Evo's who have defined the "Knock Sensor Filter Map", and not just the "Knock Load". The other odd thing is that I read in some spots people saying that a few years back, it was discovered that the "knock sensor filter maps" aren't actually knock related at all....and they recommend they be re-named, so I'm not sure exactly what the deal is here.
You would think either there is a map that shows a multiplier used on a per RPM basis (a 1D table) and the values would be calculated by some formula using load to determine what the threshold is before something is considered knock, or a predefined table that basically has that data in it (a 2D table)....but I wouldn't expect to see both. So, in the lancer rom, I can copy Mitsu.kids auto tephra rom stuff in, and see the knock thresholds in a 1D table, but also as he says the 2D tables (and I confirmed) still show up there as well.
I'm thinking....perhaps the evo's are missing the table that might straighten us out. Oh, side note, the value in the base lancer rom for 4000 rpm and up is 255, which I am guessing means "maximum sensitivity, no "reduction for noise at low rpm", so I doubt that much "up top" knock is phantom...only the low stuff, specifically at 2250-2500 rpm
Also, check https://www.evolutionm.net/forums/en...detection.html that post. The first post has a link to an xls spreadsheet with graphs of each filter map....they are no where near the same as the stock lancer ones. Not sure why there are a lot of them, or how we would compare them to ours....but I'm betting number 1 is the most important, and it sure as heck doesn't match.
If I try to put them in the Tephra rom, I see nearly jibberish, although it is somewhat close to what you'd expect to see in a few of the tables. I'm thinking that means that while the data I am looking at may be a table of somewhat similar size and data, it's not necessarily any knock data. I think what we need to do is find people with Evo's who have defined the "Knock Sensor Filter Map", and not just the "Knock Load". The other odd thing is that I read in some spots people saying that a few years back, it was discovered that the "knock sensor filter maps" aren't actually knock related at all....and they recommend they be re-named, so I'm not sure exactly what the deal is here.
You would think either there is a map that shows a multiplier used on a per RPM basis (a 1D table) and the values would be calculated by some formula using load to determine what the threshold is before something is considered knock, or a predefined table that basically has that data in it (a 2D table)....but I wouldn't expect to see both. So, in the lancer rom, I can copy Mitsu.kids auto tephra rom stuff in, and see the knock thresholds in a 1D table, but also as he says the 2D tables (and I confirmed) still show up there as well.
I'm thinking....perhaps the evo's are missing the table that might straighten us out. Oh, side note, the value in the base lancer rom for 4000 rpm and up is 255, which I am guessing means "maximum sensitivity, no "reduction for noise at low rpm", so I doubt that much "up top" knock is phantom...only the low stuff, specifically at 2250-2500 rpm
Also, check https://www.evolutionm.net/forums/en...detection.html that post. The first post has a link to an xls spreadsheet with graphs of each filter map....they are no where near the same as the stock lancer ones. Not sure why there are a lot of them, or how we would compare them to ours....but I'm betting number 1 is the most important, and it sure as heck doesn't match.
what he did will only work for auto lancer tephra since it came from a lancer, not an evo. im currently doing that right now, but before i flash the modified rom, i need to do some baseling logs first from the stock rom.
Last edited by ClixT; Nov 22, 2010 at 11:32 AM.






