I'm looking into figuring out a way to Datalog my DIY WB values but it does not corrispond with a PLX device mainly because it is non-linear.

Anybody have the reference voltage for the PLX device in the TE/ECUcontrol Plugging. That way when I log AFR I can Export to a ------ sheet and convert the AFRs to Voltages in Excel then Cross reference with the values I need.

 

The output voltages shouldnt have anything really to do with the device and more with the type of sensor used...no?

 

If they're non-linear, then it's not going to work... because those voltages won't corrospond with the voltages of the PLX.

 

does the output of the LC-1 match the PLX??
and iif it doesnt can you scale the voltages in ECUcontrol??

 

I know this, but if my sensor at 1.95volts is 11.5:1 AFR and on the PLX it is 10.1:1, ECUControl will log the 10:1, I then can take it into Excel, Convert the PLX 10:1 to voltage, and Vawla, I have my WB Voltage output that I can Corrispond to my AFR readings.

I otherwords, I just want to log the voltage of the sensor, seeing as I can't do it straight up, I will log it as a PLX Device.
i don't believe ECUControl will car if the Sensor is linear or not rights, It's still going to log what it reads, and then I can interpret the values.v Right?

FYI: The DI-WB use the Honda VX Sensor.

 

Okay I just found the equation from the PLX Site.

If I log a 15:1 AFR on a PLX Device thats

AFR=2*Voltage+10
Thus
Voltage is going to be
V=(15-10)/2
V=2.5volt
Take that to my sensor:
where 2.5 volts is 14.70AFR.

I have an equation for the Voltage to AFR for my sensor, so I won't alway have to reference to a chart, just copy and paste into cells.

Anyone see a problem with my theory.

 

Also If I have an equation to determine the Voltage to AFR could that not be written into ECUControl so that a non-linear device can be used? I'm not a Programming or ECU Genius so I don't now how the ECU would interpret this input?

 

If you have a formula that converts it, yes... otherwise, if you're using a "Table" then that is a pain in the *** because it has to be statically compared.

The ECU also doesn't "do" anything with the information. ECUs do not interpret the WBO2 data...

 

That's what I thought.
I used Excel TrendLine to dtermine it, In comparisson it is on like xx.xx2 off, so not biggy. The widebands accuracy isn't even that exact.

What are the instructions for inputing WBo2 for Datalogging using TE/ECUControl?

 

I dont' know.. you'll have to get with Nick about that. So far, I don't think he's got anything setup for userdefinable WB tables.