ECU module programming guide using FDRS

[Static]

Started getting up to date on my 21 xl again, ran into a snag with the HVAC module. I swapped in a module with Auto HVAC a while back and just had to make some forscan changes to make it work. But in the process of doing some fdrs updates, an HVAC update seems to have bricked the HVAC module. It will not update, PMI, configure, or even show up in forscan for me to load the previous asbuilt. Any ideas?

Am I SOL on this one? I can put the old module back in if I have to, but that's obviously not ideal

@Jesse-Infotainment @rugedraw

Sponsored

 

[rugedraw]

Am I SOL on this one? I can put the old module back in if I have to, but that's obviously not ideal

@Jesse-Infotainment @rugedraw

That is for sure a Jesse question. You already tried everything I would have recommended. You could try rebooting the GWM or running the GWM config procedure in FDRS to see if that makes it show back online. Bricked modules will usually appear purple in FDRS and can be recovered. If it is not showing in the module network at all, that could be a different problem. Tbh, I'm not sure. That goes beyond my scope of knowledge. If he does not respond, try messaging him. He has not been very active on the forum lately.

 

[fordtruckman2003]

Finished the TCU Update, but one of the files keeps failing. I've done the reprovision 2 more times and it still fails. Is there a way to do all of the TCU files again, FDRS keeps trying to update just the single file. Any thoughts on what I can do to try and remediate this?

When USB fails you should get an option on the screen to use CAN. It is slow so budget 3 hours every time you do that option, but it will get it done. I had a few GWM and TCU fail during my first update marathon getting 2 years of updates done but CAN always worked.

 

[HammaMan]

When USB fails you should get an option on the screen to use CAN. It is slow so budget 3 hours every time you do that option, but it will get it done. I had a few GWM and TCU fail during my first update marathon getting 2 years of updates done but CAN always worked.

Yeah, best case 1.5Mb/s. If it's small, not an issue. For instance a 270MB file would take ~26 minutes.

APIM if canbus was an option -- 10 hours

 

[Paul Neubauer]

APIM if canbus was an option -- 10 hours

That's a LOT of beer drinking hours waiting for that!

 

[HammaMan]

That's a LOT of beer drinking hours waiting for that!

More like down a 6 pack and pass out for the night. Now ya know why there's an ethernet bus between the IPMA/APIM/GWM and the TCU. Just too bad we can't go connect the USB into the APIM and have it act as a bridge to the GWM. The limiting factor at that point would be either the USB2's connection at 480Mbs or 100Mb ethernet between modules. I doubt ford used GBE like tesla does. Auto's small runs allows for a gigabit ethernet over a single shielded twisted pair.

An interesting thing has happened in defense where they used to have top of the line products, now the F35's new central brain is an intel desktop CPU with similar hardware architecture as commercial offerings due to consumers demanding cutting edge. It's even brought new VM architecture so they can run a instance of windows on the jet to access the latest ai capabilities without needing specially coded OS/s apps specifically for it. All of which has come about due to gamers. Funny how that's worked out. Given the DoD's contract to have their own sat constellations similar to starlink, won't be long before everything contains its own high-bandwidth sat uplink. Despite advanced radars being developed for subs and surface ships, they use commercial grade radars to hide among the fishing boats.
/tangent

 

[sswalters]

So I was checking the VIN for another member here, and he is showing a new IPMA/PSCM update. I checked my truck, and I am showing it, too. Looks like it may be the the BAE version for 1.3 that was first released for the Mach E.

Not sure I follow this. What is a BAE version? Should I buy another two day FDRS license and update further? Would I need to update the APIM and IPMA again for BC?

 

[rugedraw]

Not sure I follow this. What is a BAE version? Should I buy another two day FDRS license and update further? Would I need to update the APIM and IPMA again for BC?

That refers to the strategy of the new software. No need to worry about it. You don't need to do anything.

 

[Static]

That is for sure a Jesse question. You already tried everything I would have recommended. You could try rebooting the GWM or running the GWM config procedure in FDRS to see if that makes it show back online. Bricked modules will usually appear purple in FDRS and can be recovered. If it is not showing in the module network at all, that could be a different problem. Tbh, I'm not sure. That goes beyond my scope of knowledge. If he does not respond, try messaging him. He has not been very active on the forum lately.

Well unfortunately it looks like I fried the module. Jesse tried to help but it was beyond repair. Lesson learned, I didn't know not to update a module I added that wasn't original to the truck. Luckily I kept the original and was able to toss it back in, but I'll miss that auto HVAC function for sure.

 

[KissMyAsthma]

Can someone run my VIN, 1FTEW1C52PKD00008, validate what I'm seeing in my FDRS screen, and double-check that I've done the updates correctly over the past two days?

I have yet to see that I have an update for the APIM, but I'm trying to get Sync to update while I have my FDRS license.

Currently, I'm on 22147_PRODUCT Revision: 446
Is there a more current version that I could upgrade to, and how would I trigger that?

I am showing the GWM and the ACM remaining in my FDRS screen. I will attempt these updates tomorrow, but I've had issues with the GWM. It fails to run over the USB update with this message:
(This is before FDRS asks for the USB drive location and downloads the file(s) to put on the drive)

