The Complete DIY Guide to Updating Your Mach-E with FDRS

[nmundo]

So I just got another license and was able to reset the APIM configuration this time and all the DTCs are gone except for the ABS one and I'm going to try driving around in a bit to see if it clears. Repair utility still fails. It doesn't even get to the point where it asks for either cable to be connected which it had been able to do before I updated all the modules. It fails at "Programming ECG" with the "Procedure Unsuccessful - FlashDiagFileOverCAN Failed to flash MU5T-14H116-CA" error.

Looking at the logs seems to always fail right here, even though it did get past this step before I updated the other modules:

About to download: MU5T-14H116-CA
BEGIN ~~ DownloadFiles
Download file started:-MU5T-14H116-CA

Comms fail during download
END ~~ DownloadFiles
Failed to flash MU5T-14H116-CA

Versions currently are:

ABS - Antilock braking system
Part number: LJ9C-2C219-AK
Calibration level: LJ9C-2C219-AK
Strategy : LK9C-2D053-CD

GWM - Gateway Module A
Part number: MU5T-14G650-ABX
Calibration level: MU5T-14G650-ABX
Strategy : LJ8T-14H021-AKE

IPMA - Image Processing Module A
Part number: LJ8T-14G647-NA
Calibration level: LJ8T-14G647-NA
Strategy : ML3T-14H102-ACA
Calibration: ML3T-14H103-AAF

IPC - LJ8T-14C028-AL
APIM - MU5T-14G878-CA

Sponsored

 

[noway]

Clear some cache maybe if it fails before connecting? The files are downloaded to C:\ProgramData\Ford Motor Company\FDRS\fdrs\data\vehicle_software\ .. try to move those files away at least and let it re-download. (they can be valuable later in case you need to try with Forscan, so don't delete them, just move them away). There is a redownload button inside FDRS, but I don't think it removes the actual firmware files, just the "application" which downloads them.

It could also be that it is not necessary to run the repair utility, it might already have finished whatever is required to proceed with normal updates?

 

[Js1tr3]

I'm having the same problem, and i may have updated modules out of order also

Interface:
Adapter: Mongoose-Plus Ford2
Min.delay: 1 ms ( Excellent)
Errors: None

Vehicle:
Model: Ford Mach-E
Engine: Battery Electric Vehicle
Capacity: 75-99kWh
Year: 2021
Generation: 2021 MY
Fuel: Gasoline
Transmission gear: Automatic
VIN: 3FMTK3SS2MMA09725

SOBDMB - Secondary OBD Control Module B
Part number: LJ98-7S008-AA
Calibration level: LJ98-7S008-AA
Strategy : LJ98-14H297-DD
VIN: 3FMTK3SS2MMA09725

SOBDMC - Secondary OBD Control Module C
Part number: LJ98-7P120-AD
Calibration level: LJ98-7P120-AD
Strategy : LJ98-14G069-AXG
VIN: 3FMTK3SS2MMA09725

BECM - Battery Energy Control Module
Part number: LJ98-10B687-AF
Calibration level: LJ98-10B687-AF
Strategy : NJ98-14C197-AB
VIN: AP23A21015210051L

SOBDM - Secondary OBD Control Module A
Part number: LJ98-10B689-YD
Calibration level: LJ98-10B689-YD
Strategy : LJ98-14F476-AS
Calibration: LJ98-14F477-AS
VIN: 3FMTK3SS2MMA09725
Total Distance: 12795.0 km

PCM - Powertrain Control Module
Part number: MJ98-12A650-VA
Calibration level: MJ98-12A650-VA
Strategy : MJ98-14C204-AXJ
Hardware type: LJ98-12B684-AE
VIN: 3FMTK3SS2MMA09725

OBDII - On Board Diagnostic II

ACCM - Air Conditioning Control Module
Part number: LJ9H-19F611-AB
Calibration level: LJ9H-19F611-AB
Strategy : LJ9H-14D491-AB
Total Distance: 12795.0 km

SODR - Side Obstacle Detection Control Module - Right
Part number: ML3T-14H031-AH
Calibration level: ML3T-14H031-AH
Strategy : ML3T-14H094-AH
VIN: 3FMTK3SS2MMA09725

SODL - Side Obstacle Detection Control Module - Left
Part number: ML3T-14H031-BH
Calibration level: ML3T-14H031-BH
Strategy : ML3T-14H094-BH
VIN: 3FMTK3SS2MMA09725

CMR - Camera Module Rear
Part number: LJ8T-3G590-AG
Calibration level: LJ8T-3G590-AG
Strategy : ML3T-3G604-XH
Calibration: LJ8T-3G605-XG

CCM - Cruise Control
Part number: ML3T-9G768-AH
Calibration level: ML3T-9G768-AH
Strategy : ML3T-14D049-AL
VIN: 3FMTK3SS2MMA09725
Total Distance: 0.0 km

ABS - Antilock braking system
Part number: LJ9C-2C219-AK
Calibration level: LJ9C-2C219-AK
Strategy : LK9C-2D053-CD
VIN: 3FMTK3SS2MMA09725
Total Distance: 12795.0 km

PACM - Pedestrian Alert Control Module
Part number: LJ8T-14G113-DA
Calibration level: LJ8T-14G113-DA
Strategy : ML3T-14G492-BB
Calibration: LJ8T-14G493-AB

DCDC - DC to DC Converter Control Module
Part number: LJ98-14B227-AF
Calibration level: LJ98-14B227-AF
Strategy : LJ98-14D459-AC
Total Distance: 12795.0 km

PSCM - Power Steering Control Module
Part number: LJ9C-3F964-AK
Calibration level: LJ9C-3F964-AK
Strategy : LJ9C-14D003-BA
Calibration: LJ9C-14D004-BAA
VIN: 3FMTK3SS2MMA09725
Total Distance: 12795.0 km

BdyCM - Body Control Module
Part number: MU5T-14B476-RCJ
Calibration level: MU5T-14B476-RCJ (latest known: MU5T-14B476-RCM)
Strategy : MU5T-14C184-ACM
VIN: 3FMTK3SS2MMA09725

BECMB - Battery Energy Control Module B
Part number: HU5T-14G490-AF
Calibration level: HU5T-14G490-AF
Strategy : HU5T-14G499-AE

GWM - Gateway Module A
Part number: MU5T-14G650-ABX
Calibration level: MU5T-14G650-ABX
Strategy : LJ8T-14H021-AKE
VIN: 3FMTK3SS2MMA09725

IPMA - Image Processing Module A
Part number: LJ8T-14G647-FJ
Calibration level: LJ8T-14G647-FJ
Strategy : ML3T-14H102-ABS
Calibration: ML3T-14H103-AAJ

 

[Eric_C_Boston]

So I just got another license and was able to reset the APIM configuration this time and all the DTCs are gone except for the ABS one and I'm going to try driving around in a bit to see if it clears. Repair utility still fails. It doesn't even get to the point where it asks for either cable to be connected which it had been able to do before I updated all the modules. It fails at "Programming ECG" with the "Procedure Unsuccessful - FlashDiagFileOverCAN Failed to flash MU5T-14H116-CA" error.

Looking at the logs seems to always fail right here, even though it did get past this step before I updated the other modules:

About to download: MU5T-14H116-CA
BEGIN ~~ DownloadFiles
Download file started:-MU5T-14H116-CA

Comms fail during download
END ~~ DownloadFiles
Failed to flash MU5T-14H116-CA

Versions currently are:

ABS - Antilock braking system
Part number: LJ9C-2C219-AK
Calibration level: LJ9C-2C219-AK
Strategy : LK9C-2D053-CD

GWM - Gateway Module A
Part number: MU5T-14G650-ABX
Calibration level: MU5T-14G650-ABX
Strategy : LJ8T-14H021-AKE

IPMA - Image Processing Module A
Part number: LJ8T-14G647-NA
Calibration level: LJ8T-14G647-NA
Strategy : ML3T-14H102-ACA
Calibration: ML3T-14H103-AAF

IPC - LJ8T-14C028-AL
APIM - MU5T-14G878-CA

I have an ER RWD Job 1 and I do not have 14H116 listed as a base part number for any module. It may be a secondary bootloader that is used on some modules to flash the firmware in the module.

ABS is at the level of updates I applied in November and is current.
GWM is at the level of Power-Up 1.6.
IPMA is at the level of updates I applied in November. Power-Up 2.5.1 updates to ML3T-14H102-ABS
IPC base strategy part number is different.
APIM base strategy part number is different.

 

[PeeKay]

So I just got another license and was able to reset the APIM configuration this time and all the DTCs are gone except for the ABS one and I'm going to try driving around in a bit to see if it clears. Repair utility still fails. It doesn't even get to the point where it asks for either cable to be connected which it had been able to do before I updated all the modules. It fails at "Programming ECG" with the "Procedure Unsuccessful - FlashDiagFileOverCAN Failed to flash MU5T-14H116-CA" error.

How did you reset the APIM configuration within FDRS?

 

[machefan]

I am getting ready to start this update journey, so wish me luck. I have a baseline question, when I ran ForScan it said there were DTCs present, do I clear those first. I think they are left over from prior updates but thought to ask. I have attached the logs.

Second question, in terms of timing how did one go about purchasing FDRS. Meaning, buy in the early morning and run the updates that day, use day 2 as a backup? Is it Midnight to Midnight, or purchase time to purchase time 48 hours later. Aside from cost which is expensive as it stands, did anyone buy a month or a year and feel it was worth it?

Thanks to all who contributed to this thread, very helpful!

 

[GBRoc]

Second question, in terms of timing how did one go about purchasing FDRS. Meaning, buy in the early morning and run the updates that day, use day 2 as a backup? Is it Midnight to Midnight, or purchase time to purchase time 48 hours later. Aside from cost which is expensive as it stands, did anyone buy a month or a year and feel it was worth it?

Thanks to all who contributed to this thread, very helpful!

In terms of a 2 day license and timing, the last time I purchased in the AM I bought the license at 11AM in Apr 1 and it expired on Apr 3rd at 23:59. So I got two full days plus whatever part of the day I purchased. It was plenty of time to run through all of the updates to do TSB 22-2117 and 21G01 and all of the other updates my car needed since the last time I updated the car at the beginning of January.

 

[ZuleMME]

My licenses have been 48 hours on the dot.

Planning to do this myself soon. Just waiting on my 14-50 to 5-20 adaptor to come in so I can properly power my PSU...

 

[machefan]

Forscan works fine for reading

So I got the FDRS license, connected to the MME, but it said it could not read all modules. Then it said all were offline after running the self-test. However when I try to connect again it says it can't find the MME when looking up the VIN. The Mongoose says it's connected and Forscan is able to read. Strange, but story of my life.

Any ideas anyone?

 

[smartino]

Forscan works fine for reading

So I got the FDRS license, connected to the MME, but it said it could not read all modules. Then it said all were offline after running the self-test. However when I try to connect again it says it can't find the MME when looking up the VIN. The Mongoose says it's connected and Forscan is able to read. Strange, but story of my life.

Any ideas anyone?

Make sure car is on in accessory mode (start without foot on brake) not actually running.

 

[ZuleMME]

And ensure you actually closed forscan. It could be keeping the USB port in use. Maybe reboot if needed.

 

[machefan]

And ensure you actually closed forscan. It could be keeping the USB port in use. Maybe reboot if needed.

The Mongoose does not tightly fit in, it's fairly lose, does others have that problem? Should it lock in? That was the problem, was not making a enough good fit. Was partially reading.

 

[bshaw]

The Mongoose does not tightly fit in, it's fairly lose, does others have that problem? Should it lock in? That was the problem, was not a making enough good fit.

Mine was a little wobbly, but I was sure to always fully seat it into the connector. And then of course be careful not to knock it with my feet/legs when sitting in the drivers seat.

There are two status lights on the mongoose. Seems like the red stayed on indicating it has a connection to the car, and then the green flashes when sending data to the car. I may have the colors mixed up (from memory), but it was definitely two status lights.

 

[noway]

Forscan works fine for reading

So I got the FDRS license, connected to the MME, but it said it could not read all modules. Then it said all were offline after running the self-test. However when I try to connect again it says it can't find the MME when looking up the VIN. The Mongoose says it's connected and Forscan is able to read. Strange, but story of my life.

Any ideas anyone?

It seems to be a common issue. The general advice is to never run network scan or self-test. It does something that corrupts the data, especially when using cheap adapters (like you are not.. which is kind of strange).

I also tried to do a self-test after my first successful update, and I think it might have started to fail after that. Everything just locked up and it was never able to recover and get a successful network scan after that.

Looking at my logs from FDRS it might seem that the VIN check when connected to vehicle requires to do a full version check on all modules (aka network scan), and if it cannot read all of them it will just fail the VIN check. The solution to that is to not connect to the vehicle before selecting vehicle. Only problem is that it will not run the network scan, so it will not update the module versions, but it still works, and each update will update the module versions on its own, so unless modules are updated with Forscan it will work to just skip the network scan. Even if updating outside FDRS (like I had to with the CCM) it seems to be able to pick it up eventually if the network scan is repeated several times.

Just use Forscan for the self tests and fault code clearing, it work much better than FDRS.. and it will not report the audit logs to the mothership at the blue oval HQ. Keep in mind that Forscan will not complain if it cannot read all modules, it will just not show them, FDRS keeps track of which modules is supposed to be there, Forscan does not unless it is already stored in a profile, which is why it is so important to create and store a full Forscan profile before starting anything.

 

[noway]

So I just got another license and was able to reset the APIM configuration this time and all the DTCs are gone except for the ABS one and I'm going to try driving around in a bit to see if it clears. Repair utility still fails. It doesn't even get to the point where it asks for either cable to be connected which it had been able to do before I updated all the modules. It fails at "Programming ECG" with the "Procedure Unsuccessful - FlashDiagFileOverCAN Failed to flash MU5T-14H116-CA" error.

Looking at the logs seems to always fail right here, even though it did get past this step before I updated the other modules:

About to download: MU5T-14H116-CA
BEGIN ~~ DownloadFiles
Download file started:-MU5T-14H116-CA

Comms fail during download
END ~~ DownloadFiles
Failed to flash MU5T-14H116-CA

Versions currently are:

ABS - Antilock braking system
Part number: LJ9C-2C219-AK
Calibration level: LJ9C-2C219-AK
Strategy : LK9C-2D053-CD

GWM - Gateway Module A
Part number: MU5T-14G650-ABX
Calibration level: MU5T-14G650-ABX
Strategy : LJ8T-14H021-AKE

IPMA - Image Processing Module A
Part number: LJ8T-14G647-NA
Calibration level: LJ8T-14G647-NA
Strategy : ML3T-14H102-ACA
Calibration: ML3T-14H103-AAF

IPC - LJ8T-14C028-AL
APIM - MU5T-14G878-CA

Do you have any GWM updates in the list of available updates. .. it is seems to be quite important to do the GWM updates FIRST of all the GWM, IPC, APIM and TCU updates since those modules update from the GWM module, through the APIM module. (USB is connected directly to APIM module, GWM is the one having the point-to-point ethernet connections to the IPC, APIM, TCU and IPMA modules), and it is also the module having all the CAN-bus connections to every other module also when updating via the OBD port.

Sponsored