ECU module programming guide using FDRS

[JEB]

@tonesto7 and I worked on this most of the afternoon yesterday, I have updated to FDRS 31.6.4 and use a VCX Nano. As of this morning the following modules (there may be more) report corruption in my latest AsBuilt (xml showing as not properly formatted) and they are:

• BCM - PartNumber
• DDM - PartNumber
• RTM - PartNumber
• TCU - Calibration
• SODR - PartNumber

I will run another scan this morning and see if it works itself out. @iceman77 I pm'ed you my VIN and uploaded the latest AsBuilt in case I scan prior to you coming online.

Thoughts:

• If this doesn't clear up I'm thinking that FORScan may possibly help if a module change is done then 'write all', it's worth a shot.
• How fast do the changes propagate to the AsBuilt data on the Ford Servers when I do the above?

Adding @Jesse-Infotainment for his thoughts...

I spoke too soon. @iceman77 looked through my as-built data and saw some evidence of corruption there, too. Nothing serious, and he expects it eventually to self-correct, but it is there. Not known when the truck will check in with the Ford servers and upload it’s as-built data or what triggers it.

I also noticed that there is now a disclaimer on the FDRS log-in page: “FDRS users may experience difficulties with the Vehicle Identification process on vehicles equipped with Sync 4 at this time. The FDRS team is engaged in resolving the issue.” Not sure what this means or if it bears on the corruption issue we’re seeing.

Sponsored

 

[Bob_Mac]

I spoke too soon. @iceman77 looked through my as-built data and saw some evidence of corruption there, too. Nothing serious, and he expects it eventually to self-correct, but it is there. Not known when the truck will check in with the Ford servers and upload it’s as-built data or what triggers it.

A network scan in FDRS usually works and I will verify it this morning....

 

[JEB]

A network scan in FDRS usually works and I will verify it this morning....

Problem is that if @iceman77 is right about why the corruption is occurring—some issue as to how FDRS processes J2534 pass-thru scanning—a network scan is precisely what is causing the corruption. That’s why he altered his instructions to use the cloud data accessed from a manual VIN input instead of a network scan to ID the vehicle at the start of an FDRS session and perform software updates.

 

[Bob_Mac]

Problem is that if @iceman77 is right about why the corruption is occurring—some issue as to how FDRS processes J2534 pass-thru scanning—a network scan is precisely what is causing the corruption. That’s why he altered his instructions to use the cloud data accessed from a manual VIN input instead of a network scan to ID the vehicle at the start of an FDRS session and perform software updates.

That's when you initiate the first session in FDRS, subsequent connections you just click go on your profile that was created and if having issues then do a scan as outlined in his instructions here

 

[JEB]

That's when you initiate the first session in FDRS, subsequent connections you just click go on your profile that was created and if having issues then do a scan as outlined in his instructions here

We’re referring to the same thing. As I read it, that four-step procedure is not a network scan. It’s just using the VIN to download the current data from the Ford server and using that data to identify what’s out of date instead of reading the data directly from the truck and uploading it for comparison. In any event, the procedure you’ve identified is the procedure I started using and the corruption persists.

 

[Bob_Mac]

We’re referring to the same thing. As I read it, that four-step procedure is not a network scan. It’s just using the VIN to download the current data from the Ford server and using that data to identify what’s out of date instead of reading the data directly from the truck and uploading it for comparison. In any event, the procedure you’ve identified is the procedure I started using and the corruption persists.

I'm going to test my theory this morning and see if that does do anything. As for @tonesto7 I don't believe he's using the VCX Nano and said his completely cleared up so as a test I just d/l'ed his current AsBuilt as of this morning and his is still good so...

 

[tonesto7]

I'm going to test my theory this morning and see if that does do anything. As for @tonesto7 I don't believe he's using the VCX Nano and said his completely cleared up so as a test I just d/l'ed his current AsBuilt as of this morning and his is still good so...

It's not cleared up in FRDS

My APIM showed Software PN corrupted again this morning

For me, it's only my APIM data that's screwed up.

 

[Bob_Mac]

It's not cleared up in FRDS

My APIM showed Software PN corrupted again this morning

Did you check your AsBuilt? I'm looking at it now and it shows good (MU5T-14G670-PZA).

 

[tonesto7]

Did you check your AsBuilt?

 

[JEB]

I'm going to test my theory this morning and see if that does do anything. As for @tonesto7 I don't believe he's using the VCX Nano and said his completely cleared up so as a test I just d/l'ed his current AsBuilt as of this morning and his is still good so...

Yeah, it isn’t clear whether the VCX Nano is the problem or the J2534 protocol in general. @iceman77 is going to try the Mongoose—another, substantially more expensive, J2534 device—and then we should know for sure.

Please post your results. A network scan after initiating a session didn’t work for me to clear up all the corruptions. But my corruption issues weren’t with the GWM reporting an invalid software version which knocked out some of the connected services.

 

[Bob_Mac]

It's not cleared up in FRDS

My APIM showed Software PN corrupted again this morning

For me, it's only my APIM data that's screwed up.

You're not using the VCX Nano correct?

 

[tonesto7]

You're not using the VCX Nano correct?

Correct i'm using the UCDS v4 adapter.

 

[JEB]

Keep checking. The APIM is an anomaly. When I check the cloud data in FDRS, the software version disappears and reappears multiple times throughout the day. Might have something to do with the disclaimer I quoted above on the FDRS log-in page.

 

[Bob_Mac]

This is screwed up, I'm looking at your AsBuilt I downloaded less than 30mins ago and the part number for the APIM (7D0) is different then what you're posting! WTF?

 

[Bob_Mac]

Correct i'm using the UCDS v4 adapter.

What does FORScan show?

Sponsored