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

[Mike G]

Haven’t touched Forscan

Have you ever used a VCXNano?

Sponsored

 

[tobin1920]

What a great thing to wake up to after so many lumps of coal! Currently waiting my 10 minute cool down after the second / post-APIM GWM. Thank you to all for making this thread such a fantastic resource.

 

[Arjan]

When the USB drive is created by FDRS there is one file that is the .cer file. That is the certificate that the car recognizes and allows the files to be updated. The other file is written to the USB drive when the update is complete. That second file is the reason we used to have to put the USB drive back into the computer so FDRS could read and validate that the update completed sucessfully. Now FDRS just does it using the Mongoose cable instead.

So we can speed stuff up when doing multiple cars this way. Good to know.

I do hope europe gets the updates soon.

 

[cbcasas]

Have you ever used a VCXNano?

No I’ve always used a mongoose cable

 

[Mike G]

No I’ve always used a mongoose cable

Okay, you may want to try a reboot of your Sync to see if that particulate filter setting goes away. It's for Diesel engines. Something in your asbuilt got weird.

 

[737flyer]

Your info is similar.

Pulled up my module numbers on Forscan today. A lot of the Forscan numbers are different than the FDRS numbers. For example GWM Forscan is EKN and FDRS is HKD which I believe is correct.

 

[tobin1920]

Getting the PCM 'Procedure Unsuccessful - GetConfigDataFromGIVIS / Modified Configuration data is missing from Ford server' while trying to help a friend update his June/July '22 built Premium AWD ER. I've found some posts about it but there doesn't seem to be a definitive answer or root cause, other than it's probably an issue on Ford's side (the message is pretty clear on that). Can anything be done to get by it or do we just have to wait until they clear it up?

 

[FlowDesign]

hi, I am from Germany and I also have the original UCDS and did some changes on Fiesta, Explorer, Escape and Puma. My Mach E will arrive late Nov. / early Dec.

Which changes -next to updates- did you already accompish? no matter which device you used UCDS, ForScan, FRDS

Hi, a Dutchy here with a job2 2021 imported from Germany

I was wondering if you were able to successfully install all updates on your Mach-E with your UCDS cable.

And do you know where to buy the original one? I'm only finding some Russian sites and imports from China which are probably clones? I have no idea what to look for, they all look the same.

 

[FlowDesign]

If you have an official UCDS adapter it’s works really well with FRDS as well

I've been searching the Internet yesterday for a long time to find out if there's a cheaper alternative to the Mongoose adapter-cable that is still reliable for updating the MME firmware with FDRS, but it seems all cheaper clones are not reliable.

So, I was wondering if you were able to successfully install all updates on your Mach-E with your UCDS adapter-cable.

And do you know where to buy the original one? I'm only finding some Russian sites and imports from China which are probably clones? I have no idea what to look for, they all look the same.

 

[21st Century Pony]

I've been searching the Internet yesterday for a long time to find out if there's a cheaper alternative to the Mongoose adapter-cable that is still reliable for updating the MME firmware with FDRS, but it seems all cheaper clones are not reliable.

So, I was wondering if you were able to successfully install all updates on your Mach-E with your UCDS adapter-cable.

And do you know where to buy the original one? I'm only finding some Russian sites and imports from China which are probably clones? I have no idea what to look for, they all look the same.

I have the original UCDS Russian cable. Its connector is purple / blue. The Chinese UCDS is red, and reportedly a ripoff.

Unfortunately, the Russian UCDS cable, although it works well for UCDS, has some non-standard driver implementations... I could not get it to work with either ForScan or with FDRS. Maybe others here have had more success...

Try a Mongoose+ cable.

 

[snowy_91]

Getting the PCM 'Procedure Unsuccessful - GetConfigDataFromGIVIS / Modified Configuration data is missing from Ford server' while trying to help a friend update his June/July '22 built Premium AWD ER. I've found some posts about it but there doesn't seem to be a definitive answer or root cause, other than it's probably an issue on Ford's side (the message is pretty clear on that). Can anything be done to get by it or do we just have to wait until they clear it up?

The same thing happen to me on Thursday, I have not found a solution to it.

 

[tobin1920]

The same thing happen to me on Thursday, I have not found a solution to it.

I just tried again and now the PCM update is mysteriously gone, and we have a GWM waiting

 

[su-ch+mache]

@FlowDesign

unfortunately my MME has still not been delivered, still in Antwerpen port ?
Talking with customer service was of no success.

The only way to get the original is / was to buy it from the Russian guys. As of current situation today, I would not buy it today. I also made no update since Feb. 2021. To be honest I havn't even updated the softare since. The China version probably will not work.

Did anyone made any update during the last 12 months? Any significant changes?

@21st Century Pony

I also have not been able to make it work with ForScan, only UCDS.

did you update the UCDS system during last 12 months?

 

[Mike G]

Pulled up my module numbers on Forscan today. A lot of the Forscan numbers are different than the FDRS numbers. For example GWM Forscan is EKN and FDRS is HKD which I believe is correct.

Yeah I don't know where FORSCAN is getting EKN from..I just looked at your VIN again and there's no EKN anywhere in your packages for the GWM.

But on the upside you do have a shiny new GWM awaiting you with a tooltip version of G2132531-21.0 (which I understand is highly desirable), and could lead to a new APIM as well.

 

[benk016]

Yeah I don't know where FORSCAN is getting EKN from..I just looked at your VIN again and there's no EKN anywhere in your packages for the GWM.

But on the updside you do have a shiny new GWM awaiting you with a tooltip version of G2132531-21.0 (which I understand is highly desirable), and could lead to a new APIM as well.

I actually reached out to the Forscan devs on the modules not reporting the right version and this is what they said about an RFA module that didn't show a newer version after updating:

The problem is that the algorithm in Vehicle->Configuration is simplified (to keep high performance on connect) and it doesn't count auxiliary files. Usually calibration level is determined by strategy+calibration files, auxiliary files are not counted (as there can be multiple versions of aux files on the same calibration level for different models), so this simplified algorithm is fine in 99% of cases, this case with RFA is an exception.

Sponsored