Does anyone know if the BUA hack is the only one floating around for MAF cars?

thanks

I mean for the 165 ECM.

 

bub is the manual trans/OD (4+3) version of bua -

ftp://ftp.diy-efi.org/incoming/bub7943.zip

If there are others, I haven't been able to find them. So, I've become immersed in producing a commented 6E hack (arap/apyp) as this seems the only logical progression from 32B (bua/bub) for the MAF cars.

Jim
Red '86 4+3

 

Excellent! Thank you very much. My car is an '88 GTA with swapped-350/5-speed. To be honest, I don't understand your comment about the man. transmission (4+3); could you explain?

thanks again, just opened .asm file to start reading...

 

4+3 is a Y body thing - 2 spd OD behind a 4 spd super T10. OD operation is controlled using the TCC lockup line from the computer so all of the A4 tables are used, but are populated with different values compared to the auto bin. For me this makes converting to 6E more challenging since by then the 4+3 was dropped in favor of the 6 spd which does not interact with the computer. So going to a manual 6E bin means losing the OD altogether. Feh.

 

Thanks for the info. Is there another way of controlling the O/D ex. microswitch or just manually?

 

There is an override switch mounted on the shifter which is wired as an input to the computer. Sure, that could be wired directly to the relay, but a software solution seems more elegant - and the car could be put back to stock with a chip swap if need be.

Actually, '88 was the first year for 6E and '89 was the first year of 6 spds, so there IS a Y-bin out there somewhere...

Or, I could take ARAP and copy in the appropriate 32B tables...

 

Out of curiosity, what is the overdrive unit like? Is it a 2-speed box behind the transmission or integral to the tranny itself?

(edit)

Also, I just tried to run the bub7943.bin in Winbin using the 32b mask and it failed while trying to view injector constants (division by zero error). Is this the correct mask?
thanks

 

OD is a self contained, separate electrically operated unit bolted to the back of the Super T10, but is integral in that they can't be operated independently due to shared seals and frame mounting issues.

When I first fired up Winbin on the BUA/BUB bins the only ecu file I could find was a generic $32 from somewhere. Not many values lined up so I began writing a $32B ecu file using the BUA hack. The variable names and table structures are the same, only the locations bounce around from bin to bin. I haven't done much error checking and haven't included all the variables I want yet, but at least the fan temps are correct. The fi size might be using the wrong factor, but it does spit out a pair of values (single fire = 11.52 #/hr, double fire = 46.07 #/hr).

Now I'm looking at another $32 bin, ABTP from an '88 manual Y-body and using the ecu file I developed for BUA/BUB. Most of the values are nutso again. Feh.

I guess the lesson here is that locations within $32 bounce around from year to year, platform to platform so be prepared to write/modify a custom ecu file as needed. A well commented hack is an invaluable tool here.

Maybe $6E bins are more consistent?

 

There is a hack for the $6E based on the ARAP BIN somewhere. That's the one to get your hands on.

 

Glenn - my search for an ARAP hack has been futile so I've resorted to going it alone. Fortunately, a lot of the $32B code has been recycled (including the 160 baud diagnostic routine ????), but still.....

 

Send me an email, of what you want (all ya got won't hack it), and I probably can help you out some, I got a few notes, round here. Well, if Sleepy ain't wrinkled them up to bad.
nacelp@bright.net

 

Is their a ARAP hack. I'm using the bua to compare to my old hyper crap. Now I'd like to understand my Source COde using 6E
Can anyone help me find rescources Thanks, Ed

 

im new to this prom burning seen
what in the hell is a hack???

 

It means figuring out what a computer program does by "reverse engineering" it. i.e. start with the executable file and figure out what the commands were to create that file.

There are programs called Disassemblers that can generate the assembly language instructions that created the actual machine language code. Putting the whole thing together so that people can actually understand it though is quite a challenge. Once you understand what the program is supposed to do, you can start modifying it with confidence.

I've never actually done this and my hat's off to those who can.

:hail: