So more then a few odd things and quesitons, I'll post them here as best as I can and with some of the files I think are pertinent but anyone willing to help if you need more info please let me know.

 

So a summary is I purchased a Yukon Denali vin 1GKS1CKJ1GR181357 to install into my Silverado vin 3GCUKSEJ6HG178673.  I installed it and used Troy's vin change file to get milage showing and all is good besides getting a warning for and RPO the Yukon had that my Silverado does not, side collision detection.  The reason for the install was to get the red gauges and screen.  I edited the xml file to remove the warning and programmed the ECU configuration.  The warning is now gone however the screen now has the blue accent color that was factory to the Silverado.  I also tried to build an archive file from a Sierra with the same RPO codes as my Silverado so that the on screen images would be of a pickup instead of a SUV however I am getting the attached error messages when I try to program it.

 

My ultimate goal is to end up with a configuration that is correct and has the red theme and also to have the Sierra programming installed.

 

On other odd thing is when I download the Sierra IPC files from SPS it downloads 17 files when there are 8 listed in the programming list.  Sierra all is the full list of the 17 and Sierra into Silverado is the 8 that SPS lists.  Anyone know what the other files are and are for?

Sierra_programming_into_Silverado.zip Sierraall.zip XMLFile.txt XMLFile.xml ProgramLog.Txt ConfigLog.Txt

9 minutes ago, NDCharlie said:

So more then a few odd things and quesitons, I'll post them here as best as I can and with some of the files I think are pertinent but anyone willing to help if you need more info please let me know.

 

So a summary is I purchased a Yukon Denali vin 1GKS1CKJ1GR181357 to install into my Silverado vin 3GCUKSEJ6HG178673.  I installed it and used Troy's vin change file to get milage showing and all is good besides getting a warning for and RPO the Yukon had that my Silverado does not, side collision detection.  The reason for the install was to get the red gauges and screen.  I edited the xml file to remove the warning and programmed the ECU configuration.  The warning is now gone however the screen now has the blue accent color that was factory to the Silverado.  I also tried to build an archive file from a Sierra with the same RPO codes as my Silverado so that the on screen images would be of a pickup instead of a SUV however I am getting the attached error messages when I try to program it.

 

My ultimate goal is to end up with a configuration that is correct and has the red theme and also to have the Sierra programming installed.

 

On other odd thing is when I download the Sierra IPC files from SPS it downloads 17 files when there are 8 listed in the programming list.  Sierra all is the full list of the 17 and Sierra into Silverado is the 8 that SPS lists.  Anyone know what the other files are and are for?

Sierra_programming_into_Silverado.zip 304.17 kB · 1 download Sierraall.zip 961.89 kB · 1 download XMLFile.txt 87 B · 1 download XMLFile.xml 152.98 kB · 1 download ProgramLog.Txt 10.39 kB · 1 download ConfigLog.Txt 31.33 kB · 0 downloads

Just reviewed the files, with your Sierra_programming_into_silverado.zip, are you trying to load ALL of your Silverado CALs and Sierra?  I looked at that and there's to many files.  That'll fail for sure!  We need to be a little more creative on this one....  You absolutely need the Denali cluster OS (the first file - the large one) as the Silverado one you for sure can't load up.  The other part is, the calibrations should be the same if not similar, but the cluster might get really picky about your calibration numbers.  I can help you build a custom package, based on yours.

 

As for the colour, it's hidden in one of the DIDs (XML).  I can't remember which one, I actually did the opposite and flipped mine to red from blue.  It is definitely a configuration item.  And note, not ALL warnings are necessarily in the XML.  I can help you figure that out.  For example, we had a case where someone was getting adaptive cruise warnings as they didn't have that and it is actually in the calibration itself.  There's also a gear selection indicator in the calibrations that can make it fun.  In fact, you can go as far as changing the fuel mileage options.

 

Let me take a look at your files and I'll see if I can build you a custom DPS.

 

14 minutes ago, NDCharlie said:

So more then a few odd things and quesitons, I'll post them here as best as I can and with some of the files I think are pertinent but anyone willing to help if you need more info please let me know.

 

So a summary is I purchased a Yukon Denali vin 1GKS1CKJ1GR181357 to install into my Silverado vin 3GCUKSEJ6HG178673.  I installed it and used Troy's vin change file to get milage showing and all is good besides getting a warning for and RPO the Yukon had that my Silverado does not, side collision detection.  The reason for the install was to get the red gauges and screen.  I edited the xml file to remove the warning and programmed the ECU configuration.  The warning is now gone however the screen now has the blue accent color that was factory to the Silverado.  I also tried to build an archive file from a Sierra with the same RPO codes as my Silverado so that the on screen images would be of a pickup instead of a SUV however I am getting the attached error messages when I try to program it.

 

