ECU module programming guide using FDRS

[Snakebitten]

I’m only getting this Sync version after my APMI update. Should I expect another APMI update to appear for a later version?

You can expect a continuous stream of updates, including APIM updates.
The hits just keep on coming.

 

[BlackSheep]

I’m only getting this Sync version after my APMI update. Should I expect another APMI update to appear for a later version?

.
I have a Job 2 truck with Sync 4.0.21136. It doesn't show any APIM updates for me either and I have applied all updates. I'm not sure if something is wrong or if there isn't an update for my APIM hardware. I also haven't seen a GWM update, either.

 

[rpeterslll]

I believe someone said the running boards are controlled by the driver front seat module (DSM)

.
I have a Job 2 truck with Sync 4.0.21136. It doesn't show any APIM updates for me either and I have applied all updates. I'm not sure if something is wrong or if there isn't an update for my APIM hardware. I also haven't seen a GWM update, either.

mine is Job 1, so that could determine the version level to. Who knows..

 

[Ajzride]

Okay guys, I hope I haven't missed where this has been discussed before, I've been at it for 7 hours today and I've re-read the last 100 pages of the thread and didn't see this. After the IPC update I have a U2100, which is not surprising, but I can't PMI it. The PMI fails every time (i've tried 5 times now).

I am using a mongoose, I ran the checks and they all passed. All my modules updated fine except the IPC.

The only DTCs I have are the IPC U2100 and the TRM I have always had

Here is the self test on the IPC

Once I run the IPC PMI, it tells me to turn off the engine, I find this odd because the progress bar is still climbing on collecting data. However I've let that status bar fill up, and it just wraps around. I've also tried not turning it off, or turning if off and back on, none of those produce a successful result.

As soon as I click OK from the prompt, no matter what I have done, I get a failure message:

Procedures Unsuccessful - GetFilesForPMI

Exception getting flash part numbers.

I'm really stumped on this one, hoping someone has an idea. I was hoping to get my F150 and Mach-E done non a 2-day license, but at this pace I'll be lucky just to get the truck done.

Thanks for any input.

 

[Snakebitten]

You’re even with me now.

I was completely up to date just a few days ago. I thought this latest GWM and APIM update that came after the package-CCM/PSCM/IPMA was only for BC trucks. I guess we all get them all?

Did your Bluecruise kick in today?

By the way, I hesitate to say this publicly, but the APIM update that I just did never popped up on the Sync screen to tell me it was safe to remove the USB stick. But I felt like it was OK to since the version number obviously increased. I shut the truck down. Pulled the stick. Started the truck, inserted the stick back into laptop, and told FDRS it was a success. FDRS ran the file verification and stated "passed" for I believe 5 files?

I am not saying to do what I did. But I have noticed inconsistencies between certain updates and am less rigid than I was when I first started doing this.

I never pull the stick out of the truck until I shut it down, but that's twice I have decided to tell FDRS that I succeeded even though the instructions on the FDRS screen were not 100% accurate about the Sync screen.

 

[Jesse-Infotainment]

Okay guys, I hope I haven't missed where this has been discussed before, I've been at it for 7 hours today and I've re-read the last 100 pages of the thread and didn't see this. After the IPC update I have a U2100, which is not surprising, but I can't PMI it. The PMI fails every time (i've tried 5 times now).

I am using a mongoose, I ran the checks and they all passed. All my modules updated fine except the IPC.

The only DTCs I have are the IPC U2100 and the TRM I have always had

Here is the self test on the IPC

Once I run the IPC PMI, it tells me to turn off the engine, I find this odd because the progress bar is still climbing on collecting data. However I've let that status bar fill up, and it just wraps around. I've also tried not turning it off, or turning if off and back on, none of those produce a successful result.

As soon as I click OK from the prompt, no matter what I have done, I get a failure message:

Procedures Unsuccessful - GetFilesForPMI

Exception getting flash part numbers.

I'm really stumped on this one, hoping someone has an idea. I was hoping to get my F150 and Mach-E done non a 2-day license, but at this pace I'll be lucky just to get the truck done.

Thanks for any input.

I would wait until tomorrow.. Try then.

 

[Snakebitten]

Edit: Jesse posted while I was typing.
I'm guessing his suggestion is REALLY what my final suggestion below is meant to be.

@Ajzride

That PMI description sounds exactly like my nano experience with the IPC was.
The Mongoose PMI went perfect and both the IPC and TRM dtc's finally disappeared.
(The Last orange or purple I have seen, thankfully)

