I was reading another post on here, and it got me thinking about something. Is there any benifit to deleting certain parts of the bin, even if I don't need/want to add any additional code?

I personally could remove the VATS stuff, egr, anything about CSI, highway spark, shift light, speed limiter, rev limiter, and I'm sure there's a bunch of other stuff in there I don't need.

If I do this, is there a certain procedure to follow, or do I just delete the sections I don't need by following the hac for my ecu?

Oh, my car is an 87 IROC, MAF and running 165 6e.

I'm still relatively new to prom burning, but I'm looking for something I can work on while the weather is bad and I can't wrench or tune outside.

 

So far Ive only deleted when I had to or I wanted the stuff used by the code for something else. If its just there and its not doing anything then just leave it. Since its interupt driven it wont go any faster, anyway. If your going to take something out, you really need a nearly fully commented hac and you need to thoroughly sift through and see what else the code ties in with, like status words, memory addresses etc. Once your confident you can completly remove it w/o adversly effecting everything else then you remove the code and everything associated with it and test on a bench to make sure it still works right.

Edit: Youll have to have a completly compilable hac that has all the addressing relative so everything can slide around before you can change stuff. Its also worthwhile saying that you should become familar and comfortable with assembly first before making changes.

 

Alright, well that gives me a starting point at least. Do you have any links on learning assembly code? I have the bua hac and the 165 hac, not sure if they are compilable though. Any idea?

Thanks

 

It took me about a month of occasional work in my spare time to pick it up since I had no real programming experience. Best way is to grab the book on the hc11 cpu and look at the code in the hacs. The M68HC11 reference manual is available through motorola's site. Dont have any links but a search at their site will bring it up. In order for a hac to compile, you need to format it properly with all the excess labels removed from the code portion of the hac. The labels in the constants portion can be left in place since theyre handy to have. It also needs to be in a plain text format in order to compile into machine code. No word documents or anything like that since the formatting screws up the compiler. After that you compile and compare the bin made from the hac to that of the origional bin and make sure theyre the same. Sounds easy enough but this is a major understatement, really. Its alot of work. I disassembled my $4D mask and completly commented it to get an idea of how it all worked and that just seemed like it took forever. By the end I was jsut completly sick and tired of looking at it but it got done. Since I formatted it along the way it only took about 10 minutes to get it to compile w/o any errors or mistakes (well, almost. Put an immediate sign in front of the label for the knock counter by accident and got lots of code 43s when I ran it). Basically dont try to do it all at once or youll get turned off. Jsut take small steps at a time and eventually youll pick up enough to get some idea of what your doing. Youll find that heavy use of the 'search' button will bring up lots of good info that will get you started. Alot more then I can cover, or know for that matter.

 

What I try to do is to only remove code that I know I will never use. I leave code that I am not using but that has utility. Any code that I leave that has utility needs to have a cal term to disable it. May that be a temperature threshold or a user option bit.

Even a speed limiter and rev limiter I would leave in place. The speed limiter may be set high, but could come in handy for other uses.

A rev limiter is always good to have.

If the code isn't in the way and there is enough room and time for code to added, then I jsut leave it be.

RBob.

 

heres one for you pros out there! I think i want to remove the TCC values and the A.I.R. diverter junk from my prom- i have an automatic equipt ECM but i have a standard trans. or is there some way to change one of these figures and have it control a secondary aftermarket pusher fan?

 

The air stuff is easy to remove. Its all self contained so its a simple highlight and delete. The TCC would eb a slightly more difficult since there is spark control and other parameters for it in other loops. Not too hard, but youd have to make sure you unhooked everything before you took it out. Youd have to go through the code and delete as necessary. Its not run anyway and since youd be going romless to get rid of it, youd have extra space so clearing it out wouldnt be required to free up space. As for a fan, thats what I used the previous stuff for the air for. Deleting it freed up the outputs and some RAM so I had a place to put stuff.

 

My *cure*, is running a warm engine so there's a bigger temp drop from the radiator to ambient. Given a good enough tune there's nothing to be gained in running less then 180dF, in a street car, IMO.

If you want to run more fan, as your only option then I'd suggest just turning everything on the same temp..

If you really want to remove anything then you need to get familiar with assembly, and how the code runs. The KEWL that goes with running your own code, and changes is a really satisfing.

 

Gee, thanks.
I been trying to get a handle on some of this for years, and you do it in a month...............





A month....
Arrgh.

 

Beings that it's interupt driven, one would assume, no.
But, I'll swear that a low code mask I have seems to just run much better, then it's stock counterpart.

Maybe, it's just the satisfaction of having gotten it to work, that's the thrill....

 

Ok, Im a dork, Ill admit it.... I built my first desktop when I was about 10, which was an 8088 PC with a state of the art 8 bit VGA card and soundblaster card, and have been programming in basic and later C++ in highschool and MATLAB in college. So, you might say that im no stranger to using computers. W/o previous experience, it would have taken me much longer. Having prior experience with computer algorithms is a huge help since it then becomes jsut learning how to translate what I want into the computer language that im programming in. Im still no expert, though. Like always im still making dumb mistakes. Thank *** for the test bench... Would really suck to have to catch missed keystrokes and logic flaws in the car.

 

Was wondering what software could be used to make a good disassembly, then maybe WinIDE could compile.

I'm used to modify Megasquit assembly ECU code, but never tried to play with GMECM, would love to.