why is it that when I type in a value in the lambda row of the voltage conversion table, it puts a value different than what I typed.
for example if I type in 0.85, then press enter. It inserts a value of 1.18.
and if I go the other way and type in 1.18, then press enter. It inserts a value of 0.85. What is the reason for this?
Voltage / Lambda Conversion Table entry problems
I am unable to reproduce what you are describing. Can you please give a detailed description of exactly what you are doing...which cells you are changing and what you have your units set to? If you can post the calibration as well that will be helpful.
Last edited by Spunkster on Tue Dec 23, 2008 5:38 pm, edited 1 time in total.
after I downloaded the new version it worked "better". It will sometimes change a 1 to a 2 or something like that which is kind of annoying because I use a dynojet wideband commander, and its votlage conversions can go down to the millionths of a volt. Hondata doesnt allow you to type that many digits.
Also when I finally get a number that it will accept properly, its still not accurate. Is it possible to just use a formula rather than a table? dynojet provides the formula for the dynojet one specifically
(volts * 1.6) + 10 = AFR
would be pretty sweet if you could just incorporate formula's into it we wouldn't have to worry about conersion tables (at least in my situation, not sure how other brands work)
here is a link to a spreadsheet which also gives a list of the voltage conversion
http://www.widebandcommander.com/content/dataacq.xls
Also when I finally get a number that it will accept properly, its still not accurate. Is it possible to just use a formula rather than a table? dynojet provides the formula for the dynojet one specifically
(volts * 1.6) + 10 = AFR
would be pretty sweet if you could just incorporate formula's into it we wouldn't have to worry about conersion tables (at least in my situation, not sure how other brands work)
here is a link to a spreadsheet which also gives a list of the voltage conversion
http://www.widebandcommander.com/content/dataacq.xls
never mind, seems the update changed arf back to lambda...again.
Should have know to check that. Now my digital dashboard says lambda again. I'm all for improvement but...grrrrrrr. It's a little aggravating to have to change this stuff back every time there is an update.
Or maybe I should just always use lambda :?
Should have know to check that. Now my digital dashboard says lambda again. I'm all for improvement but...grrrrrrr. It's a little aggravating to have to change this stuff back every time there is an update.
Or maybe I should just always use lambda :?