Optional Product Improvement Program 21G01 - BlueCruise Programming

[Mach-Lee]

Just finished the 4th round of working on @Shaggyrn car.

SUCCESS!

Basically all I did today was go through and do a PMI operation on the modules involved in the BC update series.

The CMR and IPC then updated to show the versions that other cars had and it worked first try on the test drive!

I'll get some data together and post some version levels to look for that are known to work correctly.

Congratulations Ben, you get to write the TSB now! You beat Ford tech support.

Sponsored

 

[benk016]

Well at least for some failure to update modes, I stand corrected!

The FDRS update solved the problem of Ver. 358 -> Ver. 364 without PMI's. However, it does appear that PMIs might do the trick for other existing update failures.

That's the thing, All the updates completed successfully before. I think the bad FDRS version, when it didn't update the ford database correctly, when it would complete the update and write the config back to the module, it was not writing the correct config to enable the features because the database wasn't updated properly. Doing a PMI forced it to update Ford's database and then update the config properly.

At least, that's my theory at this point.

 

[Shaggyrn]

That's the thing, All the updates completed successfully before. I think the bad FDRS version, when it didn't update the ford database correctly, when it would complete the update and write the config back to the module, it was not writing the correct config to enable the features because the database wasn't updated properly. Doing a PMI forced it to update Ford's database and then update the config properly.

At least, that's my theory at this point.

Thank you again Ben. Ford contact Ben he work patiently and what I would call very knowledgeable on updating the Mach e. To all that are having issues find a Ben near you or contact Ben. Again I cannot say thank you enough.

 

[Mach-Lee]

That's the thing, All the updates completed successfully before. I think the bad FDRS version, when it didn't update the ford database correctly, when it would complete the update and write the config back to the module, it was not writing the correct config to enable the features because the database wasn't updated properly. Doing a PMI forced it to update Ford's database and then update the config properly.

At least, that's my theory at this point.

That's a good theory. That could mean only cars that were initially updated with the old/bad FDRS software will have this issue. If only the new FDRS version 31.6.7 was used on your car, then it will probably work. Really dumb that the network scan doesn't update the server with all the current versions before proceeding, it shouldn't take a forced PMI to do that.

 

[benk016]

In looking through some other cars that have had successful BC activation after dealer updates I noticed a few modules in FDRS that were still reporting the wrong version. I have a feeling this is a leftover symptom of the old FDRS not updating the database correctly, which didn't update the module config properly that happens at the end of a module update. It basically was just writing the old config based on the old versions.

Just a guess at this point off my observations.

Here are the modules I noted that likely needed some nudging to get updated. After doing a PMI on these they updated in the FDRS screen with the expected version and on the test drive lane centering came right back, and BC worked flawlessly.

Module	Old Version (Initial update with bad FDRS version)	New Version (PMI With Updated FDRS)
CMR	-XH	-MD
IPC	-AA	-BA
TCU	-BAY	-ADG

Other module versions of note:

Module	Known Good Version
APIM	-AH
CCM	-AL
GWM	-EKL
IPMA	-MDM
PSCM	-BA

 

[generaltso]

I'm seeing this exact pattern of codes in vehicles that are fully updated but still don't have BlueCruise FWIW. Performing the SSM steps doesn't seem to work either.

I‘m seeing those in my car too even with BlueCruise working fine. They can all be cleared, but they’re there again the next time I look for them.

 

[GrumblesTheDog]

Just finished the 4th round of working on @Shaggyrn car.

SUCCESS!

Basically all I did today was go through and do a PMI operation on the modules involved in the BC update series.

The CMR and IPC then updated to show the versions that other cars had and it worked first try on the test drive!

I'll get some data together and post some version levels to look for that are known to work correctly.

Damn you - now I want to get another FDRS license to give this a shot. (I kid - congrats on cracking this, seriously. You deserve a paycheck from Ford for this)

After I updated FDRS (having done all the updates with the old version initially) I did the GWM PMI based on the blurb in the BC maps TSB, but my update list remained empty. Now it looks like I just need to do it on more of the BC-related modules which appear to be prior versions?

Is there anything about doing a PMI operation that's different from a conventional module update? ie even if all precautions are taken (power supply, making sure laptop doesn't sleep etc) are there increased risks of bricking your car by doing this?

 

[benk016]

