Anyone worked with the 16196397 yet?

[Xnke]

So here is the big issue right now. I have NO idea if the patch has different locations in it, or if the XDF needs offsets added/subtracted to make sense of the split-bin thing, but the locations that are edited in the XDF are VERY different than the locations being called for in the patch notes.

I have attached the new attempt at getting the data transferred across the from E-side to T-side, but when I go to edit the patch in the XDF, I find a LOT of things very different.

For example, the line that changes the spark table to 0-6400RPM:

Patch Notes:
4D5A:
$65 65 ;changes spark table to 0-6400RPM range

Actual XDF Patch:
4D5A:
New Data: 65 Old data: 61

That looks OK...

Then we get to the next few lines:

Patch Notes:

1BAR emulation

99D6:
JSR L9410			BD 94 10

9BC3:
JSR L9410			BD 94 10

BD10:
JSR L940D			BD 94 0D

CCA1:
JMP L942F			7E 94 2F


940D:
LDAA L1031			B6 10 31

But then looking at the locations in the XDF:

99D6 seems to line up with 19D6
9BC3 seems to line up with 1BC3
BD10 seems to line up with 3D10
CCA1 seems to line up with 4CA1
940D seems to line up with 140D

But I have no way to really know...and patching the wrong sections of code means certain death to another PCM. I'd really rather not go through the process of disassembling the PCM again and burning the FLASH chips and re-assembling the PCM again-it isn't all that reliable and so far none of the socketed PCMs work exactly the same as they used to. They *work*, but Winflash complains about wrong responses at the end of the flash, wheras the stock unsocketed PCMs never complain.

If I can get the boost patch to work, and figure out if there is an offset for E-side code or if the numbers are just a bit off, then I can go ahead and write in the patch for the wideband sensor and get that going in the XDF as well.