ok well i just hooked up my wideband o2 sensor to the haltech last night.
its the new sm afr from plx and im running an E8 with the new firmware.

so heres the problem it will not datalog the 02 signal. the 02 sensor is outputting and the haltech is receiving. i know it is out putting because i put a dmm in the analog out port of the sm afr and it went from 2.5 to 5 as it warmed up (with the car off) according to plx this is exactly what is supposed to do and it makes sense. i then connected it to the haltech's spare AD 3 and defined it as a wideband 02. i opened the analog input data page and switched it to volts. turned the car back on and i watched the voltage go from 2.5 - 5 volts. but when i change it to units it always reads 0.1 AFR which is most definitely wrong. it also reads this in the data page that only has the wideband reading in it. in the data log while driving around it only data logs 0.1 AFR the whole time even though i can watch the voltage changing in the datalog page when switched to voltage instead of AFR.

so i have come to the conclusion that there is some setting or some conversion wrong inside the haltech that will not convert the voltage to AFRs. or it is possible i found a bug in the new firmware.

any ideas what i need to change to fix this?

and if not does any one know how i can just make the haltech data log straight voltages and i will convert it into AFR's with excel later.

 

further searching solved the problem. ignore the post

 

Care to tell what the problem/solution was?

 

oh its just that in your maps the wideband is not calibrated at all so all you need to do is go into the sensor setup/sensor calibration/wideband 02 then input some numbers. its a nice little feature that lets the user change the associated voltages to AFR to compensate for the slight difference between every 02 sensor as well as different model widebands. it was in there before i just missed it completely when i went to look at the sensors.

 

hummm new question now the appropriate AFRs appear in the data page but for some reason in the data log it does not log the AFR but rather some strange numbers between 0 and 1. any ideas as to how to correct this? as usual i will keep looken but any ideas would be great.

 

allrighty answered my own question with some help from haltech. and btw they are a very helpful group over there.

any way what i noticed is that it is logging lambda and it was only logging in .1 increments. which for lambda... sucks!!! well after a call to haltech i asked if it was possible to change that lambda number to AFR in the data log and they said no. but they then went on to explain to me that the 02 sensor does not read AFR it always reads lambda. which was news to me but when i think about it makes MUCH more sense then attempting to read AFR. so any way their main reasoning for logging lambda and not AFR is for the auto tune feature because it works on lambda, this is to compensate for all different types of fuels. which once again makes perfect sense because it is a safeguard in that you wont be able to nuke the motor if you start using a fuel with a higher concentration of alch, meth, eth or any of those additives. and then on to the fact that i could only see in .1 increments. this is obviously an issue in that a .1 change in lambda is equal to a 1.47 change in AFR. this was a simple problem solved though the "No. DPS" setting in the settings for each logged value. it stands for number of decibel places which i should have seen in the first place and the haltech guy didnt noticed it until i pointed it out. now i can see the lambda to any accuracy i want so not being accurate enough will not be an issue. now they will be able to answer that question very fast if any other stupid people like me call in asking about it.

any way i hope this will be useful in some ones search down the line.

-carlos

 

I think I am missing something here, you want to datalog and see AFR instead of lambda and haltech told you its not possible. Is that what your saying?

Instructions for Halwin 7.1 with B32 firmware (its going to be slightly different for 7.0.1 or any beta with autotune):

First you do have the WB02 hooked up to a spare analong (A/D) input correct?

In the setup drop down of halwin, go to calibrate sensors, WB02 sensor, set the work in radio button to AFR, then set the fuel type to gasoline (assuming you are burning gasoline) , and modify the table to corespond to the WB02 sensor and controller that your using.

Then when you datalog, choose whatever paramaters to log that you desire, you will find the wideband under analog to digital channels "Wband 02 input (inputspareAD#).

Datalog.

view your datalog and it will be in AFR.

I have done this with 7.1 (no autotune), 7.0.1 BETA (with autotune) and for a long time with 6.2.

Good luck.

 

yup i did all that and it logs the lambda.

i called haltech and they said it WILL NOT log AFR.

its what they said not me. i dunno if the beta im using is different but thats how it is.

 

which version of halwin are you using?

Note, that haltech recently removed the word beta from halwin 7.1 as its hosted on their website.

 

1.71