Page 1 of 1
Datalogging with external WB sensor
Posted: Tue Mar 27, 2007 9:53 am
by kurt
I have a WB o2 sensor installed on my exhaust and am thinking of using it for data-logging purposes. Can anyone tell me how I can set this up?
1. Hook it up to the ELD Pin? where is this located? I found some documentation in the S100 section but those were meant as a replacement to the NB o2 sensors.
2. Then probably tick 'Datalog ELD Voltage' in closed loop parameter
3. Choose WB sensor and set voltage to AF values under settings.
Is this right?
Thanks.
Posted: Tue Mar 27, 2007 10:48 am
by Spunkster
Posted: Tue Mar 27, 2007 11:13 am
by kurt
Read that but it looks like that is meant for replacing the stock o2 sensor vs wiring up an extra o2 sensor?
Or should I be following this portion:
Method #1 Closed/Open Loop - Wideband readings datalogged in S-Manager:
* Red wire Power cables for the PLX wideband - connect to switched power in the fuse box
* Black Ground - Attach to solid chassis ground
* White 0-5V Output from wideband - connect to ELD input making sure that the ELD is no longer connected to it (ELD is pin D10 on an OBD1 ECU)
* Gray 0-1V Output for narrowband - connect to white wire from stock O2 plug per instructions below
Posted: Tue Mar 27, 2007 12:18 pm
by Spunkster
You cannot just wire a wideband sensor into the ecu, it must have it's own separate controler such as the PLX Devices unit.
www.plxdevices.com
Posted: Tue Mar 27, 2007 5:03 pm
by kurt
This is for a Innovate LC1 which comes with a controller (like the LM1).
It works perfect on its own but am trying to figure out how to wire it up so that it sends the voltage signal to the ECU, where K-Pro/K-Manager can then data-log the LC1 readings.
Posted: Tue Mar 27, 2007 5:18 pm
by Spunkster
You must cut the wire that goes to the ELD and input the Wideband signal into that. Then in the software under Options, Settings, go to the Wideband input tab and set that up appropriately.
Posted: Tue Mar 27, 2007 8:15 pm
by kurt
Thanks, I will give that a try.
Also, I seem to notice that with rev 1.2.2.2 of K-Manager, values for min/max reading in the Knock/TPS section usually revert back to 0 when opening up a saved calibration.