My ultimate goal is to end up with a configuration that is correct and has the red theme and also to have the Sierra programming installed.

 

On other odd thing is when I download the Sierra IPC files from SPS it downloads 17 files when there are 8 listed in the programming list.  Sierra all is the full list of the 17 and Sierra into Silverado is the 8 that SPS lists.  Anyone know what the other files are and are for?

Sierra_programming_into_Silverado.zip 304.17 kB · 1 download Sierraall.zip 961.89 kB · 1 download XMLFile.txt 87 B · 1 download XMLFile.xml 152.98 kB · 1 download ProgramLog.Txt 10.39 kB · 1 download ConfigLog.Txt 31.33 kB · 0 downloads

Do you by chance have:

 

- Your Silverado stock IPC calibration files

- Sierra files you're trying to use

 

And post those here as separate zip's?  It'll make my life easier so I don't have to go DL them 🙂

17 minutes ago, codebuilder said:

Just reviewed the files, with your Sierra_programming_into_silverado.zip, are you trying to load ALL of your Silverado CALs and Sierra?  I looked at that and there's to many files.  That'll fail for sure!  We need to be a little more creative on this one....  You absolutely need the Denali cluster OS (the first file - the large one) as the Silverado one you for sure can't load up.  The other part is, the calibrations should be the same if not similar, but the cluster might get really picky about your calibration numbers.  I can help you build a custom package, based on yours.

 

As for the colour, it's hidden in one of the DIDs (XML).  I can't remember which one, I actually did the opposite and flipped mine to red from blue.  It is definitely a configuration item.  And note, not ALL warnings are necessarily in the XML.  I can help you figure that out.  For example, we had a case where someone was getting adaptive cruise warnings as they didn't have that and it is actually in the calibration itself.  There's also a gear selection indicator in the calibrations that can make it fun.  In fact, you can go as far as changing the fuel mileage options.

 

Let me take a look at your files and I'll see if I can build you a custom DPS.

 

No, the one I was trying to load was the Sierra in silverado one. The Sierra all was partly seeing if the archive took would recognize is and an easy way to put all the files together

17 minutes ago, codebuilder said:

Do you by chance have:

 

- Your Silverado stock IPC calibration files

- Sierra files you're trying to use

 

And post those here as separate zip's?  It'll make my life easier so I don't have to go DL them 🙂

I don't have the stock silverado files but I can go get them.

 

Sierra files I'm trying to use are in the Sierra into silverado file. 

 

That makes sense with the color in the XML, I can go hunting around in them as well

3 minutes ago, NDCharlie said:

No, the one I was trying to load was the Sierra in silverado one. The Sierra all was partly seeing if the archive took would recognize is and an easy way to put all the files together

I realized after looking at your log that you loaded the normal file :).  A little sleepy hahaha.

 

I think I see what's going on.  You didn't even get past the programming the routine, not even as far as the OS upload (you hit step 4).

 

I'll boot my VM up in a bit here and get the files for you.  Don't stress it.  Then I'll see if I can build you something.

 

 

No worries, it was just a matter of running down to the pickup.  Here are all the files that downloaded for the stock vin

10000159.zip

1 minute ago, NDCharlie said:

No worries, it was just a matter of running down to the pickup.  Here are all the files that downloaded for the stock vin

10000159.zip 2.05 MB · 0 downloads

I should have them all pretty quick.  The Sierra one you used, you just found a VIN?  The reason I imagine you're getting the error is because that VIN you used, the cluster might be slightly different (possibly newer).  There's some slight differences...  It won't take me long here.

 

Yea, I was looking around online at vehicles for sale and found one that was similar to mine and used that vin.

2 minutes ago, codebuilder said:

I should have them all pretty quick.  The Sierra one you used, you just found a VIN?  The reason I imagine you're getting the error is because that VIN you used, the cluster might be slightly different (possibly newer).  There's some slight differences...  It won't take me long here.

 

I should also ask, you're still locked out of the ODO as per your other post?  We can easily get that going too if so.

 

lol and that's what I do too!

Haha, yea... so yes and no.  That IPC is still locked out on the ODO yes.  I was able to find a wrecked Yukon and get the IPC at a good price so using that one that I was able to change the vin and get the ODO working correctly for the pickup project and the locked one I will work on later to see if I can get it unlocked for the practice.

Ohhh, ok...  Do you have the VIN of that IPC?  I need to ensure I get the right OS for it.

 

