ECU module programming guide using FDRS

[Snakebitten]

How long has everyone waited after inserting the USB drive into the port in the truck before it started updating automatically? I’ve waited 10 minutes and never got a message. I can see that the USB drive is detected though when inserting.

Some trucks immediately
Some trucks after several minutes and/or a few retries.
Some trucks after driving around with the USB inserted for days/weeks.

It's one of the more frustrating inconsistencies.

What's your battery voltage reading right now?

And what are your Sync update settings? Some feel that changing the settings may have kicked things off.

Sponsored

 

[nicholsbradley]

Members helping Members out of a jam.
Sometimes when you Need to get something done you have to take matters into your own hands and get it done.

Very true but it seems not all trucks are able to update and get BC without Ford and some just dont have the want to buy expensive adapters and LIC like us. They just want a promised feature to work.

 

[Fordphanatic]

Very true but it seems not all trucks are able to update and get BC without Ford and some just dont have the want to buy exspensive adaperts and LIC like us. They just want a promised feature to work.

I hear what your saying for sure.

 

[rpeterslll]

The first USB drive detected but never said indexing. I tried a second USB and it detected and it said indexing. Several minutes later and still no updating yet. I’m getting 13V right now.

So the laptop can be disconnected right now and drive around with the USB inserted to wait for the update to compete?

Sync updates are locked out. But it was set to auto before.

 

[Platinum Peasant]

So I’ve hit a roadblock, and I’m posting this in case someone knows what is failing/ going on (or in case someone else too experiences this issue). Huge thank you to @Jesse-Infotainment for working on this with me over the last 2 days, but unfortunately the issue still persists. If someone mentioned this issue already, I apologize. My eyes are almost literally on fire as I read through the entire 2000+ posts on this thread over the last 2 nights while working in the NICU in between patient rounds, and didn’t see it mentioned.

When attempting to update the IPC or GWM module, FDRS attempts to download the update for about 30 seconds and then displays: GWM software update application ended with an error state. It does the same thing for the IPC. Also, if a PMI is attempted on either module, it does the same thing, ending in an error state after attempting to download. I have never been prompted to insert a usb drive, ever. Not sure if this is related to a GWM Ethernet problem. Currently on 2.3.0

My other modules updates mostly went through just fine without issue, except, like mentioned heavily earlier in the thread, some won’t clear from the list: GSM, PSCM, IPMA, etc. When I was updating IPMA the first time, it errored out about 80% of the way through. I reapplied the update again and it went through successfully the second time. Active driver assist (what keeps your wheel centered on the highway while cruising and lane assist on) does not work at this time. No other errors are popping up on the IPC.

No DTCs are present on any of the modules present, they are also green on FDRS and pass self tests flawlessly.

I am using a mongoose cable, drivers installed, and have no used any other devices. Forscan reset of the modules was also done, went off flawlessly without issue.

I am not good with reading advanced code, so I am not 100% sure if any of my AB is corrupted or if this issue is entirely on the FDRS side. My vin is 1FTFW1E11MFB18254.

I tried pulling the battery for about 7 hours (while I slept during the day for work tonight), didn’t change anything. FDRS was reinstalled. Large quantities of coffee consumed. My voltage holds relatively steady during updates. Internet connection reset.

Also pictured: when I try to shutdown my laptop, this error pops up related to FDRS. I will be trying a newer laptop later this weekend, but I stopped right here as I don’t want to screw things up by clicking on ? without asking other first.

Any help on this would be greatly appreciated.

 

[Snakebitten]

The first USB drive detected but never said indexing. I tried a second USB and it detected and it said indexing. Several minutes later and still no updating yet. I’m getting 13V right now.

So the laptop can be disconnected right now and drive around with the USB inserted to wait for the update to compete?

Sync updates are locked out. But it was set to auto before.

Yes, you can disconnect FDRS and pick back up where you left off after the USB portion of the update.

Just for grins, change your Sync update settings to something other than what they currently are.

And I personally think that there's nothing lost trying as many times as you want to in order to get it to kick off. Although I would wait at least 3-5 minutes after "indexing" before I gave up on that attempt.

I think we just haven't discovered what the actual "condition" is that blocks the initiation copying of files to the onboard storage. (I can't remember where that actual onboard storage is located? Is it the Gateway module?)

 

[rpeterslll]

Some trucks immediately
Some trucks after several minutes and/or a few retries.
Some trucks after driving around with the USB inserted for days/weeks.

It's one of the more frustrating inconsistencies.

What's your battery voltage reading right now?

And what are your Sync update settings? Some feel that changing the settings may have kicked things off.

13V

what do you mean retry’s? Re-downloading the files into the USB or just removing and re-inserting it?

 

[Snakebitten]

13V

what do you mean retry’s? Re-downloading the files into the USB or just removing and re-inserting it?

Shutting truck down. Restarting it. Inserting USB.
Watching for recognition of USB, then indexing, then fingers crossed for "updating system". (Which you can click on with your finger and watch the file writing progress on Sync screen)

 

[Shoebox72069]

How long has everyone waited after inserting the USB drive into the port in the truck before it started updating automatically? I’ve waited 10 minutes and never got a message. I can see that the USB drive is detected though when inserting.

Which update is this? When I was all balled up on the failed OTA for 1.7.1 I had to drive around for a month before it ever picked up a USB drive. Everything else Ive been doing has been a few minutes.

IPC update would NOT go via USB and I had to go the CAN route which failed at the very end after all the blocks were updated.

