ECU module programming guide using FDRS

[BHunted1]

So does that mean my gwm is still behind?

Sponsored

 

[JEB]

NOTICE: If you happen to lose certain "connected" functionalities (such as Horn & Light, SecuriAlert and OTA) after playing around with FDRS, here is how you fix it:

1) Connect your VCX Nano to your computer and your truck.

2) Open FDRS, and run a Network Scan. (Contrary to the above post, in this case this is a necessary step)

Once done, make sure your GWM module is showing a valid Software P/N (the field should not contain any spaces or special characters). Should be ML3T-14H021-XXX. See example below:

This usually fixes the SecuriAlert and Horn&Ligths issue. If not, restart FDRS (this step is important) and run another network scan. Repeat this until GWM Software P/N is shown in proper format

Perfect!

Does post 283 completely obviate post 282? 283 tells me that if you update a module, exit FDRS, renter FDRS and then run another network scan, FDRS should be able to report accurately what still needs to be updated. Is that right?

Come to think, that might not be right for all modules because it didn't work the last time I updated my APIM. I saw that second false APIM update two days later after exiting and reentering FDRS and doing a new network scan.

 

[iceman77]

Perfect!

Does post 283 completely obviate post 282? 283 tells me that if you update a module, exit FDRS, renter FDRS and then run another network scan, FDRS should be able to report accurately what still needs to be updated. Is that right?

Well, I have never really managed to pull a network scan with J2534 interface where all node fields in my AB are correct and not "mangled" up. From what I have noticed, only GWM is what matters, as it allows your truck to communicate with the mothership. So post #283 only instructs how to fix the GWM (if affected) and have the truck talking with Ford servers properly. All the rest gets corrected once truck runs its own version of network scan. Hope this explains it

 

[Airborne_Ape]

Thanks for the great writeup and for posting important notices throughout this thread. I finally bit the bullet ordered a VCX Nano, I've been on the fence about getting one for years. As an FYI for anyone outside the United States, it's less expensive to buy through Amazon (US) than Amazon for your region. On the Canadian site they start around $250 CAD, on the USA site it's $177 CAD including tax and export fees. The only downside is that global trade routes are still a nightmare and expedited air delivery times via UPS (with Prime) is 3 weeks

 

[Airborne_Ape]

NOTICE: If you happen to lose certain "connected" functionalities (such as Horn & Light, SecuriAlert and OTA) after playing around with FDRS, here is how you fix it:

1) Connect your VCX Nano to your computer and your truck.

2) Open FDRS, and run a Network Scan. (Contrary to the above post, in this case this is a necessary step)

Once done, make sure your GWM module is showing a valid Software P/N (the field should not contain any spaces or special characters). Should be ML3T-14H021-XXX. See example below:

This usually fixes the SecuriAlert and Horn&Ligths issue. If not, restart FDRS (this step is important) and run another network scan. Repeat this until GWM Software P/N is shown in proper format

Have you ever seen this field fail to populate after multiple retries?

 

[JEB]

Well, I have never really managed to pull a network scan with J2534 interface where all node fields in my AB are correct and not "mangled" up. From what I have noticed, only GWM is what matters, as it allows your truck to communicate with the mothership. So post #283 only instructs how to fix the GWM (if affected) and have the truck talking with Ford servers properly. All the rest gets corrected once truck runs its own version of network scan. Hope this explains it

The GWM is what would worry me. So this answers my question. As long as that’s not mangled, I can wait for the rest to self-correct. Thanks!

 

[iceman77]

The GWM is what would worry me. So this answers my question. As long as that’s not mangled, I can wait for the rest to self-correct. Thanks!

That was my observation.

 

[iceman77]

Have you ever seen this field fail to populate after multiple retries?

Yes, I had a case, when I ran NS in FDRS and my GWM info got mangled up, and took me 3-4 subsequent scans to get it corrected. After this experience I just stopped using NS in FDRS, and just load Ford's cloud stored information for my truck (as described in post #282). This will not limit FDRS functionality in any way, you can still do module self-test, sw upgrade, configuration and PMI. You will be offered module SW update based on same source as OTA

Perhaps the only downside not running NS is, that you wont be able to see which modules are online and which modules exhibit DTCs in FDRS, but for that I can use ForScan

