Tweet
This is for the BCFA code (3.4 DOHC manual transmission code) only. You could try to apply it to the auto trans code and it might work, but I will not help you if it doesn't, and it's not my fault if you blow up your car. Not that is my fault if you blow up your car with this patch used the right way either 
.
Directions:
Install the patch onto a BCFA binary. It's okay if you have tuning settings. They won't be affected.
Hook up your wideband O2's 0-5V output to pin C18. Unfortunately this pin hole is blocked off on my connector; I don't know whats up with that. You may be able to salvage a connector from another ECM at the junkyard that fits in the socket and has a hole. Otherwise maybe you can drill it out and install the pin. Worst case: drill out the pin hole, feed the pin and wire through to the pin on the ECM, then install the connector.
Datalog! Stock scantool will work fine; this replaces the "corrosivity sensor" output voltage on the ALDL. It's byte 44 on the ALDL datastream. Divide the byte value by 51 to get the voltage.
This makes it way easier to tune because you dont have to try to find a way to sync your motor logs with your WBO2 logs. You get all the data in one place.
Here's the code, but note that the BCLR and BSET operations do NOT get their bit masks assembled correctly by AS11.EXE, so you'll have to modify them manually once the patch is applied. Alternatively, just start with the bcfawbo2.bin on my site (link below) and copy your tuning constants into it. Don't forget to change the checksum.
The code:
A factory BCFA binary with the WBO2 patch applied and the checksum corrected for it:
(easiest way to do this)
The directions for applying the patch are in the assembly code file if you want to do it yourself. You'll need the motorola assembler (as11.exe) and the S19 file patcher (S19_PAT.exe) which you can get here:
More info on these programs here: http://www.thirdgen.org/techboard/di...thod-demo.html
If you're going to patch it yourself make SURE you read the comments in the assembly code file. The assembler (running in dosbox at least) doesn't seem to assemble 3 of the byte values properly, so you will have to manually modify them. The note on what to change is in the .ASM file on my site.
-Steven
.Directions:
Install the patch onto a BCFA binary. It's okay if you have tuning settings. They won't be affected.
Hook up your wideband O2's 0-5V output to pin C18. Unfortunately this pin hole is blocked off on my connector; I don't know whats up with that. You may be able to salvage a connector from another ECM at the junkyard that fits in the socket and has a hole. Otherwise maybe you can drill it out and install the pin. Worst case: drill out the pin hole, feed the pin and wire through to the pin on the ECM, then install the connector.
Datalog! Stock scantool will work fine; this replaces the "corrosivity sensor" output voltage on the ALDL. It's byte 44 on the ALDL datastream. Divide the byte value by 51 to get the voltage.
This makes it way easier to tune because you dont have to try to find a way to sync your motor logs with your WBO2 logs. You get all the data in one place.
Here's the code, but note that the BCLR and BSET operations do NOT get their bit masks assembled correctly by AS11.EXE, so you'll have to modify them manually once the patch is applied. Alternatively, just start with the bcfawbo2.bin on my site (link below) and copy your tuning constants into it. Don't forget to change the checksum.
The code:
A factory BCFA binary with the WBO2 patch applied and the checksum corrected for it:
(easiest way to do this)
The directions for applying the patch are in the assembly code file if you want to do it yourself. You'll need the motorola assembler (as11.exe) and the S19 file patcher (S19_PAT.exe) which you can get here:
More info on these programs here: http://www.thirdgen.org/techboard/di...thod-demo.html
If you're going to patch it yourself make SURE you read the comments in the assembly code file. The assembler (running in dosbox at least) doesn't seem to assemble 3 of the byte values properly, so you will have to manually modify them. The note on what to change is in the .ASM file on my site.
-Steven
