ECU module programming guide using FDRS

[Snakebitten]

I have the original backup .abt file for the DSM I created in Fosrcan, but when I am in Forscan and attempt to load the file it says there is an error opening the file.. I am able to open this file in Notepad so I don't think it is corrupt. Is this the file I need to load to the DSM or am I missing something?

Had the same issue trying to load a backup of the IPC.abt backup I originally made in Forscan back when I enabled coolant and tranny digital temps.
The problem is that the module has 12 lines in it back then and now it has 14.

So Forscan gives that error because the architecture does not line up now.

I opened the abt in notepad and manually returned the IPC module back to original. There only needed to be a couple of fields edited.

Sponsored

 

[TJSparky]

All, in my case it looks like the PSCM and IPMA are doing the same thing as the GSM in FDRS. It won’t clear no matter how many times you run it. If you run it a second time it goes quickly and validates the files but doesn’t clear from the list of software updates. So now it seems we have 3 files that won’t clear.

 

[iceman77]

All, in my case it looks like the PSCM and IPMA are doing the same thing as the GSM in FDRS. It won’t clear no matter how many times you run it. If you run it a second time it goes quickly and validates the files but doesn’t clear from the list of software updates. So now it seems we have 3 files that won’t clear.

What VCI have you used ? Mongoose or the Nano ?

 

[TJSparky]

I’m using the Nano

 

[iceman77]

I’m using the Nano

PM me your VIN, I will take a look inside the "mothership"

 

[abd79]

All, in my case it looks like the PSCM and IPMA are doing the same thing as the GSM in FDRS. It won’t clear no matter how many times you run it. If you run it a second time it goes quickly and validates the files but doesn’t clear from the list of software updates. So now it seems we have 3 files that won’t clear.

Same for me, unsing a Mongoose here.

 

[TJSparky]

PM me your VIN, I will take a look inside the "mothership"

Sent, Thanks

 

[abd79]

These look odd in my AB information. This is for the IPMA. PSCM looks normal.

 

[iceman77]

Sent, Thanks

I assume you ran Network Scan recently as I see few corruption in your As-Built data set, but your IPMA and PSCM information seems to be consistent. I can see the ford servers indicating IPMA and PSCM SW module updates, but no actual update files are listed. Hence when you try to update again, nothing happens. This seems to be bug on Ford server side. I don't think its related to FDRS or the Nano device, as I don't see any corruption in your AB data for those modules neither. I'm afraid there is nothing much you can do here. Perhaps we could compare your IPMA and PSCM module SW revision with someone who has applied these updates successfully, that would give us some indication what is going on...

FYI - your IPMA is on ML3T-14H102-ABS and your PSCM is on ML3V-14D003-BC. I would want to see what is the SW revision for these two modules for folks who don't have this issue

 

[jmm3807]

No whatever you do don’t do that! That is a normal dtc clear it and that’s all it’s not a bad dtc

I haven’t been around to look much had to drive to Kansas to fix my daughters car..

Thanks for the info. I did end up clearing and retesting which worked.
Read you next post informing of the future GWM update to actually enable bluecruise… that makes sense. Will keep an eye out.

 

[abd79]

I assume you ran Network Scan recently as I see few corruption in your As-Built data set, but your IPMA and PSCM information seems to be consistent. I can see the ford servers indicating IPMA and PSCM SW module updates, but no actual update files are listed. Hence when you try to update again, nothing happens. This seems to be bug on Ford server side. I don't think its related to FDRS or the Nano device, as I don't see any corruption in your AB data for those modules neither. I'm afraid there is nothing much you can do here. Perhaps we could compare your IPMA and PSCM module SW revision with someone who has applied these updates successfully, that would give us some indication what is going on...

FYI - your IPMA is on ML3T-14H102-ABS and your PSCM is on ML3V-14D003-BC. I would want to see what is the SW revision for these two modules for folks who don't have this issue

