ECU module programming guide using FDRS

[RyanStroeder]

I almost always lock from handle. When I lock from the Fob it stows. and I believe stay stowed. Ill have to double check today. They work awesome. I find it odd they deploy right after I lock.

Mine also have the same behaviour. My guess it was due to the proximity of the FOB, but I’m not aure

Sponsored

 

[antho]

I almost always lock from handle. When I lock from the Fob it stows. and I believe stay stowed. Ill have to double check today. They work awesome. I find it odd they deploy right after I lock.

@Jesse-Infotainment
Yeah it would be weird to use the fob. Just curious if they did the same or if it was isolated to locking with the handle.

 

[Jesse-Infotainment]

@Jesse-Infotainment
Yeah it would be weird to use the fob. Just curious if they did the same or if it was isolated to locking with the handle.

Yeah I understand. I dont really know off the top of my head about the fob behavior. Thinking about it though when they re deploy I hit the lock button on the fob and they stow and stay stowed. So maybe its a glitch I was just curious if the AL update corrected it.

 

[JIMFOUNTAIN]

I have a question for those that have Power Running boards. I added them to my truck. They work great. My DSM is at the AG revision. I have hesitated to go higher due to issues others have experienced after the update. If the update fixes my issue though Ill go ahead and do it.

When I lock my truck from the handle the boards stow then immediately redeploy. Is that anything others have experienced? If so when updating to AL did that fix it?

Had that behavior originally. After completely updating and getting Bluecruise in March the DSM config was hosed and my boards didn't work. Had to Forscan to get working. And then again to get the kick switch working. But I discovered turning back "off" 744-23-02 00xx xxxx xx gave me all the functions without the stupid redeploy.

Now I can have approach activated and the lights come on.. but boards don't move. Lock.. boards fold and don't immediately reopen. Walk past the truck and the boards stay folded. Pull my full DSM to check it out. 1FTFW1ED5MFB13052

While you are at it let me know what else is new...

 

[Jesse-Infotainment]

Had that behavior originally. After completely updating and getting Bluecruise in March the DSM config was hosed and my boards didn't work. Had to Forscan to get working. And then again to get the kick switch working. But I discovered turning back "off" 744-23-02 00xx xxxx xx gave me all the functions without the stupid redeploy.

Now I can have approach activated and the lights come on.. but boards don't move. Lock.. boards fold and don't immediately reopen. Walk past the truck and the boards stay folded. Pull my full DSM to check it out. 1FTFW1ED5MFB13052

While you are at it let me know what else is new...

Thank you. I really like the boards to deploy when approaching though.. I would hate to eliminate it.

 

[JIMFOUNTAIN]

Thank you. I really like the boards to deploy when approaching though.. I would hate to eliminate it.

Right. I tend to wander past my truck frequently... fob in pocket... but don't intend to unlock or get in. I like the lights coming on... trucks sez hi.. see ya... but the boards flopping in and out made me crazy. Now they deploy when I unlock.. Kinda cool we can customize behaviors as much as we can.

 

[rpeterslll]

Right. I tend to wander past my truck frequently... fob in pocket... but don't intend to unlock or get in. I like the lights coming on... trucks sez hi.. see ya... but the boards flopping in and out made me crazy. Now they deploy when I unlock.. Kinda cool we can customize behaviors as much as we can.

If Ford really wanted to embrace technology in their vehicles, they would enable customers to make these type of customizations within Ford Pass to sync down to the vehicle rather than setting their own standards without any customer input.

 

[Snakebitten]

I always enjoyed the "approach" feature for the board deployment, but also found it irritating that they would behave as you describe after locking with the handle button.

Also, I fiddle around in the barn and if the Fob is in my pocket the approach deployment would happen continuously everytime I was close to the truck.

I then noticed that I could change the settings on the boards to "delay".

I've been happy with the less than perfect compromise.

Approach still works (even if I didn't intend to get in the truck)

I can exit the truck and lock it from the handle button and they go up and stay up if I walk away.

Now they stay down after I get in the truck and start it. But they go up if the truck starts to move.

Basically they are a lot less busy!

 

[antho]

I like the lighting approach but had to disable it. I spend a lot of time in the garage/front yard/cul de sac so the lights where constantly turning on. I could only imagine lights and running boards! Clearly could leave the key inside the house but I hate having to mess with it. 1st world problems!

 

["Steve"]

never miss an update!

https://www.f150gen14.com/forum/threads/never-miss-a-software-update.10951/

 

[Airborne_Ape]

Don't get in any trouble on our behalf, but it's so strange that any of this would be taboo in this modern extreme-information age.

It’s more to do with the particular shop than anything. They had to fire a tech for posting something profoundly stupid on Facebook involving a marked police car. As a result, shop management is on edge with how all their staff engages with the public online which I can appreciate considering the extent of what they’ve gone through.

 

[Airborne_Ape]

Here’s a fun one I ran into today and which I’m sure some of you have seen already. Updates that process over usb will fail unless if the TCU is connected to LTE or the APIM is connected to WiFi. Without external connection Sync 4 shows a general USB error.

The security certificate on the USB drive has to authenticate with the servers for the update to succeed.

I ran into this while updating the GWM

We’re still working on a powerboost with a confirmed TCU ethernet disconnect, but we can’t tear the cab apart to get to the GWM until a higher authority gives the green light.

Every indication points at eithernet being disconnected at the GWM or the connector under the centre console. Interestingly, GWM to TCU is the only network that goes to an intermediate connector like that.

One thing I noticed that stood out that relates to that Bronco with a similar issue you guys were talking about a few days ago. Up here our GWM only showed a TCU ethernet disconnected DTC after being updated with FRDS.

So maybe there is a software bug in the GWM that prevents that DTC and explains why some of you have seen it and others haven’t.

 

[tonesto7]

The security certificate on the USB drive has to authenticate with the servers for the update to succeed.

That's not really how it works at all! There is no server connection made during updates.

The certificate is encoded with the Vehicle VIN and the ESN of the GWM and is used by the GWM Module as a manifest to validate the content of the USB is meant for that vehicle and to tell it what to update.

 

[Airborne_Ape]

That's not really how it works at all! There is no server connection made during updates.

The certificate is encoded with the Vehicle VIN and the ESN of the GWM and is used by the GWM Module as a manifest to validate the content of the USB is meant for that vehicle and to tell it what to update.

I don't know what to tell you other than what was done.

Our GWM USB update repeatedly failed upon consecutive attempts (keep in mind there's effectively no TCU). As soon as the APIM was connected to the shop's wifi the USB update worked without making any changes. That seems like more than just a coincidence right?

I saw the VIN in the certificate, but it seemed as though there must have been some sort of authentication process with Ford Servers before the files install based on the observed behaviour.

 

[JEB]

I don't know what to tell you other than what was done.

Our GWM USB update repeatedly failed upon consecutive attempts (keep in mind there's no effectively no TCU), then as soon as the APIM was connected to the shop's wifi the USB update worked without making any changes or the need to re-download any of the files or restart FRDS. That seems like more than just a coincidence right?

I see the VIN in the certificate, but it seems as though there must be some sort of authentication process with Ford Servers before the files install based on the observed behaviour.

Nope. @tonesto7 has it right. Authentication takes place during the network scan, at which time vehicle-specific tools for updating modules are populated under the software update tab. For those updates that use USB, the update software and any validation information needed to run it are downloaded to the USB. The USB update can then run without any connection to the Ford servers but only on that specific vehicle. Post-install validation requires a connection, but by that point the install has already completed.

Sponsored