ECU module programming guide using FDRS

[JEB]

Agreed, you make good points. Question, has anyone with corruption using a nano or other alternatively gotten access to a VCM2/3 and re-did a network scan? Did it correct the corruption issue?

Yes, with the Nano. Corruption remained. I thought the rescan fixed things when I saw that the FDRS summary screen came out clean, but @iceman77 dug deeper into the code and found other corruptions. @Bob_Mac rescanned with a Mongoose and also had corruptions. @Jesse-Infotainment always used a VCM3, which doesn’t use J2534, and never had corruptions. I don’t know of anyone who got corruptions with a Nano and subsequently fixed them with a rescan using a VCM2 or 3. But I think it would work because it would read the local data, which is uncompromised, and then reload it to the server.

Sponsored

 

[Fordphanatic]

I will let you know as soon as my vcm3 finally shows up. Its on a tour with fed ex.

 

[abd79]

https://www.amazon.com/dp/B097NHQ7ZW?psc=1&ref=ppx_yo2_dt_b_product_details

Is there any difference in the Mongoose-Plus vs the Pro Ford? Ford does call out the Mongoose adaptor as supported however I don’t see the Mongoose-Plus on the DrewTech site, I only see the MongoosePro Ford. These are the adaptors listed on Fords site as supported.

https://www.motorcraftservice.com/Diagnostic/FJDSSupport?categoryId=247

 

[antho]

Yeah, Looking at the ASCII and hex, that one space throws it all off by placing a 20 in the HEX.

CORRUPT

ASCII = ML3 T-14H099-AF

HEX = 4D 4C 33 20 54 2D 31 34 48 30 39 39 2D 41 46

CORRECT

ASCII = ML3T-14H099-AF

HEX = 4D 4C 33 54 2D 31 34 48 30 39 39 2D 41 46

 

[JEB]

Is there any difference in the Mongoose-Plus vs the Pro Ford? Ford does call out the Mongoose adaptor as supported however I don’t see the Mongoose-Plus on the DrewTech site, I only see the MongoosePro Ford. These are the adaptors listed on Fords site as supported.

https://www.motorcraftservice.com/Diagnostic/FJDSSupport?categoryId=247

Mongoose Pro is no longer in production. It was replaced by the Mongoose Plus. Drew Tech was acquired by Opus. The Plus is on Opus’s website. https://www.opusivs.com/products/j2534-pass-thru/mongooseplus?hsLang=en

 

[JEB]

Yeah, Looking at the ASCII and hex, that one space throws it all off by placing a 20 in the HEX.

CORRUPT

ASCII = ML3 T-14H099-AF

HEX = 4D 4C 33 20 54 2D 31 34 48 30 39 39 2D 41 46

CORRECT

ASCII = ML3T-14H099-AF

HEX = 4D 4C 33 54 2D 31 34 48 30 39 39 2D 41 46

You coders scare me.

 

[TJSparky]

Just wanted to chime in on the suspected corruption of Software P/N in FDRS. I can say without a doubt it is not adaptor related. I have tested this now 12 times in the following manner;

1. No adaptor connected to the computer
2. I Deleted the vehicle profile in FDRS and restarted FDRS
3. I Re-entered VIN number and downloaded vehicle information from Ford
4. Every time I do this the part number for the APIM changes, It is always one of the following for me;
- "ML3T-"
- "FFF1-14D358-FF"
- "MU5 T-14G676-EJ"

So I believe we are chasing ghosts here and the problem is actually either FDRS or on Fords Servers not the VX or other adaptors.

So are you saying that "FFF1-14D358-FF" is a corrupt APIM. That is what I show for mine and everything has been updated to the latest info and no additional updates available. Shows Sync 21281 Rev 244
F-150 2021, Feb '21 build date, XLT 302A, 5.0L, 8" Cluster, Sync4 12" Screen

 

[antho]

You coders scare me.

Definitley not a coder! lol Buy yes, Coders scare me too!

 

[abd79]

So are you saying that "FFF1-14D358-FF" is a corrupt APIM. That is what I show for mine and everything has been updated to the latest info and no additional updates available. Shows Sync 21281 Rev 244
F-150 2021, Feb '21 build date, XLT 302A, 5.0L, 8" Cluster, Sync4 12" Screen

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 knows.

I’m trying to setup my Wireshark to capture the usb traffic on a network scan to help see if it shows anything.

 

[JEB]

So are you saying that "FFF1-14D358-FF" is a corrupt APIM. That is what I show for mine and everything has been updated to the latest info and no additional updates available. Shows Sync 21281 Rev 244
F-150 2021, Feb '21 build date, XLT 302A, 5.0L, 8" Cluster, Sync4 12" Screen

NO! Your APIM is not corrupted. The APIM is fine. The back up programming data stored on the Ford Website is corrupted.

 

[TJSparky]

OK! I haven't been doing network scans since my last updates. Just been seeing what comes down from Ford's servers first.

 

[abd79]

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.

 

[TJSparky]

FYI my Sync is at 22028 rev 358. Was the last update I did last night.

Whoa! That is a new one! Does anyone have any additional info on what 22028 Rev 358 is? I thought 21281 rev 244 (OTA 2.3) was the latest.

 

[Bob_Mac]

Yeah, Looking at the ASCII and hex, that one space throws it all off by placing a 20 in the HEX.

CORRUPT

ASCII = ML3 T-14H099-AF

HEX = 4D 4C 33 20 54 2D 31 34 48 30 39 39 2D 41 46

CORRECT

ASCII = ML3T-14H099-AF

HEX = 4D 4C 33 54 2D 31 34 48 30 39 39 2D 41 46

The 20 is a HEX value for a space so yes, this complicates it.

 

[Bob_Mac]

Whoa! That is a new one! Does anyone have any additional info on what 22028 Rev 358 is? I thought 21281 rev 244 (OTA 2.3) was the latest.

No, the latest is 22028 Rev 358 which is what mine updated to this morning.

Sponsored