Optional Product Improvement Program 21G01 - BlueCruise Programming

[Gullwingdmc]

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

My trust in the dealerships has plummeted in the last few months, both in service and sales. Granted there are good ones out there, but they seem to be rare, and the bad was are SOOOO bad.

Best of luck to you!

Sponsored

 

[mpshizzle]

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

I went through and did PMIs on all of these modules. (FDRS 31.6.7)
All of the modules changed to match what you have listed, except APIM and IPMA....sort of

APIM is at AC, and never changed. (My sync screen does show hands free as an option so maybe that's fine?)
IPMA changed from GAP to MDM. But after driving it, changed back to GAP..

It's worth noting that although BC isn't active, my lane centering has never stopped working


---EDIT---

Now all of the modules that changed have reverted back to what they were before... I have no idea what FDRS is doing here.​

​

Only CCM, GWM match the versions you listed (they did before too). TCU seem to be staying on DG (Not ADG.. Was BAY before.)​

 

[Eric_C_Boston]

I went through and did PMIs on all of these modules. (FDRS 31.6.7)
All of the modules changed to match what you have listed, except APIM and IPMA....sort of

APIM is at AC, and never changed. (My sync screen does show hands free as an option so maybe that's fine?)
IPMA changed from GAP to MDM. But after driving it, changed back to GAP..

It's worth noting that although BC isn't active, my lane centering has never stopped working


---EDIT---

Now all of the modules that changed have reverted back to what they were before... I have no idea what FDRS is doing here.​

​

Only CCM, GWM match the versions you listed (they did before too). TCU seem to be staying on DG (Not ADG.. Was BAY before.)​

Some of the modules have multiple applications, so have more than one strategy listed. It seems FDRS picks one for display in the module part numbers list. If you select a module in the list and look below the list, the DIDs (PIDs) for the module are displayed.

On my MME the IPMA or ADAS module has these part numbers as strategies. It was updated with Power-Up 2.5.1
Strategy [F188] ML3T-14H102-ABS
Strategy [F120] ML3T-14H102-MDM
Strategy [F121] NL1T-14H102-SBD
Strategy [F122] ML3T-14H102-GAP
Assembly [DA01] LJ8T-14G647-FT

As you can see both -MDM and -GAP are in the list.

The current module revisions for my RWD ER MME.
CMR
Strategy [F188] ML3T-3G604-XH
Strategy [F120] ML3T-3G604-MD
Assembly [DA01] LJ8T-3G590-XH

IPC
Strategy [F188] LU5T-10F906-AA
Strategy [F120] LU5T-10F906-BA
Assembly [DA01] DSLJ8T-1A292-AK

TCU
Strategy [F188] MU5T-14H085-DG
Strategy [F120] MU5T-14H090-ADG
Strategy [F121] MU5T-14H090-BAY
Boot Image [D027] MU5T-14H241-DG
Boot Image [8068] MU5T-14H240-DG
Assembly [DA01] DSMU5T-14H074-AAX

APIM
Strategy [F188] MU5T-14G676-EJ
Strategy [F0E9] LJ8T-044R30-AC
Image [8033] MU5T-14G682-JT
Boot Image [D027] MU5T-14H234-BD
Boot Image [8068] MU5T-14H236-LA
Assembly [DA01] DSMU5T-14G670-EJ

 

[mpshizzle]

Some of the modules have multiple applications, so have more than one strategy listed. It seems FDRS picks one for display in the module part numbers list. If you select a module in the list and look below the list, the DIDs (PIDs) for the module are displayed.

On my MME the IPMA or ADAS module has these part numbers as strategies. It was updated with Power-Up 2.5.1
Strategy [F188] ML3T-14H102-ABS
Strategy [F120] ML3T-14H102-MDM
Strategy [F121] NL1T-14H102-SBD
Strategy [F122] ML3T-14H102-GAP
Assembly [DA01] LJ8T-14G647-FT

As you can see both -MDM and -GAP are in the list.

The current module revisions for my RWD ER MME.
CMR
Strategy [F188] ML3T-3G604-XH
Strategy [F120] ML3T-3G604-MD
Assembly [DA01] LJ8T-3G590-XH

IPC
Strategy [F188] LU5T-10F906-AA
Strategy [F120] LU5T-10F906-BA
Assembly [DA01] DSLJ8T-1A292-AK

TCU
Strategy [F188] MU5T-14H085-DG
Strategy [F120] MU5T-14H090-ADG
Strategy [F121] MU5T-14H090-BAY
Boot Image [D027] MU5T-14H241-DG
Boot Image [8068] MU5T-14H240-DG
Assembly [DA01] DSMU5T-14H074-AAX

APIM
Strategy [F188] MU5T-14G676-EJ
Strategy [F0E9] LJ8T-044R30-AC
Image [8033] MU5T-14G682-JT
Boot Image [D027] MU5T-14H234-BD
Boot Image [8068] MU5T-14H236-LA
Assembly [DA01] DSMU5T-14G670-EJ

Oh interesting... I didn't realize FDRS just randomly picks which DID to display.
With the story from @benk016 and @Shaggyrn I got hopeful for a moment! But it sounds like he in fact was missing an update that was keeping him from BC activation (at least according to the Ford database)

So it looks like your software revisions match up with me (and Saggyrn) except for -AH on his APIM.

If you are on 2.5.1 that means you're missing the final BC turn on update for the GWM. Out of curiosity what are the DIDs for your GWM?

 

[MorsRedigo]

Was just at the dealer today getting the park break replaced… asked about this update / service but it is not available in Canada yet.

 

[RickMachE]

brake

 

[trenz]

Was just at the dealer today getting the park break replaced… asked about this update / service but it is not available in Canada yet.

I wouldn't worry, as it doesn't work at it's current state..

 

[mpshizzle]

Was just at the dealer today getting the park break replaced… asked about this update / service but it is not available in Canada yet.

brake

I mean..... He wouldn't be at the dealer if his brake didn't break ?

 

[Eric_C_Boston]

Oh interesting... I didn't realize FDRS just randomly picks which DID to display.
With the story from @benk016 and @Shaggyrn I got hopeful for a moment! But it sounds like he in fact was missing an update that was keeping him from BC activation (at least according to the Ford database)

So it looks like your software revisions match up with me (and Saggyrn) except for -AH on his APIM.

If you are on 2.5.1 that means you're missing the final BC turn on update for the GWM. Out of curiosity what are the DIDs for your GWM?

Hello,

I got up to 2.5.3 on my car. I was just noting when the car received the IPMA update.

My path to BC was some updates via FDRS when they were released and OTA for the later ones. I had a few failures with OTA where it looked like the OTA was updating the module(s) to the same level as I had updated via FDRS. I am wondering if the problems were caused by FDRS, and it was corrected in the recent FDRS update.

 

[gnaark]

My dealer called me today saying they have finished the Blue Cruise install on my FE but that when they took it for test drive that it didn't activate. (They said they checked the road portion and that it was a Blue Cruise route - I can see that they drove the car quite a bit too so I'm sure they really tried to make it work)
They are talking to Ford engineers about it and will let me know.

When I pick it up how can I make sure the update was applied properly? I logged into ford.com/connectedservices but do not see Blue Cruise.

My car was also affected by the 1.7.1 stucking and they said they fixed it.

 

[trenz]

My dealer called me today saying they have finished the Blue Cruise install on my FE but that when they took it for test drive that it didn't activate. (They said they checked the road portion and that it was a Blue Cruise route - I can see that they drove the car quite a bit too so I'm sure they really tried to make it work)
They are talking to Ford engineers about it and will let me know.

When I pick it up how can I make sure the update was applied properly? I logged into ford.com/connectedservices but do not see Blue Cruise.

My car was also affected by the 1.7.1 stucking and they said they fixed it.

You can check your sync version. Can also check whether you're a member of the new lane centering breakage club.

 

[gnaark]

You can check your sync version. Can also check whether you're a member of the new lane centering breakage club.

what should be my sync version?
also what do you mean with the line centering breakage?

 

[trenz]

what should be my sync version?
also what do you mean with the line centering breakage?

Check what is the revision displayed under your sync version.
After the updates, many people including myself can't get the older hands on the steering wheel lane assist to engage. Give it a try.

 

[gnaark]

Check what is the revision displayed under your sync version.

Yes, but which # should it be? I'd like to check it at the dealer and not pick it up if it's not the right one you know.

 

[trenz]

Yes, but which # should it be? I'd like to check it at the dealer and not pick it up if it's not the right one you know.

I don't know. I can tell you mine is 244 which is definitely not the right level needed.

Sponsored