PDA

View Full Version : Standalone Tactrix open port 2.0 Datalogging



Chris@Rvengeperformance
05-14-2012, 02:02 PM
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
05-14-2012, 03:44 PM
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
05-14-2012, 03:47 PM
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
05-14-2012, 04:33 PM
woohoo gunna grab a card tonight and test this out. Thanks for posting this!

Monster Stealth
05-14-2012, 05:08 PM
Thanks for the write up. I am sure this will come in hand when I get my car up and running.

3kgt1734
05-14-2012, 11:27 PM
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
05-15-2012, 12:12 AM
Yes we use ecuflash for flashing and evoscan for logging.

Boostaddict
05-15-2012, 01:36 PM
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
05-15-2012, 02:54 PM
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
05-21-2012, 03:35 PM
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.

Boostaddict
05-21-2012, 03:41 PM
Yeah I noticed that the first time I plugged in the OP2 (no standalone logging enabled yet since I haven't driven the car).

On a side note since you've been playing with the standalone logging... dothe logs append to one big csv file or does the OP2 create a separate file for each logging event? I read some evo guys complaining about 50+ log files to wade through and others say they just had one big log file.

Chris@Rvengeperformance
05-21-2012, 03:44 PM
in my case it has made a new log for each start condition. Since I'm logging all the time it makes a new log each time you start it up. It also seems to split files after they get to about 750KB, but that could've been a fluke, didn't pay that much attention.

That is the one thing that sucks, the timestamps are the file are obviously bs since there isn't a clock in the open port, so it can be hard to find the right log. Hopefully they will have a firmware update at some point that fixes this. The standlone logging is still somewhat beta from what I understand, but it does work well.

I guess your best bet is to delete the logs each time you plug the thing in so it doesn't get confusing fast. You need a computer to change the tune anyway, so you may as well just clear it out everytime you make a change.

Toni
05-30-2012, 09:55 AM
Nice, I was looking at this last year for some custom hardware but just now put down some money for the ecu. What kind of resolution are you getting in the logs?

Toni
05-30-2012, 10:01 AM
Oh, I forgot, this is probably a good place to add this. You can actually log data from the Innovate MTS toolchain. So you can log your wideband directly without going through the ecu using the serial stream. It will also log anything else you may have attached.

mb3000
10-20-2013, 08:10 PM
Awesome, subscribed for future use!

Kx1984
05-12-2014, 07:01 PM
any update on this??
Kx

green-lantern
01-28-2015, 01:44 PM
I have a Black Stealth LCDBC and it's plugged into the OBD2 port in my ECU adaptor harness. Will it hurt anything or make inaccurate logs if I plug the Tactrix in the port on the dash and run the LCDBC on the port in the adaptor harness and use them at the same time?

Chris@Rvengeperformance
01-28-2015, 02:49 PM
I have a Black Stealth LCDBC and it's plugged into the OBD2 port in my ECU adaptor harness. Will it hurt anything or make inaccurate logs if I plug the Tactrix in the port on the dash and run the LCDBC on the port in the adaptor harness and use them at the same time?

Antero would know better, but I think this may in fact cause some issues. As far as I understand MUT or OBD2 are serial protocols and the logging device basically polls for requests to the ecu and it responds with data. Running two devices would best case reduce your logging speed by half or worst case cause packet corruption. It may not even get past the handshake.

Now that I think about it a bit, I remembered that if you log with evoscan the onboard logging just turns off. You can't run both at once, but you may be able to have two physically connected at the same time. I really don't know what it will do for sure. Maybe whichever device boots fastest will connect and the second one will not be allowed to connect or it may be round robin.

DrGonzo
01-28-2015, 03:46 PM
I do remember Black Stealth saying in one of his threads that the LCDBC is compatible with Chrome, but I don't know how far that goes to running them both at the same time.

jras312
01-28-2015, 03:59 PM
I thought I read a few days ago on one of his for sale threads that you can use them both at the same time. Not sure about any side effects though.

BlackStealth
01-28-2015, 06:24 PM
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-gto-related-topics/497-my-lcd-screen-project-boost-wbo2-knock-etc-122.html#post305743

green-lantern
01-28-2015, 06:37 PM
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-gto-related-topics/497-my-lcd-screen-project-boost-wbo2-knock-etc-122.html#post305743

Yes

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

thanks!

Unlogic
01-28-2015, 07:15 PM
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
05-19-2016, 04:43 PM
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-x-engine-management-tuning-forums/469325-logging-beta-standalone-tactrix-cable-logger-no-more-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
05-19-2016, 05:07 PM
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-Tactrix-data-logging?p=238422&viewfull=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-OpenPort-2-0-Chrome-logging-without-laptop?p=260067#post260067


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

Jimvr4
05-19-2016, 10:34 PM
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
05-19-2016, 10:55 PM
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
05-19-2016, 10:59 PM
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
05-19-2016, 11:08 PM
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
05-20-2016, 12:29 PM
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

murphys_law
05-22-2016, 01:17 AM
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

Awesome! I'll have to try this out when I get a chance. It would be nice not needing a laptop.

DrGonzo
05-22-2016, 09:56 PM
Here is mine.


Added corrections for the coolant temp
Fixed the naming error when using a leading numeric character
Added in logging for Innovate WB through Chrome ECU.
MOved some logging items around for better placement in the csv file
Disabled logging HighFuelTrims.





; 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=TwoByteAirFlow
scalingrpn=Air1,256,*,Air2,+,0.09828125,*

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

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

paramname=TwoByteLoad
scalingrpn=Load1,256,*,Load2,+,0.3125,*

paramname=KnockSum
paramid=0x26
priority=2

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

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

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

paramname=WB_Innovate
paramid=0xBF
scalingrpn=0.0627,x,*,7,+

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

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

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

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

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

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

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

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

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

;paramname=ISCSteps
;paramid=0x16

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

;Coolant temp is scaled in F
paramname=CoolantTemp
paramid=0x07
scalingrpn=x,1.593,*,38,+

paramname=AirTemp
paramid=0x3A
scalingrpn=x

paramname=KnockBase
paramid=0x6B
priority=2

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

;paramname=WGDC
;paramid=0x86
;scalingrpn=x,0.39215686,*

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

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

conditionrpn=TPS,37,>
action=start

conditionrpn=TPS,37,<
action=stop

murphys_law
06-11-2016, 08:26 PM
Here is mine.


Added corrections for the coolant temp
Fixed the naming error when using a leading numeric character
Added in logging for Innovate WB through Chrome ECU.
MOved some logging items around for better placement in the csv file
Disabled logging HighFuelTrims.





; 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=TwoByteAirFlow
scalingrpn=Air1,256,*,Air2,+,0.09828125,*

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

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

paramname=TwoByteLoad
scalingrpn=Load1,256,*,Load2,+,0.3125,*

paramname=KnockSum
paramid=0x26
priority=2

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

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

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

paramname=WB_Innovate
paramid=0xBF
scalingrpn=0.0627,x,*,7,+

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

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

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

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

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

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

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

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

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

;paramname=ISCSteps
;paramid=0x16

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

;Coolant temp is scaled in F
paramname=CoolantTemp
paramid=0x07
scalingrpn=x,1.593,*,38,+

paramname=AirTemp
paramid=0x3A
scalingrpn=x

paramname=KnockBase
paramid=0x6B
priority=2

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

;paramname=WGDC
;paramid=0x86
;scalingrpn=x,0.39215686,*

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

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

conditionrpn=TPS,37,>
action=start

conditionrpn=TPS,37,<
action=stop



Just a thought, is there a way to log the scaled wb value without using a formula? Or is that what you are doing?


Sent from my iPhone 6s+ using Tapatalk

striker2
06-11-2016, 11:24 PM
Just a thought, is there a way to log the scaled wb value without using a formula? Or is that what you are doing?


Sent from my iPhone 6s+ using Tapatalk

That is what mine does, but I am using an AEM wired to the ECU.

DrGonzo
06-12-2016, 12:16 AM
The formula converts the raw output from the WB to the AFR. it logs what the formula results are not the raw WB output.

murphys_law
06-12-2016, 01:17 AM
The formula converts the raw output from the WB to the AFR. it logs what the formula results are not the raw WB output.

Ok, thanks.

Jimvr4
06-14-2016, 01:54 PM
I noticed the format for the 2Byte parameters uses a different format in your files than mine. I'm using the AEM 30-2310 wideband and an AVC-R 3 bar MAP sensor which I calibrated with a Mityvac MV8500.

Greg - it looks like you didn't correct the coolant temp in the code you posted.

Here is my code


; OpenPort 2.0 internal logging file
; Chrome v2 ECU Parameters

; Must be named logcfg.txt and be placed in the root directory
; of the microSD card inserted in the OpenPort in order to work
; Use a 2GB maximum size microSD card, formatted FAT16 for
; optimal results

; This config logs using the MUT-II protocol over the K-line,
; and is customized to work only with a flashable 3000GT/Stealth
; ECU loaded with Chrome v2.1

; Posted by "mjannusch" on 3Si and 3SGTO for use by Chrome
; purchasers


;-----------MUT2 Settings------------
type=mut2
baud=15625
;baud=62500

; Default baudrate is 15625, but can be changed in the "Protocol
; MUT3 Baud" parameter in Chrome. Must also be changed in
; EvoScan to log with a laptop. Has no effect on logging rate
; with OpenPort logging, but 25% increase in sample rate with
; EvoScan


;---------Parameters to Log----------

; Sampgroups define how often a parameter is polled from
; the ECU. Higher numbered sampgroups will poll less often.

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

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

paramname=Battery
paramid=0x14
scalingrpn=x,0.07333,*
sampgroup=15

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

;These are not the params for a 98+ ECU)
;paramname=CoolantTemp
;paramid=0x07
;scalingrpn=x,1.593,*,38,+
;sampgroup=15

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