If the VIN above (1GKS1CKJ1GR181357) is the locked cluster, I'll make you an unlock and custom for that one too.  I've already downloaded the calibrations anyways.  But yeah, get me the VIN for the new one if you can.

The above vin 1GKS1CKJ1GR181357 is the not locked one that is currently in use in the pickup.

1 minute ago, NDCharlie said:

The above vin 1GKS1CKJ1GR181357 is the not locked one that is currently in use in the pickup.

Perfect!  Send me later the VIN for the locked one and I'll get you a fix on that one too.

 

I just about have these ready.

Just now, codebuilder said:

Perfect!  Send me later the VIN for the locked one and I'll get you a fix on that one too.

 

I just about have these ready.

That vin is 3GTU2WEJ2FG347155

2 minutes ago, codebuilder said:

Perfect!  Send me later the VIN for the locked one and I'll get you a fix on that one too.

 

I just about have these ready.

No rush though!! 

1 minute ago, NDCharlie said:

That vin is 3GTU2WEJ2FG347155

Yeah, you'll want to keep that cluster as a spare or toy lol....  You'll lose Android Auto / Carplay controls with it because it's a 2015 cluster.  I'll get the files though.

14 minutes ago, NDCharlie said:

No rush though!! 

 

Ok, these files are STOCK....  I just got these for you in case you want to ever revert one (including your own).  The GMC Yukon one should unlock the ------.  Also note, we may have to do an CANBUS learn after, it picks up the hours and such but we can sort that out later.  I'll work on the custom build one now.  I'm hoping your calibrations are close enough but I'll know shortly.  In theory, if you wanted you could test with one of these.

 

Note though!!!!  It's likely going to try to upload the OS.  Expect it to take 30 minutes to program....  So maybe wait for the custom 🙂 haha.  Also, note the OS for your stock one is much larger.

 

 

 

1GKS1CKJ1GR181357-2016-GMC-Yukon-Stock.zip3GTU2WEJ2FG347155-2015-GMC-Sierra-Stock.zip3GCUKSEJ6HG178673-2017-Chevy-Silverado-Stock.zip

22 minutes ago, NDCharlie said:

No rush though!! 

 

Alright, here's your customs.  There were quite a few things different....  Including the transmission gears.

 

Try these customs, if they fail, flash the stock for that cluster in.  Don't worry about the VIN on the filename, it's meaningless, I just put it so you know which file is to which cluster.  These files have the OS's responsible for them and the calibration numbers match what they would have been programmed with (some units don't like certain ranges).

1GKS1CKJ1GR181357-2016-GMC-Yukon-Custom.zip3GTU2WEJ2FG347155-2015-GMC-Sierra-Custom.zip

Awesome, thank you so much! I'll try them probably tomorrow.

 

Do you mind if I ask what the issues were? Trying to learn more how it all works as well. Mostly from a vin with a different IPC? 

7 minutes ago, NDCharlie said:

Awesome, thank you so much! I'll try them probably tomorrow.

 

Do you mind if I ask what the issues were? Trying to learn more how it all works as well. Mostly from a vin with a different IPC? 

No worries!

There's a few things.  The trick you tried to do works in SOME cases, HMI is a great example!  With the HMI, the calibrations are literally only configuration files, no operating system.  So you can pretty much load any HMI 2.5 from any vehicle into one.  With the ECM's, TCM's, Cluster's and more, they tend to include the OS.

Here's where it get's interesting.  The 2015 Denali cluster doesn't allow Android Auto and Carplay controls as the OS just didn't support it.  You have to upgrade to a 2016+ cluster (2016 is red, 2017+ is blue).  Where it get's even better....  2015 and 2015.5 Denali Clusters (in the Diesel's at least) look the same, but the 2015.5 actually supports more features.  And you can't upgrade the 2015 one to it through software.

In your case, you tried to use a 2017 Sierra that was similar but the problem is, the OS and even the routine to start programming is too different and it rejected it.  These things are actually surprisingly fairly fail-safe....  You can unplug in the middle of programming, the cluster will be dead but you can program it again.

What I did in your case:

- Downloaded the 3 STOCK clusters
- Created the custom files off of the stock files:
  - For the two Denali clusters, I used the OS's that GM wants to load onto them.
  - I then even kept the calibration numbers (because some modules check this) but I copied the configuration in those from your cluster.

Another thing to note, not all of the XML configs are the same!  I'll show you (I expect a difference between the UDD and UHS clusters though), it's important to use the one for the cluster your programming.  And......  If you look at the files, there's actually some undocumented stuff that are different.  I can see some between the 2015 Sierra and the 2016 Yukon.

