ECU module programming guide using FDRS

[Jesse-Infotainment]

Oh! That is a welcome update!

I’m not 100% so will be good to hear feedback.

Sponsored

 

[Airborne_Ape]

Here is the IPC before update….

What program is this?

 

[Airborne_Ape]

‘21 J1 PB Lariat as well, care to take a look? 1FTFW1ED0MFB66211

I missed something.
What are we looking for?

 

[Airborne_Ape]

So I got my truck back from the dealer after they did the software updates needed for BC. While they had the truck they replaced the IPMA. They tried to PMI the new IPMA and it failed so they left it. There was a DTC that cleared after driving so they handed it back over to me. Long story short BC still doesn't work. I called Ford tech support and they told me the truck has all the needed software and BC should work. What do I do now? I made changes to the IPMA in forscan and when I try and load them back into the new IPMA module I get a configuration mismatch. Anyone run into this issue?

Usually that type of config mismatch occurs because the memory addresses of some of the as built have changed / extended. You will have to open your backups in another utility and load your original as built manually to locate the differences. I find its quicker to find out where the differences are by just browsing through the check sum bits for each line in any ECU.

 

[Airborne_Ape]

FYI,

When you guys do updates the backend logs more than you might realize. It's not hard to imagine this data could be used to invalidate a warranty claim if someone ran into a mess. We can read through diagnostic data and can tell who did updates at home and who followed the correct procedures. The system logs which technicians took which actions and when OTA updates attempt to execute.

Have a look at this example from some here who did an APIM update in their driveway.

The system logs details such as if the ignition switch was toggled as per the on screen instructions and if the Sync 4 pop up warnings were acknowledged.

 

[abd79]

I missed something.
What are we looking for?

Was just asking about OTA status.

Interesting on the U2400 DTC though. I haven’t actually seen that DTC when connected with Forscan or FDRS directly. Must be happening and correcting itself quickly during a drive or shortly after an initial start.

 

[speedracercjr]

FYI,

When you guys do updates the backend logs more than you might realize. It's not hard to imagine this data could be used to invalidate a warranty claim if someone really ran into a mess. We can read through diagnostic data and can tell who did updates at home and who followed the correct procedures. The system logs which technicians took which actions and when OTA updates execute.

Have a look at this example from some here who did an APIM update in their driveway. It logs details such as if the ignition switch was toggled after the updates as per the on screen instructions and if the Sync 4 pop up warnings were acknowledged.

While I agree everything is logged, Ford sells the software to any joe off the street. If they don't want any joe to have access to FDRS then they shouldn't sell the license.

As for the example, the only thing I'm seeing is that someone clicked "OK" on the prompt on their computer. Not that it really matters but it does not show that they started the truck, or turned it off or anything beyond what FDRS prompts come up.

 

[speedracercjr]

What program is this?

That's @tonesto7 's badass widget that pulls data for your truck.

https://www.f150gen14.com/forum/threads/fordpass-scriptable-widget-v2022-xx-ios-ipad-macos.8972/

 

[Airborne_Ape]

That's @tonesto7 's badass widget that pulls data for your truck.

https://www.f150gen14.com/forum/threads/fordpass-scriptable-widget-v2022-xx-ios-ipad-macos.8972/

Oh, I have that already, the posted screenshot is different than what I'm used to looking at so I thought it was a different utility. And yes, it is badass. It works better than the actual Ford Pass App.

 

[abd79]

Curious but could someone with PTS check and see if they are getting the same results as I am. When I log in and input my VIN I get this big blue box that says "VIN not authorized to send vehicle status, VHA and DTC data." Also I cannot see any of the diagnostic information sent not can I see any of the OTA info. Just wondering if this is a problem with my VIN or my PTS account.

 

[hotrodmex]

While I agree everything is logged, Ford sells the software to any joe off the street. If they don't want any joe to have access to FDRS then they shouldn't sell the license.

Ford sells you oil, too. If you pour it all over your engine and not inside it, that's not on them or their warranty.

It's not who did the work, it's if it was done correctly.

 

[JJ_Tex]

Ford sells you oil, too. If you pour it all over your engine and not inside it, that's not on them or their warranty.

It's not who did the work, it's if it was done correctly.

While I get your point, many of us tried the dealer route first and were unsuccessful. The next avenue was to update our trucks ourselves using Ford-approved hardware and a license purchased from Ford to do their update using their software. Its not like we are jailbreaking our trucks.
Plus I would imagine people who spent $700 out of pocket and 10 hours of their own time to get their trucks working as advertised would be willing to spend money on a lawyer for any denied warranty claims.

 

[JJ_Tex]

Welcome Steve to our great state. Where did you move? Half my neighborhood is from California so you certainly will not be alone wherever you moved.
Most of you Cali transplants are good people, but I do have my sign saying "Don't California my Texas" for the handful that get out of hand from time to time

 

[Mike G]

FYI,

When you guys do updates the backend logs more than you might realize. It's not hard to imagine this data could be used to invalidate a warranty claim if someone ran into a mess. We can read through diagnostic data and can tell who did updates at home and who followed the correct procedures. The system logs which technicians took which actions and when OTA updates attempt to execute.

Have a look at this example from some here who did an APIM update in their driveway.

The system logs details such as if the ignition switch was toggled as per the on screen instructions and if the Sync 4 pop up warnings were acknowledged.

Yes. Yes it does. And it's a double-edged sword isn't it?

As @speedracercjr points out that Ford sells (licenses) this software to any joe off the street. Who can then log in with a specific VIN and see exactly what the tech did and compare that to what the service manager says he/she did.

Like in the multiple cases on the Mach-E forums where the service desk hands back a car to the customer and says it's completely up to date and a VIN SW Updates check shows there are a pant-load of updates that never got done under a CSP that was supposed to be paying for that labor. Or in an example similar to the case you've posted the details of above, a tech kicks off an APIM update but further down the log there is a warning that battery SOC was only at 49% and they went ahead anyway (without using a powersupply?) and the update failed. And the car was given back to that customer in that state. This happens all the time. Everyday. Maybe not at your shop but it happens. And for that reason I'm glad we all have the ability to "trust but verify" what was actually done from the FDRS logs as forensic evidence.

Mike

 

[antho]

FYI,

When you guys do updates the backend logs more than you might realize. It's not hard to imagine this data could be used to invalidate a warranty claim if someone ran into a mess. We can read through diagnostic data and can tell who did updates at home and who followed the correct procedures. The system logs which technicians took which actions and when OTA updates attempt to execute.

Have a look at this example from some here who did an APIM update in their driveway.

The system logs details such as if the ignition switch was toggled as per the on screen instructions and if the Sync 4 pop up warnings were acknowledged.

After seeing some of the logs from Ford dealership techs, I'm more confident doing my own modules in the driveway. We have known that it logs the user and that the history shows all of the work done in the vehicle history in FDRS.

Sponsored