Search results

to add, make sure you get a usb 3.0 stick. the process is much faster from laptop > USB and USB > truck if your flash drive is a modern one

Honestly? I only have it because this is what was on the lot, and it was not over MSRP. BlueCruise seems to be a nifty feature, but it's not reliable enough for me use it. It doesn't center in the lane even close to what it used to before BC was enabled. It asks me to keep my eyes on the road...

yeah, that is honestly why i went down this path. i dont really care about BC, i just wanted the alarm to stop going off.

yeah, this is (to me) the scariest outcome of all this: disrupting a data store or application that can't just be dropped back on via FDRS.

Some moderately unrelated items: - the freezing when using the bed and tailgate cameras in motion, i've not been able to reproduce the freezing when switching between the two. i've really been trying! haha - all of the updates seems to fix the issue with the "trailer disconnected" alarm...

i use a different laptop so no screenshot, but here's what you got: PCM CCM CMR IPMA PSCM GSM BECM IPC

are you leaving the laptop connected and in the update mode while it does this? FDRS will ask "was the update completed?" but don't click yes until the truck says complete. once that happens, FDRS will have you turn the truck off, on, and then validate the modules, then send the data to Ford...

all i see is your GWM update as well. however, once updated, other updates will likely show up

Honestly, I wouldn't attempt anything with a Nano at this point.

My anti-dazzle lights were done in ForScan several weeks ago, and I did pre-1.7.1 all the way to BC with no issues. EDIT: just because i didnt have issues doesn't mean you should follow my example :) take the time to do things the right, safe way and you will have minimal to no issues.

i dont know that we have that answer yet. but one day, you'll either 1) get an update notification, or 2) see someone else here that is getting OTAs, so we will have the answer soon enough :)

this is the key. i had zero issues and i followed the "slow and steady" process. i'll also note i had lots of forscan changes that i didn't re-apply via backups (nor did i even re-apply them manually) and i think everything stayed (adaptive headlights, bambi mode, seat belt minders, and a few...

I'll add in a bit of info on the 1.7.1 TSB that just came out. there were a few of us that waited nearly a full month (i was 30 days exactly) from putting the APIM USB in the console and having it actually kick off the update. my guess what some are going to do is, instead of wait one month...

i wouldn't disconnect the truck. once you start an update, you gotta commit to it, even with the USB updates. a lot of times it will end up OK, but you really want it to validate the updated software and do any additional programming, ESPECIALLY with the GWM.....

it will scan the truck and get the new module. was this an APIM update?

awesome! glad it worked :)

There were paid licenses way more than a year ago. That being said, I thought that the 2 month license was gated by machine GUID or equivalent. Good to know that it's not gated that way.

mine took 30 days exactly then started. USB was in the truck the entire time. it will work.. eventually haha

100% agree. i know a few ways to get around it, but working to avoid sanctions knowing that money will end up in the hands of those sanctioned is a US federal crime :/ that being said, a cursory reading of OFAC rulings and sanctions shows that it's like swiss cheese and rather easy to navigate...

https://forscan.org/faq.html#qlic1 "FORScan for Windows is distributed under Standard License that has no configuration and programming functions, as well as some service functions. These functions become available after installing Extended License."