paramname=2ByteAirFlow
paramid=0x00
databits=16
scalingrpn=x,0.09765625,*
;This is 2-byte Airflow, named as standard AirFlow

paramname=2B_ECULoad
paramid=0x02
databits=16
scalingrpn=x,0.3125,*
;This is 2-byte Load, named as standard ECULoad

paramname=MAPScaled
paramid=0xA1
scalingrpn=x,0.2745,*,20,-
; Scaled Pin 92 input, requires MAP sensor on pin 92
; and properly populated scaling table. See:
; http://www.3sgto.org/tuning-engine-electronics-ecu-discussions/10777-chrome-v2-tech-manual-3.html#post211663

paramname=WBScaled
paramid=0xBF
scalingrpn=x,0.0627,*,7,+
; Scaled Pin 93 input, requires wideband on pin 93
; and properly populated scaling table. See:
; http://www.3sgto.org/tuning-engine-electronics-ecu-discussions/10777-chrome-v2-tech-manual-3.html#post211663

paramname=KnockSum
paramid=0x26
scalingrpn=x
;sampgroup=1

paramname=Speed
paramid=0x2F
scalingrpn=x,1.2427424,*
;sampgroup=1

paramname=F_InjPulseWidth
paramid=0x2B
;scalingrpn=x,0.256,*

