??

I'm asking only for the direct 0-5V --> A:F converstion factor. You seem to be saying it's (signal/5*100)/10. That can't be right....

EDIT: at the very least it must have stoichiometric value for gasoline in it somewhere.

d

 

From the LC-1 manual. The "second output" feeds the Xede.

Quote:

As discussed in section 7.6 above, factory settings for the second output is programmed where 0V=.5λ (AFR of 7.35 for gasoline) and 5.0V=1.523λ (AFR of 22.39 for gasoline).

 

Excellent. Thanks man. I thought it should be in the manual, but seemed to have missed it every time I looked.

thanks again.

d

EDIT: just to confirm. the scale is linear from 0v to 5v, correct. I'm adding support for smart stuff to my pyxede software.

 

What are you guys using to log this stuff?

 

Yes, only 2 points are required to "calibrate" a wideband's output 0-5v "curve."

 

My own software. A new public version is forthcoming. I just need to do some debugging first. It'll do all kinda of nice things like do specialized data collection for dyno runs, calibrate and smooth data, and draw multiplots.

In the last two weeks, i've moved cross country so car stuff has kinda fallen by the wayside. It's only in the last couple of days that I've had time to start coding for the hardware that I recieved in mid august.

d

 

Concur

 

Here is a table that Shiv posted, this is what I have been using to tune from, I hope that it is correct.....

https://www.evolutionm.net/forums/sh...d.php?t=151628

post #12

Here's calibration data for the wideband. Remember that 0-5v equates to 0-100% in the XEDE (for now, we'll translate it to AFR in the next XMAP update). But for now, 50%=2.5v=15:1AFR and 20%=1v=12:1.



Shiv
__________________
Get S.M.A.R.T.

From this I have:

Voltage--- % reading in table AN0----- A/F
0--- 0% 10
0.05--- 1%--- 10.1
0.1--- 2%--- 10.2
0.15--- 3%--- 10.3
0.2--- 4%--- 10.4
0.25--- 5%--- 10.5
0.3--- 6%--- 10.6
0.35--- 7%--- 10.7
0.4--- 8%--- 10.8
0.45--- 9%--- 10.9
0.5--- 10%--- 11
0.55--- 11%--- 11.1
0.6--- 12%--- 11.2
0.65--- 13%--- 11.3
0.7--- 14%--- 11.4
0.75--- 15%--- 11.5
0.8--- 16%--- 11.6
0.85--- 17%--- 11.7
0.9--- 18%--- 11.8
0.95--- 19%--- 11.9
1--- 20%--- 12
1.05--- 21%--- 12.1
1.1--- 22%--- 12.2
1.15--- 23%--- 12.3
1.2--- 24%--- 12.4
1.25--- 25%--- 12.5
1.3--- 26%--- 12.6
1.35--- 27%--- 12.7
1.4--- 28%--- 12.8
1.45--- 29%--- 12.9
1.5--- 30%--- 13
1.55--- 31%--- 13.1
1.6--- 32%--- 13.2
1.65--- 33%--- 13.3
1.7--- 34%--- 13.4
1.75--- 35%--- 13.5
1.8--- 36%--- 13.6
1.85--- 37%--- 13.7
1.9--- 38%--- 13.8
1.95--- 39%--- 13.9
2--- 40%--- 14
2.05--- 41%--- 14.1
2.1--- 42%--- 14.2
2.15--- 43%--- 14.3
2.2--- 44%--- 14.4
2.25--- 45%--- 14.5
2.3--- 46%--- 14.6
2.35--- 47%--- 14.7
2.4--- 48%--- 14.8
2.45--- 49%--- 14.9
2.5--- 50%--- 15
2.55--- 51%--- 15.1
2.6--- 52%--- 15.2
2.65--- 53%--- 15.3
2.7--- 54%--- 15.4
2.75--- 55%--- 15.5
2.8--- 56%--- 15.6
2.85--- 57%--- 15.7
2.9--- 58%--- 15.8
2.95--- 59%--- 15.9
3--- 60%--- 16
3.05--- 61%--- 16.1
3.1--- 62%--- 16.2
3.15--- 63%--- 16.3
3.2--- 64%--- 16.4
3.25--- 65%--- 16.5
3.3--- 66%--- 16.6
3.35--- 67%--- 16.7
3.4--- 68%--- 16.8
3.45--- 69%--- 16.9
3.5--- 70%--- 17
3.55--- 71%--- 17.1
3.6--- 72%--- 17.2
3.65--- 73%--- 17.3
3.7--- 74%--- 17.4
3.75--- 75%--- 17.5
3.8--- 76%--- 17.6
3.85--- 77%--- 17.7
3.9--- 78%--- 17.8
3.95--- 79%--- 17.9
4--- 80%--- 18
4.05--- 81%--- 18.1
4.1--- 82%--- 18.2
4.15--- 83%--- 18.3
4.2--- 84%--- 18.4
4.25--- 85%--- 18.5
4.3--- 86%--- 18.6
4.35--- 87%--- 18.7
4.4--- 88%--- 18.8
4.45--- 89%--- 18.9
4.5--- 90%--- 19
4.55--- 91%--- 19.1
4.6--- 92%--- 19.2
4.65--- 93%--- 19.3
4.7--- 94%--- 19.4
4.75--- 95%--- 19.5
4.8--- 96%--- 19.6
4.85--- 97%--- 19.7
4.9--- 98%--- 19.8
4.95--- 99%--- 19.9
5--- 100%--- 20

Once again, assuming the table Shiv posted it correct, then this should be as well.....

 

A table isn't necessary.

Just do (22.39-7.35) * signal + 7.35

where signal is 0.00 - 1.00 (0 - 100%)

Notice that 50% is not actually 15:1, rather it's 14.87:1. It might not matter to most, but when you're writing code and worrying about error in 8bit arithemetic, it matters.

d

 

Are you shure that is correct? I am not trying to be rude, but I have been tuning the past two days using the table Shiv posted, and if it is off a bit then that means my whole tune is off a bit.

At least it looks like I would be a bit rich instead of a bit lean.....

 

You can plug into the wideband and bring up the programmer software for the LC-1 to confirm the range that Innovate published in the manual. Just don't change anything.

 

I guess that I do not need too if you already have....Oh well, it looks like a bit of tweaking to my maps may be in order. And I was kind of wondering why my car liked to idel at 50-54% when that would have been 15.0-15.4 AFR......

 

Sure? No. Not yet anyways.

I have the (edit : )LC-1 manual in front of me. Here's my reasoning.

0v (0%) is 7.35:1 AFR
5v (100%) is 22.39:1 AFR

Assuming the sensor signal is linear, 50% is right in the middle, 14.87. This is what everybody should be getting for V2 Xede wideband readings.

However, V3 may do some adjustment to the voltage levels before passing them on the the user. There are various reasons why chiptorque/vishnu might want to do this, but i'm not going to speculate. I'll just call one of the boys at vishnu when I get a chance.

EDIT: also notable is that high speed data logging on the xede produces only 8bit values. While 14.87 and 14.93 _can_ be represented, 14.90 cannot.

d

 

Very good, I will just let the maps sit as they are right now, like I said it will be a bit rich rather then lean. I am glad you brought this up though as I have not even downloaded the LC-1 disk or even paid much attention to the manual although I probably should. I have just been going along with what Shiv posted sence they are the ones releasing the system. Please post when you talk to Dustin or Shiv.

 

Holy Bejesus!! If that is correct then my A/F's could be WAY off!!! Please let us know when you find out.....