Trying to understand timing map
Thread Starter
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
Is that the "phantom knock?
Quick list of mods: for refference
Hallman MBC @22psi
Buschur TBE with test pipe
Open element filter (K&N MAF adapter with the stock tube)
GSC S2 cams
GSC beehive springs
ETS LICP
and i think thats it for mods....
-Ethan
Last edited by ethan169; Feb 23, 2010 at 11:20 AM.
Tip in knock is when you just start to tip in the throttle and come onto boost. Common issue in 03s.
Phantom knock is when you get random knock for no apparent reason. Often hard motor mounts, big cams and/or metal to metal contact are the causes.
Phantom knock is when you get random knock for no apparent reason. Often hard motor mounts, big cams and/or metal to metal contact are the causes.
Thread Starter
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
Got it. So as far as tip in knock how is that resolved? More updated roms such as tephras V7?
and for the phantom knock I guess it could be from my exhaust if something is actually loose. (wich i doubt) and from the s2's? Is there a way to get rid of it? Or is this just the nature of the beast?
and for the phantom knock I guess it could be from my exhaust if something is actually loose. (wich i doubt) and from the s2's? Is there a way to get rid of it? Or is this just the nature of the beast?
Tip in knock is solved by doing the following.....
The "Knock Load" table
Raise the 2500, 3000, and 3500 rpm load values by 10.
Phantom knock is resolved by first fixing any mechanical issues then.....
Lower the "knock sum decay timer" to = 80
raise the "knock multiplier" low and mid by one or 2 points.
The "Knock Load" table
Raise the 2500, 3000, and 3500 rpm load values by 10.
Phantom knock is resolved by first fixing any mechanical issues then.....
Lower the "knock sum decay timer" to = 80
raise the "knock multiplier" low and mid by one or 2 points.
Tip in knock is solved by doing the following.....
The "Knock Load" table
Raise the 2500, 3000, and 3500 rpm load values by 10.
Phantom knock is resolved by first fixing any mechanical issues then.....
Lower the "knock sum decay timer" to = 80
raise the "knock multiplier" low and mid by one or 2 points.
The "Knock Load" table
Raise the 2500, 3000, and 3500 rpm load values by 10.
Phantom knock is resolved by first fixing any mechanical issues then.....
Lower the "knock sum decay timer" to = 80
raise the "knock multiplier" low and mid by one or 2 points.
This is for both 96530706 and 95170705.
d
Your idle was mostly affected by lowering your timing. Did you change the idle RPM as well???
The Idle Stability Timing Control table does exactly what is say.... stabilizes idle. At first we thought that raising the value helped.....I have since discovered, as you have, that idle does suffer a little if it is raised. Thus, I leave it at 128. The second value in the table will help if you are getting big swings in idle timing. Lowering it will tighten up those swings.
The Idle Stability Timing Control table does exactly what is say.... stabilizes idle. At first we thought that raising the value helped.....I have since discovered, as you have, that idle does suffer a little if it is raised. Thus, I leave it at 128. The second value in the table will help if you are getting big swings in idle timing. Lowering it will tighten up those swings.
Is this table discovered in 88590015? Thanks in advance!!
Thread Starter
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
Ok, so thanks to Appauldd and tscompusa I am up and running with Tephra V5.10 and everything is working great! Although im really only using the CEL flash on knock. But Im learning a lot more about the ECU and my xml's are now updated with what looks like more current information and not inflated with crap I dont use.... I found the "known" periphery bits listed on the Evo ECU wiki page and added that so instead of the bit0-15 I have definitions for the known values.
My MUT table looks to be modified for 2byte load,rpm. I havent checked airflow nor have I ever really used it while logging. But now Im finally catching up on this 2byte stuff and seeing people doing the 2byte to 1byte mod. I understand the reasons for this but dont see exactly where I have to modify things.
So #1 do I need to do this?
#2 how or where is the actual information on what to do. All I have read so far is that I need to change my factory in both ecuflash xml and my evoscan xml to be the same. 1.1 or 1.2 etc.... Im hitting max loads of about 290 once in a great on a hard down shift ill see 300 so I figure 1.2 is good. Capping me off at 310 load. using 1.1 would be too low at 280 I think. Especially since im only loose in small amount of resolution.
Isnt the reason for logging 2byte load more resolution anyway? Im confused?
Another note the UTEC is removed! I couldn't get home last night to Vt because of the massive amounts of snow thats coming down, so for a temp replcement of my ecu retaining tray I made one out of 1/8 inch aluminum at work. Took about 10 min
btw this is the thread that I was trying to get some info from 2byte to 1byte load mod
EDIT: hmm just took another look and maybe its more complicated then just changing things in the XML and its just "included" in V7. Once I get this tune sorted out Ill most likely switch to V7 to see how smooooth these big maps really can be..
-Ethan
My MUT table looks to be modified for 2byte load,rpm. I havent checked airflow nor have I ever really used it while logging. But now Im finally catching up on this 2byte stuff and seeing people doing the 2byte to 1byte mod. I understand the reasons for this but dont see exactly where I have to modify things.
So #1 do I need to do this?
#2 how or where is the actual information on what to do. All I have read so far is that I need to change my factory in both ecuflash xml and my evoscan xml to be the same. 1.1 or 1.2 etc.... Im hitting max loads of about 290 once in a great on a hard down shift ill see 300 so I figure 1.2 is good. Capping me off at 310 load. using 1.1 would be too low at 280 I think. Especially since im only loose in small amount of resolution.
Isnt the reason for logging 2byte load more resolution anyway? Im confused?
Another note the UTEC is removed! I couldn't get home last night to Vt because of the massive amounts of snow thats coming down, so for a temp replcement of my ecu retaining tray I made one out of 1/8 inch aluminum at work. Took about 10 min
btw this is the thread that I was trying to get some info from 2byte to 1byte load mod
EDIT: hmm just took another look and maybe its more complicated then just changing things in the XML and its just "included" in V7. Once I get this tune sorted out Ill most likely switch to V7 to see how smooooth these big maps really can be..
-Ethan
I've read over this thread a few times simply because its been REALLY informative. Thanks to not only all the guys lending a hand, but to also ethan for posting as many questions as he has. I'm about to take this leap myself in the coming months and even in reading this stuff, I'm feeling a bit less intimidated than I first felt when starting with the "how to tune your evo" thread. Not quite over to the tactrix cable and the open source alternatives, but I HAVE been able to take a look at the accesstuner street software and try to make the correlation. Although I've not actually changed the tune for my car yet (no wb quite yet), I've been following along with the thread and modifying tables just to get familiar. In not so many words, thanks again to all on this thread. Communities kinda rule when people wanna help out.
Thread Starter
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
Boozeup&riot: I'm glad it's helped you out too! I'm glad I posted my initial questions and timing maps. Generally when I ask a question or when I see other people asking questions the thread gets filled with useless garbage or people screaming to search and what not. After corraeponding with these guys in this thread mostly Ive actually started to make a few chnages here and there. Not to mention finally convert over to tephras amazing patches. I've been following tephras threads and the how to tune an Evo thread for the past two years now. I finally feel confident enough to play around in the ecu (little by little of course). Kos likley because ive received solid answers for questions I've had for a long time.
Communities do rule... When people actually help eachother out.
Communities do rule... When people actually help eachother out.
Thread Starter
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
But yeah start a thread!
Oh and anyone have any more info on the 2byte questions i posted a few posts back?
Thanks!
-Ethan
I find that 2byte has spikes sometimes and 1byte seems to be more stable. I would put your 1byte up to a level that you will not hit. It does not need to be super high but give yourself a little room.