paramname=F_InjDutyCycle
scalingrpn=F_InjPulseWidth,RPM,*,1200,/
; Requires RPM and F_InjPulseWidth params to be logged above

paramname=Gear
scalingrpn=RPM,Speed,/
; Requires RPM and Speed params to be logged above
; Will give a rough estimation of the gear ratio.
; Not a number showing the actual gear.

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

paramname=WGDCCorr
paramid=0x8B
scalingrpn=x,0.5,*,64,-

paramname=Target_Load
paramid=0xB6
scalingrpn=x,0.625,*
; This value does not include the Boost Control Load Offset

;paramname=AFTarget
;paramid=0x32
;scalingrpn=1881.6,x,/

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

;paramname=KnockBase
;paramid=0x6B
;scalingrpn=x

;paramname=Octane
;paramid=0x27
;scalingrpn=x,0.39215686,*
;sampgroup=15


;paramname=R_InjPulseWidth
;paramid=0x29
;scalingrpn=x,0.256,*

;paramname=R_InjDutyCycle
;scalingrpn=R_InjPulseWidth,RPM,*,1200,/
;Requires RPM and R_InjPulseWidth params to be logged above

;paramname=FP_O2Sensor
;paramid=0x3E
;scalingrpn=x,0.01952,*
; Front narrowband O2 sensor

