LC-1 installed, logging AFR without serial cable
The setup that mrfred is doing is using the rear O2 input of the ECU (ie pin 75 on evo8 but not sure about the evo9 input pin).
The setup that I am running is using a FREE input on a evo8 ecu (which is pin 74 for example on european spec). However - you need to check whether it is free on your as well.
The setup that I am running is using a FREE input on a evo8 ecu (which is pin 74 for example on european spec). However - you need to check whether it is free on your as well.
It would be nice, if we could replace the whole rear o2 with a wideband sensor.
VW o2 sensors are wideband o2's, Bosch Part # 17014 (this is the same o2 sensor in my turboxs wideband)
http://www.musclecarclub.com/carpart..._Oxygen_Sensor
wiring diagram:
Red = Heater +
White = Heater -
Black = Signal wire
Gray = signal gnd
Yellow = pump circuit (that adds or removes oxygen from the o2) corrects things.
If you want you can find a cheap wideband gauge to wiring it up to sensor, if you like looking @ #'s all day LOL
http://www.dynotunenitrous.com/store...?idproduct=171
VW o2 sensors are wideband o2's, Bosch Part # 17014 (this is the same o2 sensor in my turboxs wideband)
http://www.musclecarclub.com/carpart..._Oxygen_Sensor
wiring diagram:
Red = Heater +
White = Heater -
Black = Signal wire
Gray = signal gnd
Yellow = pump circuit (that adds or removes oxygen from the o2) corrects things.
If you want you can find a cheap wideband gauge to wiring it up to sensor, if you like looking @ #'s all day LOL

http://www.dynotunenitrous.com/store...?idproduct=171
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
yay someone finally bothered to do it 
few questions:
1) what voltage does the ADC accept, narrow band is 0-1v, so is that pulled down someplace in the ECU or before hand?
2) you only had to connect the signal wire? ie the ground wire (isn't one) works via the chassis?
3) is the logging via analogue faster than serial?
4) what AFR range have you configured in your LC1, I'm thinking 10(0v)-17.0(1v), then use 13.5 as .5v, should make the formula for Evoscan easy

few questions:
1) what voltage does the ADC accept, narrow band is 0-1v, so is that pulled down someplace in the ECU or before hand?
2) you only had to connect the signal wire? ie the ground wire (isn't one) works via the chassis?
3) is the logging via analogue faster than serial?
4) what AFR range have you configured in your LC1, I'm thinking 10(0v)-17.0(1v), then use 13.5 as .5v, should make the formula for Evoscan easy

