Unresponsive ECM on a 2003 S-Type 4.2L s/c (Fixed)
Senior Member
Joined: Jan 2011
Posts: 386
Likes: 32
From: Indio CA
I read the bulletin 1-186 Issue date: 11/04 - Great stuff in here, confirming some of my suspicions about the VID block.
I reinstalled the original ECM. Then checked the VID block - no communications with the ECM.
I started the IDS/SDD (software level DVD128) session with my Mongoose JLR (a SAE J2534 device) disconnected from the vehicle. Then I input the full 17 digit VIN and hit enter, based on the VIN it initiated a Legacy IDS session. I then answered no to the question, "do you wish to read the configuration from the vehicle", this forced IDS to retrieve the "as built" VID from the hard drive (a tip I garnered from the info in the bulletin). I checked the descriptions listed for equipment level and accepted them as correct. The IDS then prompted to read DTCs, I answered no and then at this point connected the IDS/Mongoose JLR to the car.
Now with a charger connected to the car set for 13.0V, I initiated a "Configure Existing Module" routine and selected the Engine Controller. I followed the prompts until communication failed out, and the IDS eventually prompted the "Rectification Procedure". Now I have performed this rectification procedure on this module before with no joy, but thanks to the bulletin when the time came to disconnect the negative battery cable I shorted together the two cables while they were disconnected. After the prompt to reconnect I followed the onscreen prompts as presented and ended up with a reported successful reflash! Still no start though, so I initiated the "Immobilisation Reset", and viola the car fired up! Next I initiated the report on all the vehicle control modules and happily the ECM was reorting the correct VIN. You have no idea how happy that made me!
I then successfully programmed the TCM to address the P0610 code. All I need to do now is perform the Transmission Adaption Routine.
I then repeated the ECM Reflash/Rectification routine on the other locked ECM, and successfully recovered that one too!
So, in closing, I learned that the VID block is very important to get right. That connecting the cables together during the disconnect portion of the "ECM Rectification" is necessary to succeed. Finally I learned never to flash a Transmission Control Module when the VID stored in the ECM is incorrect!
Thanks for your help, I hope my summary makes good reading!
Cheers
Brian
I reinstalled the original ECM. Then checked the VID block - no communications with the ECM.
I started the IDS/SDD (software level DVD128) session with my Mongoose JLR (a SAE J2534 device) disconnected from the vehicle. Then I input the full 17 digit VIN and hit enter, based on the VIN it initiated a Legacy IDS session. I then answered no to the question, "do you wish to read the configuration from the vehicle", this forced IDS to retrieve the "as built" VID from the hard drive (a tip I garnered from the info in the bulletin). I checked the descriptions listed for equipment level and accepted them as correct. The IDS then prompted to read DTCs, I answered no and then at this point connected the IDS/Mongoose JLR to the car.
Now with a charger connected to the car set for 13.0V, I initiated a "Configure Existing Module" routine and selected the Engine Controller. I followed the prompts until communication failed out, and the IDS eventually prompted the "Rectification Procedure". Now I have performed this rectification procedure on this module before with no joy, but thanks to the bulletin when the time came to disconnect the negative battery cable I shorted together the two cables while they were disconnected. After the prompt to reconnect I followed the onscreen prompts as presented and ended up with a reported successful reflash! Still no start though, so I initiated the "Immobilisation Reset", and viola the car fired up! Next I initiated the report on all the vehicle control modules and happily the ECM was reorting the correct VIN. You have no idea how happy that made me!
I then successfully programmed the TCM to address the P0610 code. All I need to do now is perform the Transmission Adaption Routine.
I then repeated the ECM Reflash/Rectification routine on the other locked ECM, and successfully recovered that one too!
So, in closing, I learned that the VID block is very important to get right. That connecting the cables together during the disconnect portion of the "ECM Rectification" is necessary to succeed. Finally I learned never to flash a Transmission Control Module when the VID stored in the ECM is incorrect!
Thanks for your help, I hope my summary makes good reading!
Cheers
Brian
Senior Member
Joined: Jan 2011
Posts: 386
Likes: 32
From: Indio CA
I read the bulletin 1-186 Issue date: 11/04 - Great stuff in here, confirming some of my suspicions about the VID block.
I reinstalled the original ECM. Then checked the VID block - no communications with the ECM.
I started the IDS/SDD (software level DVD128) session with my Mongoose JLR (a SAE J2534 device) disconnected from the vehicle. Then I input the full 17 digit VIN and hit enter, based on the VIN it initiated a Legacy IDS session. I then answered no to the question, "do you wish to read the configuration from the vehicle", this forced IDS to retrieve the "as built" VID from the hard drive (a tip I garnered from the info in the bulletin). I checked the descriptions listed for equipment level and accepted them as correct. The IDS then prompted to read DTCs, I answered no and then at this point connected the IDS/Mongoose JLR to the car.
Now with a charger connected to the car set for 13.0V, I initiated a "Configure Existing Module" routine and selected the Engine Controller. I followed the prompts until communication failed out, and the IDS eventually prompted the "Rectification Procedure". Now I have performed this rectification procedure on this module before with no joy, but thanks to the bulletin when the time came to disconnect the negative battery cable I shorted together the two cables while they were disconnected. After the prompt to reconnect I followed the onscreen prompts as presented and ended up with a reported successful reflash! Still no start though, so I initiated the "Immobilisation Reset", and viola the car fired up! Next I initiated the report on all the vehicle control modules and happily the ECM was reorting the correct VIN. You have no idea how happy that made me!
I then successfully programmed the TCM to address the P0610 code. All I need to do now is perform the Transmission Adaption Routine.
I then repeated the ECM Reflash/Rectification routine on the other locked ECM, and successfully recovered that one too!
So, in closing, I learned that the VID block is very important to get right. That connecting the cables together during the disconnect portion of the "ECM Rectification" is necessary to succeed. Finally I learned never to flash a Transmission Control Module when the VID stored in the ECM is incorrect!
Thanks for your help, I hope my summary makes good reading!
Cheers
Brian
I reinstalled the original ECM. Then checked the VID block - no communications with the ECM.
I started the IDS/SDD (software level DVD128) session with my Mongoose JLR (a SAE J2534 device) disconnected from the vehicle. Then I input the full 17 digit VIN and hit enter, based on the VIN it initiated a Legacy IDS session. I then answered no to the question, "do you wish to read the configuration from the vehicle", this forced IDS to retrieve the "as built" VID from the hard drive (a tip I garnered from the info in the bulletin). I checked the descriptions listed for equipment level and accepted them as correct. The IDS then prompted to read DTCs, I answered no and then at this point connected the IDS/Mongoose JLR to the car.
Now with a charger connected to the car set for 13.0V, I initiated a "Configure Existing Module" routine and selected the Engine Controller. I followed the prompts until communication failed out, and the IDS eventually prompted the "Rectification Procedure". Now I have performed this rectification procedure on this module before with no joy, but thanks to the bulletin when the time came to disconnect the negative battery cable I shorted together the two cables while they were disconnected. After the prompt to reconnect I followed the onscreen prompts as presented and ended up with a reported successful reflash! Still no start though, so I initiated the "Immobilisation Reset", and viola the car fired up! Next I initiated the report on all the vehicle control modules and happily the ECM was reorting the correct VIN. You have no idea how happy that made me!
I then successfully programmed the TCM to address the P0610 code. All I need to do now is perform the Transmission Adaption Routine.
I then repeated the ECM Reflash/Rectification routine on the other locked ECM, and successfully recovered that one too!
So, in closing, I learned that the VID block is very important to get right. That connecting the cables together during the disconnect portion of the "ECM Rectification" is necessary to succeed. Finally I learned never to flash a Transmission Control Module when the VID stored in the ECM is incorrect!
Thanks for your help, I hope my summary makes good reading!
Cheers
Brian
Veteran Member
Joined: May 2009
Posts: 27,519
Likes: 4,910
From: Yorkshire, England
Looks like you should try the right forum.
Junior Member
Joined: Apr 2012
Posts: 23
Likes: 8
From: NICE FRANCE
Config F
Originally Posted by 03Xtype View Post
the Config F stays on. I'm running out of idea's.
I had this problem few times and always resolved after erasing all DTCs, removed the key for 30 seconds, and re-scanning the DTCs.
Hope this help!
the Config F stays on. I'm running out of idea's.
I had this problem few times and always resolved after erasing all DTCs, removed the key for 30 seconds, and re-scanning the DTCs.
Hope this help!
Junior Member
Joined: Jan 2019
Posts: 28
Likes: 6
From: Stockport
Realise that this is resurrecting a very old thread (but an incredibly informative one) but here goes:
CONFIG F is saying that there is a mismatch on the module programming. A normal 'clear codes' is unlikely to help (but I'm willing to be proved wrong). What is required is a re-flash of the 'bad' module. In all of the lists I've seen F is missing but I was reliably informed that it is the FEM that is at fault. You would need to re-flash the General module(s) to cure it.
CONFIG F is saying that there is a mismatch on the module programming. A normal 'clear codes' is unlikely to help (but I'm willing to be proved wrong). What is required is a re-flash of the 'bad' module. In all of the lists I've seen F is missing but I was reliably informed that it is the FEM that is at fault. You would need to re-flash the General module(s) to cure it.
Veteran Member
Joined: May 2009
Posts: 27,519
Likes: 4,910
From: Yorkshire, England
Turns out it's an XJ!
https://www.jaguarforums.com/forum/x...denied-213409/
Please would any future posters use the right forum!!
Also, CONFIG F doesn't appear to be an S-Type thing at all.
https://www.jaguarforums.com/forum/x...denied-213409/
Please would any future posters use the right forum!!
Also, CONFIG F doesn't appear to be an S-Type thing at all.
Junior Member
Joined: Jan 2019
Posts: 28
Likes: 6
From: Stockport
At the risk of upsetting a veteran member.
I came across the thread via a google search as it pertained to my issue on my 2003 X350 so age of the thread is not relevant here, nor is model, as the information is a lot newer than my motor. What is relevant is that these cars throw up messages and google searches bring the threads back alive because of that, they are therefore not 'irrelevant'. The methods described here have a direct bearing on how the diagnostic tools are used, across cars with similar electrics.
Previous searches (a few years ago) turned up no hits for the CONFIG F message so I figured I would put in my 2 pennies worth regarding the message in case any other desperate soul found the thread only to be dashed on the rocks of despair when no answer or direction was forthcoming.
@mods: If this is inappropriate please delete.
I came across the thread via a google search as it pertained to my issue on my 2003 X350 so age of the thread is not relevant here, nor is model, as the information is a lot newer than my motor. What is relevant is that these cars throw up messages and google searches bring the threads back alive because of that, they are therefore not 'irrelevant'. The methods described here have a direct bearing on how the diagnostic tools are used, across cars with similar electrics.
Previous searches (a few years ago) turned up no hits for the CONFIG F message so I figured I would put in my 2 pennies worth regarding the message in case any other desperate soul found the thread only to be dashed on the rocks of despair when no answer or direction was forthcoming.
@mods: If this is inappropriate please delete.
Veteran Member
Joined: May 2009
Posts: 27,519
Likes: 4,910
From: Yorkshire, England
Well all I wanted (with what was meant to be a final post) was to be sure that if a bad web search brings someone to this wrong thread (*) they will see it is the wrong thread and as they won't have an S-Type they should immediately go elsewhere.
I still want that.
(*) oddly when I search it takes me to sensible threads for such as XJ cars, which DO have this fault on occasion - this thread wasn't even on the first page of results
I still want that.
(*) oddly when I search it takes me to sensible threads for such as XJ cars, which DO have this fault on occasion - this thread wasn't even on the first page of results
Last edited by JagV8; Jan 31, 2019 at 10:40 AM.
Member
Joined: Jul 2014
Posts: 49
Likes: 2
From: kampala
I read the bulletin 1-186 Issue date: 11/04 - Great stuff in here, confirming some of my suspicions about the VID block.
I reinstalled the original ECM. Then checked the VID block - no communications with the ECM.
I started the IDS/SDD (software level DVD128) session with my Mongoose JLR (a SAE J2534 device) disconnected from the vehicle. Then I input the full 17 digit VIN and hit enter, based on the VIN it initiated a Legacy IDS session. I then answered no to the question, "do you wish to read the configuration from the vehicle", this forced IDS to retrieve the "as built" VID from the hard drive (a tip I garnered from the info in the bulletin). I checked the descriptions listed for equipment level and accepted them as correct. The IDS then prompted to read DTCs, I answered no and then at this point connected the IDS/Mongoose JLR to the car.
Now with a charger connected to the car set for 13.0V, I initiated a "Configure Existing Module" routine and selected the Engine Controller. I followed the prompts until communication failed out, and the IDS eventually prompted the "Rectification Procedure". Now I have performed this rectification procedure on this module before with no joy, but thanks to the bulletin when the time came to disconnect the negative battery cable I shorted together the two cables while they were disconnected. After the prompt to reconnect I followed the onscreen prompts as presented and ended up with a reported successful reflash! Still no start though, so I initiated the "Immobilisation Reset", and viola the car fired up! Next I initiated the report on all the vehicle control modules and happily the ECM was reorting the correct VIN. You have no idea how happy that made me!
I then successfully programmed the TCM to address the P0610 code. All I need to do now is perform the Transmission Adaption Routine.
I then repeated the ECM Reflash/Rectification routine on the other locked ECM, and successfully recovered that one too!
So, in closing, I learned that the VID block is very important to get right. That connecting the cables together during the disconnect portion of the "ECM Rectification" is necessary to succeed. Finally I learned never to flash a Transmission Control Module when the VID stored in the ECM is incorrect!
Thanks for your help, I hope my summary makes good reading!
Cheers
Brian
I reinstalled the original ECM. Then checked the VID block - no communications with the ECM.
I started the IDS/SDD (software level DVD128) session with my Mongoose JLR (a SAE J2534 device) disconnected from the vehicle. Then I input the full 17 digit VIN and hit enter, based on the VIN it initiated a Legacy IDS session. I then answered no to the question, "do you wish to read the configuration from the vehicle", this forced IDS to retrieve the "as built" VID from the hard drive (a tip I garnered from the info in the bulletin). I checked the descriptions listed for equipment level and accepted them as correct. The IDS then prompted to read DTCs, I answered no and then at this point connected the IDS/Mongoose JLR to the car.
Now with a charger connected to the car set for 13.0V, I initiated a "Configure Existing Module" routine and selected the Engine Controller. I followed the prompts until communication failed out, and the IDS eventually prompted the "Rectification Procedure". Now I have performed this rectification procedure on this module before with no joy, but thanks to the bulletin when the time came to disconnect the negative battery cable I shorted together the two cables while they were disconnected. After the prompt to reconnect I followed the onscreen prompts as presented and ended up with a reported successful reflash! Still no start though, so I initiated the "Immobilisation Reset", and viola the car fired up! Next I initiated the report on all the vehicle control modules and happily the ECM was reorting the correct VIN. You have no idea how happy that made me!
I then successfully programmed the TCM to address the P0610 code. All I need to do now is perform the Transmission Adaption Routine.
I then repeated the ECM Reflash/Rectification routine on the other locked ECM, and successfully recovered that one too!
So, in closing, I learned that the VID block is very important to get right. That connecting the cables together during the disconnect portion of the "ECM Rectification" is necessary to succeed. Finally I learned never to flash a Transmission Control Module when the VID stored in the ECM is incorrect!
Thanks for your help, I hope my summary makes good reading!
Cheers
Brian
Junior Member
Joined: Apr 2012
Posts: 23
Likes: 8
From: NICE FRANCE
Hello!
I was with a X350 4.2L with transmission fault, Restricted performances BUT no DTC on the transmission!! The only DTC was if I remember well P1643 no communication between TCM and ECM. (some time with this Can bus error too with ABS or Instrument cluster.
When I was starting, if I was needing to pull the accelerator the car was going in limp mode and was fixed in gear 3. If this was happening after few meters, the transmission was going in gear 5 (no light on the J gate etc.) So, I drove one year in gear 3 in city, gear 5 on speedway!!
I tried the ABS connector, Instrument cluster connectors, then controlled the can bus, I also connected the TCM can bus directly to the ECM bypassing the connector, changed TCM oil, verified level few times, reseted the TCM adaptation, etc... always the same! I tried to change the Valve body for another rebuilded, still the same problem! As the problem was CAN bus communication, between TCM and ECM I changed the valve body + TCM coming from another car and installed them in my car! Same problem again!!
Finally, I found why the transmission was jerky and limp mode and no CAN bus communication. It was exactly what I was meaning since few times.... ECM Torque signal fault. It was the ignition coils!! I changed all my coil, and my car worked normally!!! Big power, no can bus fault, no misfires etc. A new car!! Reason I was meaning, was when exiting from my underground box I was needing more power, so pedal going down and ... voila! communication fault, gear 3 or 5 blocked, no lights on the J Gate!
So, I was thinking the ECM is sending a Throttle position sensor which is like big acceleration, because as he coils was not firing correctly, the Transmission was thinking I needed big power!!
So, in conclusion, if the J-gate (sport button flash or stay fixed when you turn the key) or you have the Can bus error between the ECM and TCM then Limp mode etc. look at your coils, candles etc... principaly if you have DTC with misfires. Hope this could save money and time to many peoples with transmission problems!
I must say, that in the past I changed my ignitions coils few times, but no original coils, some aftermarket. Transmission worked one week / 2000 kms, then failed!
Now I bought more expansives coils from LUCAS (www.rld-autos.com) 57,48 €
and I have my 300 HP and transmission very smooth!
So, be carrefull of ship Ignitions coils....
I was with a X350 4.2L with transmission fault, Restricted performances BUT no DTC on the transmission!! The only DTC was if I remember well P1643 no communication between TCM and ECM. (some time with this Can bus error too with ABS or Instrument cluster.
When I was starting, if I was needing to pull the accelerator the car was going in limp mode and was fixed in gear 3. If this was happening after few meters, the transmission was going in gear 5 (no light on the J gate etc.) So, I drove one year in gear 3 in city, gear 5 on speedway!!
I tried the ABS connector, Instrument cluster connectors, then controlled the can bus, I also connected the TCM can bus directly to the ECM bypassing the connector, changed TCM oil, verified level few times, reseted the TCM adaptation, etc... always the same! I tried to change the Valve body for another rebuilded, still the same problem! As the problem was CAN bus communication, between TCM and ECM I changed the valve body + TCM coming from another car and installed them in my car! Same problem again!!
Finally, I found why the transmission was jerky and limp mode and no CAN bus communication. It was exactly what I was meaning since few times.... ECM Torque signal fault. It was the ignition coils!! I changed all my coil, and my car worked normally!!! Big power, no can bus fault, no misfires etc. A new car!! Reason I was meaning, was when exiting from my underground box I was needing more power, so pedal going down and ... voila! communication fault, gear 3 or 5 blocked, no lights on the J Gate!
So, I was thinking the ECM is sending a Throttle position sensor which is like big acceleration, because as he coils was not firing correctly, the Transmission was thinking I needed big power!!
So, in conclusion, if the J-gate (sport button flash or stay fixed when you turn the key) or you have the Can bus error between the ECM and TCM then Limp mode etc. look at your coils, candles etc... principaly if you have DTC with misfires. Hope this could save money and time to many peoples with transmission problems!
I must say, that in the past I changed my ignitions coils few times, but no original coils, some aftermarket. Transmission worked one week / 2000 kms, then failed!
Now I bought more expansives coils from LUCAS (www.rld-autos.com) 57,48 €
and I have my 300 HP and transmission very smooth!
So, be carrefull of ship Ignitions coils....
Senior Member
Joined: Jan 2025
Posts: 115
Likes: 4
I'm having a similar issue
Hello, Maybe the person who solved this issue can assist me? I tried re configuring my ECM also and now my car doesn't start. Idk what else to do. When it comes to the re configuring part, it asks something about waiting "2 clicks and doing it under 10 seconds". I may be doing this part completely wrong and i'm not exactly sure how to do it. What did you do exactly?
Senior Member
Joined: Jan 2025
Posts: 115
Likes: 4
I believe I’m using Version 131 VMware SDD/IDS
Junior Member
Joined: Jan 2019
Posts: 28
Likes: 6
From: Stockport
This is going back a few years for me, but I remember the panic at the time.
On the Diagnostics screen, before clicking on recommendations after doing a scan, are any of the modules showing as the white X on a red background icon?
Have you run the the SDD option to get all of the current module details (forgive me for forgetting its name)? This should list out the version numbers of all of the modules, but it also saves a safe version of the firmware onto your hard drive.
For the car to start all of the ducks have to be lined up. The security information is stored in several parts in different modules and they all have to agree. The important ones are the Door module, dash module and ECM.
If you can can source version 1.6.2 of SDD it's much quicker and can also download the the modules if required. You need to source one that can be run online (unlike the 131). Updating the ECM using 131 on my X350 4.2 took 1.5 hours, so if you kick it off don't quit it. You WILL need to find some way of backing up your battery as you can not run that with the engine running. I used a fully charged spare battery, which was also being trickle charged. I've since purchased one of the these.
On the Diagnostics screen, before clicking on recommendations after doing a scan, are any of the modules showing as the white X on a red background icon?
Have you run the the SDD option to get all of the current module details (forgive me for forgetting its name)? This should list out the version numbers of all of the modules, but it also saves a safe version of the firmware onto your hard drive.
For the car to start all of the ducks have to be lined up. The security information is stored in several parts in different modules and they all have to agree. The important ones are the Door module, dash module and ECM.
If you can can source version 1.6.2 of SDD it's much quicker and can also download the the modules if required. You need to source one that can be run online (unlike the 131). Updating the ECM using 131 on my X350 4.2 took 1.5 hours, so if you kick it off don't quit it. You WILL need to find some way of backing up your battery as you can not run that with the engine running. I used a fully charged spare battery, which was also being trickle charged. I've since purchased one of the these.