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.

9 years later... there still doesn’t seem to be a ton of info for standalone logging with regard to how to set it up. I just picked up a new Openport 2.0 and downloaded the most recent version of EcuFlash from Tactrix. I didn’t find a lot of clear cut answers on how to set it up, without getting into a lot of coding.

So here’s what I did: hopefully this will help others.

Disclaimer: this was done on a 98 GST with Factory ECU. Hardware was the Tactrix OP 2.0 with Mitsu Adapter, and a 32GB MicroSD card. Software was EcuFlash version 1.4X.XXX.

To start logging:
On your laptop, find the logging samples folder in the EcuFlash program file directory.
There are a lot of .txt files for various makes and models of cars. Two are clearly Mitsubishi. One is for the K-Line ECU.
Open your MicroSD card folder. At the root folder, copy the K-Line.txt file from the EcuFlash logging samples folder onto the SD card. You need to rename the file as “logcfg.txt”
Now put the MicroSD card into the OP2.0 and plug it into your OBD port. DO NOT plug anything into the OP2.0 USB port.
Go for a drive.
When done, unplug the OP2.0 and remove the MicroSD cars.
That should be it.

One drive for me and it generated single Excel table. It was logging 36 values at 8 times per second. So a lot of data.

There are plenty of ways to select which values to log and other hacks, but you can figure it out on your own time.

That’s it. I did not need to download anything other than EcuFlash and I did not need to do anything other than copy, paste and rename a single file.

Hope this helps.

Its so much easier to log with the SD card on the Openport. Ive got mine set to log both the ecu parameters via obd2, but also AFR from my UEGO via 2.5mm stereo jack. Everything is configured with a simple text file which allows you to set what parameters are logged, their order and priority. But also, you can start, stop, and create new logs based on any number of driving conditions, or even the defroster switch for example.





Kodi nox

roukyweal20 said:

Its so much easier to log with the SD card on the Openport. Ive got mine set to log both the ecu parameters via obd2, but also AFR from my UEGO via 2.5mm stereo jack. Everything is configured with a simple text file which allows you to set what parameters are logged, their order and priority. But also, you can start, stop, and create new logs based on any number of driving conditions, or even the defroster switch for example.

Click to expand...

So what lines did you use in your txt file to enable defroster-activated logging?

I have my file set up the way I like it, but that would be a really cool feature to add

2Gjunkie said:

9 years later... there still doesn’t seem to be a ton of info for standalone logging with regard to how to set it up. I just picked up a new Openport 2.0 and downloaded the most recent version of EcuFlash from Tactrix. I didn’t find a lot of clear cut answers on how to set it up, without getting into a lot of coding.

So here’s what I did: hopefully this will help others.

Disclaimer: this was done on a 98 GST with Factory ECU. Hardware was the Tactrix OP 2.0 with Mitsu Adapter, and a 32GB MicroSD card. Software was EcuFlash version 1.4X.XXX.

To start logging:
On your laptop, find the logging samples folder in the EcuFlash program file directory.
There are a lot of .txt files for various makes and models of cars. Two are clearly Mitsubishi. One is for the K-Line ECU.
Open your MicroSD card folder. At the root folder, copy the K-Line.txt file from the EcuFlash logging samples folder onto the SD card. You need to rename the file as “logcfg.txt”
Now put the MicroSD card into the OP2.0 and plug it into your OBD port. DO NOT plug anything into the OP2.0 USB port.
Go for a drive.
When done, unplug the OP2.0 and remove the MicroSD cars.
That should be it.

One drive for me and it generated single Excel table. It was logging 36 values at 8 times per second. So a lot of data.

There are plenty of ways to select which values to log and other hacks, but you can figure it out on your own time.

That’s it. I did not need to download anything other than EcuFlash and I did not need to do anything other than copy, paste and rename a single file.

Hope this helps.

Click to expand...

Man, this just saved me from making permanent decisions in temporary shituations… I’ll def know for sure when I make it back home. Decided to give it a break from being worked on A cpl days. Lol. Now I just need someone to roughly detail the values of everything once, maybe twice, maybe. But I think I’ll be able to work with this setup, hopefully.