ECU module programming guide using FDRS

[rugedraw]

Validation failed. Reprogramming in progress. I formatted the USB again and it’s redownloading the data to the USB.

Let it do it's thing. I don't want to log into FDRS with your VIN while you're in there jic it causes an issue. When you're done, post the list of updates you have pending.

Sponsored

 

[PizzamanJon]

Let it do it's thing. I don't want to log into FDRS with your VIN while you're in there jic it causes an issue. When you're done, post the list of updates you have pending.

Same message “ the update on this USB is already installed”

 

[PizzamanJon]

Let it do it's thing. I don't want to log into FDRS with your VIN while you're in there jic it causes an issue. When you're done, post the list of updates you have pending.

 

[PizzamanJon]

@PizzamanJon What are you trying to update right now?

TCU. It automatically started after the APIM update.

 

[antho]

TCU. It automatically started after the APIM update.

Yeah. Its looking for the files that are in the TCU update that is pending. I would try and run the TCU update that is available in the List. @PizzamanJon

 

[antho]

Yeah. Its looking for the files that are in the TCU update that is pending. I would try and run the TCU update that is available in the List. @PizzamanJon

Nevermind. Its apparently not downloading those files to your usb. @PizzamanJon Can you look at the USB and see what files are in the folder?

 

[rugedraw]

TCU. It automatically started after the APIM update.

Close FDRS and reopen it and see if that helps.

 

[PizzamanJon]

Nevermind. Its apparently not downloading those files to your usb. @PizzamanJon Can you look at the USB and see what files are in the folder?

It seems to be downloading files to the usb. But when I plug it into the truck it says it’s already been updated.

 

[PizzamanJon]

I can’t get FDRS to complete a network test on the Truck. It’s getting stuck at requesting complex tools. Any ideas? I’ve tried uninstalling and re installing FDRS, tried running a scan without the mongoose connected. Tried a different version of FDRS. Not having any luck.

 

[antho]

@PizzamanJon I would move to some smaller updates like the DDM and PDM then reaccess.

 

[JEB]

I can’t get FDRS to complete a network test on the Truck. It’s getting stuck at requesting complex tools. Any ideas? I’ve tried uninstalling and re installing FDRS, tried running a scan without the mongoose connected. Tried a different version of FDRS. Not having any luck.

You can’t run a network scan without the Mongoose connected. Since you uninstalled and reinstalled FDRS, it might be defaulting to another adapter and not the Mongoose. After you log in and the VCI Manager asks you which adapter to connect to, make sure you are selecting “Other” and the Mongoose in the drop-down.

 

[PizzamanJon]

You can’t run a network scan without the Mongoose connected. Since you uninstalled and reinstalled FDRS, it might be defaulting to another adapter and not the Mongoose. After you log in and the VCI Manager asks you which adapter to connect to, make sure you are selecting “Other” and the Mongoose in the drop-down.

I was able to get it working. I had to go up to the top of fdrs and hit support and redownload fdrs data. After that it ran the network scan fine. Trying TCU unit again. If it doesn’t work I’ll move onto the other modules.

 

[JEB]

I was able to get it working. I had to go up to the top of fdrs and hit support and redownload fdrs data. After that it ran the network scan fine. Trying TCU unit again. If it doesn’t work I’ll move onto the other modules.

Interesting fix. I’ve never used that function before.

 

[TJSparky]

It looks like a new PCM update dropped for 2021 F150 XLT 302a 5.0l

 

[Snakebitten]

I really want to thank everyone for all their help. I know I’ve posted a ton over the last 2 days and I hope it hasn’t been to annoying, I just want to make sure I don’t mess anything up. I’ve never done this before so it’s a whole new language for me. Genuinely appreciate the help!

You might not realize that every time a new fella discovers this thread, we remember what that experience was for us. And if you are crazy enough to go back to the beginning and read how this all unfolded, we were ALL you. ?

Honesty, I doubt I am the only member that kinda celebrates quietly each time a "new guy" steps up to the plate and refuses to live with the shortcomings of Ford's OTA and/or the dealerships efforts to help.

Besides, It no longer matters who should get the blame once YOUR truck has been fixed by the collective efforts of this community.

Sponsored