Logging Tactrix ADC channel to EvoScan

Let me first say I am new to EvoScan and Tactrix. In my time I've done plenty of diagnostics, repairs, upgrades etc for a career but mostly I was into playing with older cars (I miss my '69 Mach 1 :frown: ). I am now a programmer and do not miss the wrenching life at all but love to help friends and tinker here and there. I've had my '94 SL for 16 years and it's been in the garage with a busted water pump for 2 years. Luckily I knew what happened and shut it off before the belt broke. Got it running and back on the road within a couple of days (took that long because I kept finding parts I should replace lol). I'm now starting to fix it up and wanting to play around a bit so I ordered a Jesters Chromed ECU along with some other bolt on parts. They actually make them for SLs now :cool3: . I now have my Tactrix and an AEM single channel WBO2 and am waiting on the Jesters. I want to log my WBO2 with my existing ECU and parts to gauge the improvements the Chromed ECU and different parts make and how bad my car really was before. I've been doing a lot of reading of Greg's stuff and a lot of the same stuff on chromedecu.org and have a long ways to go but I love my GT and am really looking forward to this project.

Here is my question. I can connect the AEM 0-5v to the OBD2 pin 8 (after removing the ABS (I think) diagnostic wire) and log directly to the micro SD using the Tactrix ADC channel, but can that be logged by EvoScan? I got a logcfg.txt file from a guy logging his WRX on an SD card and he is using pin 8 for WBO2 so I know that part works. I've been googling and searching forums but the only post I found was from 2 years ago on the openecu forum saying EvoScan did not support that at the time. So does anyone know if EvoScan does this now?

If that will not work and I have to log directly to an SD card can anyone verify my scalingrpn in the last line of my script?

other guys original source logcfg.txt file using Zeitronix Wideband:

Quote:

;----------------adc----------------
type=adc ; log from built in ADC channels

paramname=AFR ; on newer subarus pin 8 is connected to the ignition voltage
paramid=8 ; paramid is pin number on OBD connector
; valid pins are 8 and 16
; values are pre-scaled to millivolts
scalingrpn=x,0.002,*,9.6,+ ; here we scale to volts

What mine should look like with AEM?

Quote:

;----------------adc----------------
type=adc ; log from built in ADC channels

paramname=AFR
paramid=8 ; paramid is pin number on OBD connector
scalingrpn=x,2.375,*,7.3125,+ ;AEM's scaling for gasoline AFR = 2.375*V + 7.3125

My sources for this script are
openecu.org ? View topic - Tactrix 2.0 logging analog signal from Zeitronix-WORKING!!!
http://www.scoobymods.com/showthread...-0-13396.html?

Don't do that. You won't be able to log it with too many other (useful) parameters. Plus OBD2 is much slower than MUT for logging purposes.

I can't remember if I put wideband scaled inputs into Chrome SL. If not, that needs to go into the list of things to do. All you'd have to do is wire the 5V output into the SL ECU, scale the voltage and you'll be able to log it using the Wideband Scaled request.

I plan on wiring it in when I install the new ECU but I wanted a baseline to see AFR on a set route then when I install the new ECU and get it tuned run the same route and see the difference. My thought behind it was just to see the main difference in performance and efficiency but if you don't think I'll be able to get good data then I may just scratch that idea. Thanks for the input Greg.

Adam is supposed to be sending me the link to the SL version by the time the ECU gets here so hopefully the wb scaling will be there.

Thanks again Greg.

Sent from my iPhone using Tapatalk

Just FYI, EvoScan finally replied to my ticket and said it is not possible. They said it would be a neat feature but who knows if/when it would get done.