;paramname=F_O2FeedbackTrim
;paramid=0x4F
;scalingrpn=x,0.1953125,*,25,-
;sampgroup=15

;paramname=F_FuelTrim_Low
;paramid=0x4C
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=F_FuelTrim_Mid
;paramid=0x4D
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=F_FuelTrim_High
;paramid=0x4E
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=RP_O2Sensor
;paramid=0x13
;scalingrpn=x,0.01952,*
; Rear narrowband O2 sensor

;paramname=R_O2FeedbackTrim
;paramid=0x0F
;scalingrpn=x,0.1953125,*,25,-
;sampgroup=15

;paramname=R_FuelTrim_Low
;paramid=0x0C
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=R_FuelTrim_Mid
;paramid=0x0D
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=R_FuelTrim_High
;paramid=0x0E
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=VE
;paramid=0x31
;scalingrpn=x,100,*,128,/

;These are not correct for a 98+ ECU
;paramname=AirTemp
;paramid=0x3A
;scalingrpn=x,1.8,*,38,+
;sampgroup=15
; RETURNS INCORRECT VALUES, at least on my car

;paramname=AirTemp
;paramid=0x11
;scalingprn=x,1.8,*,40,-
;sampgroup=15

;paramname=Baro
;paramid=0x15
;scalingrpn=x,0.49,*
;sampgroup=15

;paramname=gmas
;paramid=0x00
;scalingrpn=x,0.0236,*

;paramname=AirMassGperCyl
;paramid=0x02
;databits=16
;scalingrpn=x,512,/

;paramname=CoilDwell
;paramid=0x2D
;scalingrpn=x,0.064,*

;paramname=AirflowRev
;paramid=0x1D
;scalingrpn=x,0.07843,*

;paramname=TargetIdleRPM
;paramid=0x24
;scalingrpn=x,7.8,*

;paramname=IdleError
;paramid=0x75
;scalingrpn=x,7.8125,*

;paramname=ISCSteps
;paramid=0x16
;scalingrpn=x

;paramname=MAPVolts
;paramid=0xA1
;scalingrpn=x,0.01952,*
; Raw volts on ECU pin 92

;paramname=WBVolts
;paramid=0xBF
;scalingrpn=x,0.01952,*
; Raw volts on ECU pin 93


;---------Logging Conditions---------

; Log whenever car is runing
conditionrpn=RPM,100,>
action=start

conditionrpn=RPM,0,==
action=stop

; Log only when TPS > 80%
;conditionrpn=TPS,80,>
;action=start

;conditionrpn=TPS,80,<
;action=stop

DrGonzo
06-14-2016, 03:10 PM
I noticed the format for the 2Byte parameters uses a different format in your files than mine. I'm using the AEM 30-2310 wideband and an AVC-R 3 bar MAP sensor which I calibrated with a Mityvac MV8500.

Greg - it looks like you didn't correct the coolant temp in the code you posted.

Here is my code


; OpenPort 2.0 internal logging file
; Chrome v2 ECU Parameters

; Must be named logcfg.txt and be placed in the root directory
; of the microSD card inserted in the OpenPort in order to work
; Use a 2GB maximum size microSD card, formatted FAT16 for
; optimal results

