Standalone Tactrix open port 2.0 Datalogging

[BlackStealth]

Why do you want to plug in two devices to the OBD2/MUT socket at the same time? Is it because you want to datalog via SD Card?

The LCDBC's second serial ports pretends to be an ECU, to allow programs such as Evoscan and HHH to make ECU datalog requests. There can only be one device plugged into the OBD2/MUT socket. The OBD2 Y-cables you see on ebay are used for monitoring/spying the protocol.

Just so this doesn't go off topic, please put LCDBC comments in this thread:
http://www.3sgto.org/3000gt-stealth-...tml#post305743

[green-lantern]

Why do you want to plug in two devices to the OBD2/MUT socket at the same time? Is it because you want to datalog via SD Card?

The LCDBC's second serial ports pretends to be an ECU, to allow programs such as Evoscan and HHH to make ECU datalog requests. There can only be one device plugged into the OBD2/MUT socket. The OBD2 Y-cables you see on ebay are used for monitoring/spying the protocol.

Just so this doesn't go off topic, please put LCDBC comments in this thread:
http://www.3sgto.org/3000gt-stealth-...tml#post305743

Yes

I don't really think this is off topic but I'll elaborate in your thread.

thanks!

[Unlogic]

I connect my laptop to the second serial port of the LCDBC and run EvoScan on it. That way I get the values on both the LCDBC and in EvoScan however a SD-card logging solution for the LCDBC would be a lot simpler.

[DrGonzo]

Just wanting to bump this back up as I'm just now getting around to setting this up. Doing some searching it does look like it is capable to handling the 1 or 2 byte responses from what I am reading in another thread on the evo forums.

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.

Here is what the EVO guys found:

If ResponseBytes is 1, nothing needs to be done.

For Example:
Code:

paramname=Timing
paramid=0x808a07
scalingrpn=x,20,-

If ResponseBytes is 2, add "databits=16".
For Example:
Code:

paramname=RPM
paramid=0x808746
databits=16
scalingrpn=x,3.90625,*

http://www.evolutionm.net/forums/evo...-computer.html

Maybe I am just late to the party on this. I wasn't finding much info on the SD card logging on this forum.

Thanks Forest for the logcfg.txt file. Saved me from having to build one out as that was specifically what I was searching to find.

[striker2]

Here is a thread where I posted my setup for the SD card logging, including how I am logging 2byte load and airflow. Its the second time that I post my config file in that thread but the link should go straight to it. I have also figured out the coolant temp logging issues (which also led me to notice a discrepancy in evoscan for coolant temp).
http://www.3sgto.org/threads/11884-T...l=1#post238422


There is also this thread which talks about SD card logging (with links to both the first thread i posted and the one we are currently in)
http://www.3sgto.org/threads/12794-O...067#post260067


But this is pretty much the extent of the info on this forum regarding SD card datalogging via Tactrix.

[Jimvr4]

I have also figured out the coolant temp logging issues (which also led me to notice a discrepancy in evoscan for coolant temp).

In the thread you linked you stated you had a discrepancy on coolant temp reported by Taxtrix and you hadn't yet worked it out. Have you since figured it out?

[striker2]

In the thread you linked you stated you had a discrepancy on coolant temp reported by Taxtrix and you hadn't yet worked it out. Have you since figured it out?

Yes. It turns out that I was looking at the wrong paramid. However I had been basing it off of evoscan which is why I was confused and couldnt figure out the problem. As it turns out, if you look around you discover that the PID for coolant temp on 98+ Mitsus isnt 0x07 (which is what is in evoscan for the 3S and what I was using on the tactrix) but actually 0x10 and the formula should be x*1.8-40 (not x*1.8+32). I noticed this when I was using evoscan to verify low fuel trims (I had made a change to the tune) and saw that my cooling fans didnt come on until evoscan said it was 205 degrees for the low and 215 for the high, even though my tune is set for the low speed fans to come on at 194 and high fans at 199. Using the new PID and formula the fans come on at the correct temp in evoscan and the tactrix datalogs the correct temp now as well.

[DrGonzo]

Thanks for the link to your logcfg file and the thread.

I did notice some errors in it though. When I tried to load it the out file showed errors with the naming of the 2 byte load parameters. Guess you can't use a number as the first character of a parameter name.

Coolant is also not configured correctly. I added in the formula along with logging WBO2 using Innovate. I'll try to remember to upload them tomorrow as they are on the shop computer.

[striker2]

Thanks for the link to your logcfg file and the thread.

