LBZ copy entire segment

[Biodiesel66]

I'm updating a tune file to some of the newer TIS calibrations from the GM web site. I'm using a segment from a stock 07 tune I have.
I've done this for the LB7 & LLY and the ID number change with the check sum.
When I do this for the LBZ the check sum changes but not the ID number.
I use this for tuning if I need to update one of the segment. Is there a fix for this? :nixweiss:

[GMPX]

I can't duplicate that problem here.
As a test I loaded a stock LBZ truck tune, then loaded an LBZ Express VAN tune, copied the engine segment over, saved the file, and I could see the difference.........

Before:
Operating System 12606128 $2FE01B201553
Engine Operation 12610870 $B9C2C627088
Engine Diagnostics 12610872 $1861EC249F13
Engine 12610878 $178D54035683
Fuel System 12610875 $7869DB092C7B
System 12606155 $802030A636AB
Speedometer 12606159 $7071255085B5

After:
Operating System 12606128 $2FE01B201553
Engine Operation 12610870 $B9C2C627088
Engine Diagnostics 12610872 $1861EC249F13
Engine 12606175 $178D5403617D
Fuel System 12610875 $7869DB092C7B
System 12606155 $802030A636AB
Speedometer 12606159 $7071255085B5

Cheers,
Ross

[Biodiesel66]

I can do it with the LB7 and LLY tunes. Not the LBZ. Only the Check sum changes.
All I was trying to change is fuel system. Tried others ID segments and the same thing happen.

What do you suggest?

[Boost]

I have the same problem.

[Biodiesel66]

Before

12606128.cal

Operating System...............12606128.............$2FE01B2 01553
Engine Operation................12606145.............$B9C 2A727385
Engine Diagnostics..............12606146.............$18A 2C02A325
Engine..............................12606160...... .......$2FE01B206673
Fuel System......................12606151.............. $5CB7B9773877
System............................12606155........ ......$802030A636AB
Speedometer.....................12606159.......... ....$7071255085B5


After change

Operating System...............12606128.............$2FE01B2 01553
Engine Operation................12606145.............$B9C 2C627088
Engine Diagnostics..............12606146.............$186 1EC249F13
Engine..............................12606160...... .......$2FE01B205678
Fuel System......................12606151.............. $5CB7BA772A7B
System............................12606155........ ......$802030A636AB
Speedometer....................12606159........... ...$7071255085B5

Copy of Segments that should have changed.


Operating System.....12606128.....$2FE01B201553
Engine Operation......12610870.....$B9C2C627088
Engine Diagnostics....12610872.....$1861EC249F13
Engine....................12610878.....$2FE01B2056 78
Fuel System............12610877......$5CB7BA772A7B
System...................12606156......$7E3930A635 AB
Speedometer...........12606159......$7071255085B5

Ross. If I can use the version of software that you used I'll be ALL SET :notacrook: Other wise I'm SOL :bawl:

[Biodiesel66]

Ross

I looked at this again.
This time I didn't delete the changed tune. The tune was saved and reopened.

Your right it does work. :cheers: But!! :nixweiss:

Why is it when I save a change from copy entire segment the ID doesn't change only the check sum until I close the tune and reopen again? Even if I save all changes to a new file, the tune has a new tune number but the ID numbers don't change until the tune is also closed and reopened?



I haven't noticed this when doing changes to LB7 or LLY tunes.

[GMPX]

We would need the technical explanation from Paul, but, I would suspect it has to do with the Segment I.D's being read only when the file is initially loaded. Because the checksums change everytime you make a change in the calibrations then they need to be updated for every action.

I guess in a way it's like the Windows message 'you must restart your machine for the changes to take effect'.

Cheers,
Ross

[ScarabEpic22]

Aggghh, I thought we killed the "you must restart windows for changes to take effect" with win xp, I havent seen that in a while (ok, it comes up when you change network settings for the first time with a fresh install) on my desktop.

At least you got it figured out though man!