ECU module programming guide using FDRS

[fordtruckman2003]

I don't think so. The reason our trucks can't get IPC updates the traditional way is hardware related; not software.

I mean that when IPC can't update it would start updating other things. Just a thought because I don't know how my truck had the updates it did get with never having an IPC update. Didn't have the decimal point on the odometer in April. ?

Sponsored

 

[rugedraw]

I mean that when IPC can't update it would start updating other things. Just a thought because I don't know how my truck had the updates it did get with never having an IPC update. Didn't have the decimal point on the odometer in April. ?

Oh, that can definitely happen. As a matter of fact, Jesse is helping @kdrew with this exact issue now. In some cases like his, the IPC update is not showing in FDRS at all; even after all. When that happens, the only way to get the update is to side-load it with FORscan.

When my truck was stuck on the 2.7.3/2.7.4 IPC updates, the IPC update was not showing up for me with a manual VIN lookup in FDRS. Fortunately, when I did a network scan with FDRS, it popped up on the list and I was able to install with FDRS using the CAN process. In the case of @kdrew, it had to be side-loaded with FORscan.

 

[JEB]

It seems like that same failed path used for OTA updates would cause other issues with normal cross communication between modules.

Not in this case. Different paths. The modules communicate with each other via the CAN bus, not the Ethernet. When you do a network scan in FDRS, you’ll see all of the modules organized under different CAN buses (FD1, HS1-4, MS1-2). If the IPC is showing up on one of the buses (HS3), it’s communicating fine on the network. The ethernet not working properly will only make updating that module a pain in the ass. Operationally, it shouldn’t be an issue once updated.

 

[Snakebitten]

I only post this historical SSM to support Jeb's point above.

That GWM is so mission critical to the insane complexity of the "network" design on these trucks.
I'm not in the automotive industry, so I'm probably very naive about the reasons Ford (or anyone) would take such a design approach. 42 modules? Multi bus/multi protocol/multi network

I'm still AMAZED that you can get one of these trucks fully loaded and the thing is completely functional and well behaved. (knock on wood)

 

[robry]

I've seen the discussions around the ethernet adapter being used to connect a mach-e to a laptop with FDRS to update, is there a similar process for the 21+ f150, any benefit to speed of updating when using ethernet?

 

[Snakebitten]

I've seen the discussions around the ethernet adapter being used to connect a mach-e to a laptop with FDRS to update, is there a similar process for the 21+ f150, any benefit to speed of updating when using ethernet?

I really don't know for sure what is or isn't possible with a direct connection between the laptop and the ethernet network in the F150.
But wouldn't it SEEM reasonable for a truck like these to just have an ethernet port available on the center stack somewhere? ?

Again, I'm certain I am being naive, but it would make so much sense to be able to interface with the truck over such a thing. It could have whatever levels of security necessary to determine what is accessible and what isn't at the customer level, the technician level, or the manufacturer level.

We pretty much have all those levels of access already, just through OBD interface instead.

 

[robry]

I really don't know for sure what is or isn't possible with a direct connection between the laptop and the ethernet network in the F150.
But wouldn't it SEEM reasonable for a truck like these to just have an ethernet port available on the center stack somewhere? ?

Again, I'm certain I am being naive, but it would make so much sense to be able to interface with the truck over such a thing. It could have whatever levels of security necessary to determine what is accessible and what isn't at the customer level, the technician level, or the manufacturer level.

We pretty much have all those levels of access already, just through OBD interface instead.

Makes sense to me, just curious if that's even an option.

 

[JEB]

I've seen the discussions around the ethernet adapter being used to connect a mach-e to a laptop with FDRS to update, is there a similar process for the 21+ f150, any benefit to speed of updating when using ethernet?

I think you might be mixing up a couple of different kinds of ”Ethernet.” What we’re talking about here is a direct link to a module via an Ethernet port on the module itself. What you’re talking about, I think, is using an Ethernet adapter on a laptop so you can go from the laptop’s Ethernet port to the truck’s OBDII port. Not sure there’s a benefit to it over just using the laptop’s USB port.

 

[robry]

I think you might be mixing up a couple of different kinds of ”Ethernet.” What we’re talking about here is a direct link to a module via an Ethernet port on the module itself. What you’re talking about, I think, is using an Ethernet adapter on a laptop so you can go from the laptop’s Ethernet port to the truck’s OBDII port. Not sure there’s a benefit to it over just using the laptop’s USB port.

No I'm talking about the vehicle using a USB adapter (IIRC mache requiring one with a direct connection to the GWM A or something) and then running direct to the laptop's ethernet port (or USB-> ethernet adapter).

Properly implemented ethernet would be worlds faster for larger updates and would negate the need to use a USB stick to transfer files.

 

[JEB]

No I'm talking about the vehicle using a USB adapter (IIRC mache requiring one with a direct connection to the GWM A or something) and then running direct to the laptop's ethernet port (or USB-> ethernet adapter).

Properly implemented ethernet would be worlds faster for larger updates and would negate the need to use a USB stick to transfer files.

You mean a direct connection from the laptop’s ethernet port to the module itself, bypassing everything—OBDII and USB hub? Or laptop Ethernet to vehicle USB? Either way, I haven’t heard of it being done on an F150 nor am I sure you could get FDRS to recognize a different pathway.

 

[Snakebitten]

I think the architecture that he is desiring doesn't actually exist.
Or at least what I described as desirable doesn't.

The ability to connect seems to, because the TSB from the OTA purgatory days suggest it's possible. But the ability to do much more than a very finite task list probably isn't supported.

 

[robry]

https://www.macheforum.com/site/threads/tsb-22-2117-fix-for-stuck-power-up-1-7-1-update.15814/

This is what I'm talking about, there is mention of F150 in here as well. Coordinating between ODBII AND ethernet (USB on the car side). Figured I'd ask. Maybe something we'll see more of in the future.

In another MachE thread, it's mentioned the GWM has both CANBUS network and ethernet connectivity to some modules and ethernet is used for larger transfers. But that seems more internal use only for obvious reasons.

 

[JEB]

https://www.macheforum.com/site/threads/tsb-22-2117-fix-for-stuck-power-up-1-7-1-update.15814/

This is what I'm talking about, there is mention of F150 in here as well. Coordinating between ODBII AND ethernet (USB on the car side). Figured I'd ask. Maybe something we'll see more of in the future.

In another MachE thread, it's mentioned the GWM has both CANBUS network and ethernet connectivity to some modules and ethernet is used for larger transfers. But that seems more internal use only for obvious reasons.

Ah. I see where you’re going now and I agree with @Snakebitten. The architecture probably doesn’t exist except with respect to discrete tasks like the APIM recovery procedure, which is a direct access to the APIM itself. Not sure other modules with Ethernet ports could be as easily accessed and I’m not sure if the increased data speed would much of a timesaver over the existing methodology if you count the time it takes to dismantle your dash or remove trim panels just to access the module.

There are several modules that have both Ethernet and canbus ports that work as you describe. In fact, FDRS will offer canbus as a fallback update method for these modules if for some reason the primary update via Ethernet/USB fails.

 

[robry]

Figured out the “charge only use device” message when attempting to update my APIM, I was using a usb 3.0 stick. As soon as I grabbed a 2.0 stick it worked perfectly. I’m fairly certain the usb 3 one worked when I did the GWM A update.

 

[fordtruckman2003]

That is a process to get updates to work that fail by other means. I wouldn't expect it to work for other use.

Sponsored