BA Falcon Instrument Cluster EEPROM Programming

[Rerouter]

I've just modified your last dump to 123456km, so give it a try, if it works, i will be willing to share the how by PM only, as it was not easy to nut out,

[LangasLS]

I'd gotten to the same point as Tim in that I'd narrowed down the ODO location to the first line of hex (from memory and was able to swap the readings between my two dumps, but that was it.) Congrats for nutting it out Rerouter!! Impressive work

[LangasLS]

Just wacked your 123456 bin onto my test BA cluster and got 249069km (as pictured).

[Rerouter]

0x2E - 0x41 looks to me like a gauge mapping thinking fuel
0x44 - 0x54 looks like another thinking temp

0xFC - 0xFD looks like a test for a non-virgin dump
0xFF changes with every dump,

If i am right about the gauge mappings, then all odometer stuff should be before 0x2C,

Could you run one of your original dumps up 5 or so km, without a cluster on hand looks like i will need to go back to the drawing board for a while,

[LangasLS]

Yep - I will try and get this POS BA running on the weekend for some more dumps.

[tim36]

Hey guys, firstly I found this:

http://mhhauto.com/Thread-Tachosoft-s-M ... tor-v-23-1

I got to the point of being able to find the relevant representations of the odo value in the top line of code (using the Ford Falcon selection)

however it has to be more complicated than simply putting values in, all I have been able to achieve is 'odoerror'.

The 123456.bin made the odo in my BF read 848829km's... Haha

[LangasLS]

Interesting little program there - however I can't really spot any correlation between it and the BA cluster dumps. The 93C46 eeprom is what is used in AU clusters and the locations for the odo work for the AU - however I'm not convinced it is calculating the hex values correctly - will have to test it and see.

Attached is a dump from an AU cluster - its worth taking a look at even if it is of little relevance to the BA cluster.

[aumatt]

0xFF is the EE version number that is written on the label of the cluster

[tim36]

The part that I found interesting was that when I entered the actual odometer reading from each bin into the calculator function with the Ford Falcon selected, the hex bits it showed as the translation were the first four digits in the bin. (Give or take 10km or so when entering the odo reading into the calculator).

As far as data positioning goes, it's nothing like it. From what I could see going through all of the other Ford options, the programmers on the BA/BF clusters obviously didn't talk to the other kids much.

[LangasLS]

Correct 0xFF appears to be the EE version number - whatever that means.

Here are the details from the stickers on the clusters to go with the two dumps I originally posted:

BA_457225km (This is from the car I have in my possession)
Part No. 3R23 10849-AD
BA Mk1 Forte (XT) Sedan - Petrol
SW: 0203251
DOM: 27/02/03 14:29
HW: 05
EE: 1.02
CI: 08

BA_793361km
Part No. 3R23 10849-KA
BA MkII XT Wagon - Possibly dedicated LPG - Vehicle long retired to the crusher.
SW: 0308203
DOM: 23/02/05 08:51
HW: 01
EE: 2.07
CI: 15