Combining .bin files .....

[Nasty-Z]

Running a TBI 454/700R4 in my '84 S10 Blazer ('7427 PCM ) , on this incarnation I kicked around the idea of going with a 4L60E so I can have PCM control of engine and trans .

Using the '7427 PCM right now , I have .bin's for $0E for 454/4L80E and .bin's for $0D for 350/4L60E , but obviously nothing for a 454/4L60E in either mask

Anyone who can guide me through either copying the 454 engine parameters to the 350/4L60E $0D .bin , or the trans parameters to the 454/4L80E $0E .bin ?

I have never tried overwriting engine and/or trans before , and do not know exactally what all would need to be carried over for either instance.

Or has somebody created a 454/4L60E .bin I could start with that I have not found ?

Thanks for any advice or help

TOM

[PJG1173]

I am switching from $E6 to $0D and am coping the info parameter at a time. Its taking quite a while.

[JeepsAndGuns]

Knowing nothing about automatics, why not use a 4L80E? I thought the 4L60E was a light duty trans, and wouldnt stand up to something big like the 454?

[93V8S10]

Edit: Nevermind what I said won't work.

[Nasty-Z]

Pretty much the only real reason is length , I can save 4+ inches by doing the '60e , it'll be plenty strong enough for what i'm doing . Anymore you can bulid a 700R4 (4L60) to be pretty bulletproof. That being said , if I could find a decent '80e at a good price I would find a way to make it work :)

Thanks

TOM

[Nasty-Z]

Edit: Nevermind what I said won't work.

What was that ?...... LOL

TOM

[93V8S10]

It was a paragraph of words that upon further thought, won't work right. :)

[dave w]

I would use the $OD / 4L60E .bin to start with to make sure the transmission settings are correct for a 4L60E. I would copy / paste ALL the 454 fuel and spark settings from a 454 $OE into the $OD .bin file. When I say ALL fuel and spark programming, I would include things like DFCO, warm up and anything else used for fuel and spark for the 454. It's very time consuming, but worth every minute!:thumbsup: I'm more familiar with engine programming, so that's why I'd swap $OE 454 programming into $OD.

dave w

[EagleMark]

Edit: Nevermind what I said won't work.


It was a paragraph of words that upon further thought, won't work right. :)Yeah but it may make people think! I have done that before and got to end and relized... "That won't work" so I said "that won;t work" and explained why. Then we picked up how to do it becuae we were thinking outside the box!

[EagleMark]

I read this on an LT1 forum about hacking the code and it comes in 2 pieces with gap in middle, guys were trying to combine a bin for LT1 auto to manual but did not want to give up his tuning done to engine. Seems theres some gaps in hex code. So I opened all scalers, bitmasks and tables in parameter tree in TunerPro with $OE bin then opened Tools, advanced and hex tool.

Big gap at top and then on line 4000 I find OE so I click on it and Mask ID is highlighted in parameter tree, Click on first one and it's Prom ID highlighted, scroll down and click on others and also parameter tree moves to spot you click on in hex viewer. Does not work for all so I guess I was clicking something not in XDF or maybe a table or sequence for that parameter in xdf?

Then found all engine stuff.

Big gap...
Then found beginning of transmission controls.

I think with a little time you could take hex from $OD 4L60E and replace hex in $OE and have all trans controls changed, then do the same with the XDF in notepad and copy all trans controls from $OD and replace all xdf parameters. You would have a custom 4l60E $OE xdf and bin!

XDF would be easy. Hex would have to be a little more careful and get some advice from somone around here as if you changed a cut off point and lost a line the address would not line up in xdf...

[93V8S10]

That was my ideal, but there are two problems:

1. Hex editor is real strange with copy and paste. Will have to spend lots of time trying to get things pasted in correct place.
2. There are subtle differences between $0D and $0E. Some tables are longer, some parameters aren't there. This adds up to things being shifted slightly. Would have to take this into account, or it will be the same as using the wrong xdf to view bin. If you try to run engine, at best won't start, at worst damage.

[EagleMark]

Yeah but it may make people think! I have done that before and got to end and relized... "That won't work" so I said "that won;t work" and explained why. Then we picked up how to do it because we were thinking outside the box!See I told you! :rockon:

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.

[gregs78cam]

I have looked into this as well and there are some XDF parameters in $0D that are not in $0E trans code. And addresses for what are in both are very likely different.

[EagleMark]

Right! But if XDF was modified and trans hex placed correctly it could be verified, why wouldn't it work? Seriously I am asking I don't know?

There's big gaps in hex of all 00 or all FF inbetween sections...

HiJack thought of another thread, this looks like plenty of room to make that one XDF/ADX/Bin for all engines type thing we were talking about...

Back to topic.

[gregs78cam]

I am sure it could be possible to get the two transmissions to work properly with the same .bin/.xdf/.adx, but I think that would take at the least re-ordering some of the code to make it work, and at most re-WRITING a lot of it, because of the mechanical differences in the transmissions, i.e. input speed sensor, different # of shift solenoids, PWM vs. non-PWM. One could just make the tranny dependant defferences be skipped over when either of two flags are set. Ya know one flag for 4L60E that disables or skips 4L80E specific stuff, and vice versa.

[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! :rockon:

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.