; This config logs using the MUT-II protocol over the K-line,
; and is customized to work only with a flashable 3000GT/Stealth
; ECU loaded with Chrome v2.1

; Posted by "mjannusch" on 3Si and 3SGTO for use by Chrome
; purchasers


;-----------MUT2 Settings------------
type=mut2
baud=15625
;baud=62500

; Default baudrate is 15625, but can be changed in the "Protocol
; MUT3 Baud" parameter in Chrome. Must also be changed in
; EvoScan to log with a laptop. Has no effect on logging rate
; with OpenPort logging, but 25% increase in sample rate with
; EvoScan


;---------Parameters to Log----------

; Sampgroups define how often a parameter is polled from
; the ECU. Higher numbered sampgroups will poll less often.

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

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

paramname=Battery
paramid=0x14
scalingrpn=x,0.07333,*
sampgroup=15

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

;These are not the params for a 98+ ECU)
;paramname=CoolantTemp
;paramid=0x07
;scalingrpn=x,1.593,*,38,+
;sampgroup=15

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

paramname=2ByteAirFlow
paramid=0x00
databits=16
scalingrpn=x,0.09765625,*
;This is 2-byte Airflow, named as standard AirFlow

paramname=2B_ECULoad
paramid=0x02
databits=16
scalingrpn=x,0.3125,*
;This is 2-byte Load, named as standard ECULoad

paramname=MAPScaled
paramid=0xA1
scalingrpn=x,0.2745,*,20,-
; Scaled Pin 92 input, requires MAP sensor on pin 92
; and properly populated scaling table. See:
; http://www.3sgto.org/tuning-engine-electronics-ecu-discussions/10777-chrome-v2-tech-manual-3.html#post211663

paramname=WBScaled
paramid=0xBF
scalingrpn=x,0.0627,*,7,+
; Scaled Pin 93 input, requires wideband on pin 93
; and properly populated scaling table. See:
; http://www.3sgto.org/tuning-engine-electronics-ecu-discussions/10777-chrome-v2-tech-manual-3.html#post211663

paramname=KnockSum
paramid=0x26
scalingrpn=x
;sampgroup=1

paramname=Speed
paramid=0x2F
scalingrpn=x,1.2427424,*
;sampgroup=1

paramname=F_InjPulseWidth
paramid=0x2B
;scalingrpn=x,0.256,*

paramname=F_InjDutyCycle
scalingrpn=F_InjPulseWidth,RPM,*,1200,/
; Requires RPM and F_InjPulseWidth params to be logged above

paramname=Gear
scalingrpn=RPM,Speed,/
; Requires RPM and Speed params to be logged above
; Will give a rough estimation of the gear ratio.
; Not a number showing the actual gear.

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

paramname=WGDCCorr
paramid=0x8B
scalingrpn=x,0.5,*,64,-

paramname=Target_Load
paramid=0xB6
scalingrpn=x,0.625,*
; This value does not include the Boost Control Load Offset

;paramname=AFTarget
;paramid=0x32
;scalingrpn=1881.6,x,/

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

;paramname=KnockBase
;paramid=0x6B
;scalingrpn=x

;paramname=Octane
;paramid=0x27
;scalingrpn=x,0.39215686,*
;sampgroup=15


;paramname=R_InjPulseWidth
;paramid=0x29
;scalingrpn=x,0.256,*

;paramname=R_InjDutyCycle
;scalingrpn=R_InjPulseWidth,RPM,*,1200,/
;Requires RPM and R_InjPulseWidth params to be logged above

;paramname=FP_O2Sensor
;paramid=0x3E
;scalingrpn=x,0.01952,*
; Front narrowband O2 sensor

;paramname=F_O2FeedbackTrim
;paramid=0x4F
;scalingrpn=x,0.1953125,*,25,-
;sampgroup=15

