I want to possibly get a WB02 with some money I have been saving for several months, but I don't have a laptop to log the info. Is there a way to splice into the standard 02 sensor? Or would that not be accurate enough? If not... is there something else I can do aside from getting a laptop?

 

If you had a tactrix cable you could log to a memory card in it.

You can run it into the secondary o2 sensor, but the AP doesn't have the ability to log from it (I need to request that actually, even after putting an AP map on there my Tactrix cable can log the my LC1 wired into the secondary o2 sensor input (nothing else though)).

Honestly, it's my opinion that headless logging with the AP kind of sucks. Clunky after using the tactrix cable (just plug it in and it logs all the time is how I had it, with the AP its: wait for it to connect, select monitor, log, click ok, wait for it to fail, click ok, click ok, scroll down to knock, click OK and finally it's logging UGH). And don't get me started about having to use the AP manager to pull the logs off... ghey. Make them files on the device would be way easier....

 

yeah, having the ability to use a WB right from the AP would be a very cool feature.

 

so splicing into the OE wiring wouldn't really be accurate enough then huh?

 

I log via the ECU... so yeah splicing is fine...

LC1 is ok, but to be honest a PITA, especially when its not working properly..

ZT2 is probably much better for people that dont want to stuff around...

 

?

It's just as accurate as any other analog output. It just doesn't work with the AP, unless Cobb were to add the Rear O2 sensor address to the logging capability.

 

Nice i have the lc-1 and recently it has just been reading 15.0 across the boards. you guys think this is just the o2 sensor tht needs to be replaced?

 

ok, so one vote that splicing is ok, anybody else feel the same way and if so... which 02 do I splice into?

 

I have the LC-1 and it is a PITA to get it/keep it working with evoscan. I have had to recalibrate it 4 times in the past 3 months that I have had it.

It regularly reads in evoscan, but it likes to switch to lamda readings at will, requiring a full sensor recalibration.

Either get the AEM and pray that you can log on evoscan or save a little longer and get the Zetronics.

 

Good thing I stumbled on this thread had no idea the LC-1 was giving people problems. Now I will definitely go with the zeitronix.

 

Methodical4u - You will not be able to read or log via the AP if you splice it into the ECU.

 

no? well that sucks some *** doesn't it? lol

 

Yeah the trick is:
1) leave the serial cable disconnected ALWAYS
2) update the firmware
3) install a power-on delay timer, so that it waits 30 seconds (ie after cranking) before turning the LC1 on...

 

so far np's with lc1 working fine for me. just gotta calibrate it properly during setup.

 

nah the LC1 (well at least mine) is sensitive to power spikes, occasionally it will throw away the calibration settings (ie Custom instead of Gas in LMprogrammer)

LC1 is a good bit of kit, but it needs a little extra to be perfect