454 with 4L60 $0D 16196395

[1project2many]

Often, GM uses a chip with more storage capacity than the calibration requires. Due to the design of the ecm, the calibration must be loaded so the last byte as at the highest address in the chip. So the first part of the chip is often "empty" or full of garbage. If you look at the cal in a hex editor you'll probably be able to see where the actual calibration starts.

FWIW, while you might find people willing to share a calibration, many folks here are of the "teach a man to fish" mindset. Cast your net into the waters, not among the people, and you'll probably find some help. ;)

[kevinvinv]

Often, GM uses a chip with more storage capacity than the calibration requires. Due to the design of the ecm, the calibration must be loaded so the last byte as at the highest address in the chip. So the first part of the chip is often "empty" or full of garbage. If you look at the cal in a hex editor you'll probably be able to see where the actual calibration starts.

FWIW, while you might find people willing to share a calibration, many folks here are of the "teach a man to fish" mindset. Cast your net into the waters, not among the people, and you'll probably find some help. ;)

Understood about the bin offset. Probably the highest address is like a reset vector or something like that and so they offset the entire image up that high. OK

Also understood about getting a cal. I get that about "freeloaders" etc. My problem is that I feel like the merging of a 454 fuel/spark setup into a $0D mask bin (b/c I have the 4L60) is more than I can do right now b/c of life and other issues. I had hoped I could automate that by writing a mapper program in C, reading in the two XDF files and mapping the data from one to the other but sort of got convinced that that wouldn't work well either :)

I appreciate your taking time to answer my questions!