- Technically, the LC-1 signal ground should be grounded to the exact same point as the ECU signal ground wire. The ECU is grounded to several places on the car via a multipoint ground wire that runs from the battery to the motor to the firewall and onto the driveshaft tunnel. Rather than mess with tapping into the signal ground wire on the ECU harness, I choose to ground the LC-1 signal wire to a bolt near the ground location on the driveshaft tunnel. Seems to have worked fine as the I see 4.99 V momentarily as the LC-1 is transitioning from preheating to normal operation.
- The LC-1 analog output #2 produces a 0-5V signal that covers 7.35 AFR to 22.39 AFR. The EvoScan formula is: 0.05859*x + 7.35. And if anyone has any need, I think this range can be reconfigured using the LM Programmer software.
Thread Starter
EvoM Guru
iTrader: (50)
Joined: Mar 2006
Posts: 9,675
Likes: 132
From: Tri-Cities, WA // Portland, OR
I'll put together a more detailed write up this week.
Here is a question for everyone: The ADC inputs all have two scaling ranges, one that scales 0-5V over one byte (255 bins) or 0-5V over 4 bytes (1023 bins). I did my initial setup using the 1-byte range. This gives an AFR resolution of 0.06 AFR using the LC-1 factory setting of 7.35:1 AFR to 22.39:1 AFR = 0 - 5 V. I think that this is a reasonable resolution for AFR logging. If I were to have used the 4-byte range, I would have an AFR resolution of 0.015 AFR, but this seems like overkill, and I'd have to log AFR using the 2-byte method like for load which slows down EvoScan a little bit more. Its also a bit more work to setup the ROM for the higher resolution.
And another way to get better resolution would be to reprogram the LC-1 to cover a narrower range. 8.5:1 AFR to 17:1 AFR would give a resolution of 0.033.
What do you folks prefer for resolution vs logging method?
Here is a question for everyone: The ADC inputs all have two scaling ranges, one that scales 0-5V over one byte (255 bins) or 0-5V over 4 bytes (1023 bins). I did my initial setup using the 1-byte range. This gives an AFR resolution of 0.06 AFR using the LC-1 factory setting of 7.35:1 AFR to 22.39:1 AFR = 0 - 5 V. I think that this is a reasonable resolution for AFR logging. If I were to have used the 4-byte range, I would have an AFR resolution of 0.015 AFR, but this seems like overkill, and I'd have to log AFR using the 2-byte method like for load which slows down EvoScan a little bit more. Its also a bit more work to setup the ROM for the higher resolution.
And another way to get better resolution would be to reprogram the LC-1 to cover a narrower range. 8.5:1 AFR to 17:1 AFR would give a resolution of 0.033.
What do you folks prefer for resolution vs logging method?
nice stuff mrfred quick question since I am using a different wideband my afr range is 9.0 -24.9 would the formula for evoscan be 0.05859*x + 9.0?
what MUT request ID is the rear o2 sensor?
you have a great point about the higher resolution be an overkill unless ppl are that picky.
what MUT request ID is the rear o2 sensor?
you have a great point about the higher resolution be an overkill unless ppl are that picky.
Last edited by bnice01; Apr 7, 2008 at 08:27 AM.
Depending on the sensor being logged, there might be interest in finer-grained resolution (wideband input isn't the only potential use for this
). So, having the ability to do multi-byte recovery might be handy.
(But as you pointed out, for this particular use case where the sensor output can be recalibrated anyway, a single byte of resolution is plenty.)
). So, having the ability to do multi-byte recovery might be handy.(But as you pointed out, for this particular use case where the sensor output can be recalibrated anyway, a single byte of resolution is plenty.)
excellent
next question how do we find the mut addresses for the ADC in different roms???
is it trial and error inject 5v into the analog input and monitor mut for changes??
or is someone going to disassemble the roms to find the addresses,
as I am using an evo 7 rom.
next question how do we find the mut addresses for the ADC in different roms???
is it trial and error inject 5v into the analog input and monitor mut for changes??
or is someone going to disassemble the roms to find the addresses,
as I am using an evo 7 rom.
The analog outputs of the LC-1 and Zeitronix ZT2 are QUITE faster than the serial output. I forget the LC-1's specs but the ZT2's serial output updates 75 times per second but their analog outputs (they have two types) update 1000 times per second! Quite a difference.
Ohhh please do a write up, I broke my USB plug inside my laptop from throwing my laptop around in the car! Damit, I have to take apar my laptop to fix it now. But, this woul dbe cooler, only having to have the open port plugged into it.
It's pretty easy, wireup the WB like normal, then replace the O2 connection (As pictured for IX's) with the analogue output from the LC1.
Then use LMProgrammer to configure the output parameters of that analogue channel.
it is 0-5v (unlike I thought previously) the EvoScan formula restricts the Rear02 to 0-1v.
I'm definatley going todo this, because this morning I couldn't get the serial to talk to the LC1 - grrrr.. piece of ****!!
Then use LMProgrammer to configure the output parameters of that analogue channel.
it is 0-5v (unlike I thought previously) the EvoScan formula restricts the Rear02 to 0-1v.
I'm definatley going todo this, because this morning I couldn't get the serial to talk to the LC1 - grrrr.. piece of ****!!
tell me about it - this time ive wired it in totally properly and im still having problems.
LMprogrammer or logworks or evoscan just would NOT connect this morning - hence why I want analogue, hopefully set and forget...
LMprogrammer or logworks or evoscan just would NOT connect this morning - hence why I want analogue, hopefully set and forget...



