2013 MKZ DDM Flash Issue
3LN6L2LU0DR824450 Came in for not going in gear, customer said he had to cycle ignition switch several times to get car into gear or to move. Found P16E4-00 stored in PCM. Known tsb to reflash pcm for this code.
Used autel j2534 maxiflash pro, fjds and midtronics batt maintainer to reflash PCM, TRCM, SOBDM, BECM, and ABS modules(as per fjds generated list of modules that needed flash at this time.) Flashing went fine and cleared all stored u-codes when done. Performed ivd relearn when done also. all modules clean.
Performed test drive and full function test when done all showed fine. Moved car in lot before calling customer and got a headlight message on cluster, scanned got B1088-83 stored in HCM. Found tsb for reflashing HCM for this code also. Flashed HCM and decided to manually check all other modules for updates. I got to DDM and tried to reflash. Came up with vcm lost comm message on fjds. Instructed me to do a PMI to resolve issue. PMI didnt take as well, I tried clearing all codes and resetting vcm and fjds but same issue.
I’m still a rookie at flashing but have done many fords and 6 other manufacturers all with same hardware. Looking for input.
Chris, After having issues with the Autel J2534 I quit using it. Last I checked it was not approved by any OEM for flashing. This would suggest it has not been tested to work. Using an unapproved tool is quite risky. You may have success 99 times but the 100th can bite you. We switched to VCMII / IDS way back because we needed more features. The last 3 iterations of IDS have been buggy. This…
Thank you for reply i am trying to find someone with ids if not we will have to bite the bullet and ship to dealer. Anyone had luck doing a master reset for issues like this?
If you are doing that much work with Ford products, I would recommend that you invest in a Ford IDS. Your flashing worries will almost be gone and you will love the great scan tool capabilities.
And the annual subscription is the same price
What version of FJDS are you using? Is this comms issue isolated to the DDM? Some modules even though listed may not communicate through FJDS with a J2534 tool depending on network. The DDM is on MSCAN. Your passthru may be your limitation.
FJDS version 115.01 , it looks like just DDM there is bunch of other codes stored in various modules but all pertain to comm with DDM. Passthru let me do 6 other modules besides PCM without issue. I should have not gotten greedy updating other modules and stopped with just HCM but didnt want to return to customer and get the phone call that something else came up. Its weird thou as my passthru…
If the module failed during programming, the original session may be required to recover it. Session files are located in C:\Programdata\fordmotorcompany\fjds\sessions. These files should include a partial vin (maybe 6+ files?). If the module is blanked after the erase procedure, copying these files to the computer used for recovery programming may be a solution. FJDS and IDS session files are…
thank you for the time and all the great info . I will look into all of this and report back. Just when i thought it wasn't going to be frantic friday!!
Hi Chris: It was an educational Friday, anyhow.. You learned that reprogramming a module is like throwing a football. When you throw a football, 3 things can happen. Two are not good. When you program a module, 3 things can happen. Two are not good. If you have a reason to go there, that's one thing. Just because a cal file is available is not a reason to go there. Just something to keep in…