Search results

Check the post above. Both of your modules seems to be updated correctly with all revision info correctly posted to your AB data. I think you are really in good shape and this is a bug on FDRS (server) side. If it's not fixed soon, you should still receive the latest missing piece, a GWM update...

I managed to further track down your PSCM update which as per Ford is labeled as "Blue Cruise capability Coordinated SA for ADAS, PSCM, CCM and DSMC" <NODEID> 730 <F10A>ML34-14D007-BDH</F10A> <= ECU_CONFIGURATION (MATCHES WITH FORD) <F110>DSML34-3F964-AC</F110>...

I assume you ran Network Scan recently as I see few corruption in your As-Built data set, but your IPMA and PSCM information seems to be consistent. I can see the ford servers indicating IPMA and PSCM SW module updates, but no actual update files are listed. Hence when you try to update again...

PM me your VIN, I will take a look inside the "mothership" :)

What VCI have you used ? Mongoose or the Nano ?

Time to "hack" the motheship! :D

For better understanding here's an example of a formatted As-Built dataset downloaded from the Ford Server: <?xml version="1.0" encoding="UTF-8"?> <AS_BUILT_DATA> <VEHICLE> <VIN>1FTFW1E85MFAXXXXX</VIN> <VEHICLE_DATA> <DATA LABEL=""> <CODE>3AE8</CODE>...

Again, I am yet to see an evidence that VCX Nano corrupts the actual configuration data in As-Built data set. If he has some corruption, it is likely a result of "human error" when applying ForScan changes. So, assuming he has VCX Nano device and he ran Network Scan, his configuration data for...

Yes it would. Each module SW update thread runs "module configuration" which basically restores the "latest known" configuration to the module. Either is the one retrieved by Network Scan or the one retrieved from the cloud. The thing is, both of the sources might already have his corrupted (or...

VCX Nano will not corrupt your configuration data in As-Built, only the "NODE" data that contain the report from the recent Network Scan (if performed) in FDRS. He should have definitely not load configuration data into the module (if changed in ForScan) prior to PMI. Hope he has a configuration...

You can safely do these with the Nano, just DO NOT perform Network Scan in FDRS. Follow steps documented here and you will be fine!

FYI - new FDRS has been released:

NOTICE: I have updated the guide to reflect the changes to the preferred VCI device being the Mongoose-Plus as well as well as posted warning not to perform Network Scan if you decide to stick with the VCX Nano device I apologize for the delay, I have promised to update the guide a week ago...

Where did you get the media bin light ? Everywhere I asked, this part is back ordered

Excellent writeup @JEB! I will be updating the guide this weekend and will include your post above, as this is yet the best description of tools of choice

As long as you are "online" and connected to Ford servers, the tool will download the freshest version of your vehicle data. The progress bar duration should not deceive you

Yes it will!

I will check your AB data in cloud tomorrow morning and let you know!

Any noticeable changes in Sync ? Did they fix the ACC SSR ? How is CarPlay screen look like ? I had a full list of bugs reported to them.

Yes I am sure! At least my old Job 1 truck did it. It took 2-3 days though.