ECU module programming guide using FDRS

[dolsen]

This is usually an indication that a file failed to load and now FDRS doesn’t recognize the state of your system. Can you post the part numbers that show up when you highlight the IPMA?

I'm not entirely certain what you're looking for but here's some info

Sponsored

 

[dolsen]

It's also possible that FDRS went down for maintenance (which happens every Sunday) while you were attempting this update. I would avoid doing any FDRS stuff on Sunday, personally.

Ah I didn't even consider that... I hate that I am now going to lose a whole day with the license. I also have to update my wife's explorer which has 14 updates. I guess it's pretty likely I won't get those done with one license

 

[Ajzride]

Ah I didn't even consider that... I hate that I am now going to lose a whole day with the license. I also have to update my wife's explorer which has 14 updates. I guess it's pretty likely I won't get those done with one license

It's usually only a half day. I can't get in right now to look at my IPMA and compare it to yours, so likely it could just be the server maintenance. Try again after lunch.

 

[dolsen]

It's usually only a half day. I can't get in right now to look at my IPMA and compare it to yours, so likely it could just be the server maintenance. Try again after lunch.

I just now logged on fine, unless I got in right before they shut it down. I guess this gives me time to get the rest of my day going and I’ll come back to the other updates later

 

[Ford4Ever]

From what I understand, a BCM will not update over the air. My question is, will an uninstalled BCM update prevent other OTA updates from installing?

 

[Fordphanatic]

As far as I know it shouldn't stop you from getting OTA updates.

 

[speedracercjr]

From what I understand, a BCM will not update over the air. My question is, will an uninstalled BCM update prevent other OTA updates from installing?

No it will not. Just recently I got 3.5.2 OTA and I've had the BCM sitting in my que to install for months.

 

[dolsen]

I updated 13 of 14 modules for my Explorer ST. For some reason the auto-up does not work on either front window now after updating the DDM and PDM, and I have no idea why. Also the ACM was updated but that update continues to pop up. Is this just a network error on Ford's end?

What can I do about all of the modules showing DTC's? How do I figure out what is wrong with them? I see the self-test feature, but I do not want to screw anything up by doing something weird either. Any help is appreciated

 

[BlackSheep]

I updated 13 of 14 modules for my Explorer ST. For some reason the auto-up does not work on either front window now after updating the DDM and PDM, and I have no idea why. Also the ACM was updated but that update continues to pop up. Is this just a network error on Ford's end?

What can I do about all of the modules showing DTC's? How do I figure out what is wrong with them? I see the self-test feature, but I do not want to screw anything up by doing something weird either. Any help is appreciated

you need to run the windows Initialization to address your windows issues after an update. You will see it in the menu for those modules. The self-test will not hurt anything and will give you the option to clear them.

 

[dolsen]

you need to run the windows calibration to address your windows issues after an update. You will see it in the menu for those modules. The self test will not hurt anything and will give you the option to clear them.

Awesome, that did the trick. This FDRS is finicky though, not sure why but I got an error saying the calibration was unsuccessful for both windows, but the auto up works on both now... but now I am getting DTC's for both rear windows

 

[BlackSheep]

Awesome, that did the trick. This FDRS is finicky though, not sure why but I got an error saying the calibration was unsuccessful for both windows, but the auto up works on both now... but now I am getting DTC's for both rear windows

I would select clear and retest at the top of the screenshot. Also, the correct name is Window Initialization. If you ran the configuration that's okay but you only need to run the initialization.

 

[dolsen]

I would select clear and retest at the top of the screenshot. Also, the correct name is Window Initialization. If you ran the configuration that's okay but you only need to run the initialization.

Thanks, I ran the initialization and it worked beautifully, I cleared and retested twice on the PDM and DDM and the error wouldn’t go away, but nothing stopped working that I could tell. Front rear windows had auto up and down and the rear windows worked as expected. I’m not too worried about the DTC’s, more annoyed than anything

 

[heffer86]

Anyone else loose their camera's at speed ability with the latest 22228 APIM update? When I hit the button now I am just greeted with the rear-view-camera with no option to switch it.

Here are my current values. They match the ForScan sheet to enable cameras at speed. Job 1 Lariat with 360 camera's

APIM
7DO-01-01 xxxx xxxx Fx
7DO-01-04 xxxx EDxx xx

IPMA
706-02-02 xxxB CExx xx

 

[Jesse-Infotainment]

Anyone else loose their camera's at speed ability with the latest 22228 APIM update? When I hit the button now I am just greeted with the rear-view-camera with no option to switch it.

Here are my current values. They match the ForScan sheet to enable cameras at speed. Job 1 Lariat with 360 camera's

APIM
7DO-01-01 xxxx xxxx Fx
7DO-01-04 xxxx EDxx xx

IPMA
706-02-02 xxxB CExx xx

7D0-01-01
XXXX XXXX BDXX

7D0-01-04
XXXX FC2X XX

706-02-01
XXXX FFC4 XXXX

706-02-02
XXXF CEXX XXXX

 

[heffer86]

7D0-01-01
XXXX XXXX BDXX

7D0-01-04
XXXX FC2X XX

706-02-01
XXXX FFC4 XXXX

706-02-02
XXXF CEXX XXXX

Thanks, I give them a try.

Sponsored