Can't update SCCM

[walanis]

Hi, here is my problem. On saturday I updated most of the modules using the latest version of FDRS, but I'm having problems with the SCCM module. It has 2 DTC errors that can't be reset and therefore the update fails. As you can see in the pictures one is that it lost communication with the IPMA module and the other is an incompatible configuration. I also tried to do a PMI on the module but it also fails.

A little background. The IPMA update failed at first but reading through the forum someone said they had a DTC when using the FixCam dash camera and once they removed the bypass that connects to the same cable as the mirror the DTC went away. So being that I have the camera I removed it temporarily and the IPMA was able to finish the update. I do have the Glare-Free lightning activated through Forscan so I don't know if this could be causing a problem. The next thing I did was to try and return the SCCM to the AS-BUILT config but nothing. So thinking it was the IPMA I tried the AS-BUILT but forscan told me that the AS-BUILT file does not match the number or registries or lines. It does give me the change to continue but I chose not to. Could it be that the IPMA module did not update correctly?

Before all the updates the SCCM did not have any DTCs, I also uploaded a picture just in case (its the last picture).

I also uploaded a picture to show the other 2 modules that I can't update. One is the BCM, but this one asks for a Dealer login, and the ACM for some reason goes through the update but keeps on showing in the list even thought it looks like it was successful.

Anyway, does anyone have an idea how I can fix the SCCM not updating, how can I remove the two DTCs?

Thanks!

Sponsored

 

[rugedraw]

Are you using a Mongoose or another cable?

Assuming you are using a Mongoose or better, I would try clicking the SCCM in the toolbox tab to bring up all the guided routines. Try running a self-test on the SCCM and then try running the configuration procedure on it.

If that fails, try running a PMI on the SCCM and when FDRS asks if it is the original module, select no.

 

[walanis]

I am using a mongoose cable.

I did the self-test and it showed the DTCs and then I ran the PMI but it failed. I have not tried the configuration procedure, this would program the module to the AS-BUILT correct? Wouldn’t it be the same as doing it with Forscan?

 

[rugedraw]

I am using a mongoose cable.

I did the self-test and it showed the DTCs and then I ran the PMI but it failed. I have not tried the configuration procedure, this would program the module to the AS-BUILT correct? Wouldn’t it be the same as doing it with Forscan?

Sorry, just seeing this. Just re-read your OP and see you had tried the PMI already.

Message me the VIN and I'll poke around tomorrow to see if I find anything useful.

@Jesse-Infotainment Any insight here?

 

[walanis]

@rugedraw, I sent you the VIN.

I was thinking that it could be the IPMA module programming and so maybe try the PMI on that module. There are no DTCs in the IPMA but like I said in the OP when I tried to return the IPMA to AS-BUILT using Forscan it gave me a warning that the number of registries did not match. I could still tell it to continue but I chose not to.

What do you think, could the problem be in the IPMA config and this is why the SCCM is not able to communicate?

 

[Jesse-Infotainment]

2101 PREVENT THE UPDATE FROM CLEARING. You have an issue with the as build online.. until the as build is fixed online it wont allow the update to complete successfully.

IF the module flashed. Im sure it did. All we need to do is correct the 2101 and leave it be. Eventually the interrogator will run and update the online as build

 

[rugedraw]

This is only file FDRS wants to flash with the PMI:

This is the strategy file on your SCCM:

As per usual, Jesse is right. Seems to be a config mismatch between what's on your truck and on the server. When your truck syncs up with the mothership, it should clear the code. If everything is working as it should, then you can ignore the code.

 

[rugedraw]

When you can, plug the truck back in to FDRS, clear codes and see if it comes back now.

 

[walanis]

Thanks for the response guys. Sorry for being so late responding but I got caught up at work.

Again thanks for the info!

@rugedraw I sent you a DM with my situation.

 

[Mike G]

Thanks for the response guys. Sorry for being so late responding but I got caught up at work.

Again thanks for the info!

@rugedraw I sent you a DM with my situation.

Between my 22 model with glare-free enabled and your truck....this value is the only difference in all of the SCCM register values.

The "0" at the start of the second octet means you don't have (or never got) the heated steering wheel. "8" on my truck means I do have it (and I do). I see in the system that you have an outstanding FSA to have the heated wheel retrofitted. But given your location that may not happen soon.

The next value is "C" for both of us and relates to number of blinker flashes when changing lanes.

What I don't know (spreadsheet doesn't say what it is) are the last two values in the octet (these are NOT checksums, those are not shown here at all for clarity).

On your truck it shows "70" and on my truck it's "2D". Maybe that's what's causing the configuration issue?

You can try changing your 70 to 2D and see what happens.

My truck has everything working with zero DTCs on anything.

 

[walanis]

Hey Mike G, checking a picture I took in forscan of my SCCM configuration it is the same as your configuration. I also have the 2D values.

 

[Mike G]

Hey Mike G, checking a picture I took in forscan of my SCCM configuration it is the same as your configuration. I also have the 2D values.

Well, then the next thing to try is to push the values that your truck actually has to the cloud server using FDRS by selecting the SCCM module on the left side of the screen and then selecting the Read Configuration Data tool on the right side. This will read the values you currently have and push them to the cloud so that the asbuilt data would be synched up. After a shutdown and reboot, that DTC might go away after that. Then you could update that SCCM.

The values I posted earlier in the comparison of our two trucks, were asbuilt values for your truck that are currently in the cloud. So obviously what the cloud has stored doesn't match what you actually have now. Reading the configuration data and posting it to the cloud should fix that.

 

[bmwhitetx]

Just FYI, in looking at my database of trucks, all Lariats (22-25) have 2D. The only trucks that have 70 are some 22-23 Pro and XLT's. Livinitup's spreadsheet indicate that value is Assisted Lane Change Timeout. So safe to change.

However, I noticed my original AsBuilt for my 22 Lariat was a 70. But some time in late 2023 it got updated to 2D (in truck and online). So maybe that's the issue - your truck was 70, got updated but not synced.

(Also you should update your account to include year.)

Fun thing to try off-topic. ALC Timeout is 2D hex which is 45 decimal. Someone with BC 1.4 should see how long ALC will attempt to change lanes (flash blinker) in busy traffic before cancelling. Is it 45 seconds?

 

[Mike G]

I must have an older version of that spreadsheet. I'll look for an updated version.

I've run into things like this before, where the spreadsheet values on some modules have sections that are seemingly just 'skipped over' and are missing. I've asked Livin' about it before and I don't really remember what the outcome of that discussion was. Also, while on that topic, I've never gotten an answer as to where these spreadsheet values for the module variables come from. Seeing as how the format of the asbuilt values appears to be fairly consistent across all the modules (how each option and all the possible permutations are laid out in a tabular format), it would seem it must be coming from some official source rather than something somebody reverse engineered. And that's what puzzles me about the occasional missing settings...like whole sections of some the module asbuilt values are just skipped over for some reason. Very strange.

 

[bmwhitetx]

There are SCCM tabs for 21-23 and 24+. For 21-23 the parameter is "LaneChangeMaxTime (LCMT)". For 24+ it is "MaxALCFlashingDuration (MALCFD)". ALC=Assisted Lane Chane, a BlueCruise 1.2 feature.

21-23 was before BC 1.2 and ALC. But for 2024 ALC became a thing with BC 1.2 so they likely renamed it.
All years will "soon" be getting BC ALC.

Sponsored