Ok, I will use "output" when talking about table content from now on. I know the output of the BTS table is requested lambda, my question is if the BTS table output that you see in the pic(ex: 1.0079@ intersection of x? and y? ::it's an example just pick one::..) is a direct representation of lambda or is it something else? So in other words if I have a value of 1.001 @ an intersection of the table, the AFR of that cell will be 14.7xx. (this would mean the table values are a direct representation of lambda(actually requested lambda)) what I mean by something else is: Do I need to perform some other kind of arithmetic to figure the AFR using the table output?
Why would you need to do that? The z axis of tables is always the output of the table. Have you looked at the FR yet? If there are other conversions/scaling to be done, they are described in the FR.
Unless you are referring to the fact that the ACTUAL value stored in the ECU's memory (8 or 16 bit) isn't actually an infinitely precise floating point, and must be represented as a fixed point integer.... which is an entirely different discussion.
lambda voltage is the number represented as the lambda value
This terminology is NEVER used for a reason. Sensor voltage is converted to a lambda value. Depending on the sensor, the conversion is different. Same with MAFs.
Sensor voltage is sensor voltage.
After it is converted to different units (g/sec or lambda or AFR), it no longer has the "voltage" units.
Thus it is NEVER referred to as "lambda voltage" or "g/sec voltage", which would be confusing because there would be no way to know if the person is talking about the resulting (calculated) lambda value, or the actual voltage coming from the sensor.
It would be properly referred to as "O2 sensor voltage" or "MAF sensor voltage"
