Look at post two. It tells you exactly where to put the file.

You then have to set the path (the program asks you for it) where it can find the definitions for evoscan.txt

 

i read the post, i dont have that directory that i saw... is it somewhere else ? im very computer literate, but i feel like a dumbass here with this program... am i suppose to create the folder... name it that and then create the path ? or is there an existing directory

 

Go to "program files."

Look for the Dataloglab folder.

The folder should be somewhere in there.

If not, run a search and find the folder. It should be in there. It's filled with all the other definitions for the other cars it supports.

 

Sweet, thank you MalibuJack.

I changed MDP to MAP:
[Column]
Name=MAP
Description=MAP
ColumnTitle=MAP
DataItemID=71
Type=1
ColumnDecimalPlaces=1

I also added:
[Column]
Name=LoadCalc
Description=LoadCalc
ColumnTitle=LoadCalc
DataItemID=73
Type=1
ColumnDecimalPlaces=3
[Column]
Name=O22
Description=O2 Sensor 2
ColumnTitle=O2Sensor2
DataItemID=74
Type=1
ColumnDecimalPlaces=4
DisplayDecimalPlaces=4
[Column]
Name=AirVolume
Description=Air Volume
ColumnTitle=AirVol
DataItemID=75
Type=1
ColumnDecimalPlaces=0

 

i just did a search, no folder anywhere, this is BS lol... please help

 

I don't recall where the 'default' location of the folder is, but if you open DLL, go to customise/options, click on the "file locations and power graph" tab, and look at the 3rd box down from the top. That path is where you need to place the evoscan.txt file. If the box is empty, make one up!

 

No folder necessary (if you really want to put it somewhere it should be in a directory called Universal Data Log Formats) But just save the file somewhere you can find it easily, then go into options, then the File locations and Power graph tab, then under the path to universal data log format file, click the button with three dots (...) and navigate to that path, then click the load button..

From there you can then load your CSV files in the app itself.

I really don't know how to explain that in a more descriptive manner.

 

Thanks.. I'll merge this into the existing logger definition.. It should override or replace missing items if these exist instead.

 

ive got a question... is there anything you need to do to setup evoscan in order to log the data properly... i logged a run in a fairly modded viii today, added the map into DATALOGLAB and it came out saying 161 hp..... im sure it is something i was doing. anyone got any suggestions ?

 

Honestly, I have not played with Evoscan .97 and gotten any logs to try to make sense out of.

I suspect its one of two things, either your setup (wrong gear, or something else in your pull) and how you made your pull... OR the samples are not loading via timestamps. I would need to see the raw format of the logs to know for sure.

 

sounds like your using the car deffinations for a Miata (default). Check the listings of available cars, MalibuJack made a profile for the EVO, you have to find it on the list and move it to the top. That way it will always default to that car when you do the calcs.

 

+1 what he said.

You are probably using the miata car def. Choose Evo VIII from the pull down menu.

 

no, i had the evo selected... what i think happened is, we did a pull from 3d gear on, and it was reading second showing 161, when i changed the gear to 3d, it jumped to 309 which makes more sense to me... but the graph still looked terrible but im assuming that its because it was logging from 3d through 5th....

when you guys are making your log... are you logging 1 gear and then stopping at the shift ? or are you logging an entire run ? it would make more sense to me to start the log before you start the pull and then stop when finished logging like on a dyno. Im pretty sure i got this right, just want a warm fuzzy

 

Yes, when you do "Dyno Pulls" you do the data from a single gear only..

start your pull on a flat road at around 2000rpm, run in a single gear through redline, then select only that range of items..

If you make gear changes, it will throw off the calculations and give you loops and all sorts of funky looking drawings.. LOL

 

Here's another cool part.. If you then move the power data back from the power graph to your regular graph and plot it, you can look at knock count, afr if you have a wideband, Load, timing, all relative to horsepower and torque.. Its VERY enlightening and is where this program really shines.

Typically if I have specific dyno runs, I clip them out of my logs FIRST and save them so I can always come back to them.. Then when I'm done I save the graphs and other data so I can do overlay comparisons.