Standalone Tactrix open port 2.0 Datalogging

[Chris@Rvengeperformance]

The openport 2.0 cable supports an amazing feature. 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 main thing you need to get started is an appropriate logcfg.txt in the root folder of the micro sd card. Insert the micro sd card into the tactrix openport 2.0 and then plug the openport's usb cable into your computer. 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.

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.

Thanks to a poster on geekmapped I had a good start by using a evo 5/6 file. It uses similar logging and parameters to us. I modified the file to point to a few of our specific parameters. 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.

There is one special thing you need to do. Evoscan support logging 2 requests IDs at the same time for one value. This is in part how the 2 byte load logging is possible. 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:

=((I2*256) + J2) *5/16

where I2 is request 02 column and J2 is request 03 column.

Then you'll have the option to start logging when you want:

conditionrpn = TPS,10,>
action = start
;

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.

Please let me know if anyone has any ideas or changes to make. You can add parameters to your logcfg.txt as you see fit.

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. I have tested this on my car, but not extensively, so if there are any errors please report. Keep in mind the cable will not log standalone if it is plugged into your computer at the same time.

; sample logging configuration file for openport 2.0
; must be named logcfg.txt and be placed in the root directory of the
; microSD card inserted in the openport in order to work

; this sample logs using the MUT-II protocol over the K-line, which works
; for many mitsubishis, including the EVO 8 and 9

;----------------mut2----------------

type=mut2				

; you can also set an OBD pin to a voltage, ground, or a high impedance state
; the first number is the OBD pin number, the second number is the pin voltage with the following values:
;
; 8000-18000 : voltage in millivolts for OP2 Rev C and earlier
; 5000-25000 : voltage in millivolts for OP2 Rev D and later
; -1         : set pin to high impedance (default state)
; -2         : pull pin to ground
;
; keep in mind that if you are applying a non-zero voltage to more than one pin, all of those voltages
; must be the same

; the following setpinvoltage sets OBD pin 1 to ground, which is needed to enable logging on older Mitsubishis
; it is commented out as it is not needed for newer models (e.g. EVO 8/9)
;

setpinvoltage=1,-2

paramname=TPS
paramid=0x17
scalingrpn=x,0.39215686,*

paramname=RPM
paramid=0x21
scalingrpn=x,31.25,*

conditionrpn = TPS,10,>
action = start
;
conditionrpn = RPM,7000,>
action = stop

paramname=KnockSum
paramid=0x26

paramname=TimingAdv
paramid=0x06
scalingrpn=x,20,-

paramname=InjPulseWidth
paramid=0x29
scalingrpn=x,0.256,*

paramname=AEMUEGO
paramid=0x39
scalingrpn=0.03913,x,*,10,+

paramname=2ByteLoadRAW02
paramid=0x02

paramname=2ByteLoadRAW03
paramid=0x03

paramname=FFUELTRIMLOW
paramid=0x0C
scalingrpn=0.1961,x,*,-25,+

paramname=FFUELTRIMMID
paramid=0x0D
scalingrpn=0.1961,x,*,-25,+

paramname=FFUELTRIMHIGH
paramid=0x0E
scalingrpn=0.1961,x,*,-25,+

paramname=FSTFT
paramid=0x0F
scalingrpn=0.1961,x,*,-25,+

paramname=RFUELTRIMLOW
paramid=0x4C
scalingrpn=0.1961,x,*,-25,+

paramname=RFUELTRIMMID
paramid=0x4D
scalingrpn=0.1961,x,*,-25,+

paramname=RFUELTRIMHIGH
paramid=0x4E
scalingrpn=0.1961,x,*,-25,+

paramname=PrimaryO2Front
paramid=0x13
scalingrpn=0.01952,x,*

paramname=PrimaryO2Rear
paramid=0x3E
scalingrpn=0.01952,x,*

[Greg E]

Great work man!

I've avoided it because it didn't seem necessary but I can setup a 1byte value separate of the 2 byte ones for logging purposes. They would lose just a little bit of resolution compared to the 2 byte values BUT they wont have the limitations of the normal 1 byte Values It's just more chunks of code to write but if there is enough demand, I'll set it up no prob.

[Chris@Rvengeperformance]

Great work man!

I've avoided it because it didn't seem necessary but I can setup a 1byte value separate of the 2 byte ones for logging purposes. They would lose just a little bit of resolution compared to the 2 byte values BUT they wont have the limitations of the normal 1 byte Values It's just more chunks of code to write but if there is enough demand, I'll set it up no prob.

I'm not sure that it is necessary, at least in my case it certainly doesn't bother me to run the extra column in excel.

Thank you for all the help, I wouldn't have figured out how to handle the 2 byte logging without it.

[jras312]

woohoo gunna grab a card tonight and test this out. Thanks for posting this!

[Monster Stealth]

Thanks for the write up. I am sure this will come in hand when I get my car up and running.

[3kgt1734]

Wow. This stuff is confusing. I was reading up on using the tactrix in conjunction with EcuFlash for my ralliart earlier and kinda made my brain numb. Is there a reason no one uses ecuflash for a 3s? Different processors maybe?

[sublime_whatigo]

Yes we use ecuflash for flashing and evoscan for logging.

[Boostaddict]

Very cool. I wondered how the standalone logging was configured for the OP 2.0. Now I have some insight Glad to hear that it will work for us!

[Chris@Rvengeperformance]

it works like a dream, now I don't have to worry about the laptop dying, and everyday is a chance to improve the tune.

[Chris@Rvengeperformance]

hey fellas I ran into something I wanted to make you aware of. I'm not sure if it is because of the standalone logging or if it always does it, but the openport 2 stays on and draws power as long as it is in the obd2 port.

This doesn't really matter except if you park your car for several days it may kill your battery.