I've noticed when I've pulled data out of entire tables to edit or run computations on with Excel, that the data in the cell seems to be a "rounded" representation of the real number. That is to say that if a cell shows 615, when I copy that cell and paste it into a MS excel sheet, 614.7698 could be the nuber that gets pasted in.
So this brings up two questions.
1. How many decimal places are usually used?
2. If I put 657.19 in a cell for tire revolutions per mile lets say, and when I hit enter or click off that cell, it changes to 657 only, is the actual data I put in still there and will be used or does it round and only use the 657?

The calculations used in EFILive are not rounded.

You can change your table displays by clicking on the +.00 icon or the -.00 icon in the tuning tool to show the number of decimals you wish to see.

Cheers
Cindy

Ah yes, I recall seeing that button now.:duh:
So only the "display" of the numbers is rounded based on how many decimal places you have choosen to display.

i also noticed this a while back, I now use 3 decimal places in a lot of tables

look at the pilot tables,if you dont use decimal places it can be a little confusing

Yup. Still new to tuning with EFI and just trying to learn...:o:

I dont think it matters, the decimel is always there, whether its hidden or not

Larry its more so for us, when we look at the tables

example look at b0748 pilot inj quant. if you have the numbers with no decimal places
you would only have 3 #s 0,1 & 2

now take this to the 3rd decimal place and we have alot more numbers! when i was referencing the b0750 table this didnt make sense to me because i didnt have enough decimal places set up:D

Number games:

The numbers are stored as binary integers. One byte can have 256 values, so let's say you need to describe 0-5 volts with it. So divide 256 by 5, and get 51.2 per volt, or increments of .0195... volts. So you type in 1.5 volts and how is it stored? Nearest binary value is 77, which is close enough, but is actually: 1.50390625 volts, not 1.500000 that you typed in.

To make it more complicated, the units are in metric, not Imperial, which put it through another level of mismatched resolution.

So don't sweat the resolution of the data, it is not what it really appears in most cases. If it says 23.89067 degrees of timing, don't assume the ...067 means anything. Just be grateful it's in decimal numbers so you don't have to figure how many degrees 0xFF4A is.

Useful Excel function for this.

= ROUND(RC, n)
This will reduce the decimal places of the data permanently if you wish.

example

=ROUND (2.33333333333, 2) is 2.33

Now you highlight it, right click, COPY.
Go to the same cell you started at and right click PASTE SPECIAL (not paste)
Select VALUES.

Now the number is permanently rounded. Very useful when posting data on the internet or printing.

Number games:



The numbers are stored as binary integers. One byte can have 256 values, so let's say you need to describe 0-5 volts with it. So divide 256 by 5, and get 51.2 per volt, or increments of .0195... volts. So you type in 1.5 volts and how is it stored? Nearest binary value is 77, which is close enough, but is actually: 1.50390625 volts, not 1.500000 that you typed in.



To make it more complicated, the units are in metric, not Imperial, which put it through another level of mismatched resolution.



So don't sweat the resolution of the data, it is not what it really appears in most cases. If it says 23.89067 degrees of timing, don't assume the ...067 means anything. Just be grateful it's in decimal numbers so you don't have to figure how many degrees 0xFF4A is.


Awesome! That's exactly what I was looking for. Thanks.

Number games:


To make it more complicated, the units are in metric, not Imperial
.

Something wrong with Metric:D

and thanks for the excel formula Pat