Trying to understand timing map
Account Disabled
iTrader: (38)
Joined: Aug 2005
Posts: 9,319
Likes: 1
From: Virginia Beach, Virginia

I don't want this to become a pissing match, but the purpose of this thread was to "understand timing maps". Comments about what a person does or does not need, is really not necessary. Who are you to determine what someone else "needs", or wants for that matter?
Please help these people to understand what they are wanting to try to learn rather than trying to stop them.
Thank you.
OK so anyway. Back on topic.
Last edited by Mellon Racing; Feb 18, 2010 at 08:40 AM.
Thread Starter
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
Its no problem. I understand what you are saying Chris. I agree ive got a lot going on just trying to learn the basics here...And I understnad what your saying as well Paul. I think one of the main reasons that I have put off doing any of tephra's mods is that there was so many additions that I wasnt sure I was going to use. I just thought the CEL knock light is a great idea and NLTS of course. But I still dont really need that. Just the CEL ot monitor things.
Thanks guys
-Ethan
Thanks guys
-Ethan
The flash cel on knock feature is an great one. I have yet to try the NTLS but I know a local kid with a virtually stock 9 running 7.7 consistently in the 1/8mi. I have seen him hit a few 7.6 runs as well. I am going to try it some track day soon.
heres my small map fully converted over to big map. this is somewhat conservative for a e85 car isnt it? 
also what are the advantages if i smoothen it more around the higher load low rpm cells? does this allow the car to run more timing if you ease into it slowly? i imagine a smoother transition will result in a better performing car?

also what are the advantages if i smoothen it more around the higher load low rpm cells? does this allow the car to run more timing if you ease into it slowly? i imagine a smoother transition will result in a better performing car?
It is very blocked. Your mid pull areas are not aggressive at all. Neither is your top end.
Your best bet is to go with what you have and log a few pulls. Plot where you are on the table based on the pulls. Then you can see where you can make changes.
Hopefully you knew this already.
Big jumps in timing have a tendency to induce knock conditions because the ECU will be interpolating a value rather than using a known value. Thus, smoother is better and no big jumps from one cell to the next.
Your best bet is to go with what you have and log a few pulls. Plot where you are on the table based on the pulls. Then you can see where you can make changes.
Hopefully you knew this already.
Big jumps in timing have a tendency to induce knock conditions because the ECU will be interpolating a value rather than using a known value. Thus, smoother is better and no big jumps from one cell to the next.
It is very blocked. Your mid pull areas are not aggressive at all. Neither is your top end.
Your best bet is to go with what you have and log a few pulls. Plot where you are on the table based on the pulls. Then you can see where you can make changes.
Hopefully you knew this already.
Big jumps in timing have a tendency to induce knock conditions because the ECU will be interpolating a value rather than using a known value. Thus, smoother is better and no big jumps from one cell to the next.
Your best bet is to go with what you have and log a few pulls. Plot where you are on the table based on the pulls. Then you can see where you can make changes.
Hopefully you knew this already.
Big jumps in timing have a tendency to induce knock conditions because the ECU will be interpolating a value rather than using a known value. Thus, smoother is better and no big jumps from one cell to the next.
my only concern tuning wise is whats the best way to log load with the current tephra roms? im under the impression i can get a good accurate reading by changing 2byte load to 1byte factor on rom to about 1.6 and than set it from 1.2 in evoscan to 1.6 and use the 1byte as an accurate log of load? other than that i understanding everything else.
Ok....by changing the factor higher you will have the logging ability to hit higher cell (I think that is how it works). But based on your load, I wouldn't change it from 1.2. You have plenty of room to go higher before you will bust the table.
How much boost are you running??
How much boost are you running??
Im going to go way paste 306 soon though, i plan on running 38psi if e70 allows it on my new setup. the higher the number the more load you can log without the load capping off, thats what i got from what tephra said on here
loadfactor of 1.2 will allow a Max Loggable Load of 306, 1.3 = 331 , so i figured atleast set it to 1.6
loadfactor of 1.2 will allow a Max Loggable Load of 306, 1.3 = 331 , so i figured atleast set it to 1.6
Last edited by tscompusa2; Feb 18, 2010 at 11:40 PM.
I was going to say....you should be at a much higher load. I see 320ish with my green at 27psi.
Try 1.2 first....then up it as you deem necessary. I believe that you lose resolution the higher it is.
Try 1.2 first....then up it as you deem necessary. I believe that you lose resolution the higher it is.
ya you do lose resolution, but tephra thinks that doesnt really matter. but i will set it to 1.3 for now thats still only 330load. and as i said above 38lbs is going to be flowing like 55lb/min certainly going to hit higher loads then 330. im looking for 600whp+ in this current setup.
hey man.. nevermind im already maxing that load. my logs show 306 max, and 1.2 = 306 max. i bet im closer to 400 load right now.
last time i had the car out vdr evom mode showed 540hp and 480tq
last time i had the car out vdr evom mode showed 540hp and 480tq
Thread Starter
Evolved Member
iTrader: (3)
Joined: Mar 2007
Posts: 562
Likes: 0
From: Connecticut / Vermont
I gotta go buy some parts...
HELL YES!!
i will be pined to my seat. lol


