I did the update in February when it first came out. If someone doesn't mind checking my VIN to see if a second TRM module update is waiting I'd appreciate it.
1FTFW1E85MFA49677
So if we apply the update via FDRS would that clear the recall notice? Does the dealership do something on another system that shows the recall was fixed?
What I'm getting at is I don't mind applying the fix via FDRS myself, but don't want the dealer being stupid the next time I take it in for...
It's not your laptop. I have a brand new top of the line HP and it wrote just as slow as my old laptop I replaced. I'm not sure what FDRS uses to write to a USB but apparently its still in the stone ages.
I saved all my modules from way back before I started any updates, so I'll go ahead and save them all again so I'm current of sorts. Appreciate the the info!
@Jesse-Infotainment this is probably a stupid question but should those of us who've done these massive amounts of update be refreshing (redownloading) our as-built information from Forscan? I don't truly understand how the as-builts get updated (or do they) but I feel like something needs to...
@Administrator Any chance there will be a membership or some kind of payment to get an add free viewing experience? I'll gladly support this site from all the help it's provided me and no ads would be a bonus.
it should match, but it doesn't on mine at least. In the truck it still has the place holder of 10/something/2022 but on the Ford website it reflects the full year with a date of 3/13/2023.
It does ping pong a bit coming out of a curve but overall I think it does a good job. I did a trip to Dallas and back and used BC extensively during the trip. Probably 400 miles were done via Bluecruise.
Yes I did.
I got my 1.7.1 unstuck a few months ago, but before that the OTA status showed the failed 1.7.1 update. About a week later after I got over the hump Ford tried to push OTA 2.3 to my truck but it failed because of a bad battery. My OTA status to this day still reflects the failed...