1 : set pin to high impedance (default state) 5000-25000 : voltage in millivolts for OP2 Rev D and later 8000-18000 : voltage in millivolts for OP2 Rev C and earlier the first number is the OBD pin number, the second number is the pin voltage with the following values: you can also set an OBD pin to a voltage, ground, or a high impedance state for many mitsubishis, including the EVO 8 and 9 this sample logs using the MUT-II protocol over the K-line, which works microSD card inserted in the openport in order to work must be named logcfg.txt and be placed in the root directory of the sample logging configuration file for openport 2.0 Keep in mind the cable will not log standalone if it is plugged into your computer at the same time. I have tested this on my car, but not extensively, so if there are any errors please report. I am a noob at working on these things, but thought I'd share this data because it did take me a while to put all this together and the standalone logging is extremely useful. You can add parameters to your logcfg.txt as you see fit. Please let me know if anyone has any ideas or changes to make. 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 SD logging