I did notice some errors in it though. When I tried to load it the out file showed errors with the naming of the 2 byte load parameters. Guess you can't use a number as the first character of a parameter name.

Mine does not show any errors, but in case I made some changes that I dont remember doing (it has been a while) Ill check my cfg file tomorrow to compare and post an updated version of what I am using currently.

Coolant is also not configured correctly. I added in the formula along with logging WBO2 using Innovate. I'll try to remember to upload them tomorrow as they are on the shop computer.

Yes, coolant temp is what I had noted as being incorrect in that file, but I have since figured out the problem, as outlined in my last post just above yours.


Edit: I also just noticed that I was having problems with the air temp being accurate as well and looking at evoscan it seems like it has the same problem as coolant temp with using the wrong PID and formula for 98+ cars. I will have to change that and see if its more accurate tomorrow as well.

[striker2]

So after looking at the current logcfg file I am using I had made some changes, but not to any of the 2byte stuff (load or airflow). Some of the things are commented out since they dont need to be logged all the time and, like the method of telling it when to start logging, could be changed by simply removing the semi-colons in front of the lines. Also, both coolant temp and air temp now work properly.

 ; 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=TimingAdv
paramid=0x06
scalingrpn=x,20,-


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


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


paramname=Air1
paramid=0x00
scalingrpn=x
isvisible=0


paramname=Air2
paramid=0x01
scalingrpn=x
isvisible=0


paramname=2ByteAirFlow
scalingrpn=Air1,256,*,Air2,+,0.09828125,*


paramname=Load1
paramid=0x02
scalingrpn=x
isvisible=0


paramname=Load2
paramid=0x03
scalingrpn=x
isvisible=0


paramname=2ByteLoad
scalingrpn=Load1,256,*,Load2,+,0.3125,*


paramname=KnockSum
paramid=0x26


paramname=KnockVoltage
paramid=0x30
scalingrpn=x,0.0195,*


paramname=KnockBase
paramid=0x6B


paramname=MAPScaled
paramid=0xA1
scalingrpn=x,0.27545,*,21.1,-


paramname=AFR
paramid=0xBF
scalingrpn=x,0.03913,*,9,+


paramname=AFRMAP
scalingrpn=1881.6,x,/
paramid=0x32


paramname=IPWFront
paramid=0x2B
scalingrpn=x,0.256,*


paramname=IDCFront
scalingrpn=IPWFront,RPM,*,1200,/


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


paramname=IDCRear
scalingrpn=IPWRear,RPM,*,1200,/


paramname=WGDC
paramid=0x86
scalingrpn=x,2,/


paramname=TargetLoad
paramid=0xB6
scalingrpn=x,0.625,*,20,+


paramname=WGDC Correction
paramid=0X8B
scalingrpn=x,0.5,*,64,-


paramname=Speed
paramid=0x2F
scalingrpn=x,1.242742384,*


paramname=RearFuelTrim_Low
paramid=0x0C
scalingrpn=x,0.19607843,*,25,-
priority=2


;paramname=RearFuelTrim_Middle
;paramid=0x0D
;scalingrpn=x,0.19607843,*,25,-
;priority=2


;paramname=RearFuelTrim_High
;paramid=0x0E
;scalingrpn=x,0.19607843,*,25,-
;priority=2


paramname=RearO2Sensor
paramid=0x13
scalingrpn=x,0.0195,*


paramname=FrontFuelTrim_Low
paramid=0x4C
scalingrpn=x,0.19607843,*,25,-
priority=2


;paramname=FrontFuelTrim_Middle
;paramid=0x4D
;scalingrpn=x,0.19607843,*,25,-
;priority=2


;paramname=FrontFuelTrim_High
;paramid=0x4E
;scalingrpn=x,0.19607843,*,25,-
;priority=2


paramname=FrontO2Sensor
paramid=0x3E
scalingrpn=x,0.0195,*


paramname=Battery
paramid=0x14
scalingrpn=x,0.0733,*
priority=2


;paramname=ISCSteps
;paramid=0x16


paramname=CoolantTemp
paramid=0x10
scalingrpn=x,1.8,*,40,-


;paramname=AirTemp
;paramid=0x11
;scalingrpn=x,1.8,*,40,-


paramname=OCTNumber
paramid=0x27
scalingrpn=x,0.39215686,*
priority=2


;conditionrpn=RPM,100,>
;action=start


;conditionrpn=RPM,0,==
;action=stop


conditionrpn=TPS,60,>
action=start


conditionrpn=TPS,60,<
action=stop