ECU module programming guide using FDRS

[kb3421]

Definitely try disabling the McAfee - the built-in Windows Defender should suffice. I've also heard issues with McAfee after 30 days or so if you don't pay for the license. Hopefully others can chime in as well as I'm not as familiar with FDRS as others.

The firewall was what was holding it up. Working through the updates now. Currently locked in doing the IPMA update. If I knew this one takes 3hrs, I'd have done something else, lol. But now I'm wondering if I need to install EVERYTHING that comes up under the ALL tab or just certain ones?

Sponsored

 

[Snakebitten]

Not ALL tab.

Only updates tab.

 

[Static]

So got to a point where no more updates are showing, but I am only on sync version 22192_PRODUCT Revision: 498.

I still have the orange tcu so I started to look into it and now I'm thinking I might not have installed the new one correctly. The error lists ssm49690 which states something about establishing an FDRS session before removing the old module, and then only replacing it when told. I however just swapped them and then opened up FDRS to pmi the new module. My question now is, to fix this error, do I need to install my old tcu and start a pmi in FDRS, or will that screw everything up since it's not up to date to the point that all my modules are now? @Jesse-Infotainment any input?

 

[fordtruckman2003]

Just noticed the serial number on my Mongoose is quite low. 15xx.
Are all 1500 Mongoose owners from this forum? ?

 

[Jesse-Infotainment]

So got to a point where no more updates are showing, but I am only on sync version 22192_PRODUCT Revision: 498.

I still have the orange tcu so I started to look into it and now I'm thinking I might not have installed the new one correctly. The error lists ssm49690 which states something about establishing an FDRS session before removing the old module, and then only replacing it when told. I however just swapped them and then opened up FDRS to pmi the new module. My question now is, to fix this error, do I need to install my old tcu and start a pmi in FDRS, or will that screw everything up since it's not up to date to the point that all my modules are now? @Jesse-Infotainment any input?

You can put it in but I think you need to do the tcu provisioning in fdrs

 

[Static]

We could load customr firmware if we were able to break the bootloader.

You can put it in but I think you need to do the tcu provisioning in fdrs

?

 

[rugedraw]

Greetings,
My Mongoose should be here later this week, and I plan on the FDRS process starting early Saturday morning. Today I connected via FORScan to look at DTC's and there is only one but it is with the APIM and it reads as follows. . .

Code: U3000 - Control Module

Additional Fault Symptom:
- General Checksum Failure

Status:
- DTC Present at Time of Request
- Malfunction Indicator Lamp is Off for this DTC

Module: Accessory Protocol Interface Module

So is that error going to cause issues during the FDRS process? Also, I have read the part that FDRS will reset any changes you have made with FORscan, and I have only made two so far. One to disable horn honk, and the other was tire size since I am running 35x12.5. Will it reset both of those? should I change them back to "as built" of just let FDRS do it's thing and check them after I am done?
Thank you in advance!

I don't think the DTC matters for FDRS updates. As far as the FORscan changes, if you did them a while ago and your truck synced up with the mothership, they are most likely part of your as-built data now.

 

[SanJuanTech]

I don't think the DTC matters for FDRS updates. As far as the FORscan changes, if you did them a while ago and your truck synced up with the mothership, they are most likely part of your as-built data now.

Yes, I did those very early on. Was thinking at one point if that is why my truck quit getting OTA updates.
Thank you for the information.

 

[Jesse-Infotainment]

?

Sorry the top part was not supposed to be there.
You need to do the tcu provisioning in fdrs

 

[Static]

Sorry the top part was not supposed to be there.
You need to do the tcu provisioning in fdrs

I give up. I tried the provisioning, but the u2101 dtc won't go away. I can put my old TCU back in and get no DTC's but it won't update. And now my truck's location in fordpass is somewhere in michigan.

 

[elaudermilk]

I give up. I tried the provisioning, but the u2101 dtc won't go away. I can put my old TCU back in and get no DTC's but it won't update. And now my truck's location in fordpass is somewhere in michigan.

