I tried searching but not much luck.

I would like to know how you guys log exactly and what are the important things you are logging and taking into consideration when tuning.

Do you just go out and do one 3rd gear pull from 2500-7500 rpm and then study the log and make changes to the maps or do you do multiple pulls and look at averages?
Do you do any other kind of driving for logs?

Thanks

 

I log, speed,load,rpm,maf,inlet temp, knock sum,octane flag,timing.
I start with a 3rd gear run multiple times on flat road at least 6. times/ look at data if all is good. go home and redo it again. if all good. add timing/fuel/mivec redo process again.
keep doing this until knock or your slower. then back off fuel/timing/mivec.
do process again. if ok now do 1st-2nd gear run and see if there is any problems.
then finally I do a full out 1-2-3-4 run. then find a hill and varying roads to test out the tune. Finally on the freeway I put it in 5th gear at 70mph and WOT it and see any problems.
TOp things I look for is knock and accelation (0-70mph in how man seconds)

 

My .02

I would start w/ going out and doing 3-4 pulls from 2000 - 7500 (3rd gear) Consistency is what your looking for so the more logs you do, the better. Try and log in the same spot every time, on a flat surface!
Fist thing... If your stock, dont be alarmed by all of the knock. @ whatever rpm/load you see in your log... For every 3 counts of "knock" "retard or take away" 1* in that rpm/load cell. So if your seeing 9 counts, you would retard the timing 3* in that rpm/load cell. To correct this you would need "ECUFLASH" to flash the car w/ the new info... Lots of info on here to read up on reguarding tuning...
I log:

TPS
RPM
WGDC
2ByteLoad
Boost (if you have a JDM/Evo X map sensor)
WB (if you have 1)
Knock (most important)
Timing
Load Error (dont really need to worry bout unless tuning)
WGDCC (dont really need to worry bout unless tuning)

 

How flat???

Thanks guys, very helpful so far.

 

FLAT! any variance on plain will affect the load/boost.

 

i like to do my tuning up hills so it loads the car more and will make problems in the tune more apparent

 

So is it flatness or consistency that matters. I have a very slight incline street close to my house that i like to log on because its easy to watch for cops and not much traffic.... so instead of doing pulls on my way up, and on my way down, can i just do pulls on the way up only to keep consitency?

 

consistency

 

Lol... You want a flat surface to log on, and consistancy in the logs! Like I said any variance in plain will affect the boost/load curve. I.E. If you keep logging on an incline/decline, and adjust your maps to the logs, you will end up throwing off the boost/load curve, cause you wont see the same load on straight/flat plain/street!
Most commonly used are freeway onramps. Wait till you get to the top of the onramp, check for the popo, then smash on it @ 2000-7500.

Now if your not considering tuning @ this point, (which I dont think u are) you can log anywhere, and just look for knock. If you log uphill, it will load up the car a lil more. Which would result in a slight increase in boost. And vice versa for downhill.

 

I am new to this also, I have evoscan 2.5, the problem that I have is that I do not know how to analyze the data. How would I go about it, I done some logs, but I do not know how to analyze the data.

 

I am in the process of my first tune actually. That is why i want to know the best way to log.
I was getting different values on some of the logs, so i was taking averages, but its confusing, i want my logs to be close in numbers so there isnt that guesswork.

 

You have 2 ways to go about it...
1. you can actually look at the logs in a graph inside Evoscan. Click on the graph icon @ the top, choose open log (first one) and double click the log you wanna see.

2. you can open the logs through the saved datalogs folder, and open w/ Excell!

 

are you guys editing your tables @ all, or just logging? You dont need to logs to be exact. You wanna be w/in -5 "load error" points of what you actually have in your maps. Obviously you would wanna be perfect, but neither of us are there yet! so shoot for -5 "load error" points through out the entire log. I have for the most part -5 "load error" and less in my logs from whats actually in my BDELs and a few spots that are perfectly on point w/ my BDELs. example if you have @ 3500/load of 240 in your BDEL+BCLO, you wanna be w/in - 5 "load error" of the 240, so like 235-240 would be perfect for that rpm/load cell. You do NOT wanna wanna overshoot the BDEL, cause the ECU will correct for that!

hope that makes sense for ya.

 

Uh, what language are you speaking...
Im not familiar with those acronyms.

And yes, im editing tables.

 

if you are editing your tables, u should be familiar w/ those acronyms! They are called exactly the same things when you pull up your rom in ecuflash!
BDEL= Boost Desired Engine Load
BCLO= Boost Controll Load Offset
MWGDC= Max WasteGate Duty Cycle.

These tables are what controll "boost"

"Load Error" = how far off you are from your BDEL.

I would suggest reading the "how to tune an evo" by NJ, thread as well as TB's version of it. I read both of them about 5 times before I understood any of it, and then I still needed to get hands on to really understand it!
Trial and error! Keep logging and comparing to your maps, and before you know it, u will understand.