Logging through Tactrix

[DMC7492]

Hi guys, I am trying to log through the Tactrix 2.0 onto an SD card.
One of the parameters is from the AEM analog 0-5 ADC wide band O2 sensor.
I have the pin out sheet from Tactrix and it looks like I can hook into OEM 12 or OEM 8.
To accomplish this I need a OBD2 terminal with a section of wire on it to terminate to for input OEM 8. However I cannot find one of these terminals any where but the OBD connector and I have no spares. The subaru harness repair literature does not list this connector.
Or I use a 2.5 mm stereo jack and wire into the tip and sleeve of the jack.

Has any body done this set up to log an O2 wide band with 0-5 volt output?

Does anybody have a spare B40 OBD2 black plug terminal with a short section of wire on it?
Thanks guys, I'll call Brian over at Iwire a little later

[Bob_n_Cincy]

Hi guys, I am trying to log through the Tactrix 2.0 onto an SD card.
One of the parameters is from the AEM analog 0-5 ADC wide band O2 sensor.
I have the pin out sheet from Tactrix and it looks like I can hook into OEM 12 or OEM 8.
To accomplish this I need a OBD2 terminal with a section of wire on it to terminate to for input OEM 8. However I cannot find one of these terminals any where but the OBD connector and I have no spares. The subaru harness repair literature does not list this connector.
Or I use a 2.5 mm stereo jack and wire into the tip and sleeve of the jack.

Has any body done this set up to log an O2 wide band with 0-5 volt output?

Does anybody have a spare B40 OBD2 black plug terminal with a short section of wire on it?
Thanks guys, I'll call Brian over at Iwire a little later

Don
I have not done this so don't take my word for it.
The tactrix 2.0 has a ear bud type port on it to be used with the wideband sensor.
See picture.
Bob

51386

[STiPWRD]

Use the stereo jack Bob has shown and connect the 0-5V wideband signal to OEM 12. That way you don't have to cut anything on the OBD2 wiring. I also have not done this so just going off what's in this link:

https://www.tactrix.com/index.php?option=com_content&view=article&id=76:what-are-pinout-and-pin-functions-of-the-openport-20&catid=39:openport-20&Itemid=41

[FFRSpec72]

This is what I'm using http://www.amazon.com/Innovate-Motorsports-3812-Serial-Patch/dp/B001S7URFW/ref=pd_sim_263_3?ie=UTF8&dpID=31hYN0rQ4XL&dpSrc=sims&preST=_AC_UL160_SR160%2C160_&refRID=1WEB6FPQBHT48BZV43EK and it plugs into the Tactrix and also the main harness http://www.amazon.com/gp/product/B00FFTAJPC/ref=s9_cartx_gw_g263_i1_r?ie=UTF8&fpl=fresh&pf_rd_m=ATVPDKIKX0DER&pf_rd_s=desktop-5&pf_rd_r=1MYKCSDHE7PNWZFM1NEZ&pf_rd_t=36701&pf_rd_p=2090148982&pf_rd_i=desktop

[DMC7492]

Update on the AEM alnalog O2 sensor 0-5 volt out put. I wired a 2.5 mm, three conductor plug, + to the tip and - to the sleeve. This plugs into the Tactrix 2.0, like Bob has shown in post2.
Then had to get the logcfg.text file to read as shown,
type=adc
paramname = wb02
paramid =12
scalingrpn=x,0.002375,*,7.8125,+

Now I am looking for a logcfg.text file for a 2005 wrx with an ECU3E14444006 and a CAL ID A4TF800E.
Does any body have the correct file??

[FFRSpec72]

Update on the AEM alnalog O2 sensor 0-5 volt out put. I wired a 2.5 mm, three conductor plug, + to the tip and - to the sleeve. This plugs into the Tactrix 2.0, like Bob has shown in post2.
Then had to get the logcfg.text file to read as shown,
type=adc
paramname = wb02
paramid =12
scalingrpn=x,0.002375,*,7.8125,+

Now I am looking for a logcfg.text file for a 2005 wrx with an ECU3E14444006 and a CAL ID A4TF800E.
Does any body have the correct file??

OK, I have the Innovate LC-2 and have the 2.5mm jack adapter and have plugged that into the Tactrix but no idea how to tell RR or Tactrix to log this. I believe that Tactrix will also log to a micro SD card also and don't need RR but what will that log ?

[STiPWRD]

OK, I have the Innovate LC-2 and have the 2.5mm jack adapter and have plugged that into the Tactrix but no idea how to tell RR or Tactrix to log this. I believe that Tactrix will also log to a micro SD card also and don't need RR but what will that log ?

I've done some research on this since March and was able to successfully log my wideband AFR with Rom Raider Logger and a lap top. I'm using the AEM Uego and logging via their serial data wire but the LC-1 has the same type of output. All you have to do is open up the logger (not the ECU editor) and you'll see a Plugins tab at the top. Select your device (AEM UEGO AFR or Innovate Wideband AFR) and it should appear as a parameter that you can log under external sensors. This applies when trying to log with a lap top. I'm also using the 2.5mm jack and have wired it to an RS232 connector to connect to a lap top. I haven't played around with trying to log the 0-5V analogue AFR signal.

For the longest time I couldn't understand all of the posts about people modifying logcfg files with the wideband parameters but then I figured it out. This approach is when you're not using a lap top but plugging in a microSD card directly into the Tactrix unit. I haven't tried this out yet but my understanding is that you just need to put a logcfg.txt file on the microSD card that specifies which parameters to log and the trigger (i.e. begin logging at turn on or start/stop logging by pressing the defogger button). In general, this method is more limited than logging with a lap top since the tactrix is doing the data processing and recording so stand alone logging is usually slower and is better for logging fewer parameters.

