Well, another head scratcher, after getting that error, the IPMA update went away and now FDRS is showing all modules up to date?Any idea what is causing this error? Initially I was getting an error that said the module could not be configured, then after attempting to refresh the download, I got an error on that. so I tried just running the SW update again and got this error
![]()
It’s painfully slow. 1hr to download files (I have blazing internet, FDRS server is slow), 1.5 hours to copy to thumb drive, 1.0 hours to update.how long did it take for you guys to do the 6gb apim update to go from 3.5.2 to 3.5.3? wanna know before i give up use of the truck for the day.
This is usually an indication that a file failed to load and now FDRS doesn’t recognize the state of your system. Can you post the part numbers that show up when you highlight the IPMA?Well, another head scratcher, after getting that error, the IPMA update went away and now FDRS is showing all modules up to date?
this has been moved to a new thread. Try asking there.Anyone mind sharing if I have anything available?
1FTFW1ED0MFB66211
While it's writing the USB, there's no harm in having the truck running.Well I’m in the middle of updates right now, so far it has been easy and smooth. PCM, BCM, and ABS were all quick and easy, probably took 10-15 mins for those 3. Currently working on APIM updates, this is a big one. Been downloading up copying to USB for about an hour now and still have 3.5 GB to copy to USB. I assume IPMA will be the longest update. (Only had 5 modules to update).
I got a low battery warning at 12v and 60% charge (recommended min is 10v and 80%) so I turned up the maintainer to a 10A charge (from 2A). Is that an appropriate setting? According to the user manual the 2A is for smaller batteries andbigger batteries can use bigger settings. I would hate to screw something up or catch something on fire
It's also possible that FDRS went down for maintenance (which happens every Sunday) while you were attempting this update. I would avoid doing any FDRS stuff on Sunday, personally.Any idea what is causing this error? Initially I was getting an error that said the module could not be configured, then after attempting to refresh the download, I got an error on that. so I tried just running the SW update again and got this error
![]()
I'm not entirely certain what you're looking for but here's some infoThis is usually an indication that a file failed to load and now FDRS doesn’t recognize the state of your system. Can you post the part numbers that show up when you highlight the IPMA?
Ah I didn't even consider that... I hate that I am now going to lose a whole day with the license. I also have to update my wife's explorer which has 14 updates. I guess it's pretty likely I won't get those done with one licenseIt's also possible that FDRS went down for maintenance (which happens every Sunday) while you were attempting this update. I would avoid doing any FDRS stuff on Sunday, personally.
It's usually only a half day. I can't get in right now to look at my IPMA and compare it to yours, so likely it could just be the server maintenance. Try again after lunch.Ah I didn't even consider that... I hate that I am now going to lose a whole day with the license. I also have to update my wife's explorer which has 14 updates. I guess it's pretty likely I won't get those done with one license
I just now logged on fine, unless I got in right before they shut it down. I guess this gives me time to get the rest of my day going and I’ll come back to the other updates laterIt's usually only a half day. I can't get in right now to look at my IPMA and compare it to yours, so likely it could just be the server maintenance. Try again after lunch.