Search results

@icemann77 saw those values outside of the Ford Pass widget too. He said AB data looks good but isn’t sure what those values are or why they’re the way they are. Some day we’ll figure out when these trucks do a scan and report by themselves to the mother ship but for now I guess we wait.

Sorry, yes I ran all the diagnostics with the same result.

Nice! Thanks for having a look., much appreciated.

I have the same 3 marked as “Other” with the same values as you do. I used a Mongoose to update my modules so not sure what these mean or if they’re corrupted. I’ve tried multiple network scans and ope/close FDRS with no change.

Yes, mine is a power boost.

I did mine yesterday without issue and you should have my VIN also already.

I’ve done all the updates and those 4 modules (ABS, GSM, IPMA and PSCM) won’t clear for me either. This is what I have for IPMA and PSCM. I also have 3 odd balls in the IPMA.

These look odd in my AB information. This is for the IPMA. PSCM looks normal.

Same for me, unsing a Mongoose here.

Looks like FDRS 31.6.5 was also released today. Other than a mention of EVAP check now be supported on hybrid vehicles not sure if there was anything else fixed.

Is it just the GSM and ABS modules that won’t update and be removed from the list in FDRS? Those are the 2 for me that just won’t go and I’m wondering if it’s normal or is there a specific procedure to do to get them to update?

This could just be the difference in the GWM software level. Mine is up to date as of yesterday, yours seems to be a bit behind.

Maybe I’m running a different version of the FordPass widget but my GWM does not look like that.

PM’d you

VCM2 will work just fine, is supported by FDRS and shouldn’t have any corruption. VCM3 is newer than the VCM2 and is said to be able to flash modules over CAN faster than the VCM2.

I’ve fired off support messages to both the hardware and software vendors. I’ll see what they come back with if anything and PM you.

If you don't mind could you check this one as well?

For the smarter guys in here, I was able to pull logs from the nano itself, wireshark works as well but includes all the USB overhead so I'm trying to filter it out and see if there is anything of use. I'm suspecting that the problem maybe timeouts/buffering in the nano that needs to be tweaked...

2nd the “Not Corrupt” message. Software sucks! I diagnose it everyday, Communications is 4 times as bad! FYI my Sync is at 22028 rev 358. Was the last update I did last night.

Not saying anything other than even when you don’t do a network scan and are completely disconnected the FDRS program is showing different PN’s for at least the APIM. I’m not sending them anything when this happens. Could be a result of a corrupted PN being sent to Ford from a bad scan who...