Apparantly, TunerPro doesn't like whole values so it doesn't save them. Please delete as I have figured this out. Thanks!

 

What was the problem and what did you figure out? TunerPro likes whole values whole bunches. But only if you tell it to like them.

 

Well, in my spark advanced table....I just wanted whole values so that it was easier to read tuning it. So, I did in the toolbox, absolute fill in with value....whatever it was, clicked on the cell/cells I wanted it at and executed. Saved it. Closed it then opened it up to see if it saved and it didn't so after I posted my topic, I just tried to save it with another value and it saved so if there is a trick I didn't use, that would be very helpful.

 

Set the number of decimal places in the XDF item (i.e. select the table in the list and hit F2) to 0.

TunerPro converts the raw binary using the math specified in the XDF and rounds to nearest resolution allowed by the raw binary data. For instance, if the factor is 1.5 and the bin is data is 1 (bin data will always be a whole number), then you'll get an output of 1.5. If you put 1.6 in a cell and try to save it, it will round to 1.5. 1.7 rounds to 1.5. 2.8 rounds to 3 (which gets saved as 2 in the raw binary, since 3/1.5 = 2). Clear as mud? =)

This is by design. In gerenal, though, you wouldn't want to round your spark/fuel tables to the nearest integer. You'll lose a relatively significant amount of resolution by doing so.

 

Yea.....crystal! Thanks....never knew that existed.....interesting stuff in there.

Yea I know but since I was starting out I figured this would be easier to begin with whole numbers and then put decimal values in later to get the max out of it. Or would it?