B3701 not updating when i save... Please help....

[BlackGMC]

Well i was trying to adjust my tune for new injectors and everytime i update B3701, and save the tune it, close it, then reopen it, the values are the same... For example, i wanted to add 1% to 13.5V column, it applies the percentage, and I save it.. It appears to have updated... I flash in the tune then download it and nothing has changed... Or if I just close the file and reopen it, the values are the exact same... I have tried reinstalling the software (twice) and it still does it...

please help....

[GMPX]

What ECM type?

[BlackGMC]

what ever a 2004 Sierra uses.. sorry i don't know... but it is not the truck computer it is the software...

[GMPX]

I asked what type so I didn't go looking for a problem on a 2011 Corvette, or 2001 Duramax. Is it a Duramax or LS?

[BlackGMC]

It is a LS.... It is weird.. Sometimes it updates if i use a larger percentage, but i have never got it to save trying 1 or 2 percent. I have 3 computers at my house with the latest EFI Live software, and none of them worked....

I am attaching my tune, see if you can update one column in the B3701 by 1%...

[GMPX]

Works fine here...see below, first column.

Before change:
0 13.997333
5 13.997333
10 13.997333
15 13.997333
20 13.997333
25 13.997333
30 13.997333
35 13.997333
40 13.997333
45 13.997333
50 13.997333
55 13.997333
60 13.997333
65 13.997333
70 13.997333
75 13.997333
80 13.997333

After Adding 1%, saving and reopening the file:
0 14.136533
5 14.136533
10 14.136533
15 14.136533
20 14.136533
25 14.136533
30 14.136533
35 14.136533
40 14.136533
45 14.136533
50 14.136533
55 14.136533
60 14.136533
65 14.136533
70 14.136533
75 14.136533
80 14.136533

[BlackGMC]

i just tried it again. I was able to add 1% to the first column.. But when i go to add 1 % to some of the values in column 13.5V, it still does not save... When i mean save, i mean closing and reopening the file...

[joecar]

How many decimal digits are you displaying...? Try increasing the number of decimal digits (the button labeled "+.00").

[BlackGMC]

I tried the decimal thing, still does not work. I can see it update on the screen however when i reopen the file it is not updated. I have also tried updating it, then flashing it in then downloading it and it is still not updated... It is really strange... I have had efi live for 5+ years and I have never ran across something like this...

[BlackGMC]

another thing it shows up in the history as being updated, but it is not...

[BlackGMC]

I just tried to update these values

LABELS Battery Volts {link: GM.VOLTS}
Manifold Vacuum kPa {link: GM.MANVAC} 14.0
0 0.077333
5 0.077333
10 0.077333
15 0.061867
20 0.061867
25 0.061867
30 0.061867
35 0.061867
40 0.061867
45 0.061867
50 0.061867
55 0.061867
60 0.061867
65 0.077333
70 0.077333
75 0.077333
80 0.077333

I tried 1%, 2%, 3%, 4%, 5%, 7%, 10%, 11%, nothing ever happened. Then on 13% it looked like this when i saved it

LABELS Battery Volts {link: GM.VOLTS}
Manifold Vacuum kPa {link: GM.MANVAC} 14.0
0 0.077333
5 0.077333
10 0.077333
15 0.069909
20 0.069909
25 0.069909
30 0.069909
35 0.069909
40 0.069909
45 0.069909
50 0.069909
55 0.069909
60 0.069909
65 0.077333
70 0.077333
75 0.077333
80 0.077333

Then after i closed it and reopened it it looked like this

LABELS Battery Volts {link: GM.VOLTS}
Manifold Vacuum kPa {link: GM.MANVAC} 14.0
0 0.077333
5 0.077333
10 0.077333
15 0.077333
20 0.077333
25 0.077333
30 0.077333
35 0.077333
40 0.077333
45 0.077333
50 0.077333
55 0.077333
60 0.077333
65 0.077333
70 0.077333
75 0.077333
80 0.077333



I am only trying to update the 0.061867 value....


seriously i am not crazy even thou it appears that way...

[joecar]

Post your before and after files here, please.

[BlackGMC]

I can post them tonight, i don't efi live on my work laptop :(

[joecar]

ok.

[Blacky]

The LS1 PCM (and most* vehicle controllers) are calibrated using integers (i.e. whole numbers) to reduce the cost and processing load on the CPU.
High precision floating-point values require dedicated hardware (more expensive) or software floating-point routines which slow down calculations.

* Note: Later model controllers use CPUs with built in floating point hardware and they do make limited use of high precision floating point data.

Storing calibration data as integers like the LS1 PCM does, allows only a discreet set of scaled floating point values.
For example if the PCM requires a table to contain data from 0.00-100.00 (for example throttle percentage) using only the set of integers from 0..255 (i.e. a single byte) then it would scale that set of integers by dividing each one by 2.55.
That would mean the following conversion would be in effect:
0 = 0.0
1 = 0.392157
2 = 0.784314
...
245 = 99.607843
255 = 100.0

As you can see, if the PCM can only store the values from 0..255, then when it has a 1 stored the PCM will interpret it as 0.392157, when it has a 2 stored the PCM will interpret it as 0.784314.
Since it is impossible to store an integer value between 1 and 2, which means it is also impossible to represent any value between the two discreet values: 0.392157 and 0.784314.

What you are seeing in the B3701 table is the effect of the limits of the integer to floating point scaling that I described above - just with different scaling.
The EFILive tuning software allows the user to enter full precision floating point values. It has to do that to preserve as much precision as possible while the user is editing/manipulating the data. Because of that you can enter any floating point value that you want into the tables. When the data is saved back to the tune file, the software must convert the final floating point values back to their nearest scaled integer values that the PCM requires.

There is no way to calibrate any values between the two values (0.061867 and 0.077333) that you are seeing. Its either one or the other.

Regards
Paul

[BlackGMC]

Thanks for the respone Paul, i appreciate it. Yesterday it was driving me crazy...