I have mine set to log all the time by starting at 10% or above, but once my tune is more solid I will consider increasing this to a higher value to keep from logging constantly. Then you'll have the option to start logging when you want: Where I2 is request 02 column and J2 is request 03 column. Unfortunately I am not currently aware of a way to do this in the logcfg.txt file, so what I have done is logged request 2 and request 3 seperately and I use excel to combine them with this formula: This is in part how the 2 byte load logging is possible. Evoscan support logging 2 requests IDs at the same time for one value. There is one special thing you need to do. The o2 parameters have recently been discovered to not be named correctly, once the new evoscan data files are released I will edit the code below to reflect the changes. I modified the file to point to a few of our specific parameters. It uses similar logging and parameters to us. Thanks to a poster on geekmapped I had a good start by using a evo 5/6 file. There are many options in the logcfg.txt file, but below I have a very simple one that will play fairly well with Greg's chromed mods, namely support of wideband logging and the 2 byte load logging. The sd card will now show up as a drive letter, this is how you will add the logcfg.txt and retrieve your logs later.

Insert the micro sd card into the tactrix openport 2.0 and then plug the openport's usb cable into your computer. The main thing you need to get started is an appropriate logcfg.txt in the root folder of the micro sd card.

You can insert a micro sd card into the device and with the appropriate setup it will automatically output log files in the root folder. The openport 2.0 cable supports an amazing feature.

Tactrix openport 2.0 evo x