Linear-fill

[Chevy366]

Found the linear-fill . it seems if you move the left hand side repository tree it causes the linear-fill to be hidden when window is not fully opened .

Just noticed when I saved the Original tune that was read form the PCM , before flashing with Custom OS , to another name it changed the VIN number .
Checked a old .tun and saw it as well has a different VIN number ?
Also when I did the read of the Custom OS back off the PCM data was still present from another session of Custom OS .
Why is old Custom OS data still in PCM after full re-flash ?
http://s71.photobucket.com/albums/i138/My-fotos/?action=view&current=vin.jpg

[Blacky]

Found the linear-fill . it seems if you move the left hand side repository tree it causes the linear-fill to be hidden when window is not fully opened .
Its the way the toolbars have been setup. At the time it was the best compromise between usability and functionality.


Just noticed when I saved the Original tune that was read form the PCM , before flashing with Custom OS , to another name it changed the VIN number .
Checked a old .tun and saw it as well has a different VIN number ?

The VIN displayed in the tuning tool software is the VIN contained in the *.tun file (not necessarily the VIN in the attached PCM). When you full-flash a PCM, EFILive first saves the VIN, BCC etc from the PCM, then reprograms the PCM from the *.tun file, then overwrites the VIN, BCC etc with the original VIN, BCC etc in the PCM *before* the full-flash was started. You can always manually change the VIN using the Scan Tool (or the Tuning Tool's VIN change option in the PCM Locking window).


Also when I did the read of the Custom OS back off the PCM data was still present from another session of Custom OS .
Why is old Custom OS data still in PCM after full re-flash ? I don't know why (or how) custom data can be left in the PCM. The PCM is totally erased during a full flash. So the only way for custom data to remain would be if EFILive explicitly copied it back into the PCM after erasing it.
I'll have to get Ross to answer that. Just for our reference, what data was left in the PCM? If you just mean VIN, BCC etc (i.e. not table/calibration data) then that is explained by the response above.

Regards
Paul

[Chevy366]

I don't know why (or how) custom data can be left in the PCM. The PCM is totally erased during a full flash. So the only way for custom data to remain would be if EFILive explicitly copied it back into the PCM after erasing it.
I'll have to get Ross to answer that. Just for our reference, what data was left in the PCM? If you just mean VIN, BCC etc (i.e. not table/calibration data) then that is explained by the response above.
Thank you for the response .
No it was the upper segment of the Custom OS , EFILive Custom Calibrations , Parameters , Boost VE Table , IAT VE Table .....etc , all with values intact .

[Chevy366]

Just so I did not drive myself crazier , I re-flashed a stock OS and did the process again , still get values in the Custom EFILive tables , is there default values placed there now ?

Thanks
Gil

[Chevy366]

Process I did :
Full Re-Flash Stock OS > Full Re-Flash with Custom OS form folder in Tune Tool , correct COS3 > Calibration only flash to COS3 with stock .tun file > read PCM > values present in EFILive Custom Calibrations , Boost VE fully mapped , A0014 has curve present in value field , A0008 same has curve in value field , curve meaning values as entered formed a curve in the graph , these values should not be present the Boost VE should be 0 (zeroed) and A0014 should have all 1's or 0's and A0008 all 1's or 0's not any previous values .
What is strange the values are not consistent with any I have ever used in those fields , Boost VE , A0014 or A0008 .

[Blacky]

Can you send the two *.tun files that you are flashing to me ([email protected]). I can check what is in each of them and where the "data" is coming from (and hopefully why).

Regards
Paul

[GMPX]

Yeah, I'm with Paul, need to see the 'stock' tune and the others you are flashing in. It sure doesn't make much sense.

Cheers,
Ross

[Chevy366]

Sent to you both .

[Chevy366]

Just checking to make sure you both received the e-mails .

[Blacky]

I don't think I've seen the email.
Paul

[Chevy366]

O-k sending again then .
Will label "COS3" .
Please let me know what you find out .

[Blacky]

O-k sending again then .
Will label "COS3" .
Please let me know what you find out .

Ok, got the files :)
I also got the first set, just didn't correlate the files to this thread. :(

Regards
Paul

[GMPX]

right, it just clicked what it is. On that custom OS, due to size limitations in the flash we disable a couple of 'redundant' tables in the PCM and use that space for the new tables we add. It just so happens in your tune GM populated that area already (most have that area blank).

Nothing has gone wrong, it's normal.

Cheers,
Ross

[Chevy366]

right, it just clicked what it is. On that custom OS, due to size limitations in the flash we disable a couple of 'redundant' tables in the PCM and use that space for the new tables we add. It just so happens in your tune GM populated that area already (most have that area blank).

Nothing has gone wrong, it's normal.

Cheers,
Ross
How can that space be cleared then ?
I figured that the software had written to a sector in the EPROM and then kept retrieving that info every time , but shouldn't the software have some way of clearing that sector if needed ?
I don't know how to describe it but the tunes just seem odd like not writing info properly .
When I did the COS3 last time and re-flashed because of emission testing I did not get the same symptoms as now , same PCM , when I re-flashed no data was present , hmmmm .
I am not questioning your logic just seems odd it just now shows up .