ECU module programming guide using FDRS

[RapidRedRick]

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 backup. If he does, he needs to load the default configuration back to the module via ForScan, then run a Network Scan in FDRS if he has the Mongoose-Plus device (DO NOT do it with VCX Nano) and then do the PMI.

If he has VCX Nano, do the PMI then restore original configuration with ForScan.

I have VCX Nano, when I go to Forscan to load my original backup file it says "Error opening file".

Sponsored

 

[jmm3807]

So like 4-5 hours from start to finish?

Yeah I’d go with 5 hours to be safe.
Drove the truck and came to scan it again.
Got an IPMA DTC so should I PMI it or run the update on IPMA like it’s asking?

 

[JEB]

Yeah I’d go with 5 hours to be safe.
Drove the truck and came to scan it again.
Got an IPMA DTC so should I PMI it or run the update on IPMA like it’s asking?

I’d start more simply first. Clear the DTC and see if it comes back. This is a communication error, not a configuration error. It might have been a one-time glitch.

 

[tonesto7]

So I finished… it all went successfully as far as I could tell. Ran network test on mongoose and the IPMA still says update along with the PSCM.
Instead I’m going to leave the truck off for 30 minutes, drive it. And see again later.

Mine is showing the same after completing the updates.

I will be doing a road test here in the next hour.

 

[RapidRedRick]

When I lost my power running boards I did a PMI on the DSM with no improvement until I did a self test after the PMI. This fixed it. You might try a self test on the DSM if you haven't.

Appreciate the tip. I ran the Self Test after the PMI. Running boards went in and out, seat and steering wheel moved and the results say it passed. Unfortunately the functions have not returned. Thx again!

 

[JEB]

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 backup. If he does, he needs to load the default configuration back to the module via ForScan, then run a Network Scan in FDRS if he has the Mongoose-Plus device (DO NOT do it with VCX Nano) and then do the PMI.

If he has VCX Nano, do the PMI then restore original configuration with ForScan.

I hear what you’re saying. But what if a network scan had just been performed subsequent to the module flash, followed almost immediately by the use of the FDRS [module] configuration command. Wouldn’t that pull down the very version of the as-built that the Nano just corrupted?

 

[jmm3807]

Did the clear and retest.
Then my PCSM went offline. Fixed that.
Reran network test

Updates still available for IPMA and PCSM. GSM always there anyway.

Read some blue cruise posts. Either the IPMA update didn’t take or bluecruise just isn’t activated yet. Something about under driver assistance + lane keep assist section, I should be seeing some new options and am not. Still plan on waiting to Jesse Infotainment chimes in and others that do this series of updates.

I’d start more simply first. Clear the DTC and see if it comes back. This is a communication error, not a configuration error. It might have been a one-time glitch.

 

[iceman77]

I hear what you’re saying. But what if a network scan had just been performed subsequent to the module flash, followed almost immediately by the use of the FDRS [module] configuration command. Wouldn’t that pull down the very version of the as-built that the Nano just corrupted?

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 misconfigured) data hence the best bet is to restore the ForScan backup taken prior changing the configuration (with ForScan). PMI in fact is not even needed here, especially if his module SW version is up to date. Just ForScan backup restore. That's it

 

[JEB]

Did the clear and retest.
Then my PCSM went offline. Fixed that.
Reran network test

Updates still available for IPMA and PCSM. GSM always there anyway.

If the errors are gone, I’d leave it alone and check again tomorrow.

 

[JEB]

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 misconfigured) data hence the best bet is to restore the ForScan backup taken prior changing the configuration (with ForScan). PMI in fact is not even needed here, especially if his module SW version is up to date. Just ForScan backup restore. That's it

Ok. That’s what I thought. I was focusing on how it happened for future avoidance. Less on the remedy, which entails finding an uncorrupted source for the as-built data. I think how it happened—running the FDRS configuration command right after the module update confirms that using FDRS’s configuration tool is very risky if using the Nano and should be avoided. Stick to the PMI as the initial course of action if you need it to complete the configuration post-update.

 

