ECU module programming guide using FDRS

[ReverendQ]

IM not sure I understand? Did I say not to do that or something?

Oh, sorry I wasn't clear. I'll try again.

I was replying to your post #12008 where I read it to mean you are suggesting to roll-back an update to clear a DTC P160A. I am wondering why you didn't suggest the procedure in ForScan first?

Background: P160A didn't and wouldn't clear for me until I followed the procedure shown in #12798. But I don't know if I got the P160A from using FDRS last weekend or from getting new tires the week before, or other reason.

Sponsored

 

[Jesse-Infotainment]

P160A isnt the code anyone had. Thats why I was confused. The reason for the roll back was a Brake light and a Voltage code in the ABS module

 

[Kanuck]

I had that error.... I had changed my tires size for the new tires. This caused P160 error to show up. I just set the tire size back to what it was. The speedometer is only out 2kkph at 100kph with the new tires.

 

[ReverendQ]

I had that error.... I had changed my tires size for the new tires. This caused P160 error to show up. I just set the tire size back to what it was. The speedometer is only out 2kkph at 100kph with the new tires.

I got P160A before I changed the tire size in the BCM and somewhere during the updates done with FDRS. It didn't clear after a week's worth of commutes, but I had tinkered with different tire size changes in the BCM during the week. So, I am not sure if my FDRS programming or tire size changes, see P160A – Control Module Vehicle Options Reconfiguration Error (Ford) – TroubleCodes.net , caused the P160A but the procedure does seem to clear it...and I hope to return my truck to operating efficiently. (My milage hit for the heavier tires is a bit more than expected). If nothing else maybe these posts will help anybody else with DTC P160A-00.

 

[Kanuck]

My error code was P160A:00-2F. It is a mismatch between IPC and BCM according to Google. I changed my tire size back to factory and the error cleared.

 

[Kanuck]

From what I can figure out from reading different write ups on this P160A error. Changing the tire size, also causes different calculations through out the truck to go out of set parameters within different systems. EG. Odometer, transmission shifting, fuel mileage, just for example. Knowing this, makes me consider the fact that to change tire size to correct speedometer error, I would also have to change a bunch of calculations in different areas of the truck. Not something I want to do.

I will just have to live knowing that my speedometer is out by 2kph at 100kph. As proving with 3 different apps on my phone.

 

[Cabrinha]

If you try the PMI, make sure you select "no" when asked if it is the original module.

Yes I tried it but it didn't work, and I selected no

 

[Kanuck]

It did work - same error I had on a buddy's truck yesterday. Do a network scan and clear the DTC's. is all I did.

 

[JEB]

PCM and SOBDMC updates dropped for my ‘21 Powerboost this morning. Installation was unremarkable.

 

["Steve"]

hey guys, got a question. what does this process do, and how can you tell if it is needed? besides just saying if you update ddm/pdm do this... is there a symptom to watch for to know you need to do this, or can you do it with forscan/outside fdrs (like pushing buttons in a certain sequence)? we updated a homie's truck, and didn't run these. wondering if we need to grab another license just for this.

APPENDIX II:

If you updated the DDM/PDM modules, you need to run the 'Power Door Window Initialization' for both modules. This can be found in each of the module task window (on the right hand side) in FDRS. This is needed for your windows auto open/close to work

 

[sbi]

If the trucks never been updated and your locked out on 1.7.1 this will have to be overcome first. At that point it will take 12 to 18 hours to update all of the modules in the truck to the current levels.

Stupid question - how/where do I see what version I am stuck on? It's not the SYNC SW version, is it?

 

[Big Dog Daddy]

Stupid question - how/where do I see what version I am stuck on? It's not the SYNC SW version, is it?

Yes, it has to do with the SYNC version. In your "about SYNC" screen, if your version number is 20312 revision 243. Then your stuck on the bad 1.7.1 update. This only applies to Job1 2021 trucks.

 

[rugedraw]

hey guys, got a question. what does this process do, and how can you tell if it is needed? besides just saying if you update ddm/pdm do this... is there a symptom to watch for to know you need to do this, or can you do it with forscan/outside fdrs (like pushing buttons in a certain sequence)? we updated a homie's truck, and didn't run these. wondering if we need to grab another license just for this.

I didn't do this when I updated mine and everything works fine. You having any issues?

 

[sbi]

Yes, it has to do with the SYNC version. In your "about SYNC" screen, if your version number is 20312 revision 243. Then your stuck on the bad 1.7.1 update. This only applies to Job1 2021 trucks.

Thanks.
So I am 2021 Job 2 and my SYNC shows Software Version: 21223_PRODUCT Revision: 197.

 

[Snakebitten]

It's amazing there are trucks running around with 2020/2021 build dates for Sync4

That's so Gen12/13

Sponsored