openecu.org

by **Mingi** » Wed Jul 05, 2006 1:51 pm

Do I do anything other than plug in the LC-1 to my laptop to have evoscan log the output?

by **A418t81** » Wed Jul 05, 2006 4:48 pm

Mingi wrote:Do I do anything other than plug in the LC-1 to my laptop to have evoscan log the output?

Yeah, see if it actually will.

by **c-spec** » Wed Jul 05, 2006 4:57 pm

awsome job Evo4mad, also i will see if my zeitronix work with it. i think you have to set it up for the software to see what comm the signal is comming from.

by **andenbre** » Wed Jul 05, 2006 9:15 pm

I noticed that you added a custom request. that is fantastic I was just going to ask if there was a way to put our own requsts into the ecm to try and figure out some other data that way you are not the only one

I will be trying some requests over the next week or so and will let everyone know what I find.

by **MalibuJack** » Thu Jul 06, 2006 7:29 am

My contribution to the EvoScan project..

www.dataloglab.com

This is one of the best log analyzers I've ever seen, It has native support for many ECU's and has a universal importer tool that you can create a definition for EvoScan to digest its log files..

I dont have enough complete logs (all columns logged) to create a definition for the program, but I know for a fact some of you guys do, and have the time and patience to create a universal definition file for it..

Its well worth the effort to use this program, I used it for 2 years with my UTEC and does a nice job of calculating horsepower and torque along with visualizing all sorts of useful data...

If we want to use Data Log Lab, Either their software has to support hexidecimal, I doubt they will, or EvoScan should output should have an option to record data as a raw decimal conversion from hex.. let DLL definition file handle the other conversions.

by **laakness** » Thu Jul 06, 2006 10:57 am

Looks interesting. I may have time to do this.

by **epifan** » Thu Jul 06, 2006 11:58 am

MalibuJack wrote:www.dataloglab.com

This is one of the best log analyzers I've ever seen, It has native support for many ECU's and has a universal importer tool that you can create a definition for EvoScan to digest its log files..

Try ecuEdit :wink:

by **MalibuJack** » Thu Jul 06, 2006 12:30 pm

epifan wrote:
MalibuJack wrote:www.dataloglab.com

This is one of the best log analyzers I've ever seen, It has native support for many ECU's and has a universal importer tool that you can create a definition for EvoScan to digest its log files..

Try ecuEdit

Different type of application altogether..

I have made progress with the definition in the program though.. I should have a working definition by the weekend..

EvoScan .8 outputs its data in Decimal, and it has mostly appropriate header data that can be used by the software.

by **laakness** » Thu Jul 06, 2006 12:32 pm

I created this, which might help you MalibuJack. I can't seem to load it with the demo version though. It keeps telling me I have an Invalid Header Attribute but I've checked the spelling a million times with their help file and everything I have listed is valid. Maybe a second set of eyes will help.

Code: Select all: Edit: See Post below

by **laakness** » Thu Jul 06, 2006 12:44 pm

Now I'm confused. I took their DataDefinition example and thier column example and loaded in into a text file. I then tried to load that file as a Universal Data log format and it gave the same error message I mentioned above

by **laakness** » Thu Jul 06, 2006 1:00 pm

Ok, this loads and seems to work. Give it a try Malibu and let me know if it works for you.