[iceman77]

Ok. That’s what I thought. I was focusing on how it happened for future avoidance. Less on the remedy, which entails finding an uncorrupted source for the as-built data. I think how it happened—running the FDRS configuration command right after the module update confirms that using FDRS’s configuration tool is very risky if using the Nano and should be avoided. Stick to the PMI as the initial course of action if you need it to complete the configuration post-update.

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 given module would be intact, or contain the same corruption that ForScan changes produced. Not by VCX Nano itself

 

[imnuts]

For those that have updated, there was a screenshot of a procedure for "enable BlueCruise" or something like that a week or two ago. It was in someone's list long enough to get a screenshot and then disappeared. Is there something like that back in the list that needs to be run to get BC working after the updates?

 

[jmm3807]

For those that have updated, there was a screenshot of a procedure for "enable BlueCruise" or something like that a week or two ago. It was in someone's list long enough to get a screenshot and then disappeared. Is there something like that back in the list that needs to be run to get BC working after the updates?

Saw that in a post too but not on my truck still after the updates. Currently just waiting it out.

 

[JEB]

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 given module would be intact, or contain the same corruption that ForScan changes produced. Not by VCX Nano itself

Well, that’s why I asked the question a couple of posts ago. Take this hypothetical. User has never, ever, run FORScan. User updates module X with the Nano, but for some reason, the update has a problem—something akin to a U2100 configuration error. Instead of running a PMI to complete the configuration, user executes the FDRS configuration command which attempts to grab the as-built data. This all happens so close in time that the truck has not had the opportunity to self-report. Wouldn’t the config command grab the as-built data that the Nano just corrupted? That is the question I asked previously.

 

[iceman77]

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>
<CODE>FFFF</CODE>
<CODE>FF1F</CODE>
</DATA>
</VEHICLE_DATA>
<BCE_MODULE>
<DATA LABEL="6F0-01-01">
<CODE>0100</CODE>
<CODE>0108</CODE>
<CODE>0103</CODE>
</DATA>
<DATA LABEL="6F0-01-02">
<CODE>001F</CODE>
<CODE>FF00</CODE>
<CODE>041B</CODE>
</DATA>
<DATA LABEL="6F0-01-03">
<CODE>B001</CODE>
<CODE>AB</CODE>
<CODE />
</DATA>
<BCE_MODULE>
<NODEID>
6F0
<F110>DS-MU5T-14D068-CB</F110>
<F111>MU5T-14G635-CB</F111>
<F113>ML3T-14D068-GG</F113>
<F124>MU5T-14G631-CB</F124>
<F188>MU5T-14G630-CB</F188>
<F18C>201008 00467</F18C>
</NODEID>
<NODEID>
6F2
<F110>DSML3T-14H031-AF</F110>
<F111>ML3T-14H099-AE</F111>
<F113>ML3T-14H031-DG</F113>
<F17F>1AE042ZL</F17F>
<F188>ML3T-14H094-DH</F188>
<F18C>2032303635R</F18C>
</NODEID>
</VEHICLE>
</AS_BUILT_DATA>

The BCE_MODULE section (marked green) is what represents the actual configuration data for given module. This section DOES NOT get corrupted by VCX Nano NetworkScan. The NODEID section (marked in red) is what contains the module information report (SW version, strategy, calibration level etc), this section is the one that gets corrupted during Network Scan when VCX Nano device is used and is only affected on Ford server side. When restoring configuration to your module as a result of a PMI or module SW update function, only the BCE_MODULE data get restored. The NODEID section has no effect. It servers no purpose for your truck, only for the "mothership" to announce what revisions are in your truck so Ford connected services (including future OTAs) are tailored to your trucks specific needs.


Hope this helps to explain things around VCX Nano corruption better

Sponsored