I’ve done all the updates and those 4 modules (ABS, GSM, IPMA and PSCM) won’t clear for me either. This is what I have for IPMA and PSCM. I also have 3 odd balls in the IPMA.

 

[iceman77]

Sent, Thanks

I managed to further track down your PSCM update which as per Ford is labeled as "Blue Cruise capability Coordinated SA for ADAS, PSCM, CCM and DSMC"

<NODEID>
730
<F10A>ML34-14D007-BDH</F10A> <= ECU_CONFIGURATION (MATCHES WITH FORD)
<F110>DSML34-3F964-AC</F110>
<F111>ML34-14F079-AC</F111>
<F113>ML34-3F964-BM</F113>
<F124>ML34-14D004-BM</F124> <= CALIBRATION (MATCHES WITH FORD)
<F188>ML3V-14D003-BC</F188> <= STRATEGY (MATCHES WITH FORD
<F18C>10080399</F18C>
<F190>1FTFW1Exxxxxxxxxx</F190>
</NODEID>

In other words, you PSCM is up to date and mothership is aware of it!

Now for IPMA:

<NODEID>
706
<F10A>ML3T-14H106-AFN</F10A> <= ECU_CONFIGURATION (MATCHES WITH FORD
<F110>DSML3T-14G647-AL</F110>
<F111>ML3T-14H107-DF</F111>
<F113>ML3T-14G647-LA</F113>
<F120>ML3T-14H102-MDM</F120> <= STRATEGY (MATCHES WITH FORD)
<F121>NL1T-14H102-SAD</F121> <= STRATEGY (MATCHES WITH FORD)
<F122>ML3T-14H102-GAP</F122> <= STRATEGY (MATCHES WITH FORD)
<F124>ML3T-14H103-AAJ</F124> <= CALIBRATION (MATCHES WITH FORD)
<F125>ML3T-14H103-ABP</F125> <= CALIBRATION (MATCHES WITH FORD)
<F127>ML3T-14H103-GAM</F127> <= CALIBRATION (MATCHES WITH FORD)
<F12A>ML3T-19G490-BB</F12A>
<F16B>ML3T-14H310-BMR</F16B>
<F17F>1AA13HR9</F17F>
<F188>ML3T-14H102-ABS</F188> <= STRATEGY (MATCHES WITH FORD)
<F18C>ECUR2103901732</F18C>
<F1DC>ML3T-14H103-GCF</F1DC>
<F1E0>PXML3T-14G647-AA</F1E0>
<F1F3>28741962</F1F3>
</NODEID>

 

[Jesse-Infotainment]

Sent, Thanks

Did you update to the latest fdrs ?

Nevermind Iceman is looking at it

 

[TJSparky]

I managed to further track down your PSCM update which as per Ford is labeled as "Blue Cruise capability Coordinated SA for ADAS, PSCM, CCM and DSMC"

<NODEID>
730
<F10A>ML34-14D007-BDH</F10A> <= ECU_CONFIGURATION (MATCH)
<F110>DSML34-3F964-AC</F110>
<F111>ML34-14F079-AC</F111>
<F113>ML34-3F964-BM</F113>
<F124>ML34-14D004-BM</F124> <= CALIBRATION (MATCH)
<F188>ML3V-14D003-BC</F188> <= STRATEGY (MATCH
<F18C>10080399</F18C>
<F190>1FTFW1E54MKD66105</F190>
</NODEID>

In other words, you PSCM is up to date and mothership is aware of it!

Stand by for IPMA... (i will update this post)

Thanks Iceman. I appreciate you looking into it!

 

[iceman77]

Thanks Iceman. I appreciate you looking into it!

Check the post above. Both of your modules seems to be updated correctly with all revision info correctly posted to your AB data.

I think you are really in good shape and this is a bug on FDRS (server) side. If it's not fixed soon, you should still receive the latest missing piece, a GWM update in 2.5.2 PowerUp via OTA which will activate the BlueCruise. The mothership is aware you are up to date, I see no reason this would not be happening

Sponsored