Combining .bin files .....

[EagleMark]

Hmmm? I've been watching things you do like that... so you could add 4L60E to $OE?

Simpler approach may be just run $OD, why were we trying to do this in the first place? Interesting topic but I lost track of original purpose?

[gregs78cam]

Hmmm? I've been watching things you do like that... so you could add 4L60E to $OE?

Simpler approach may be just run $OD, why were we trying to do this in the first place? Interesting topic but I lost track of original purpose?

I couldn't do that, but someone more capable probably could. The only drawback to this is much like the Code$59 if someone wanted to use it they would have to move all trans data by hand, or start over from nothing. I think the best place to start for this though would be to compare the two best hacs for each so you can "map" out the process the PCM uses to control each tranny, and then you would see how they handle the data differently.

[93V8S10]

See I told you!

Since the transmission seems to be on bottom I don't think it would be that bad. Using notepad to cut $OE trans from XDF and replace $OD trans would be easy and no chance of address change. So you have a way to check bin after splitting and replacing hex. Open 2 instance of TunerPro one with new custom XDF and custom bin and one with $OD 4I60E xdf and bin you just cut bottom off of. Compare each parameter.

I think that it's important to clarify terms. The bin/code can be broken down into some major sections; RAM, engine calibration (includes 700R4, manual), ALDL, 4L60E/4L80E calibration, and operating code.

I would recommend that only the engine section be swapped, the operating code is very similar, but the code for 4L60E and 4L80E are very different (as far as I can tell, 4L80E not hacked very well).

Also, it is possible to run a 4L80E with $0D. Requires a few small code changes. I haven't done this, but there is Oldred at FSC that has done this with the help of Fast 305.

[gregs78cam]

I think that it's important to clarify terms. The bin/code can be broken down into some major sections; RAM, engine calibration (includes 700R4, manual), ALDL, 4L60E/4L80E calibration, and operating code.

I would recommend that only the engine section be swapped, the operating code is very similar, but the code for 4L60E and 4L80E are very different (as far as I can tell, 4L80E not hacked very well).

I would tend to agree, and also you have to remember that your .bin stores data from the engine segment in the RAM area for the datastream, you would need to make sure all addresses that get written to are the same from one engine segment to the other. You also have make sure that the data that the trans segment uses such as TPS are in the same location.

[EagleMark]

Ahh, see I didn't know that. That was probably areas that had hex and did not come up highlighted in XDF paremeters.

So if he wanted to go 4L60E he'd be way better off starting with $OD 4L60E bin and making changes to engine for his 454?

[gregs78cam]

Actually in the case of this PCM the RAM is the first section from L0000-L3FFF and is usually blank when you look at it in hex editor.

But yes I agree with 93V8S10, just change the engine stuff to match, as those items are mostly the same, may different addresses, but should all be there.