Optional Product Improvement Program 21G01 - BlueCruise Programming

[Logal727]

To me, it sounds like the tech can't read English.

From the instructions:

24. Testing BlueCruise to confirm repair (BlueCruise test drive over 0.5 hours is optional).
• Ensure BlueCruise is fully installed and activated by going to SYNC and selecting Adaptive Cruise Control. Ensure Adaptive Cruise Control is turned ON and Lane Centering with Hands-Free is switched ON.
• Ensure availability of BlueCruise operation by going to SYNC and selecting General, then Settings, then About. Ensure the “Hands-Free Driving Mode available” shows a date in the future
• Determine the nearest hands-free Blue Zone roadway entry ramp locations near your Dealership.
• If test drive can be completed within the allocated Labor Time of 0.5 Hours, perform test drive.

So do they have access to a Blue Cruise map? I’m confused about that part for the test drive.

Sponsored

 

[benk016]

So do they have access to a Blue Cruise map? I’m confused about that part for the test drive.

There is a list with every dealership and the closest section of road it is active on. It's not a full map or list.

 

[Mike G]

Mine is pretty much in the same place (been doing my own FDRS since last year). The question is are we "stuck" because something is not right? Or, are we just waiting for our VIN to be eligible for the last update that gets us to Sync Ver. 364 (an APIM update)?

As in your list (although I do almost all updates, so my list is clear now), there is no new APIM to update Sync from Ver. 358 to 364 yet.

Can you check to see if your GWM version is LJ8T-14H021-EKL ?

If it's an earlier version like EKK you may need to do a PMI to see if that will force the update to EKL. My last APIM update didn't show up until my GWM was updated to EKL (after the network scan).

I went from APIM Sync version 358 completed, to a new download for the GWM, and then as soon as that completed, and was reported to the mothership the last APIM Sync 364 showed up for download.

So there was a GWM update between the two APIM updates for me.

Mike

 

[Mike G]

So do they have access to a Blue Cruise map? I’m confused about that part for the test drive.

It's an attachment to the instructions they get.

Mike

 

[Mike G]

I would not be surprised if the GWM update triggers a bunch of others. They should do the GWM first.

Eggzackly! Doing the GWM almost always leads to more dancing.

Mike

 

[Mike G]

Are you in EA?

EA?....EA? Weee don't need no steenking EA!! We got FDRS!

?

Mike

 

[louibluey]

Can you check to see if your GWM version is LJ8T-14H021-EKL ?

If it's an earlier version like EKK you may need to do a PMI to see if that will force the update to EKL. My last APIM update didn't show up until my GWM was updated to EKL (after the network scan).

I went from APIM Sync version 358 completed, to a new download for the GWM, and then as soon as that completed, and was reported to the mothership the last APIM Sync 364 showed up for download.

So there was a GWM update between the two APIM updates for me.

Mike

Just tried it, PMI GWM (no joy). I am at EKK. Also tried APIM PMI, same, no change. All updates still clear.

I do worry a bit that because I did the updates by FDRS alone (before the 21G01 procedure was available), I may have stopped the process by something being out of the critical order.

Open to all ideas, tried this one right away!

Everyone might not know what PMI is - In FDRS, select the All tab, and search on PMI, or GWM. There is a routine to run called, "GWM - Programmable Module Installation (PMI)". You just run it like any other FDRS routine.

I was running some configuration routines on a couple of nights ago hoping to trigger an update, also no luck that way either.

 

[Nikos]

As I read thru the pages of this forum I sense the impatience or urge to install the BC as quickly as possible. Why not. Waited long enough for this feature.
Well....for me it started last night. The alert showed up at 3pm, scheduled it to start in the evening. I parked my vehicle around 7pm and set up for starting the update.
Within 3 hours was done. So far so good.
Now......how long I have to wait for the entire thing to download.....it is something most of us are going to find out. Hopefully all the Programmable Modules will take the updates and not have to visit the dealers for repairs or reprogramming.
Good luck everyone.

 

[louibluey]

For those with FDRS access, and not yet to Sync Ver. 3.64 the open question is: Is there some way to cause the FDRS server to offer us the next round of updates? Or, does FDRS enable various updates to certain VINs, or ranges of VINs, or by some kind of sign up order, e.g. maybe from when the server first saw our MME?

I vaguely remember some talk of past updates which did not show up on my VIN's FDRS SW Update page for days or weeks (not sure).

The mildly frustrating / annoying case would be if I really do have access now, to the APIM update that would get me Sync 3.64 and hands free, but I just do not know how to signal a request to cause FDRS to offer it. The other minor complication for me, is that I did the updates following FDRS instructions, but before the 5 pages of complex flow of Attachment III of 21G01. After reading it, I did go back and reset the APIM twice using FDRS, but no change. As of yesterday, my FDRS SW Update list still shows all modules updated, nothing left to do.

FWIW, I am at Sync Ver. 2.58, Widget: SYNC4 v4.0.22028 Last Updated: null (thanks Tony!)