Here are some helpful links I found:

http://legacygt.com/forums/showthread.php/logging-aem-uego-wideband-directly-sd-via-tactrix-op2-0-208859.html?

http://forums.nasioc.com/forums/showthread.php?t=2638188

LogCFG Generator:
http://subaru.hunterjm.com/

[FFRSpec72]

I've done some research on this since March and was able to successfully log my wideband AFR with Rom Raider Logger and a lap top. I'm using the AEM Uego and logging via their serial data wire but the LC-1 has the same type of output. All you have to do is open up the logger (not the ECU editor) and you'll see a Plugins tab at the top. Select your device (AEM UEGO AFR or Innovate Wideband AFR) and it should appear as a parameter that you can log under external sensors. This applies when trying to log with a lap top. I'm also using the 2.5mm jack and have wired it to an RS232 connector to connect to a lap top. I haven't played around with trying to log the 0-5V analogue AFR signal.

For the longest time I couldn't understand all of the posts about people modifying logcfg files with the wideband parameters but then I figured it out. This approach is when you're not using a lap top but plugging in a microSD card directly into the Tactrix unit. I haven't tried this out yet but my understanding is that you just need to put a logcfg.txt file on the microSD card that specifies which parameters to log and the trigger (i.e. begin logging at turn on or start/stop logging by pressing the defogger button). In general, this method is more limited than logging with a lap top since the tactrix is doing the data processing and recording so stand alone logging is usually slower and is better for logging fewer parameters.

Here are some helpful links I found:

http://legacygt.com/forums/showthread.php/logging-aem-uego-wideband-directly-sd-via-tactrix-op2-0-208859.html?

http://forums.nasioc.com/forums/showthread.php?t=2638188

LogCFG Generator:
http://subaru.hunterjm.com/

yea, I also just figured that out (the logcfg.txt), how do you view this file though ? Since I will be on the track, I really don't want to have to figure a way to tie down a tablet/laptop and explain that to the grid folks.

[STiPWRD]

yea, I also just figured that out (the logcfg.txt), how do you view this file though ? Since I will be on the track, I really don't want to have to figure a way to tie down a tablet/laptop and explain that to the grid folks.
I believe tactrix will generate a .xml or .csv file on the microSD card (or multiple files if you trigger the start/stop logging ability). It's best to have this process ironed out before you hit the track. Also, some parameters consume more data bandwidth than others so play around with that a bit and make sure the sampling frequency is good enough for what you want to log. If you want to log more than a handful of parameters I've heard it can get extremely slow in stand alone mode.

[FFRSpec72]

I believe tactrix will generate a .xml or .csv file on the microSD card (or multiple files if you trigger the start/stop logging ability). It's best to have this process ironed out before you hit the track. Also, some parameters consume more data bandwidth than others so play around with that a bit and make sure the sampling frequency is good enough for what you want to log. If you want to log more than a handful of parameters I've heard it can get extremely slow in stand alone mode.

Are their limits on the size of the micro SD cards that are supported ?

[STiPWRD]

Are their limits on the size of the micro SD cards that are supported ?
There's probably a limit but several people have posted that a 1 gig card works. These log files shouldn't be that large anyways.

[FFRSpec72]

There's probably a limit but several people have posted that a 1 gig card works. These log files shouldn't be that large anyways.

Do you have a logcfg.txt file for a Subaru engine ?

[Bob_n_Cincy]

Do you have a logcfg.txt file for a Subaru engine ?

Here is a link where you can make one specific for your ECU.
http://subaru.hunterjm.com/

[FFRSpec72]

Here is a link where you can make one specific for your ECU.
http://subaru.hunterjm.com/

tried that and does not generate a with useful info just a trigger

[DMC7492]

tried that and does not generate a with useful info just a trigger

I had the same luck. Here's a link that is very helpful. http://www.scoobymods.com/showthread.php/logging-tactrix-2-0-13396.html?

In step 6 of the first post, the samples logging file works on my 2005wrx. I then learned how to find my logger xml file through Internet explorer. Then find the parameters you want to log and modify the logcfg.txt file. I spent a lot of time modifying the file make only one parameter Change,then test the file by plugging in the Tactrix adapter. The LEDs will show if it's working. Learn this by reading that same link as above after step seven it explains the LEDs. Good luck! It is very rewarding once you get it to work! Don

[RM1SepEx]

I'm finding that the data logs cut out under full throttle around 4500 rpm. Any ideas out there?

[FFRSpec72]

I'm finding that the data logs cut out under full throttle around 4500 rpm. Any ideas out there?

I have done some pulls up to 8K and no logging issues with Tactrix or Rom Raider so far

[JeromeS13]

I'm finding that the data logs cut out under full throttle around 4500 rpm. Any ideas out there?

How many parameters are you trying to log? I've never logged with Rom Raider, but with all other logging software that I've used if you try to log too many parameters, it can overwhelm the system. Sometimes you just lose resolution. Sometimes it freaks out and stops/disconnects. Try reducing the number of parameters.

[DMC7492]

Take a look at your CONFIG file and check your triggers, maybe it is written to stop logging at that rpm or throttle position. Here is an example from the sscooby mods link a few posts earlier.
the ; in front of the line of code Ignores the code
no ; allows the line to run or be read.

;-------------triggers---------------

; only log when the engine is running
conditionrpn = RPM,0,>
action = start

conditionrpn = RPM,0,==
action = stop

; start logging to a new file when the throttle goes from previously below 95 to above 95
; #throttle refers to the previous throttle sample
conditionrpn = throttle,95,>,#throttle,95,<=,&&
action = newfile