Code: Select all: [DataLogDefinition] Name=EvoScan 0.8 Version=1.0 Comments=EvoScan Definition by Mike Laak (Laakness) FileExtension=csv FileIDTextLinesBefore=0 FileIDTextColumnsBefore=0 FileIDText=LogID ColumnHeadersLinesBefore=0 DataLinesBefore=1 DelimiterAsciiCharacter=44 [Column] Name=LogID Description=Log ID ColumnTitle=LogID DataItemID=51 Type=1 ColumnDecimalPlaces=0 DisplayDecimalPlaces=0 [Column] Name=LogEntryDate Description=Log Date ColumnTitle=LogEntryDate DataItemID=51 Type=1 ColumnDecimalPlaces=0 DisplayDecimalPlaces=0 [Column] Name=LogEntryTime Description=Log Time ColumnTitle=LogEntryTime DataItemID=51 Type=1 ColumnDecimalPlaces=0 DisplayDecimalPlaces=0 [Column] Name=LogEntrySeconds Description=Log Seconds ColumnTitle=LogEntrySeconds DataItemID=63 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=5 [Column] Name=AccelEnrich Description=Accel Enrichment ColumnTitle=AccelEnrich DataItemID=51 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=2 [Column] Name=C Temp Description=Coolant Temperature ColumnTitle=CoolantTemp DataItemID=23 Type=1 ColumnDecimalPlaces=2 DisplayDecimalPlaces=2 [Column] Name=RPM Description=Engine RPM ColumnTitle=RPM DataItemID=3 Type=1 ColumnDecimalPlaces=2 DisplayDecimalPlaces=0 [Column] Name=F Trim High Description=Fuel Trim - High ColumnTitle=FuelTrim_High DataItemID=51 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=3 [Column] Name=F Trim Low Description=Fuel Trim - Low ColumnTitle=FuelTrim_Low DataItemID=51 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=3 [Column] Name=F Trim Med Description=Fuel Trim - Med ColumnTitle=FuelTrim_Middle DataItemID=51 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=3 [Column] Name=Inj Pluse Width Description=Injector Pulse Width ColumnTitle=InjPulseWidth DataItemID=13 Type=1 ColumnDecimalPlaces=5 DisplayDecimalPlaces=3 [Column] Name=O2 Feedback Description=O2 Feedback Trim ColumnTitle=O2FeedbackTrim DataItemID=7 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=4 [Column] Name=O2 Description=O2 Sensor ColumnTitle=O2Sensor DataItemID=7 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=4 [Column] Name=TPS Description=TPS ColumnTitle=TPS DataItemID=17 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=3 [Column] Name=AirFlow Description=Air Flow ColumnTitle=AirFlow DataItemID=81 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=2 [Column] Name=Air Temp Description=Air Temperature ColumnTitle=AirTemp DataItemID=31 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=2 [Column] Name=Baro Description=Barometer ColumnTitle=Baro DataItemID=5 Type=1 ColumnDecimalPlaces=2 DisplayDecimalPlaces=2 [Column] Name=ISCSteps Description=ISC Steps ColumnTitle=ISCSteps DataItemID=51 Type=1 ColumnDecimalPlaces=1 DisplayDecimalPlaces=1 [Column] Name=Knock Description=Knock Count ColumnTitle=KnockSum DataItemID=30 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=2 [Column] Name=Timing Description=Timing Advance ColumnTitle=TimingAdv DataItemID=21 Type=1 ColumnDecimalPlaces=1 DisplayDecimalPlaces=1 [Column] Name=Battery Description=Battery Voltage ColumnTitle=Battery DataItemID=22 Type=1 ColumnDecimalPlaces=8 DisplayDecimalPlaces=3 [Column] Name=EGR Temp Description=EGR Temperature ColumnTitle=EGRTemp DataItemID=51 Type=1 ColumnDecimalPlaces=2 DisplayDecimalPlaces=1

by **djmikeymike** » Thu Jul 06, 2006 2:02 pm

did anyone try the widebands yet??

by **djmikeymike** » Thu Jul 06, 2006 6:02 pm

the wideband did not work i have the LM-1.......

but i had a problem when i started data logging...... i was idleing and i started
to data log my rpms jumped up to around 2500rpm and i throw a code... i turned the car off and started it back up everything was fine no code then i started to datalog and the same thing happened..... what is wrong???

Are you supposed to have both of the connecters hooked up when your logging or just the OB2 port?

by **MalibuJack** » Thu Jul 06, 2006 6:07 pm

Laakness... Definition works good, only there are spaces appended to the code you posted, you probably should attach it as a file to avoid issues.. I was almostt as far as you got when I noticed a issue.. DLLs definition files dont allow combining of column data...

Hence the One glitch I found, Evoscan breaks out the time and seconds as separate columns, they need to be combined otherwise you can only have 60 seconds of data displayed when it goes back to zero it all drops off the end... Hopefully Evo4Mad can give us a cumulatve seconds from start of logging column, or combine the time and seconds columns together.. I havent found a workaround other than to use the samples (LogID) but the software doesnt maintain a specific sample rate, so none of the time calculations work right..

Hamish, ya think you can accomodate something for us so we can also use this tool? Maybe release sourcecode so I can create a simple logger for this?

by **laakness** » Thu Jul 06, 2006 6:46 pm

Ah, nice catch. A simple perl script might be able to read in the CSV and combine those two fields to create one time field.

I was wondering why the data didn't look really long in the graphs :lol:

openecu.org

Mitsubishi Lancer Evolution 4/5/6/7/8/9 EvoScan Project v0.8

LC-1

Re: LC-1

Who is online