Damn you - now I want to get another FDRS license to give this a shot. (I kid - congrats on cracking this, seriously. You deserve a paycheck from Ford for this)

After I updated FDRS (having done all the updates with the old version initially) I did the GWM PMI based on the blurb in the BC maps TSB, but my update list remained empty. Now it looks like I just need to do it on more of the BC-related modules which appear to be prior versions?

Is there anything about doing a PMI operation that's different from a conventional module update? ie even if all precautions are taken (power supply, making sure laptop doesn't sleep etc) are there increased risks of bricking your car by doing this?

PMI is normally used when replacing a module with a new one. It downloads the current software and checks it is at the right levels, then it pulls the config for your VIN down and writes all the settings. So since the software was already up to date, it writes the config from Ford's side back to the module and then updates Ford's database. Takes about 1 minute per module when it doesn't have to do an actual update.

 

[trenz]

In looking through some other cars that have had successful BC activation after dealer updates I noticed a few modules in FDRS that were still reporting the wrong version. I have a feeling this is a leftover symptom of the old FDRS not updating the database correctly, which didn't update the module config properly that happens at the end of a module update. It basically was just writing the old config based on the old versions.

Just a guess at this point off my observations.

Here are the modules I noted that likely needed some nudging to get updated. After doing a PMI on these they updated in the FDRS screen with the expected version and on the test drive lane centering came right back, and BC worked flawlessly.

Module	Old Version (Initial update with bad FDRS version)	New Version (PMI With Updated FDRS)
CMR	-XH	-MD
IPC	-AA	-BA
TCU	-BAY	-ADG

Other module versions of note:

Module	Known Good Version
APIM	-AH
CCM	-AL
GWM	-EKL
IPMA	-MDM
PSCM	-BA

Is there any way to explain all of this to the dealer, or we'd have to wait 5 more months for Ford to come up with a new solution.

 

[Gullwingdmc]

Is there any way to explain all of this to the dealer, or we'd have to wait 5 more months for Ford to come up with a new solution.

Good luck. Some dealers don’t want to hear about info you read online. Even if it is more reliable than anything they’re getting from Ford. Some don’t even read what Ford says.

 

[trenz]

Good luck. Some dealers don’t want to hear about info you read online. Even if it is more reliable than anything they’re getting from Ford. Some don’t even read what Ford says.

Yeah, I'll probably end up selling this car, had enough.

 

[Gullwingdmc]

Yeah, I'll probably end up selling this car, had enough.

Don’t do that. Just wait for the OTA updates. It’s not the cars fault the dealers suck.

 

[trenz]

Don’t do that. Just wait for the OTA updates. It’s not the cars fault the dealers suck.

Wait for how long? For how many OTA s? The total lack of communication is also one of the reasons. Is it guaranteed that those OTA updates will be rolled out to my car? Will they solve the current new breakge? Who knows.
I doubt that people who went only through OTA were ever in this broken state.

 

[Gullwingdmc]

Wait for how long? For how many OTA s? The total lack of communication is also one of the reasons. Is it guaranteed that those OTA updates will be rolled out to my car? Will they solve the current new breakge? Who knows.
I doubt that people who went only through OTA were ever in this broken state.

I get it, but unless you are going to Tesla (the only company that seems to be able to do OTA updates right) you are going to have the same problems. In fact they will be worse because ever other auto maker is behind Tesla & Ford on OTA updates.

I am an early adopter, I want the latest and greatest as soon as possible. My plan with this though is to sit back and wait until the dust settles and make a choice on which road to drive down. Currently the OTA road looks to be less of a PITA.

 

[trenz]

I get it, but unless you are going to Tesla (the only company that seems to be able to do OTA updates right) you are going to have the same problems. In fact they will be worse because ever other auto maker is behind Tesla & Ford on OTA updates.

I am an early adopter, I want the latest and greatest as soon as possible. My plan with this though is to sit back and wait until the dust settles and make a choice on which road to drive down. Currently the OTA road looks to be less of a PITA.

That's all true. I'm considering going back to an ICE car for a few years until this industry matures.
The promise that I was sold on is probably not going to happen here, given this very sad state of dealership knowledge and competency. I had a hard time trying to explain to them that a feature I had before is broken now.
Their suggestion was to wait a day or two and see if it resolves by itself.
I'm in the software industry, and if I told this to any of my customers I'd get fired

Sponsored