I am without Nav/satradio after doing all the updates and the Nav currently just shows me motionless in Dearborn on the Nav screen in my truck (I’m in Dallas)

 

[JEB]

I give up. I tried the provisioning, but the u2101 dtc won't go away. I can put my old TCU back in and get no DTC's but it won't update. And now my truck's location in fordpass is somewhere in michigan.

I’m not sure if there is really anything to this—or if Ford Is simply trying to cut out the aftermarket sale of parts—but Ford recently released an SSM cautioning dealers not to swap modules for testing or ordering modules that were originally ordered for another VIN due to hardware variations.

SSM 51536 2000-2024 Various Vehicles - Errors Caused By Swapping Modules From Like Vehicles Or Ordering Modules Using Another VIN

For 2000-2024 Ford and Lincoln vehicles, swapping a module from a vehicle for diagnosis purposes is likely to cause errors and is not recommended. It is also not recommended to order a replacement module using a vehicle identification number (VIN) from a different vehicle. Most modules on these affected vehicles are VIN/vehicle specific and hardware variations between modules do exist. Swapping a module from a vehicle or ordering a module using a different vehicle/VIN can cause ineffective repairs and additional vehicle down time. Make sure all appropriate Workshop Manual (WSM) procedures are followed when diagnosing the condition prior to all module replacements and only order modules using the correct VIN.

 

[Static]

I’m not sure if there is really anything to this—or if Ford Is simply trying to cut out the aftermarket sale of parts—but Ford recently released an SSM cautioning dealers not to swap modules for testing or ordering modules that were originally ordered for another VIN due to hardware variations.

SSM 51536 2000-2024 Various Vehicles - Errors Caused By Swapping Modules From Like Vehicles Or Ordering Modules Using Another VIN

For 2000-2024 Ford and Lincoln vehicles, swapping a module from a vehicle for diagnosis purposes is likely to cause errors and is not recommended. It is also not recommended to order a replacement module using a vehicle identification number (VIN) from a different vehicle. Most modules on these affected vehicles are VIN/vehicle specific and hardware variations between modules do exist. Swapping a module from a vehicle or ordering a module using a different vehicle/VIN can cause ineffective repairs and additional vehicle down time. Make sure all appropriate Workshop Manual (WSM) procedures are followed when diagnosing the condition prior to all module replacements and only order modules using the correct VIN.

This tracks, Jesse told me I should get the same part number to be safe, but I found a different one for $40 on ebay, so lesson learned. Cheapest one with my same part number was $160 but then I'd probably have a working tcu. I just kinda got sick of dumping money into a problem that I shouldn't have to fix, but I know if I took it to the dealer for this I'd either not have a truck for a month, or they'd screw something up more.

 

[JEB]

This tracks, Jesse told me I should get the same part number to be safe, but I found a different one for $40 on ebay, so lesson learned. Cheapest one with my same part number was $160 but then I'd probably have a working tcu. I just kinda got sick of dumping money into a problem that I shouldn't have to fix, but I know if I took it to the dealer for this I'd either not have a truck for a month, or they'd screw something up more.

I was perilously close to making the same mistake. I was having problems with my TCU last summer and bought a replacement TCU on eBay for about $150 that @Jesse-Infotainment recommended that was not the same part number. This was long before the SSM came out and Ford started cautioning dealers that even minor module hardware variations could cause problems. Fortunately, I was able to get mine working again before I installed it and never had to learn the lesson the hard way. I ended up donating the TCU to him so he could put it to better use.

This thread is littered with people who shouldn’t have had to spend money to repair a truck under warranty. But I consider it money well spent. Mine has remained in service and the time I waste at the dealer has plummeted.

Your dog has an awesome nose.

 

[robry]

Has anyone replaced their PCM with a new one? Any instruction/walkthrough with that? I have a mongoose cable, all of the software installed, and about to order a license.

Sponsored