12P disassembly

[antus]

I wouldnt think it was too hard. You have the spark controller addresses in the code patch above, so you should be able to find it in 12p by searching for those addresses. I only have the release binary like you do but thats what I'd do. Just be aware if you take the same approch you might cause other strange issues like overflowing the time the loop takes to execute if you add too many clock cycles and delay.

[34blazer]

That patch was for code 59, and I haven't been able to reach BL85c for a few years now to retrieve the original 6E patch.

[antus]

The addresses do appear to be the same. I can see B controller last ref is L3FEC in 12P and the patch, and B controller begin next dwell is L3FE4 in both. My gut feel is if those two match it is probably the same hardware and so they all will and you should be able locate the code you need to re-work in 12P and try it from that. Let us know how you go!

[34blazer]

In the thread previously linked, go to post #199. The "power adder" 6E zip is still there and that has the launch control strategy in the the files. I just looked at launch control and the best I can do is the scalers for that start at 0x574. If you're interested, that is.

[VL400]

Quickly revisited the spark cut on a 808, I dont have any of the code from way back when initially testing this so not sure what was tested/tried and how only that it wasnt ideal.

Setting dwell to 0 causes the chip controlling spark to briefly interrupt spark but then maybe goes to a sort of limp mode and outputs a fixed 50% duty cycle EST which will continue to fire the coil.

But, setting dwell to 200us seems to work. This would still cause a spark cut as it wont charge the coil with enough energy to fire it. Will need to be tested properly but it may be a possibility.

[34blazer]

Quickly revisited the spark cut on a 808, I dont have any of the code from way back when initially testing this so not sure what was tested/tried and how only that it wasnt ideal.

Setting dwell to 0 causes the chip controlling spark to briefly interrupt spark but then maybe goes to a sort of limp mode and outputs a fixed 50% duty cycle EST which will continue to fire the coil.

But, setting dwell to 200us seems to work. This would still cause a spark cut as it wont charge the coil with enough energy to fire it. Will need to be tested properly but it may be a possibility.

I think that is why the EST was held high and not low

[34blazer]

Well, the person that was helping me decided it's too much of an inconvenience. So I'm out. Going to wire up the MS3X I have and move on. It's just not worth messing around with OBD1 anymore.


Thanks gents.

/thread