I hope Ford notices it and fixed the J2534 stack in the tool, but at the same time I have my doubts, as the Fords official VCM3 device (which is not J2534 based) does not exhibit this problem

 

[Airborne_Ape]

Has anyone tried to have APIM updated at the dealer, which failed, then successfully updated themselves?

If Taylor Ford will let me in their shop I'll make it work.

 

[Airborne_Ape]

Yes, I had a case, when I ran NS in FDRS and my GWM info got mangled up, and took me 3-4 subsequent scans to get it corrected.

That's not what I meant, I was wondering if you've seen it fail after repeated attempts to the point that you have to perform a PMI / flash the GWM. I'm glad there's a work around. Do you think selecting a manual baud rate could avoid this read error? is that an option in the VX Manager?

 

[Bob_Mac]

That was my observation.

Have you had time to look at a private message I sent you?

 

[MikeYQM]

If Taylor Ford will let me in their shop I'll make it work.

I was able to get it working myself.

 

[iceman77]

That's not what I meant, I was wondering if you've seen it fail after repeated attempts to the point that you have to perform a PMI / flash the GWM. I'm glad there's a work around. Do you think selecting a manual baud rate could avoid this read error? is that an option in the VX Manager?

This went through my mind, but since the flashing procedure was working well, I did not want to risk misconfiguring the device. I flashed IPMA with this tool, a procedure which took 3-4 hours and it went through flawlesly. No failures. Also, I have flashed multiple configurations using VCX Nano and ForScan and never failed. Compared to what I seen other users complaining about "procedure interrupted" with the original ODBEx adapter I was pleasantly surprised.

Also, there is a similar thread on mach-e forums where users used FDRS in conjunction of the Mongoose-Plus J2534 interface and they exhibited similar symptoms of "ghost" updates just as we seen it here using the VCX Nano.

In the end, I am not against trying out changing baud rate of the J2534 interface. Would be worth trying but at this point I am reluctant running another NS using FDRS on my truck

 

[Fordphanatic]

I do understand the VCM 3 is expensive but is this the one guaranteed to work without causing any problems reading the modules

This went through my mind, but since the flashing procedure was working well, I did not want to risk misconfiguring the device. I flashed IPMA with this tool, a procedure which took 3-4 hours and it went through flawlesly. No failures. Also, I have flashed multiple configurations using VCX Nano and ForScan and never failed. Compared to what I seen other users complaining about "procedure interrupted" with the original ODBEx adapter I was pleasantly surprised.

Also, there is a similar thread on mach-e forums where users used FDRS in conjunction of the Mongoose-Plus J2534 interface and they exhibited similar symptoms of "ghost" updates just as we seen it here using the VCX Nano.

In the end, I am not against trying out changing baud rate of the J2534 interface. Would be worth trying but at this point I am reluctant running another NS using FDRS on my truck

I do realize that this VCM 3 is expensive but is this the adapter guaranteed to work and not cause any issues doing a FDRS network scan? My recently purchased 1 year license to FDRS Doesn't do me a damn bit a good If the VCX nano is corrupting my modules when it scans them. Don't exactly want to put 1500 bucks out but I also don't mind investing money in tools.

 

[iceman77]

I do understand the VCM 3 is expensive but is this the one guaranteed to work without causing any problems reading the modules

I do realize that this VCM 3 is expensive but is this the adapter guaranteed to work and not cause any issues doing a FDRS network scan? My recently purchased 1 year license to FDRS Doesn't do me a damn bit a good If the VCX nano is corrupting my modules when it scans them. Don't exactly want to put 1500 bucks out but I also don't mind investing money in tools.

I believe that is the tool @Jesse-Infotainment is using and his As-Built data does not exhibit the data corruption mentioned above upon inspection. But is it worth investing into this tool just because of NS report gets corrupted ? You can update your modules via FDRS just fine without running network scan (I documented how to do it here).

You need to understand that your actual modules, nor SW revisions are NOT corrupted inside your truck. Its only portion of the As-Built data on Ford servers, that gets corrupted when FDRS uploads NS results gathered over J2534 interface. Even that gets self-corrected one your truck reports its own network scan.

The choice is yours after all. If you wish to spend that amount of money, go for it! I am sure that device will serve you well!