The "official" word from my dealer is you just have to wait for your time, even if using dealer or DIY FDRS.

 

[Logal727]

Pretty sure last updated date falls off after a certain amount of time, I haven’t done or got these updates yet but mine says null 3 months after I got 2.3.0. It used to say the date 2.3.0 was installed OTA.

 

[RickMachE]

Pretty sure last updated date falls off after a certain amount of time, I haven’t done or got these updates yet but mine says null 3 months after I got 2.3.0. It used to say the date 2.3.0 was installed OTA.

That's correct.

Scheduled to go in 4/18 for this, let's see if the OTA updates start rolling out so I can cancel that.

 

[generaltso]

The other minor complication for me, is that I did the updates following FDRS instructions, but before the 5 pages of complex flow of Attachment III of 21G01. After reading it, I did go back and reset the APIM twice using FDRS, but no change. As of yesterday, my FDRS SW Update list still shows all modules updated, nothing left to do.

FWIW, I am at Sync Ver. 2.58, Widget: SYNC4 v4.0.22028 Last Updated: null (thanks Tony!)

The "official" word from my dealer is you just have to wait for your time, even if using dealer or DIY FDRS.

I don’t think the order of updates you had already done in FDRS is related since I did the same thing, but was offered the APIM update right away. At first, it seemed that some of the updates only showed up in FDRS for cars that were in Early Access. But now that 21G01 was released, they should be offered for all Job 1 VINs. I think Ford is just late in authorizing all VINs for the updates (or is unaware that they haven’t).

 

[SnBGC]

For those with FDRS access, and not yet to Sync Ver. 3.64 the open question is: Is there some way to cause the FDRS server to offer us the next round of updates? Or, does FDRS enable various updates to certain VINs, or ranges of VINs, or by some kind of sign up order, e.g. maybe from when the server first saw our MME?

I vaguely remember some talk of past updates which did not show up on my VIN's FDRS SW Update page for days or weeks (not sure).

The mildly frustrating / annoying case would be if I really do have access now, to the APIM update that would get me Sync 3.64 and hands free, but I just do not know how to signal a request to cause FDRS to offer it. The other minor complication for me, is that I did the updates following FDRS instructions, but before the 5 pages of complex flow of Attachment III of 21G01. After reading it, I did go back and reset the APIM twice using FDRS, but no change. As of yesterday, my FDRS SW Update list still shows all modules updated, nothing left to do.

FWIW, I am at Sync Ver. 2.58, Widget: SYNC4 v4.0.22028 Last Updated: null (thanks Tony!)

The "official" word from my dealer is you just have to wait for your time, even if using dealer or DIY FDRS.

My car goes in tomorrow. I plan on handing over my key fob and driving away in the rental car without any special instructions and see what happens.

That being said....
I happened to be at the dealership on Friday for something else and came across Mike (service manager) in the hallways and we chatted for a bit. Somehow he already knew I was bringing in my car on Monday and cautioned me that he may not get the BlueCruise installed that same day. Might run into Tuesday which I said was fine.

He said the updates to the modules don't really take that long but waiting for the car to reconcile with the mothership servers can take a few hours. He made it sound like they install stuff, wait for a bit and more stuff appears and then they install those things and so on. He did ask me to give him a call on Monday or Tuesday when I see a message in FordPass that BlueCruise is ready as that is their cue to do the test drive. I will do one better and leave him my old Samsung Galaxy S10 Phone since it still has PaaK and FordPass so they can check it themselves (provided I remember to connect it to their WiFi before I leave)

This will be interesting....

 

[RickMachE]

My car goes in tomorrow. I plan on handing over my key fob and driving away in the rental car without any special instructions and see what happens.

That being said....
I happened to be at the dealership on Friday for something else and came across Mike (service manager) in the hallways and we chatted for a bit. Somehow he already knew I was bringing in my car on Monday and cautioned me that he may not get the BlueCruise installed that same day. Might run into Tuesday which I said was fine.

He said the updates to the modules don't really take that long but waiting for the car to reconcile with the mothership servers can take a few hours. He made it sound like they install stuff, wait for a bit and more stuff appears and then they install those things and so on. He did ask me to give him a call on Monday or Tuesday when I see a message in FordPass that BlueCruise is ready as that is their cue to do the test drive. I will do one better and leave him my old Samsung Galaxy S10 Phone since it still has PaaK and FordPass so they can check it themselves (provided I remember to connect it to their WiFi before I leave)

This will be interesting....

You cheated.

You also have a Service Manager that is on top of things, as I believe I do.

 

[Murse-In-Airy]

That's correct.

Scheduled to go in 4/18 for this, let's see if the OTA updates start rolling out so I can cancel that.

Nothing for you either @RickMachE ? I wasn’t initially concerned as the wife’s car wasn’t in Early Access. But now lots of people seem to be getting OTA’d. Her car still shows no OTA according to Tonesto’s widget. I’m starting to think her car is being left behind.

Sponsored