;paramname=F_FuelTrim_Low
;paramid=0x4C
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=F_FuelTrim_Mid
;paramid=0x4D
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=F_FuelTrim_High
;paramid=0x4E
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=RP_O2Sensor
;paramid=0x13
;scalingrpn=x,0.01952,*
; Rear narrowband O2 sensor

;paramname=R_O2FeedbackTrim
;paramid=0x0F
;scalingrpn=x,0.1953125,*,25,-
;sampgroup=15

;paramname=R_FuelTrim_Low
;paramid=0x0C
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=R_FuelTrim_Mid
;paramid=0x0D
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=R_FuelTrim_High
;paramid=0x0E
;scalingrpn=x,0.19607843,*,25,-
;sampgroup=15

;paramname=VE
;paramid=0x31
;scalingrpn=x,100,*,128,/

;These are not correct for a 98+ ECU
;paramname=AirTemp
;paramid=0x3A
;scalingrpn=x,1.8,*,38,+
;sampgroup=15
; RETURNS INCORRECT VALUES, at least on my car

;paramname=AirTemp
;paramid=0x11
;scalingprn=x,1.8,*,40,-
;sampgroup=15

;paramname=Baro
;paramid=0x15
;scalingrpn=x,0.49,*
;sampgroup=15

;paramname=gmas
;paramid=0x00
;scalingrpn=x,0.0236,*

;paramname=AirMassGperCyl
;paramid=0x02
;databits=16
;scalingrpn=x,512,/

;paramname=CoilDwell
;paramid=0x2D
;scalingrpn=x,0.064,*

;paramname=AirflowRev
;paramid=0x1D
;scalingrpn=x,0.07843,*

;paramname=TargetIdleRPM
;paramid=0x24
;scalingrpn=x,7.8,*

;paramname=IdleError
;paramid=0x75
;scalingrpn=x,7.8125,*

;paramname=ISCSteps
;paramid=0x16
;scalingrpn=x

;paramname=MAPVolts
;paramid=0xA1
;scalingrpn=x,0.01952,*
; Raw volts on ECU pin 92

;paramname=WBVolts
;paramid=0xBF
;scalingrpn=x,0.01952,*
; Raw volts on ECU pin 93


;---------Logging Conditions---------

; Log whenever car is runing
conditionrpn=RPM,100,>
action=start

conditionrpn=RPM,0,==
action=stop

; Log only when TPS > 80%
;conditionrpn=TPS,80,>
;action=start

;conditionrpn=TPS,80,<
;action=stop



For the 2byte para I am using Strikers formula for that which he went over here:


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-Tactrix-data-logging?p=238422&viewfull=1#post238422



As for the coolant, My guess is due to mine being a different year than yours. I have a 93 Stealth but my engine/ecu harness is from a 92. so wiring for coolant is different than later models. My coolant logs with a couple degrees of my temp gauge and matches what EVOscan is telling me.


As for the wideband, yes it will be different for you. AEM WB is scaled at 10-20 AFR where as my Innovate is scaled from 7.5-22.5 AFR so the formulas are different.

Jimvr4
06-16-2016, 11:13 AM
As for the coolant, My guess is due to mine being a different year than yours. I have a 93 Stealth but my engine/ecu harness is from a 92. so wiring for coolant is different than later models. My coolant logs with a couple degrees of my temp gauge and matches what EVOscan is telling me.


Interesting. I thought you had a Chrome ECU which would mean the paramID would be for a 98+ ECU which is 0x10 from Striker's post. Yours is 0x07. I'm not aware of sensor wiring affecting the paramID although I could see it affecting scaling. On the other hand I note that when I use Evoscan v2.9 for logging the 0x07 paramID and scaling always worked fine - it just didn't work in the standalone logging. My car is asleep until I move so I won't be testing this for a while.

DrGonzo
06-16-2016, 01:51 PM
Yeah I am using a Chrome Ecu. Maybe I am confusing the fan circuit difference between the years and not the coolant. Been awhile since I looked at that wiring.

I'm not sure what the 0x10 is, I just know that 0x07 works fine on my car.