is it better to have 0-1v or 0-5v set in lc1 for the output to the ecu?

 

Use the 0-5V linear analog out on the LC-1.

 

superb . working on pin73 for me jdm 3plug e8
with log reference WBO2 request 3c (most use mut12)
i did not have to make any xml changes for ecuflash or evoscan using tephra5.1
only had to scale the setting that was set in lc1 i.e 7.35 to 22.39afr in the formula
using 0-5v
1 happy customer

 

If I use the analog output #2 (brown wire) will I be able to hook up a gauge to the wideband also which version of evoscan will this work in?

 

Out of random curiosity why is it necessary to change the MUT table and log it via request 12? If you leave it alone and just log the rear o2 value (with the appropriate formula in place in Evoscan) will it conflict with anything? I haven't looked at your code, but I suppose it's possible that it would conflict.

 

The rear NB O2 signal is simulated, so if you log the rear O2 MUT channel, you'll just get that simulated signal.

 

That's interesting because I'm actually doing it, and NOT getting the simulated rear o2 value. I've got an FJO wideband (old school) with an NTK sensor. To test the accuracy I logged it with FJO's software/serial cable combination, and EVOScan simultaneously. They agreed out to .01.

I wonder if I'm doing something wrong somewhere? I'm using the 5.10 Tephra image and the emissions readiness check modifications. Car hasn't thrown any o2 or catalyst efficiency codes in over 4 months of driving so I'm pretty sure I did that part right.

 

First off, big thx to MrFred for this excellent patch.

I finally got around to getting the LC1 installed and replacing the std rear 02 sensor with the one that came in the kit.
The kit I bought included the LC1 with an O2 sensor but no gauge.

Wired it up to my ECU (using the brown wire into pin 75 on the ECu).....(I am running 96530706 on my Evo8) and made the changes to the data.xml for Evoscan (Ver 2,7 Beta2) and it is logging the Wideband AFR.

But I am having a small issue.....

When doing a 3rd geat WOT, The logging of the Wideband works great up to 5500rpm and then the AFR just shoots up to 22.XX and stays there until I come off the throttle, then the AFRs return to normal.

I then connect my laptop to the LC1 via a serial to USB convertor, and do another WOT log, logging the AFR's with Logworks3 while simultaneously logging the LC1 WideBand AFR with Evoscan.

Logworks logs the AFR perfectly throughout the WOT pull, right up to redline, while Evoscan logs the LC1 fine until 5500rpm, then the readings shoot up to 22.XX AFR again at roughly 5500rpm.

Where did I go wrong?
I doubt there is anything wrong with my LC1, as Logworks logs the complete WOT pull 100%.


Thx

Edit: I have performed the the heater and O2 calibration on the LC1/sensor.

 

Does it happen exactly at 5500 rpm?

 

After checking again, no it is not exactly at 5500rpm.

I have two logs here, where one happens at 4906rpm and the other 5750.

Attached below

 

Just had a thought....

If I am logging WideBand AFR from the ECU, is it still possible in Evoscan to log the LC1 through the USB/Serial convertor.

If so, which option should I check?
I tried logging WB02, but I get values of 10,2 - 10,4 at idle.

If I can log the AFR in Evoscan through the serial port and also from the ECU, this may show if it is a LC1 problem or a Evoscan problem.

 

I'm not sure about the LC1, but the AEM UEGO outputs both signals (serial and 5V) simultaneously, so you should be able to log from both. Sounds like a good way to check the equation used in EVOScan to translate the 5V signal.

 

Ok another update

I logged......
1.) Wide band AFR - which I believe is the anoluge input into pin 75 from the LC1
and also
2.) External wide band which is the input via the serial-USB converter from the LC1.

Basically the same results....
Both seems to stop reading at more or less the same place and display values of 62 AFr or 22 AFR.

Using my LM Programmer, I checked and my LC1 is running Ver 1.10 Firmware. One thing I did find odd, is that my analogue out 2 is always set to Lambda, and even when I set it to AFR and then program it, when I go back in to check, it has defaulted back to Lambda.
I am referring to this setting which won't stay on AFR.


Do you think this may be causing my problem with the logging in Evoscan?
Bearing in mind that Logworks is logging the AFR from the LC1 fine.

Attached is the new log showing the serial input and the Ecu input for AFR, and also a pic of the MUT table to show that I hopefully put Ox8409 in the correct place.

 

that thing about lamba or afr showing is normal.

it's just changing the display for you - i dont think it remembers the previous setting..

 

Maybe that page has changed in the 18+ months since this was posted. Is there still a source for Evo VIII harness pins?

d