Lightning Software Updates using FDRS

[ditkafan1985]

This might be a dumb question... I tried looking through the thread and didn't see this really discussed before. What are the less risky modules to update? (i avoiding using the word least due to risk being so relative here). Trying to gauge where to start this weekend once the cable and powersupply arrive.

Sponsored

 

[rugedraw]

This might be a dumb question... I tried looking through the thread and didn't see this really discussed before. What are the less risky modules to update? (i avoiding using the word least due to risk being so relative here). Trying to gauge where to start this weekend once the cable and powersupply arrive.

GWM, APIM and TCU first.

 

[ChrisCon]

. Thank you. Hoping the Costco HP suffices. Not interested in paying Alienware money to do updates!

The best part is that FDRS runs no better on a high end laptop or a budget . I bought this laptop mainly because I use obscure design software for landscape architecture that runs best on a native PC and now I can do some work from home at night.

On another note, the SOBDMA update cleared this morning in FDRS

 

[Magendi]

So I finished all my updates this morning and afterwards found that saved charging locations isn’t working. It shows no prior locations and when I took a drive and came back it is showing my home location as a new charging location that I can save but it doesn’t allow me to name it home because there is already a home saved location but it isn’t showing up or working (the prior charge limit not working). Is there any way to fix that? I searched and found some old threads with similar issues but no clear way to fix. Do I need to disconnect negative terminal to reset? Hoping for a less invasive fix. Thanks!

 

[TaxmanHog]

So I finished all my updates this morning and afterwards found that saved charging locations isn’t working. It shows no prior locations and when I took a drive and came back it is showing my home location as a new charging location that I can save but it doesn’t allow me to name it home because there is already a home saved location but it isn’t showing up or working (the prior charge limit not working). Is there any way to fix that? I searched and found some old threads with similar issues but no clear way to fix. Do I need to disconnect negative terminal to reset? Hoping for a less invasive fix. Thanks!

Check your Ford Pass, delete any old locations listed, then try saving the current configuration, if the ghost entry persists, use another name "home2" to get around the holdup.

 

[Magendi]

Check your Ford Pass, delete any old locations listed, then try saving the current configuration, if the ghost entry persists, use another name "home2" to get around the holdup.

Great, thanks. I tried deleting all the old charges in the charge log since there were no other locations listed in the saved charges and it did allow me to name the new location as Home. Here’s hoping.

 

[ditkafan1985]

anyone else having issues logging into FDRS?

 

[ditkafan1985]

anyone else having issues logging into FDRS?

hmmm.. uninstalled and re-installed and that seemed to fix the issue.

 

[rugedraw]

hmmm.. uninstalled and re-installed and that seemed to fix the issue.

Closing FDRS and re-opening it will fix many issues you may come across, too.

 

[ditkafan1985]

Closing FDRS and re-opening it will fix many issues you may come across, too.

That’s actually where i started at, but it didn’t fix it… which is why i went to the reinstall. Been at this for a few hours so far. The power supply i got has been rock solid in the 14.2-14.4 range

 

[ditkafan1985]

Is it common to have occasional crashes of FDRS? I have had 2 so far while using the software. Luckily it doesn’t seem to have caused any issues to any modules. I just restarted the software updates once i reopened fdrs and all was good.

 

[rugedraw]

Is it common to have occasional crashes of FDRS? I have had 2 so far while using the software. Luckily it doesn’t seem to have caused any issues to any modules. I just restarted the software updates once i reopened fdrs and all was good.

I would not say it is common, but it can happen and can be a PITA if it happens in the middle of the writing process.

 

[ditkafan1985]

I would not say it is common, but it can happen and can be a PITA if it happens in the middle of the writing process.

It happened for me when installing the GWM update. I think it finished but it keeps popping up an error. I posted it about it here - https://www.f150lightningforum.com/...programming-guide-using-fdrs.8249/post-385427

 

[sstevetx]

I had a handful of updates including PCM, ABS, SOBDMB, SOBDMC, SOBDM, BECM, GFM2, FHCM and HVAC. I installed them all successfully starting with the PCM which kicked off a number of chained updates. After all the updates, I had some errors for the SOBDM and SOBDMC which wouldn't clear. They mentioned losing connectivity. I tried a PMI on both, but the errors remained. I also had an error for the frunk which I think might be due to me removing the frunk beeper a while back. The FHCM error was about a short. That FHCM update might have allowed it to see if was removed. I'll take it for a drive to see if those SOBDM related ones clear. I'm also going to remove the black wire on the speaker inside that frunk beeper module and reinstall. I'll see if that removes the error.

 

[rugedraw]

I had a handful of updates including PCM, ABS, SOBDMC, BECM, SOBDM, SOBDMB, FHCM and HVAC. I installed them all successfully starting with the PCM which kicked off a number of chained updates. After all the updates, I had some errors for the SOBDMA and SOBDM which wouldn't clear. They mentioned losing connectivity. I tried a PMI on both, but the errors remained. I also had an error for the frunk which I think might be due to me removing the frunk beeper a while back. The FHCM error was about a short. That FHCM update might have allowed it to see if was removed. I'll take it for a drive to see if those SOBDM related ones clear. I'm also going to remove the black wire on the speaker inside that frunk beeper module and reinstall. I'll see if that removes the error.

Over on the Mach E forums, it is being advised to not do the drivetrain updates now due to some issues. I was under the impression this was an Mach E thing only. Maybe @Mike G can chime in if he knows anything about this.

Sponsored