ECU module programming guide using FDRS

[Mike G]

After each successful update using the USB drive and the sync screen saying that you can remove the USB and return it to your computer, I clicked on the yes button in FDRS saying that the update was successful with the USB still plugged into the truck. FDRS never asked for the USB drive to be inserted into the computer and continued without any obvious issues. Does the USB need to be plugged into the computer before clicking the yes button and if if wasn't, did this create any problems?

The reason it asks for that USB to be removed from the vehicle and re-inserted into the laptop is that when the update is successful the APIM writes a 'confirmation file' to the USB (with a *.vson file extension, or something like that) so that when you click the "Yes" button in FDRS to indicate the vehicle says it was successful, FDRS supposedly used that file to report success to the mothership. I believe this behavior is a legacy carryover from the 'updating Sync with a thumb drive days', but as you have found out it may no longer be technically necessary since the system does a network scan and reports anyway.

That's my take on it anyway.

Mike

Sponsored

 

[Shoebox72069]

Here Is a screen shot for you.

Thanks! Maybe Ill pick up the torch again but I wouldn't mind seeing an OTA 1st...

 

[tcp]

Keep power cycling the truck until it says update completed, no need to plug back into computer. I’m not sure of the timing but I’ve read people have turned off their truck for x minutes then turned it on. Had a few updates do the same as you described ended up doing a CAN update but should have waited longer or keep cycling until it says successful then FDRS will verify it as successful.

 

[Shoebox72069]

So that BECM on the HS1.....that's the one you're talking about being missing?

Mike

I had some early day issues with the BECM missing its config. Per Jesse it is because the as built is missing the lines "7E4" - they still haven't shown up almost 2 months later.

 

[Mike G]

I had some early day issues with the BECM missing its config. Per Jesse it is because the as built is missing the lines "7E4" - they still haven't shown up almost 2 months later.

So if you 'restored' the AB info in FORSCAN with the module from a similar vehicle would that work?

Mike

 

[Paul Neubauer]

The reason it asks for that USB to be removed from the vehicle and re-inserted into the laptop is that when the update is successful the APIM writes a 'confirmation file' to the USB (with a *.vson file extension, or something like that) so that when you click the "Yes" button in FDRS to indicate the vehicle says it was successful, FDRS supposedly used that file to report success to the mothership. I believe this behavior is a legacy carryover from the 'updating Sync with a thumb drive days', but as you have found out it may no longer be technically necessary since the system does a network scan and reports anyway.

That's my take on it anyway.

Mike

Some of the small details are not real clear and causes confusion. I have not had any major issues other that my power running board motor runs longer than normal occasionally after all the updates. Is there an program to run that recalibrates them?

 

[Mike G]

Some of the small details are not real clear and causes confusion. I have not had any major issues other that my power running board motor runs longer than normal occasionally after all the updates. Is there an program to run that recalibrates them?

I can't help you there. I have no experience with power running boards.

Mike

 

[Paul Neubauer]

Keep power cycling the truck until it says update completed, no need to plug back into computer. I’m not sure of the timing but I’ve read people have turned off their truck for x minutes then turned it on. Had a few updates do the same as you described ended up doing a CAN update but should have waited longer or keep cycling until it says successful then FDRS will verify it as successful.

I always did the required restarts and waited until it said the updates were successful and the USB drive could be removed. I just started second guessing myself a week later and was not sure if I potentially messed anything up by not putting the USB in the computer after the update. My way of thinking is that is that if FDRS wanted the info from the drive, it would have asked for it to continue but who knows with Ford anymore.

 

[Paul Neubauer]

Having this very same experience this afternoon. I’m getting closer.

The IPC update is going to be brutal if it refuses to start using USB. I tried 4 times and finally gave up and selected the other option that took 6 hours. Make sure you have some cold beer in the fridge while waiting for this update if the USB fails!

 

[FordConvert]

I always did the required restarts and waited until it said the updates were successful and the USB drive could be removed. I just started second guessing myself a week later and was not sure if I potentially messed anything up by not putting the USB in the computer after the update. My way of thinking is that is that if FDRS wanted the info from the drive, it would have asked for it to continue but who knows with Ford anymore.

I never plugged the USB back into the computer except to wipe it clean for the next update. I'm Blue Cruising with no issues.

 

[Paul Neubauer]

I never plugged the USB back into the computer except to wipe it clean for the next update. I'm Blue Cruising with no issues.

My Bluecruise has been working well also. I just started second guessing what I did with the USB drive and didn't want any issues because of not plugging it into the computer afterwards. I strangely run an entire repair process through my head with all projects after the fact and over analyze every step thinking about possible errors made.

 

[Jesse-Infotainment]

I always did the required restarts and waited until it said the updates were successful and the USB drive could be removed. I just started second guessing myself a week later and was not sure if I potentially messed anything up by not putting the USB in the computer after the update. My way of thinking is that is that if FDRS wanted the info from the drive, it would have asked for it to continue but who knows with Ford anymore.

Run a self test on the DSM. I found out that’s how you calibrate the running boards after I adddd them to my truck

 

[Shoebox72069]

So if you 'restored' the AB info in FORSCAN with the module from a similar vehicle would that work?

Mike

This is a very good question actually... Most certainly have not tried it.

 

[21PlatinumF150]

After lots of help from all the fine people on this forum, my weekend worth of work paid off! Thank you, thank you to everyone that is selflessly contributing to growing this knowledge base. Happy Blue Cruising gang. Appreciate all the advice and guidance.

 

[Mike G]

Got a question that somebody here may be able to answer. A member on the Mach-E forum who's APIM was 'stuck' due to an OTA used the USB method to get himself unstuck, rather than doing the whole TSB 22-2150 procedure with the various cables. He now has a concern that since he used the USB method to get unstuck and updated (don't know what version he's on currently) that he won't be able to get OTAs (says 2.6.0 has failed repeatedly) because corrupted data is still in the APIM even though he did get unstuck using the USB method.

I have not heard anything about this potential issue from anyone on this forum who has reported getting unstuck using the USB stick and leaving it in until it finally 'takes'.

Can anybody comment on the potential of this actually happening?

Mike

Sponsored