BA Falcon Instrument Cluster EEPROM Programming

[TazzI]

Or, make the first line all 0xFF's. That should make the odo 0.. I think.

[Rerouter]

Now it could well be the scaling that i messed up, but the top row starting from 0x0F to 0x00 in 2 bytes, looks like a div2 sequence in all the dumps i have seen, if that helps.

My previous attempt involved trying to work out what both number where subtracted from then scaling the result, but it could well have been the opposite sequence

[aumatt]

Police mode is part of the feature list.

0xFF the top line will indeed zero the odometer

Matt

[Rerouter]

Seems i made a basic mistake in my first 123456 file, I had the first byte swapped, care to try this one?

Based on your 457255 file they are subtracting from the second nibble in what i would guess to be a sequenced pattern, (more dump files would confirm this)

[aumatt]

My calculations on that bin give me the following

248801km
Serial 30227390
Low Cluster Style
Part Number 3R23 10849-AD
Hardware v05
CI 08
EE 1.02
Police Mode offset 0
Autolight Off
220kmh Speedo
7000rpm Tacho
Wagon/Petrol Fuel Map
3 x DTC (B1201,B1503, B1499)
Seat Belt Reminder off

Matt

[LangasLS]

Rerouter - your modified bin is still reading 249069km.

Aumatt:
Everything is correct for that cluster bar the ODO reading. Rerouter: You modified the 793361km bin didn't you?

Attached is my modified dump file from the 457225km cluster. Speedo Zero'ed and Police mode enabled with 100km showing on the trip meter.

[aumatt]

Yep that is 0km,

With the police mode bit enabled and the seat belt reminder bit disabled

Trip A and B are set at 100.0km

Matt

[TazzI]

Well, that was easy enough. Odo reset and police mode have been sorted!

Now for the algo... Try changing the last odo byte section from FF to FE. I would expect the odo to read 2kms.

What has me stumped is how we would get 1?

[Rerouter]

I've gone and generated just about every sequence i can for-see to decrease the odometer by 1, and compressed them into a pack, lets see if this kicks things over.

Also i would think 0x14 is a bit mask for modes, so i have set it to F in all these to see if anything interesting turns up.

They are all based upon your 457255 dump,

[TazzI]

That looks like a good collection of test subjects!

Maybe its something like.. a couple bytes in the first line increase/decrease which causes the odo to "decrease" by 1.
And the other bytes decrease which causes the odo to increase by 2 each time?

Hopefully that kinda makes sense?

Would have to go through the top line decrease each byte by 1 to see what happens. Alternatively, get the scantool on there, change the odo and then read out whats changed... since we will expect to see the DTC set byte to change when the odo is set by a scantool.

Also.. the byte that turns the police mode on, what happens if we set that to FF? Id assume that byte will have multiple "options" that can be turned on so FF will enable everything.

Sorry LangasLS, it seems your the only one with a cluster to tinker with! Im currently overseas so no playing till the newyear!