2016 Yukon (note the DidLength):

    <DidItem>
      <ID>DID0003</ID>
      <DidNo>0003</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_03</Name>
      <Description>This DID enables or disables 'Extended Set' warnings</Description>
      <DidLength>26</DidLength>
      <DefaultValue>880007D2E97D0EFA0F00CFFFE40180F8BFF1E7FFE1FFFFFFFF00</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>

Your Silverado:

    <DidItem>
      <ID>DID0003</ID>
      <DidNo>0003</DidNo>
      <DidDataIndicator>0000</DidDataIndicator>
      <Name>DID_03</Name>
      <Description>This DID enables or disables 'Extended Set' warnings</Description>
      <DidLength>32</DidLength>
      <DefaultValue>880007D2E9010FFA0F00CFFFE40180FCBFF1E7FFE7FFFFFFFF1FEE0000007F00</DefaultValue>
      <verifyIfSecured>false</verifyIfSecured>
      <isCustomerData>false</isCustomerData>
    </DidItem>

I have the XML files if you need too.  

 

 

After DPS Programming, you're going to likely need the CANBUS learn and of course the XML configuration.  I wouldn't be surprised if you still get a few warnings, we may have to tweak some of the config.

 

 

What Codebuilder says about the length of the DIDs is correct. The same thing happens in Astra K, the 2016 UDD instrument has shorter DIDs than the 2017 UDD onwards. I understand that it will happen on all speedometers, and that the newer it is, the longer the DIDS is. Now, on a 2016 DID, with a length of 26, can you change it by hand and put 32? I have not tried...

8 hours ago, codebuilder said:

 

Alright, here's your customs.  There were quite a few things different....  Including the transmission gears.

 

Try these customs, if they fail, flash the stock for that cluster in.  Don't worry about the VIN on the filename, it's meaningless, I just put it so you know which file is to which cluster.  These files have the OS's responsible for them and the calibration numbers match what they would have been programmed with (some units don't like certain ranges).

1GKS1CKJ1GR181357-2016-GMC-Yukon-Custom.zip 313.21 kB · 3 downloads 3GTU2WEJ2FG347155-2015-GMC-Sierra-Custom.zip 302.82 kB · 2 downloads

So fun outcomes cuz you know, why not.  Anyway, unfortunately both the Yukon stock and custom files would not program, I got the same error.  I wondered if it was something with the xml file being different so I loaded the stock XML for the Sierra Vin I was trying to use to get the programming files from.  I still got the same error after that and actually any archive file I tried to program in fact as the vin went back to the GMC and my ODO disapeared.  HOWEVER, I was able to just change the vin in the build file and that correct just fine and the sierra xml file has the correct vehicle image, red theme, and close enough RPO's to were I am getting no error messages and ultimately I am exactly were I wanted the IPC to be at. So I'm counting that as a victory.

 

I am still wondering why it will not let me load any archive files to it though.

4 hours ago, NDCharlie said:

So fun outcomes cuz you know, why not.  Anyway, unfortunately both the Yukon stock and custom files would not program, I got the same error.  I wondered if it was something with the xml file being different so I loaded the stock XML for the Sierra Vin I was trying to use to get the programming files from.  I still got the same error after that and actually any archive file I tried to program in fact as the vin went back to the GMC and my ODO disapeared.  HOWEVER, I was able to just change the vin in the build file and that correct just fine and the sierra xml file has the correct vehicle image, red theme, and close enough RPO's to were I am getting no error messages and ultimately I am exactly were I wanted the IPC to be at. So I'm counting that as a victory.

 

I am still wondering why it will not let me load any archive files to it though.

Hmm that should have worked, something else is wrong.  The XML will have nothing to do with the calibrations loading.  Can you post the programlog.txt file for the DPS archives?   it would help a lot.

 

8 hours ago, NDCharlie said:

So fun outcomes cuz you know, why not.  Anyway, unfortunately both the Yukon stock and custom files would not program, I got the same error.  I wondered if it was something with the xml file being different so I loaded the stock XML for the Sierra Vin I was trying to use to get the programming files from.  I still got the same error after that and actually any archive file I tried to program in fact as the vin went back to the GMC and my ODO disapeared.  HOWEVER, I was able to just change the vin in the build file and that correct just fine and the sierra xml file has the correct vehicle image, red theme, and close enough RPO's to were I am getting no error messages and ultimately I am exactly were I wanted the IPC to be at. So I'm counting that as a victory.

 

I am still wondering why it will not let me load any archive files to it though.

I meant to ask too, did it fail right away or after a long time?