@DeltaDeuce and @jmm3807 how long after your APIM did it take to get the activation email? When I go to connected services on Ford online it says activation pending. Hopefully this just takes some time to run through the system.
Procedure Unsuccesful - InitializeCommsHardware Could not communicate with the VCM. This is most likely a data issue |
There are many who are experiencing the ABS, IPMA, GSM and PSCM still showing after successful updates. My suggestion is to reboot the GWM from FORScan and try that update again and see what happens.Good morning. I have 5 updates that won't go away Yesterday. ABS, IPMA, PSCM, GWM and GSM.
the last thing I went to do was the GWM that showed up after doing the long IPMA module.
When I try to run it, I get the below. Any thoughts what is causing that? Soon as its light, I will try this all again. Went at these for over 5 hrs with the Mongoose.
Procedure Unsuccesful - InitializeCommsHardware Could not communicate with the VCM. This is most likely a data issue
Will do. Will let yaz know.There are many who are experiencing the ABS, IPMA, GSM and PSCM still showing after successful updates. My suggestion is to reboot the GWM from FORScan and try that update again and see what happens.
It was almost instant.@DeltaDeuce and @jmm3807 how long after your APIM did it take to get the activation email? When I go to connected services on Ford online it says activation pending. Hopefully this just takes some time to run through the system.
I never did get one and it’s still pending activation on Ford online. But it worked this morning just fine. Another thing I noticed with these last updates is my camera in motion for the bed and hitch finally work. Also the side card bed view is there.It was almost instant.
For future reference, having a USB formatted with an MBR partition table does not seem to affect the likelihood of the initial APIM update kicking off immediately or not. The two USB's I've used are both MBR and neither caused an update to start. Cant say if using GPT would cause it though. That said, while testing this, and after a couple of weeks of keeping my second USB drive in and then moving back to the first USB, the truck has decided it will go ahead and take the update this morning.I wanted to add a note for others on this subject. A lesson learned from Sync 3 is that the partition table of the USB drive also matters. With Sync 3 the USB drive must have an MBR partition table not GPT. I assume Sync 4 operates the same way. It's possible someone could buy a recommended drive and still have updates fail if this is overlooked.