Did you run those Mongoose tests after you activated it?
Did you have good voltage at the PMI moment?
And maybe try driving the truck a few minutes and then a fresh FDRS session, network scan, and then PMI?

 

[Platinum Peasant]

So my running boards will not respond to anything. The DSM logging does not show running boards as a testing object. They show up on my car console and I can change the settings for them, but I can find no module in FDRS that actually controls them.

I have run the configuration several times, but obviously to no avail. Same with the self test.

I have PMId it a few times and not joy either.

I am using a Mongoose.

Suggestions?

My truck is doing the exact same thing. Wont respond to PMI of the DSM and self test wont resolve the issue. Still trying to figure it out, gonna try a new computer tomorrow. I do want to ask tho, when you do the PMI, does the IPC shut off and do you see FDRS writing "blocks" during the PMI? When I do mine, it jumps straight to configuration, no matter if i pick "replaced" or "original" module.

 

[Ajzride]

Did you run those Mongoose tests after you activated it?

Yes and all 3 passed

Did you have good voltage at the PMI moment?

13.1V

EDIT: I just realized FRDS is showing 14.5V during the PMI. I am using the recommended charge in power supply mode, and has been pretty steady at 13.1 all day. That 14.5V seems off. Perhaps I will try it with the PS disconnected since I have a full charge just for kicks.

And maybe try driving the truck a few minutes and then a fresh FDRS session, network scan, and then PMI?

I took a 15 minute drive between PMI attempt numbers 3 and 4 so the PSCM would calibrate, didn't seem to help. The one thing I did not do was reboot the laptop during the drive (I did close FDRS). I'm trying a reboot of the car and the truck (20 minutes, key away and all doors closed) and I guess that is the last thing I can try tonight.

 

[Snakebitten]

I'm guessing there's strategy and reason for what Jesse suggested.
So if your last attempt fails to work, just let it go, but don't be discouraged.

I lived with that DTC for quite a while myself. I admit to a mini-celebration when they both cleared.

Your moment is coming

 

[Jesse-Infotainment]

My truck is doing the exact same thing. Wont respond to PMI of the DSM and self test wont resolve the issue. Still trying to figure it out, gonna try a new computer tomorrow. I do want to ask tho, when you do the PMI, does the IPC shut off and do you see FDRS writing "blocks" during the PMI? When I do mine, it jumps straight to configuration, no matter if i pick "replaced" or "original" module.

PMI wont always write blocks. That is only if the module it is reading is out of date or the module is detected as missing a file. Sounds like Ford had a bad DSM update released. I can side load files and load it to the older files if push came to shove. You would have to send the module though..

 

[Ajzride]

I'm guessing there's strategy and reason for what Jesse suggested.
So if your last attempt fails to work, just let it go, but don't be discouraged.

I lived with that DTC for quite a while myself. I admit to a mini-celebration when they both cleared.

Your moment is coming

If it was just a DTC, I would probably would be fine, but it seems like that is holding me back from the getting the GTWY update I need for BC to work. Pretty disappointing to buy the license and not get it working, I've literally be on the verge of trading it a few times I've been so frustrated with not having it.

 

[Platinum Peasant]

PMI wont always write blocks. That is only if the module it is reading is out of date or the module is detected as missing a file. Sounds like Ford had a bad DSM update released. I can side load files and load it to the older files if push came to shove. You would have to send the module though..

Ive seen you mention "side loading" files a few times, is that module removal and loading it manually like you had in the video you posted? The DSM self test works everything except the running boards. Im not sure what caused it to fail tho. I unplugged my battery and they havent worked since then, updating the DSM didnt bring them back either. Anyone know if there is a "learn" or reset procedure for the running boards??

 

[Shoebox72069]

100% had this same issue yesterday. CANBUS IPC failed after it wrote everything and was on the last steps of the configuration when it failed. Left me with a U2100 and PMI was no joy (Nano user).

The IPC update did eventually go away but the DTC remained. Much to my surprise after a GWY update this morning it magically went away.

Bummer to see it even happening with a Mongoose...as I have another IPC sitting in the queue and I splurged for a Mongoose to get it all topped off. The tiny bit of driving I did with the U2100 I didn't notice anything off.

Hope it clear for you soon. If you PMI'ed a couple times with no success I'd leave it alone as other users have indicated you could have even more breakage.

 

[speedracercjr]

Oops. I guess my sweet talk is still working.

Dang that was fast for an 800magabyte update

Same as me and I’m on BC now. You should have cameras in the sidebar without Forscan changes. That’s all I noticed different other than my BC option.