Hurricane77

[QUOTE=Livnitup;5252824If it were me I wouldn't write your original whole eeprom dump to the new cluster just in case there's different values for the bigger size cluster, just write the mileage, etc manually to new cluster.[/QUOTE]

I don't think that will work either. There's seems to be some offset where different things are stored. Couldn't find enough correlation between the two to definitively say what's different between the tow version.

I just modified the mileage, hours, VIN and the part number is stored in there as well.

The As-built block is in there as well, but I don't think the IPC uses these values while operating. I though I'd be smart and pre-program my IPC with my factory As-built so I wouldn't have to do it via Forscan after the fact. But it didn;t seem to read those as I still had all the warnings and DTC associated with BLIS, CTA etc. and still had to go and modify it via Forscan. Almost like the functional As-built values are stored somewhere in the NVRAM of the micro itself or one of the two other NVRAM chips on the board. Maybe the values in the EEPROM are only used is one does a factory reset of the module using IDS or something?

the reason I think there are gauge calibrations in there is because when I put the blank EEPROM (which was all $FF) in there I put it in the truck just to see if it worked or if I had bricked the entire IPC It powered up and worked, but all the digital gauges across the top were orange instead of blue and the tach and speedo did nothing. So the IPC was freaking out a bit and even the gauge calibration in the Engineering Mode didn't do anything to resolve it. Again, this is more of a guess on my part, but I know my analog speedo is more than 10% from the digital one

DanMc85

It is protected from the top to a line or two just past the part number of the IPC.

DanMc85

The running/working mileage and as-built is in the SPC5606 chip on the motherboard of the IPC. It is backed up in the 24C32 EEPROM and read from the EEPROM after a power loss (disconnection or battery) or fresh firmware flash.

Livnitup

I had someone contact me who bought a 8" cluster from someone thinking it would be plug and play or something but he had tons of warnings on the display and of course the mileage, engine hours, etc. were all off. This guy also didn't know anything about FORScan. Long story short...I programmed the as-built block of my spare cluster with his VIN's IPC as-built values, corrected mileage, engine hours, engine idle hours and swapped him clusters yesterday in a Wal-Mart parking lot. I then plugged into it with FORScan there and all the as-built values I wrote via EEPROM were there in IPC so not sure why you didn't see the same writing to your EEPROM.

wristshot

When I removed my 4.2" cluster to see if I could read the EEPROM, via an SOIC8 Clip, I read and saved the EEPROM 5 - 6 times (removing and repositioning the clip a few times to verify my read/s).

When I put the cluster back in, my mileage had increased from 24024.0 to 24024.5. I took a before picture of my cluster screen/mileage - so I didn't imagine this.
I compared all my saved reads and they were the same, so apparently while I was doing this the microcontroller was back powered, received some some garbage data, updated and saved a new mileage value in another location (i.e. not the 24C32 EEPROM because its data never changed from the 1st to last read).

I guess what I'm saying is that, in my case like Hurricane77s, it must NOT have read from the EEPROM on power up or my mileage would not have changed.

Hurricane77

That makes sense. The EEPROM would have fairly limited write cycles compered to the internal memory of the micro. The datasheet for the 24C32 is spec'd to 4,000,000 write cycles. If it used the EEPROM as working memory and wrote to it each 1/10th of a mile, the design life would only be 400,000 miles

flsdiver

iTrader: (1)

sounds like that's what the manufacturer would want! planned obsolescence!

joking aside, your point is valid and brings up a couple questions.
What is the save event(s) and or frequency?

i can calculate the mileage hex values from any mileage to within 0-2 miles, but without being able to set the 10ths. I have been looking for the 10ths in the eeprom (or stored more granular than 10ths?)
I think it must be in the eeprom somewhere as well though.
not in the 4 bytes of hex already identified, as those 4 bytes of hex definitely don't have 10ths included in them.
Reason i say this is that it remembers the 10ths of a mile after removing the cluster, programming it to new mileage, and plugging cluster it back in, which to me eliminates the on board processor, unless the processor memory is kept alive by capacitor storage for some extended period of time.

I have been working from bin dumps, clip is on the way, and i will be able to read/program with my old 4" cluster.
hopefully i figure out the whole math puzzle.

breakers28

I upgraded my 4" cluster to an 8" cluster. All went well except for one aspect - the Trailer Backup Assist is not working and acting a bit strange. Of course, the trailer setup was lost when I swapped clusters so I tried to add my trailer. Per the cluster screen, went into set up the trailer, and as part of that process can enable the Backup Assist. Selected it and said to pull forward to straighten trailer. Select OK and the Backup Assist **** light comes on and the cluster states to follow the book for procedure. No OK or other option on the screen.... This also locks the instrument cluster screen, I cannot move left, right, up, down or enter. Stuck until I turn the truck off and restart. Then, the Backup Assist **** light comes on, and when I put the truck in Drive, the APIM screen is stuck on a View Trailer (rear camera engaged, but not typical reverse screen). I cannot get out of the APIM screen or turn off the Backup Assist **** light - regardless of selecting no trailer attached via the instrument cluster. Only way to get back from here is to use FORScan to disable Backup Assist (720-03-02 change last digit in 1st section to 8 -- C848), then re-enable it again (change it back to 9 -- C849). Anyone else try their backup assist after doing a cluster upgrade? Anyone have any other ideas?

IPC config
;Block 1
720 01 01 2C0B 3064 6054
720 01 02 2017 1071
;Block 2
720 02 01 4DC0 3C31 1CC0
720 02 02 1000 A9E4
;Block 3
720 03 01 2805 5400 00AC
720 03 02 C849 013E
;Block 4
720 04 01 C441 0000 0031
720 04 02 5553 00D5
;Block 5
720 05 01 0000 0000 002D
720 05 02 0000 113F
;Block 6
720 06 01 0000 0000 002E
720 06 02 0000 002F
;Block 7
720 07 01 8401 8E50 60F2
720 07 02 0000 0030

XLT SCREW, 2.7, 3.55, 18" wheels

Livnitup

Did you backup your original cluster's IPC and write those values to the new cluster in FORScan first?

breakers28

Yes, and I tried restoring those and still does not work. Same result. I'm considering putting the 4" cluster back in and see what happens.