ECU module programming guide using FDRS

[Jesse-Infotainment]

The only thing I can do is side load the file at this point. It would take 5-6 hours to flash it. Im not sure TheY would be willing to let me do it or not. If they are Id have to remote in and do it. I doubt they would let me do it. I would have to install software and they would need to let me do it through Teamviewer.

Sponsored

 

[speedracercjr]

Thats what I mean, connected services shows:

Connected built-in Navigation Trial Exp. Date 3/18/24
Ford BlueCruise Trial Exp. Date 5/15/23
Ford Pass app shows Blue Cruise exp date 5/15/23

The above are all correct

My question is why do I see so many guys (me include) see this on the sync screen
"Hands Free Driving Mode Available Through 10-9-2022"

That's just the date that was pushed to all of us. Sometime before 10-9 everyone who has BlueCruise is going to need an update that pushes that date out further. If they screw that up it'll get real interesting....

 

[JEB]

That's just the date that was pushed to all of us. Sometime before 10-9 everyone who has BlueCruise is going to need an update that pushes that date out further. If they screw that up it'll get real interesting....

If? You’re hilarious!

 

[TJSparky]

FDRS has an update to the software out. Version 32.5.3

 

[Mike G]

FDRS has an update to the software out. Version 32.5.3

I'm on it!

Mike?‍

 

[rack04]

Is VCI Software a required install to work with FDRS? Just trying to make sure I have the software side all configured before the license clock starts.

 

[ken325i]

Can anyone with FDRS please check my VIN# for any indication of cause of failure for OTA 2.1.1 -- VIN: 1FTFW1E89MFA78177 .

In the last 4 weeks I have had 3 failed OTA 2.1.1 updates. I don't understand why.

In late March my dealer repaired the frozen 1.7.1 update. A couple of weeks later, I received OTA 2.1.0. As shown on the Widget, I began having queued the 2.1.1 OTA update. It would fail in the first 24-48 hours. Then, after a week, it would reset. There has been 3 OTA update failures for 2.1.1.

Any help and direction would be appreciated.

Thanks
Ken

 

[Mike G]

Is VCI Software a required install to work with FDRS? Just trying to make sure I have the software side all configured before the license clock starts.

I have it installed. I'm pretty sure it's required. I use a Mongoose-Plus Ford 2.

Mike

 

[Mike G]

Can anyone with FDRS please check my VIN# for any indication of cause of failure for OTA 2.1.1 -- VIN: 1FTFW1E89MFA78177 .

In the last 4 weeks I have had 3 failed OTA 2.1.1 updates. I don't understand why.

In late March my dealer repaired the frozen 1.7.1 update. A couple of weeks later, I received OTA 2.1.0. As shown on the Widget, I began having queued the 2.1.1 OTA update. It would fail in the first 24-48 hours. Then, after a week, it would reset. There has been 3 OTA update failures for 2.1.1.

Any help and direction would be appreciated.

Thanks
Ken

Service history shows that the OTA dashboard was checked yesterday evening (PTS, OTA dashboard) but that's all it shows. The service manager may be able to see more.

Here's a list of the updates you have pending if that's helpful.

Mike

 

[ken325i]

Service history shows that the OTA dashboard was checked yesterday evening (PTS, OTA dashboard) but that's all it shows. The service manager may be able to see more.

Here's a list of the updates you have pending if that's helpful.

Mike

Thanks for your help! I believe it is time to get the Mongoose......

 

[JoeBlowFord]

Will someone with a 2021 Job 1 Plat 701A please post their value for:

DSM
744-23-02

 

[Snakebitten]

Is this what you are looking for?

 

[jperry5835]

Is this what you are looking for?

I can confirm this is the same on mine

 

[JoeBlowFord]

Thank you both, that is exactly what I'm looking for.

Mine changed:
Was - 0100 0071
Is - 0100 0000 71

 

[JoeBlowFord]

One more thing...

The DTC references the attached the TSB 21-2179, but it seems like that TSB doesn't apply because I have a truck that came with the factory brake controller.

@Jesse-Infotainment Is there a way to force a build data push to Ford? Is it possible that a bad value somewhere could prevent the module from either sending data to Ford or Ford rejecting it and not update the module's values on their side?

I've had this persistent DTC on the DSM, despite running a PMI and config on it, ever since completing all updates 11 days ago on 5/8.

I just did a more thorough comparison of all module values from before and after running the software updates, along with the current build data at Ford. I'm seeing:

• Neither the IPMA or the DSM have updated new info at Ford, both show the original values before running any software updates
• PCM value for 7E0-165-52 at Ford doesn't match either the before or after update values
  • Value description - DID_DEA4_Transmission Identification block (DIDDEATI)
• PCM values for 7E0-166-xx don't exist at Ford
  • Value description - DID_DEA5_Misfire Neutral Profile Correction 256 (DIDDEAMNPC)

The PCM discrepancies probably make sense.

Sponsored