This all started from wanting to do a Denali IPC upgrade to my pickup and change of theme from the Chevy blue to GMC red.  Got screwed over by some other places and stumbled on cameraloops and have already found alot more help and information her then anywhere else.

 

I've wrenched on everything from motorcycles to tractors for 25 years and have not a bit of EFI tuning but thats the extent of my knowledge as far a computer programming so this is all pretty new.

We'll sort the HMI issue first but need to know what year the new cluster is.  I can get your year from your VIN.

17 hours ago, codebuilder said:

We'll sort the HMI issue first but need to know what year the new cluster is.  I can get your year from your VIN.

Here is the vin I pulled from the new cluster. 3GTU2WEJ2FG347155

 

I was able to change the vin but I think the odometer is locked out as it won't read still.

33 minutes ago, NDCharlie said:

Here is the vin I pulled from the new cluster. 3GTU2WEJ2FG347155

 

I was able to change the vin but I think the odometer is locked out as it won't read still.

Pin for that VIN is 5650.  Once the VIN is corrected the mileage usually appears from what I've seen.

41 minutes ago, BLKATSG said:

Pin for that VIN is 5650.  Once the VIN is corrected the mileage usually appears from what I've seen.

I was able to get the VIN changed over but it is still showing dashes. Troy directed me to a post talking about the odometer lock out being active which is what I think is going on however chip level programming is a bit advanced for me right now

4 hours ago, NDCharlie said:

I was able to get the VIN changed over but it is still showing dashes. Troy directed me to a post talking about the odometer lock out being active which is what I think is going on however chip level programming is a bit advanced for me right now

In DPS, did you do a read from the IPC to ensure the VIN is actually changed?  I believe there is a lockout but I haven’t had that happen with a few clusters myself. 

6 hours ago, NDCharlie said:

I was able to get the VIN changed over but it is still showing dashes. Troy directed me to a post talking about the odometer lock out being active which is what I think is going on however chip level programming is a bit advanced for me right now

Yes I've seen this before you'll need Troy's mileage correction type 4 file and it will fix odometer issue, I suppose you drove with that cluster on the vehicle for too long before changing the vin and caused it to lock up. 

2 hours ago, codebuilder said:

In DPS, did you do a read from the IPC to ensure the VIN is actually changed?  I believe there is a lockout but I haven’t had that happen with a few clusters myself. 

I did yes, it is coming back with the correct vin for the vehicle.

2 minutes ago, Flex_user said:

Yes I've seen this before you'll need Troy's mileage correction type 4 file and it will fix odometer issue, I suppose you drove with that cluster on the vehicle for too long before changing the vin and caused it to lock up. 

Oh ok. I'm guessing I did yes

3 hours ago, NDCharlie said:

Oh ok. I'm guessing I did yes

We might be able to pull the DIDs and then see about resetting it remotely if you want to try?  There is in GDS2 an "Odometer Lock" or similar that I remember too....  I can't say for sure but we can try to unlock it.

Maybe this can help you to understand the ------ in odometer:

 

The instrument cluster displays the engine coolant temperature, fuel level, vehicle speed and the engine speed based on the information from the engine control module (ECM). The ECM sends information via serial data to the body control module (BCM). The BCM then sends the information via serial data to the instrument cluster to display the engine coolant temperature, fuel level, the engine speed, the vehicle speed and the distance travelled, either in kilometers or miles, based on the vehicle requirements. The instrument cluster will display dashes when its VIN does not match the VIN received from the BCM.

 

If the VIN mismatch is corrected the odometer will once again be displayed in the instrument cluster. If the vehicle is driven for a calibrated distance with a VIN mismatch, it will cause the instrument cluster odometer to enter into an error mode and lock itself. When this occurs the dashes will remain on the display even after correcting the VIN mismatch. The vehicle odometer status data display on the scan tool can be used to identify a locked odometer. The only way to unlock the instrument cluster (clear the dashes from the display) is to perform an SPS programming event. Failure to follow the diagnostic and programming procedures may result in either an improper odometer value or a module replacement.

 

15 hours ago, codebuilder said:

We might be able to pull the DIDs and then see about resetting it remotely if you want to try?  There is in GDS2 an "Odometer Lock" or similar that I remember too....  I can't say for sure but we can try to unlock it.

How do I/we do that? What can I do to help? 

On 2/7/2024 at 3:27 PM, NDCharlie said:

How do I/we do that? What can I do to help? 

I kind of disappeared on you on this one :).  Got crazy busy at work and just haven't been on the forum.  I can show you more of this once we get the CALs loaded up.

On 2/7/2024 at 2:56 AM, Arbe_gtc said:

Maybe this can help you to understand the ------ in odometer:

 

The instrument cluster displays the engine coolant temperature, fuel level, vehicle speed and the engine speed based on the information from the engine control module (ECM). The ECM sends information via serial data to the body control module (BCM). The BCM then sends the information via serial data to the instrument cluster to display the engine coolant temperature, fuel level, the engine speed, the vehicle speed and the distance travelled, either in kilometers or miles, based on the vehicle requirements. The instrument cluster will display dashes when its VIN does not match the VIN received from the BCM.

 

If the VIN mismatch is corrected the odometer will once again be displayed in the instrument cluster. If the vehicle is driven for a calibrated distance with a VIN mismatch, it will cause the instrument cluster odometer to enter into an error mode and lock itself. When this occurs the dashes will remain on the display even after correcting the VIN mismatch. The vehicle odometer status data display on the scan tool can be used to identify a locked odometer. The only way to unlock the instrument cluster (clear the dashes from the display) is to perform an SPS programming event. Failure to follow the diagnostic and programming procedures may result in either an improper odometer value or a module replacement.

 

I actually didn't know how the lockout worked.  I have seen it in GDS2 but never really worried about it haha.  Thank you @Arbe_gtc for sharing that, very good info!