Evo X Logging
Jun 6, 2009 | 06:02 PM
#136
Jun 6, 2009 | 06:52 PM
#139
I've had this problem if I have the log file open in Excel and then try to run the logger. You don't have the log file open do you? Or perhaps the program doesn't have permission to write to the folder that the .exe is in. On Vista, this can happen if you have the .exe under "Program Files" somewhere. Try putting it on the desktop instead as a test. Otherwise, you may also need to run the .exe as administrator.
Jun 6, 2009 | 10:09 PM
#140
tephra and crew, you can import these values into an excel spreadsheet csv file(comma seperated value) and it will put each portion of the log into columns to make it easier to read.
also, if you guys wanted we could make(or i) could make a spreadsheet with formulas so that way when you import this information into the spreadsheet it will convert everything into what the reading is that we would like to see. for example the Injector Duty Cycle = Injector Pulse Width * RPM / 1200, well that could be written in a formula inside of excel to convert the numbers into something more readible for the technically challenged!
also, if you guys wanted we could make(or i) could make a spreadsheet with formulas so that way when you import this information into the spreadsheet it will convert everything into what the reading is that we would like to see. for example the Injector Duty Cycle = Injector Pulse Width * RPM / 1200, well that could be written in a formula inside of excel to convert the numbers into something more readible for the technically challenged!
Last edited by olsookie; Jun 6, 2009 at 10:10 PM. Reason: spelling
Jun 6, 2009 | 11:58 PM
#142
tephra and crew, you can import these values into an excel spreadsheet csv file(comma seperated value) and it will put each portion of the log into columns to make it easier to read.
also, if you guys wanted we could make(or i) could make a spreadsheet with formulas so that way when you import this information into the spreadsheet it will convert everything into what the reading is that we would like to see. for example the Injector Duty Cycle = Injector Pulse Width * RPM / 1200, well that could be written in a formula inside of excel to convert the numbers into something more readible for the technically challenged!
also, if you guys wanted we could make(or i) could make a spreadsheet with formulas so that way when you import this information into the spreadsheet it will convert everything into what the reading is that we would like to see. for example the Injector Duty Cycle = Injector Pulse Width * RPM / 1200, well that could be written in a formula inside of excel to convert the numbers into something more readible for the technically challenged!
You can also make graphs like tephra posted on the first page of this thread.
Jun 8, 2009 | 08:14 AM
#144
tephra, i have rom 8260015.
1. i downloaded the executable
2. i downloaded the txt file and renamed it to config.txt
3. i placed both above in folder on my desktop.
question, is what i did above ok?
can you send me an updated 8260015.xml file?
also, once i put that file back to ecuflash directory, i need to resave my rom and then reflash?|
Thanks
1. i downloaded the executable
2. i downloaded the txt file and renamed it to config.txt
3. i placed both above in folder on my desktop.
question, is what i did above ok?
can you send me an updated 8260015.xml file?
also, once i put that file back to ecuflash directory, i need to resave my rom and then reflash?|
Thanks
Jun 8, 2009 | 10:09 AM
#145
EvoScan v2.6beta14.zip now supports the above mentioned Mode23 Datalogging.
EvoScanv2.6Beta14.zip (evoscan.exe and \datasettings\data.xml file included, overwrite the files into your existing evoscan installation directory)
This version also supports upwards of 120 samples per second datalogging via CAN for EvoX!
In the data.xml file the requestid must begin with 23 and then followed by the RAM location you wish to read. For example RPM 0x808746 just enter the RequestID="23808746" and the ResponseBytes="1" or ResponseBytes="2" for PSIG and Load and IPW.
The inbuilt dataitem editor will be available in the next version, there is currently an xml bug so I disabled the editor for now.
I am working on updating all the EvoX formulas. expect to see another release very shortly.
EvoScanv2.6Beta14.zip (evoscan.exe and \datasettings\data.xml file included, overwrite the files into your existing evoscan installation directory)
This version also supports upwards of 120 samples per second datalogging via CAN for EvoX!
In the data.xml file the requestid must begin with 23 and then followed by the RAM location you wish to read. For example RPM 0x808746 just enter the RequestID="23808746" and the ResponseBytes="1" or ResponseBytes="2" for PSIG and Load and IPW.
The inbuilt dataitem editor will be available in the next version, there is currently an xml bug so I disabled the editor for now.
I am working on updating all the EvoX formulas. expect to see another release very shortly.
Jun 8, 2009 | 11:46 AM
#147
EvoScan v2.6beta14.zip now supports the above mentioned Mode23 Datalogging.
EvoScanv2.6Beta14.zip (evoscan.exe and \datasettings\data.xml file included, overwrite the files into your existing evoscan installation directory)
This version also supports upwards of 120 samples per second datalogging via CAN for EvoX!
In the data.xml file the requestid must begin with 23 and then followed by the RAM location you wish to read. For example RPM 0x808746 just enter the RequestID="23808746" and the ResponseBytes="1" or ResponseBytes="2" for PSIG and Load and IPW.
The inbuilt dataitem editor will be available in the next version, there is currently an xml bug so I disabled the editor for now.
I am working on updating all the EvoX formulas. expect to see another release very shortly.
EvoScanv2.6Beta14.zip (evoscan.exe and \datasettings\data.xml file included, overwrite the files into your existing evoscan installation directory)
This version also supports upwards of 120 samples per second datalogging via CAN for EvoX!
In the data.xml file the requestid must begin with 23 and then followed by the RAM location you wish to read. For example RPM 0x808746 just enter the RequestID="23808746" and the ResponseBytes="1" or ResponseBytes="2" for PSIG and Load and IPW.
The inbuilt dataitem editor will be available in the next version, there is currently an xml bug so I disabled the editor for now.
I am working on updating all the EvoX formulas. expect to see another release very shortly.
Jun 8, 2009 | 05:14 PM
#150
Evoscan Mode23 XML for USDM
I've been working with Hamish and let him use my PC/Car to write this new Evoscan. Currently the supplied XML is set for the JDM (also AUSDM/EDM) so I went ahead and made a quick one for the USDM. Replace your current xml with this one and Mode23 will work
*edit, added new data.zip file
*edit, added new data.zip file
Last edited by SiC; Jun 13, 2009 at 02:55 AM.