I need to use a custom lambda conversion since I'm not using neither the horiba or the motec unit. First of all i think it's widely known that if you input the lambda values in Custom, it will erase them next time you stop or start the program..so I have a registry file that i import after starting rom editor.
Below is what I've set for my conversion..since it only lets you use 2 digits, I already rounded to .0x.
"0"="1.4 0.69"
"1"="1.5 0.71"
"2"="1.7 0.75"
"3"="1.8 0.77"
"4"="2.0 0.83"
"5"="2.1 0.86"
"6"="2.2 0.89"
"7"="2.3 0.92"
"8"="2.4 0.96"
"9"="2.6 1.08"
"10"="2.7 1.17"
"11"="2.9 1.41"
Well, after they are imported, RomEditor rounds them again to .x.
So my values turn out to be:
"0"="1.4 0.60"
"1"="1.5 0.70"
"2"="1.7 0.70"
"3"="1.8 0.70"
"4"="2.0 0.80"
"5"="2.1 0.80"
"6"="2.2 0.80"
"7"="2.3 0.90"
"8"="2.4 0.90"
"9"="2.6 1.00"
"10"="2.7 1.0"
"11"="2.9 1.0"
The corresponding A/F to these values are as follows:
.70 = 10.38
.80 = 11.76
.90 = 13.31
1.0 = 14.7
So out of the 12 points of reference, it only uses 4...does it extrapolate in-between????
The biggest amount of difference would from my original values would be 1.5v and 1.8v...it rounded them both to .70..but in actuality 1.5v=10.08 and 1.8v=11.38...over a FULL point.....BIG difference. Anyone else notice this problem..or have a fix?? Please respond. Maybe I'm missing something simple. Thanks.
Setting lambda issue.
Hmm, not quite....I guess that works, but its still rounding somehow. It must be rounded to a preprogramed lambda value? When i put the numbers in they stay fine...If i close the program and re-open it, they are pretty close, but defintely not the numbers i put in. Can't find any ryhme or reason as to it's rounding. Derek? Is this fixed in v3.0?G3-TEG wrote:I've found that if you setup the CUSTOM table using A/F values for the voltages rather than Lambda, it works just fine and saves them in the registry.