Any interest is colaborating on the later TBI PCM $0D hack?
Thread Starter
Supreme Member
iTrader: (2)
Joined: Jan 2002
Posts: 9,962
Likes: 5
From: Moorestown, NJ
Car: 88 Camaro SC
Engine: SFI'd 350
Transmission: TKO 500
Axle/Gears: 9-bolt w/ 3.23's
Any interest is colaborating on the later TBI PCM $0D hack?
Ive been chugging along with the $0D for awhile now, but Ive done only some work with the transmission side of the code. While I know how the standard 700-R4 works, I have zero knowlege of how the electronic contol works, no real resources to find out, and have very little desire to learn as Im going to be using a stick.
There are a few of you guys out there who like to work with the later CC transes. So, are any of you interested in hacking the trans code? My goal was to get a nearly complete, compilable hack of the $0D so it could be used for patches, or all out custom source coding. Ive made a first pass on a good deal of the rest of the code, so there should be at least some info on some of the transmission related routines.
As far as teh actual comments...
-First, obviously, I want the code to be compilable, or nearly so
-RAM addresses in the code need to be documented at the start of the code where they reside address wise in the PCM. Example: state what the address is and any pertinent info, such as filtering, etc.
-All addressing shall be relative, so instead of a table address load appearing as #$1234, it should be #L1234 with the address of the table given as a label. Also, the address itself should be given as the label rather then using a unique name instead for the stock code. From my experience, this keeps unique names free for custom code and makes added/altered code stand out, which dramatically simplifies debugging. Extranious addresses/lables shall also be removed. This is fairly clear in the code as to whats a label.
-Tabbing/semicolon formatting shall also be the same as whats currently there, for ease of reading.
-Lastly, the comments should be reasonably complete so someone can come along and have a good walkthrough of what the code does without having to come along and provide additional comments.
Seems stringent, but this results in a complilable, readable, immediatly usable hack
Other then that, the format of teh comments/credits is up to you. the trans code seems to have some isolation from the code controlling the motor so they shoudl be able to be done seperatly. At the end, I will additavly combine your work with mine and post the end result on moates or something.
If anyones interested, ill post what I have thus far and we can start working on it.
There are a few of you guys out there who like to work with the later CC transes. So, are any of you interested in hacking the trans code? My goal was to get a nearly complete, compilable hack of the $0D so it could be used for patches, or all out custom source coding. Ive made a first pass on a good deal of the rest of the code, so there should be at least some info on some of the transmission related routines.
As far as teh actual comments...
-First, obviously, I want the code to be compilable, or nearly so
-RAM addresses in the code need to be documented at the start of the code where they reside address wise in the PCM. Example: state what the address is and any pertinent info, such as filtering, etc.
-All addressing shall be relative, so instead of a table address load appearing as #$1234, it should be #L1234 with the address of the table given as a label. Also, the address itself should be given as the label rather then using a unique name instead for the stock code. From my experience, this keeps unique names free for custom code and makes added/altered code stand out, which dramatically simplifies debugging. Extranious addresses/lables shall also be removed. This is fairly clear in the code as to whats a label.
-Tabbing/semicolon formatting shall also be the same as whats currently there, for ease of reading.
-Lastly, the comments should be reasonably complete so someone can come along and have a good walkthrough of what the code does without having to come along and provide additional comments.
Seems stringent, but this results in a complilable, readable, immediatly usable hack
Other then that, the format of teh comments/credits is up to you. the trans code seems to have some isolation from the code controlling the motor so they shoudl be able to be done seperatly. At the end, I will additavly combine your work with mine and post the end result on moates or something.
If anyones interested, ill post what I have thus far and we can start working on it.
I am definetly interested, and willing to help, but I am just not in much of a position to at this point in time. We are short one engineer in my area, and free time is scarce these days. I am getting farther and farther behind on my own projects, but this project is on my list, just not at the top. While I learned 6800 machine language in college, my assembly skills are far from polished and it takes me a long time to crank it out, but I get it. I have also messed with the tranny and virtually any other $0D related stuff you can think of so I know I can help. The questtion is how much. I am willing to commit whatever little time I can spare as I feel I have a vested interest here. LMK, HTH.
Thread Starter
Supreme Member
iTrader: (2)
Joined: Jan 2002
Posts: 9,962
Likes: 5
From: Moorestown, NJ
Car: 88 Camaro SC
Engine: SFI'd 350
Transmission: TKO 500
Axle/Gears: 9-bolt w/ 3.23's
Its all good... I can always just release it w/o the trans stuff commented and you can repost with whatever you have.
I work quite a few hours as well, but also only sleep 4-5 hours a day. Might as well do something with all those extra red eye hours
Beats watching TV.
I work quite a few hours as well, but also only sleep 4-5 hours a day. Might as well do something with all those extra red eye hours
Beats watching TV. Thread
Thread Starter
Forum
Replies
Last Post
ZZ3Astro
Power Adders
1045
Aug 13, 2019 12:57 AM






