knochgoon24
DSM Wiseman
- 6,135
- 92
- Jan 29, 2008
-
Troy,
Michigan
There doesn't seem to be much info out the on the Openport 2.0 cable and its standalone logging feature. This thread is to help people get it setup, since this is a really nice feature. No more laptop in the car at autox or the drags. You can leave it in the pits.
This explains the feature:
openecu.org • View topic - Openport Stand-Alone Logging Beta
But as of today, it's 38 pages. Here's the basics:
-You need a MicroSD card. I'm using a 8GB one, but that's overkill. In my experience, 1 hour of datalogging uses about 4 MB. So that 8GB card I have is good for 2000 hours. Smaller cards may be faster since they can be formatted as FAT16 instead of FAT32. I'm getting about 175 samples / second with one formatted as FAT32. I'll have to swap it with the 1GB card out of my phone to see if it makes a difference. You can have up to 4GB and still use FAT16.
-Warning when using FAT16: You can only have 512 files in a folder. So make sure you occasionally move old logs to another folder.
-I have my LC-1 wired through my rear o2 sensor input. So I'm able to datalog it without updating to the new beta version of EcuFlash that's pickier about xml file format. You can update the firmware on the OP2.0 after updating EcuFlash. Then you can make a 3/32" stereo male-male cable to log your LC-1.
-Ceddy includes a sample logcfg.txt file with his Ceddymod pack. It is a great starting point. You can modify it to log what you need. The semicolon ; comments out lines. Use it to modify what logs without deleting it from the file.
-I don't know if it's necessary, but I changed all my parameter names in the logcfg file to match the Log Reference field in EvoScan.
But finally, the main point of starting this thread. Datalogs that are made using the standalone feature can't be directly opened in EvoScan due to a formatting issue. EvoScan adds 3 extra columns to the logs that the Openport doesn't do on its own. I got tired of manually adding the columns, so I made a little program in C++ that does it for you. It runs through the command line, but it works as far as I can tell. It's just a small (<50KB) file that adds the 3 columns necessary to make it so EvoScan can open the log.
Download File:
OP to EvoScan.zip - 4shared.com - online file sharing and storage - download (15KB ZIP)
Maybe I'll dust off the VisualBasic books and make something that looks a little nicer. If I do that, I'll also try and make a program to make creating the logcfg files easier.
This explains the feature:
openecu.org • View topic - Openport Stand-Alone Logging Beta
But as of today, it's 38 pages. Here's the basics:
-You need a MicroSD card. I'm using a 8GB one, but that's overkill. In my experience, 1 hour of datalogging uses about 4 MB. So that 8GB card I have is good for 2000 hours. Smaller cards may be faster since they can be formatted as FAT16 instead of FAT32. I'm getting about 175 samples / second with one formatted as FAT32. I'll have to swap it with the 1GB card out of my phone to see if it makes a difference. You can have up to 4GB and still use FAT16.
-Warning when using FAT16: You can only have 512 files in a folder. So make sure you occasionally move old logs to another folder.
-I have my LC-1 wired through my rear o2 sensor input. So I'm able to datalog it without updating to the new beta version of EcuFlash that's pickier about xml file format. You can update the firmware on the OP2.0 after updating EcuFlash. Then you can make a 3/32" stereo male-male cable to log your LC-1.
-Ceddy includes a sample logcfg.txt file with his Ceddymod pack. It is a great starting point. You can modify it to log what you need. The semicolon ; comments out lines. Use it to modify what logs without deleting it from the file.
-I don't know if it's necessary, but I changed all my parameter names in the logcfg file to match the Log Reference field in EvoScan.
You must be logged in to view this image or video.
You must be logged in to view this image or video.
But finally, the main point of starting this thread. Datalogs that are made using the standalone feature can't be directly opened in EvoScan due to a formatting issue. EvoScan adds 3 extra columns to the logs that the Openport doesn't do on its own. I got tired of manually adding the columns, so I made a little program in C++ that does it for you. It runs through the command line, but it works as far as I can tell. It's just a small (<50KB) file that adds the 3 columns necessary to make it so EvoScan can open the log.
You must be logged in to view this image or video.
Download File:
OP to EvoScan.zip - 4shared.com - online file sharing and storage - download (15KB ZIP)
Maybe I'll dust off the VisualBasic books and make something that looks a little nicer. If I do that, I'll also try and make a program to make creating the logcfg files easier.
Last edited by a moderator: