Unsolvable Automatic Window Issue (SOLVED w/ FORScan)

[MachoManBroncoSavage]

Hey folks I need to pick your brains on this window issue. I have successfully done the window teach procedure from the manual before, but this time it won't let me do the teach because the window won't stay at the top of the frame long enough for it to happen. I've searched the forum, searched Google, an TouTube and everybody generally does the same method. I've seen a couple variations of using the first detent versus a second detent, holding down for 3 seconds, 5 seconds, 10 seconds, engine on or engine off, etc. I've got an appointment with Ford in a couple weeks to look at it but as you know if the window is all the way up you can't open the door without risking damage to the window. I'm sort of comfortable with forscan if that can help. At this point the part is like 50 bucks from AutoZone but it's the time and effort to change the thing that I don't want to deal with and honestly I'm pretty pissed that Ford can't even look at this for another couple weeks much less have the parts or anything else ready.

Please tell me one of you has the magic button combination!

A shot in the dark here. Maybe there is obstruction or friction that is blocking the window from going up. Maybe it’s possible to lubricate and tracks the window slides in? Then again, there doesn’t seem to be any audible squeaking in your video.

Sponsored

 

[Ukko Wildtrak]

I had the same issues in my 06 beemer back in the day, but it was a dumb enough system to let the learn process work regardless of the currently taught limits. This software is crazy.

A shot in the dark here. Maybe there is obstruction or friction that is blocking the window from going up. Maybe it’s possible to lubricate and tracks the window slides in? Then again, there doesn’t seem to be any audible squeaking in your video.

I did wonder about this, so I lubed up the window. Also, it's not seeing the "slow down" area as it gets close to the top like the other windows do. Just full speed then retract.

 

[Ukko Wildtrak]

Ready to have my mechanic install rollup/down handles now. Won't be a problem once I get the door off.

I'm taking the top off today so truly this might not be a big issue but it's pretty wild that there's no faults, no DTCs, or anything, but it still doesn't work and the factory teach method is being overridden by the safety loop. Must be some of that ChatGPT or Copilot code left over!

 

[Headsong]

Yeah, mine has actually worked for maybe two weeks. I hate picking up Rx's/going to the bank....or just wanting to chat up someone outside, figuring I'll spend the next half hour trying to get it to work again. . .not aggravated enough to go to dealer, and they'll likely tell me they can't look at it for a week. Not leaving it for that.

 

[battering ram]

Open the door
Raise the window.
Does it work correct now?

id guess it’s hitting weather stripping and the window thinks its a kids finger stuck in the window

 

[B-Dog15]

Mine did this when I first got it. As crazy as it sounds you literally need to just keep trying the window reset method until it lets you hold it up. Mine literally took probably 10-15 minutes of me constantly trying it in order for it to let me do the reset process.

 

[JediMcMuffin]

Mine comes and goes with this. Seems to happen the most when I use the remote to lower the windows. Sometimes relearn is quick and easy, sometimes its painful. It doesn't seem to matter if the door is open or closed when I do it.

 

[mikeofthenorth]

I had this exact same issue, self resets did not help me either. It started on my driver's window only the morning after an August firmware update, so I was very convinced it was not mechanical and rather a firmware update induced bug.

I had to go through 3 local dealerships to find one who would listen to my explanation and look at it without preliminarily charging me a diagnostic fee. They told me that there is a Technical Service Bulletin/Advisory and they did some sort of reset/re-pair different than the typical reset procedure, it has been fixed since and was covered as a warranty item, no charge.

 

[Gluestick]

I had this exact same issue, self resets did not help me either. It started on my driver's window only the morning after an August firmware update, so I was very convinced it was not mechanical and rather a firmware update induced bug.

I had to go through 3 local dealerships to find one who would listen to my explanation and look at it without preliminarily charging me a diagnostic fee. They told me that there is a Technical Service Bulletin/Advisory and they did some sort of reset/re-pair different than the typical reset procedure, it has been fixed since and was covered as a warranty item, no charge.

Oh wish you had more details!

 

[Ukko Wildtrak]

Over the weekend I did take about 15 straight mins to just continuously do the relearn and no luck and no behavior change in the window movement. I did try door open and door closed again and truck running and off.

Since there was little I could do, I keep going back to ForScan since I can see the module state. I pulled some PIDs for the DDM and could see that the LOSS_INI_REAR_DDM pid was showing: Windows Position Counts Above Maximum Position and DR_WINDSTAT was Not Learned. I could not get this to change no matter the procedure. However since there were no DTCs, I knew the module was fine, just stuck in a safety loop. Search didnt bring much more than I had before, but I happened to ask the right question to Copilot and ended up figuring out a fix.

In ForScan I pulled up the DDM in the Wrench Menu and the only option is for me to "Reboot Module." I selected this and the warning popped up and I left the warning on the screen.

To get the DDM to wake up and look for the learn signal, I manually bumped the window up to the top, then pressed down to the first detent and held it there. As the window was moving down and, I clicked OK on that safety popup and it reset WHILE I was holding the button. the logic was that the current spike at the bottom of travel would be pulling about the same time the module was reset and that *SHOULD* corrupt the modules memory and make it look for the Learn.

This changed the State of LOSS_INI_REAR_DDM to Moving Reset. DR_WINDSTAT remained unchanged at Not Learned. This is the key to get the module to learn anything.

At this point, the safety that was causing my windows to instantly drop (and preventing the learn procedure) was inactive and I could perform the Relearn. I saw no changes when I did the relearn and this is where Copilot made me nervous, but I FAFO'ed.

Next step ended up being to go to the DDM (as built) and changing 3 blocks
740-05-01 was 4419 | 002B | 01D6 to 4419 | 0000 | 01AB
The rationale for this is that the 2nd block in the address is a status code. Setting it to 0000 lets the module recover from the safety/fault loop. Block 3 is a matching checksum

740-05-02 was 0776 | 02BC | 0089 to 0776 | 02C0 | 008D
Changing the 3rd and 4th characters in the 2nd block to 02 seems to be a standard Ford value that sets the rear window to Init Pending. Block 3 is a matching checksum.

Write All to set the new values

Now I was able to perform the relearn!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

and it worked first try.

Idk if anyone else will find this useful, but this one was a beast for me and now I get to cancel my service appointment!!
Unfortunately, I did not take screenshots as I went, but here is where I made changes and which PID I was using. You can see a lot more PIDs, but I highlighted the two that were important

 

[Beach_Bum]

Over the weekend I did take about 15 straight mins to just continuously do the relearn and no luck and no behavior change in the window movement. I did try door open and door closed again and truck running and off.

Since there was little I could do, I keep going back to ForScan since I can see the module state. I pulled some PIDs for the DDM and could see that the LOSS_INI_REAR_DDM pid was showing: Windows Position Counts Above Maximum Position and DR_WINDSTAT was Not Learned. I could not get this to change no matter the procedure. However since there were no DTCs, I knew the module was fine, just stuck in a safety loop. Search didnt bring much more than I had before, but I happened to ask the right question to Copilot and ended up figuring out a fix.

In ForScan I pulled up the DDM in the Wrench Menu and the only option is for me to "Reboot Module." I selected this and the warning popped up and I left the warning on the screen.

To get the DDM to wake up and look for the learn signal, I manually bumped the window up to the top, then pressed down to the first detent and held it there. As the window was moving down and, I clicked OK on that safety popup and it reset WHILE I was holding the button. the logic was that the current spike at the bottom of travel would be pulling about the same time the module was reset and that *SHOULD* corrupt the modules memory and make it look for the Learn.

This changed the State of LOSS_INI_REAR_DDM to Moving Reset. DR_WINDSTAT remained unchanged at Not Learned. This is the key to get the module to learn anything.

At this point, the safety that was causing my windows to instantly drop (and preventing the learn procedure) was inactive and I could perform the Relearn. I saw no changes when I did the relearn and this is where Copilot made me nervous, but I FAFO'ed.

Next step ended up being to go to the DDM (as built) and changing 3 blocks
740-05-01 was 4419 | 002B | 01D6 to 4419 | 0000 | 01AB
The rationale for this is that the 2nd block in the address is a status code. Setting it to 0000 lets the module recover from the safety/fault loop. Block 3 is a matching checksum

740-05-02 was 0776 | 02BC | 0089 to 0776 | 02C0 | 008D
Changing the 3rd and 4th characters in the 2nd block to 02 seems to be a standard Ford value that sets the rear window to Init Pending. Block 3 is a matching checksum.

Write All to set the new values

Now I was able to perform the relearn!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

and it worked first try.

Idk if anyone else will find this useful, but this one was a beast for me and now I get to cancel my service appointment!!
Unfortunately, I did not take screenshots as I went, but here is where I made changes and which PID I was using. You can see a lot more PIDs, but I highlighted the two that were important

Nice Troubleshooting. Your post should be bookmarked by others who are having issues with the relearn. You might want to copy and share your post to the ForScan Working Spreadsheet as this thread will fall off the radar.

Sponsored