I just got in from doing a GWY via USB that detected a USB after a few minutes.

Ironically at the end of the procedure it failed. It prompted me with two options (aside from exiting). First option I forgot what it called... did not work. Second one worked and it said it completed!

After that, there was... another APIM update waiting for me. Truck is currently snoozing/restarting.

I still need to sort through my IPC woes, which Ill probably clear/self test and see what happens.

 

[rpeterslll]

Which update is this? When I was all balled up on the failed OTA for 1.7.1 I had to drive around for a month before it ever picked up a USB drive. Everything else Ive been doing has been a few minutes.

IPC update would NOT go via USB and I had to go the CAN route which failed at the very end after all the blocks were updated.

I just got in from doing a GWY via USB that detected a USB after a few minutes.

Ironically at the end of the procedure it failed. It prompted me with two options (aside from exiting). First option I forgot what it called... did not work. Second one worked and it said it completed!

After that, there was... another APIM update waiting for me. Truck is currently snoozing/restarting.

I still need to sort through my IPC woes, which Ill probably clear/self test and see what happens.

I’m also stuck on a failed 1.7.1 and I’m running the APIM update offered by FDRS right now. Follow the steps on the screen to insert USB after building the files onto it and it’s not starting the updates.

 

[Shoebox72069]

I’m also stuck on a failed 1.7.1 and I’m running the APIM update offered by FDRS right now. Follow the steps on the screen to insert USB after building the files onto it and it’s not starting the updates.

Put the USB in and forget about it. Eventually it will find its marbles and see the stick.

Some folks got it sorted in a few days. Some a few weeks. Some over a month.

I was in the just over a month group.

Nobody has nailed down the magic fix for it... Seems to be totally random.

 

[christophers]

So... I've done APIM a few times and GWM now, but when trying to do CCM and PSCM, the entire truck shuts off except the sync screen, FDRS establishes comms, then it tells me that it can't communicate. After around 60seconds the truck will "come alive" again, but it won't work with any other modules now.

Known issue? I'm using Mongoose cable.

 

[Snakebitten]

So... I've done APIM a few times and GWM now, but when trying to do CCM and PSCM, the entire truck shuts off except the sync screen, FDRS establishes comms, then it tells me that it can't communicate. After around 60seconds the truck will "come alive" again, but it won't work with any other modules now.

Known issue? I'm using Mongoose cable.

Did you do the Mongoose test routines in the Mongoose software program?

And have you done a fresh FDRS session network scan to see if your CCM and PSCM are healthy?

 

[Jaug]

So I’ve hit a roadblock, and I’m posting this in case someone knows what is failing/ going on (or in case someone else too experiences this issue). Huge thank you to @Jesse-Infotainment for working on this with me over the last 2 days, but unfortunately the issue still persists. If someone mentioned this issue already, I apologize. My eyes are almost literally on fire as I read through the entire 2000+ posts on this thread over the last 2 nights while working in the NICU in between patient rounds, and didn’t see it mentioned.

When attempting to update the IPC or GWM module, FDRS attempts to download the update for about 30 seconds and then displays: GWM software update application ended with an error state. It does the same thing for the IPC. Also, if a PMI is attempted on either module, it does the same thing, ending in an error state after attempting to download. I have never been prompted to insert a usb drive, ever. Not sure if this is related to a GWM Ethernet problem. Currently on 2.3.0

My other modules updates mostly went through just fine without issue, except, like mentioned heavily earlier in the thread, some won’t clear from the list: GSM, PSCM, IPMA, etc. When I was updating IPMA the first time, it errored out about 80% of the way through. I reapplied the update again and it went through successfully the second time. Active driver assist (what keeps your wheel centered on the highway while cruising and lane assist on) does not work at this time. No other errors are popping up on the IPC.

No DTCs are present on any of the modules present, they are also green on FDRS and pass self tests flawlessly.

I am using a mongoose cable, drivers installed, and have no used any other devices. Forscan reset of the modules was also done, went off flawlessly without issue.

I am not good with reading advanced code, so I am not 100% sure if any of my AB is corrupted or if this issue is entirely on the FDRS side. My vin is 1FTFW1E11MFB18254.

I tried pulling the battery for about 7 hours (while I slept during the day for work tonight), didn’t change anything. FDRS was reinstalled. Large quantities of coffee consumed. My voltage holds relatively steady during updates. Internet connection reset.

Also pictured: when I try to shutdown my laptop, this error pops up related to FDRS. I will be trying a newer laptop later this weekend, but I stopped right here as I don’t want to screw things up by clicking on ? without asking other first.

Any help on this would be greatly appreciated.

The best advice is get a newer laptop as you mentioned you plan to do. I had this happen with my older laptop for the IPC and GWM and the best I could figure in my case was the newer faster laptop with a better wifi card in it was my issue. In fact, I don't recommend anyone doing updating without a mongoose (run the three tests), newer fast laptop, great wifi signal, and 13 plus volts holding strong. Anything less than this and you are asking for issues to develop. Then again issues seemed to happen even with this, just seems the best chances are meeting these things. I am not one of the experts here but everything went smooth for me after making sure to follow these steps.

Basically hold tight until you get the better laptop

 

[christophers]

i ran the test routines at the beginning of the evening (yeah, long day with all the modules on this baby haha). CCM and PSCM show healthy on network scan. i think there may be a mandatory order as SOBDM C took an update, and then pushed a bunch more through.

Sponsored