After hours of debugging my micro assembly, I have been able to read out the 32 bytes of data in the X24C44 chip.

Now I just gotta figure out what it all means, and we can set the odometer to whatever we want.

Once I have got it sussed, I hope to offer the programming circuit for hire, preprogrammed with the desired value.

To minimise the potential for misuse, I want hirers to supply as much evidence as possible that they have swapped clusters. You will need to tell me the current value on the odo you want changed, and I will give you a 1500km 'window' to use the programmer. Odometers reading outside this 'window' will not able to be changed. Once the odo is sucessfully changed, the programmer will be disabled.

This service will include the following:

* Express postage to Australian address
* Postage paid package to return programmer
* Comprehensive, simple instructions on how to connect it up
* Full interconnect kit for cluster RHS connector
* Flying leads to solder to test points
* $10 donation to Fordmods, because they made this possible

The service is not yet available, as I still need to sus out how the data is stored. If I can't do that, it ain't happening.

I'm looking for expressions of interest at this stage, to give me some sort of idea of what the market would be and whether this is viable. Please PM me if you have interest or comments.

Thanks,
Dang.

well, i'm interested - my current cluster reads ~114,000kms when it should be close to 250,000kms

pfft, just drive around a bit!

hahah LOL

fras dont worry about it

i am sure there would be HEAPS of ppl interested in this

Dang, what are the 32 bytes, post them along with your odometer and trip meeter reading, we may be able to help decode
Can you write the same 32 bytes back ?

Cheers.

It's OK, I got it figured out now. An error in my assembly code got bit 14 of each word stuck high, fixed that and it all made sense.

First cut of the write it back code didn't work. I'll have to trace it through a bit more carefully.

Should be fairly straightforward......

Dang.

Damn. I got the writes working properly (don't you hate it when your subroutine screws with the input variables....), but trying to set it to 259999 (to clock it past a service interval to figure out which bit the spanner is) it came back as 555555. I'm guessing thats a default "you screw with me, your car's done shadloads of Kms" message from the cluster. I wonder what a completely blank chip would do. (Hey, I could find out!) I think there is a checksum byte in the mix. 555555h may have a checksum of 77h. 0000h (trip meter) may have a ffh checksum.
255512 may have a checksum of 98h.

I'll post more combos as I get them.

Free programmer hire for any hack who can guess correctly how it works.

Dang.

Man, that's all over my head! My brain hurts.

Dang, I believe you are correct regarding the 555555 reading in the odometer. I believe this is along the lines of...

"You've trid to play with me and now everyone knows you've tried to play with me. Please proceed to your nearest Ford dealer for immediate lecture and bring your credit card."

As to the mechanics of how it knows this... i wish you good luck!

Hey Dang..
Sorry to necro an old thread, but how did you get on with your eeprom project?
Didn't see any followups..
I'm keen to poke in the guts of the data there, particularly to enable Police mode for a cluster which doesn't currently have it.
The X24C44 is a bit of an oddball, a*** supported.
Anyway I'd like to know where you got to with it all!