[I see in my history that the dealership also had an issue like this back in August when I had the truck in the shop to have them update the system and fix a problem with my front camera and lane keep assist that kept going offline. They told me I should be good to go, but I wonder if they actually got the GWM to update correctly. I was also told that this module could be the reason why I have yet to get OTA updates since I bought the truck in July, 2023.]

I will try the update on the GWM using the CAN method tomorrow. I don't have time to do it tonight.

I did have an issue with my TCU. One of the five updates failed, so I did a PMI on the TCU, which updated properly afterward.

This has been an experience. It's triggered nerves, frustrations, and my wife questioning if I'm breaking our truck or not, lol. But overall, this thread has been super helpful and I am grateful to @rugedraw @fordtruckman2003 @HammaMan @svtzx2 and @Paul Neubauer for the patience with my messages and questions!

 

[Jesse-Infotainment]

Can someone run my VIN, 1FTEW1C52PKD00008, validate what I'm seeing in my FDRS screen, and double-check that I've done the updates correctly over the past two days?

I have yet to see that I have an update for the APIM, but I'm trying to get Sync to update while I have my FDRS license.

Currently, I'm on 22147_PRODUCT Revision: 446
Is there a more current version that I could upgrade to, and how would I trigger that?

I am showing the GWM and the ACM remaining in my FDRS screen. I will attempt these updates tomorrow, but I've had issues with the GWM. It fails to run over the USB update with this message:
(This is before FDRS asks for the USB drive location and downloads the file(s) to put on the drive)

[I see in my history that the dealership also had an issue like this back in August when I had the truck in the shop to have them update the system and fix a problem with my front camera and lane keep assist that kept going offline. They told me I should be good to go, but I wonder if they actually got the GWM to update correctly. I was also told that this module could be the reason why I have yet to get OTA updates since I bought the truck in July, 2023.]

I will try the update on the GWM using the CAN method tomorrow. I don't have time to do it tonight.

I did have an issue with my TCU. One of the five updates failed, so I did a PMI on the TCU, which updated properly afterward.

This has been an experience. It's triggered nerves, frustrations, and my wife questioning if I'm breaking our truck or not, lol. But overall, this thread has been super helpful and I am grateful to @rugedraw @fordtruckman2003 @HammaMan @svtzx2 and @Paul Neubauer for the patience with my messages and questions!

Ill create the update for you

 

[Paul Neubauer]

Can someone run my VIN, 1FTEW1C52PKD00008, validate what I'm seeing in my FDRS screen, and double-check that I've done the updates correctly over the past two days?

I have yet to see that I have an update for the APIM, but I'm trying to get Sync to update while I have my FDRS license.

Currently, I'm on 22147_PRODUCT Revision: 446
Is there a more current version that I could upgrade to, and how would I trigger that?

I am showing the GWM and the ACM remaining in my FDRS screen. I will attempt these updates tomorrow, but I've had issues with the GWM. It fails to run over the USB update with this message:
(This is before FDRS asks for the USB drive location and downloads the file(s) to put on the drive)

[I see in my history that the dealership also had an issue like this back in August when I had the truck in the shop to have them update the system and fix a problem with my front camera and lane keep assist that kept going offline. They told me I should be good to go, but I wonder if they actually got the GWM to update correctly. I was also told that this module could be the reason why I have yet to get OTA updates since I bought the truck in July, 2023.]

I will try the update on the GWM using the CAN method tomorrow. I don't have time to do it tonight.

I did have an issue with my TCU. One of the five updates failed, so I did a PMI on the TCU, which updated properly afterward.

This has been an experience. It's triggered nerves, frustrations, and my wife questioning if I'm breaking our truck or not, lol. But overall, this thread has been super helpful and I am grateful to @rugedraw @fordtruckman2003 @HammaMan @svtzx2 and @Paul Neubauer for the patience with my messages and questions!

Jesse is the best to get you through all of this. With him helping, everything is going to end well!

 

[FirstFord]

I think I have a rough / crude idea as to what the CANBUS is, its purpose / function, etc., but can someone explain to me what the "CAN method" is when trying to force a FDRS update when the USB method failed? What is involved, how to do it, etc? Its my understanding that it is (for lack of better words) a method of last resort due to the extended length of time to implement, but on the other hand, has a high success rate. Thanks.

 

[HammaMan]

I think I have a rough / crude idea as to what the CANBUS is, its purpose / function, etc., but can someone explain to me what the "CAN method" is when trying to force a FDRS update when the USB method failed? What is involved, how to do it, etc? Its my understanding that it is (for lack of better words) a method of last resort due to the extended length of time to implement, but on the other hand, has a high success rate. Thanks.

Just updates like all of the other modules. Can bus is ~1.5Mbs data rate (think 2000s level DSL). USB can read write around 100-300Mbs (depending on USB drive's characteristics). Basically you're transmitting large amounts of data through a very limited bitrate.

 

[FirstFord]

Just updates like all of the other modules. Can bus is ~1.5Mbs data rate (think 2000s level DSL). USB can read write around 100-300Mbs (depending on USB drive's characteristics). Basically you're transmitting large amounts of data through a very limited bitrate.

So, is that to say at some point during the update process, the choice pops up on the screen where you can choose between USB and CAN?

Sponsored