ECU module programming guide using FDRS

[JEB]

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

Yes, this helps. Sounds like the dataset has split purposes—part of it is for module restoration, part of it is for reporting/administrative purposes. The same part of the dataset is not used for both purposes and the Nano corrupts only the administrative portion. I understand now. Thanks.

Certainly makes makes the dataset safer to use but really adds to the overhead.

Sponsored

 

[TJSparky]

So what should you do if you ran IPMA and PSCM and everything seemed to run fine (after 5 hours) but haven’t cleared from FDRS? Don’t really want to do Network Scan/Test. Just drive it and check again later? Or is this something that will stay populated like the GSM module update in FDRS

 

[JEB]

So what should you do if you ran IPMA and PSCM and everything seemed to run fine (after 5 hours) but haven’t cleared from FDRS? Don’t really want to do Network Scan/Test. Just drive it and check again later? Or is this something that will stay populated like the GSM module update in FDRS

Check for DTCs and clear them. If they don’t return, leave it alone and check again later to see if the updates are removed from FDRS. That’s all I’d do right now until more is known about these updates.

 

[jmm3807]

Alrighty so I’m in AZ where the major freeways are definitely mapped for blue cruise. Drove the truck and used cruise. Dash said bluecruise enabled be prepared to take control. However it didn’t go full bluecruise just normal so I think I’ve still got some waiting. Like the truck knows it has it but maybe Ford hasn’t enabled?

 

[TJSparky]

Check for DTCs and clear them. If they don’t return, leave it alone and check again later to see if the updates are removed from FDRS. That’s all I’d do right now until more is known about these updates.

I don't show any DTC's and don't really want to run a scan with the VX Nano. However, the PSCM and the IPMA still show as available to Run like GSM. These still show when logging into FDRS without the VX Nano connected.

I'm not going to update it again. Just going to leave it alone and if things change in FDRS.

 

[JEB]

Alrighty so I’m in AZ where the major freeways are definitely mapped for blue cruise. Drove the truck and used cruise. Dash said bluecruise enabled be prepared to take control. However it didn’t go full bluecruise just normal so I think I’ve still got some waiting. Like the truck knows it has it but maybe Ford hasn’t enabled?

Makes sense. You probably aren’t supposed to have BC yet because you weren’t in the first wave scheduled to get 2.5.1. You stole it by updating it yourself—something Ford probably didn’t plan for. But Ford still needs to flip a switch on their side to activate you. It’s like other connected services. You might have all the necessary hardware and software but it still doesn’t work because you need to subscribe before they turn it on.

 

[JEB]

I don't show any DTC's and don't really want to run a scan with the VX Nano. However, the PSCM and the IPMA still show as available to Run like GSM. These still show when logging into FDRS without the VX Nano connected.

I'm not going to update it again. Just going to leave it alone and if things change in FDRS.

I’d stop and wait for more developments.

 

[imnuts]

Almost sounds like FDRS let's you get to the equivalent of PowerUp 2.5.1, and you need to get to 2.5.2 for full BlueCruise functionality. Maybe in a few days it'll be available?

 

[tonesto7]

This is such a stupid rollout stagegy.
I tested mine and the BlueCruise On box showed up in the IPC, but not hands-free!
We still require the final update for GWM which is Power-Up 2.5.2 that must tell the cloud that we are authorized and activate the feature.

 

[DW2020]

We still require the final update for GWM which is Power-Up 2.5.2 that must tell the cloud that we are authorized and activate the feature.

I agree, looks to me like what is available in FDRS today are the modules that updated with 2.5.1. I'm thinking of ignoring the DTC in the IMPA that cropped up - it relates to network communication with the GWM....and knowing a GWM update (should) show up in FDRS later.

 

[speedracercjr]

I finally have time to run the updates on CCM, CMR, IPMA, & PSCM but reading through yalls comments I wonder if I should just wait a little longer or push ahead? Decide my fate!

On another note I'm on Sync 22028, Revision 358. I've said it before but I'll say it again, thanks to everyone in this thread for helping me out. It was just a month ago I was stuck on OTA 1.7.1!

 

[Kanuck]

Hi.... would someone be able to run my VIN and see what updates I need. I received 2.3.0 on March 1st. 1FTFX1E81MKE01710

Thank you in advance

 

[speedracercjr]

Hi.... would someone be able to run my VIN and see what updates I need. I received 2.3.0 on March 1st. 1FTFX1E81MKE01710

Thank you in advance

You got alot!

 

[Kanuck]

You got alot!

Thanks...I do have a lot...

 

[RapidRedRick]

Yes, this helps. Sounds like the dataset has split purposes—part of it is for module restoration, part of it is for reporting/administrative purposes. The same part of the dataset is not used for both purposes and the Nano corrupts only the administrative portion. I understand now. Thanks.

Certainly makes makes the dataset safer to use but really adds to the overhead.

Sponsored