Unresponsive ECM on a 2003 S-Type 4.2L s/c (Fixed)
#1
![Default](/forum/images/icons/icon1.gif)
I am dealing with a 2003 S-Type R (4.2L supercharged).
I reflashed the ECM and TCM wanting to have the latest calibrations in each (the ECM to possibly help with the lean codes, and the TCM with an eye to running the trans adaption routine to fix a shift quality issue). Upon trying to restart the car I find that the car wont start.
After trying to reflash and run the immobilisation routine we concluded that the ECM must be dead. We installed a used ECM, ran the immobilisation routine and viola the car started and ran. The message display center indicated a gearbox fault. Upon further investigation a P0610 was found indicating the wrong configuration file was loaded in the TCM. We successfully reflashed the used ECM with new firmware using the "Configure Existing Modules" routine in IDS. The car started after doing this. The only glitch is that when we read the list of modules in the car the ECM reported the VIN from the car it came out of. We re-read the description listed under "Configure New Modules" and decided to try this. To make a long story short, after erroring out, we have ended up with another unresponsive engine controller.
Does anyone know why this is happening? Can these unresponsive modules be recovered? Or are they dead forever?
Can we replace the VIN in the module with the correct one? I have discovered the VID read utility and can load a VID from a previous session but because the module is unresponsive I cannot write it back to the module.
Any assistance would be useful. I would love to find a good resource for info/training on these IDS/SDD units too!
thanks
Brian
I reflashed the ECM and TCM wanting to have the latest calibrations in each (the ECM to possibly help with the lean codes, and the TCM with an eye to running the trans adaption routine to fix a shift quality issue). Upon trying to restart the car I find that the car wont start.
After trying to reflash and run the immobilisation routine we concluded that the ECM must be dead. We installed a used ECM, ran the immobilisation routine and viola the car started and ran. The message display center indicated a gearbox fault. Upon further investigation a P0610 was found indicating the wrong configuration file was loaded in the TCM. We successfully reflashed the used ECM with new firmware using the "Configure Existing Modules" routine in IDS. The car started after doing this. The only glitch is that when we read the list of modules in the car the ECM reported the VIN from the car it came out of. We re-read the description listed under "Configure New Modules" and decided to try this. To make a long story short, after erroring out, we have ended up with another unresponsive engine controller.
Does anyone know why this is happening? Can these unresponsive modules be recovered? Or are they dead forever?
Can we replace the VIN in the module with the correct one? I have discovered the VID read utility and can load a VID from a previous session but because the module is unresponsive I cannot write it back to the module.
Any assistance would be useful. I would love to find a good resource for info/training on these IDS/SDD units too!
thanks
Brian
The following 3 users liked this post by Jagman1984:
![](https://www.jaguarforums.com/forum/images/kirsch/buttons/collapse_tcat.gif)
Top Answer
02-02-2012, 05:03 PM
![Default](/forum/images/icons/icon1.gif)
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
#2
#3
![Default](/forum/images/icons/icon1.gif)
Did you copy and save the original VID block??
Did the battery voltage drop below recommended threshold??
Whenever I clear adaptations or re-flash, I hook up a battery charger. When I worked at the dealer we were advised by Jaguar tech-line to ALWAYS keep a battery charger on the car when configuring/programming.
You should probably download the VID block before you re-configure.
I don't know if the ECM can be saved if a fault occurs during programming.
If you are not a Dealer then you cannot send the VID block to Jaguar engineers to rebuild and re-load onto the ECM.
TSB 1-186 has alot of info. Read pages 4,6,7 & 8 about problems and resolutions.
bob gauff
Did the battery voltage drop below recommended threshold??
Whenever I clear adaptations or re-flash, I hook up a battery charger. When I worked at the dealer we were advised by Jaguar tech-line to ALWAYS keep a battery charger on the car when configuring/programming.
You should probably download the VID block before you re-configure.
I don't know if the ECM can be saved if a fault occurs during programming.
If you are not a Dealer then you cannot send the VID block to Jaguar engineers to rebuild and re-load onto the ECM.
TSB 1-186 has alot of info. Read pages 4,6,7 & 8 about problems and resolutions.
bob gauff
#4
![Default](/forum/images/icons/icon1.gif)
+1
There are lots of warnings to provide external power in addition to the battery - even I've seen them and I don't reflash the things!
Jaguar and/or SPX surely offer courses for IDS/SDD and again I've seen the kind of stuff Bob mentions. For Fords, too, which again have VID blocks.
The lost comms is either a fault in wiring/etc, which sounds intermittent, or voltage dropped. If the programming was part way through I guess you could need a specialist fix. There are ECU repair companies which can probably sort it out (basically, initiate a lower level reflash).
The underlying thing is that there are chunks of replicated vehicle data scattered across several modules. That makes it more robust and assists with anti-theft (e.g. you can't just swap PCM and drive away). It also means you need to choose the IDS actions so that you keep previous data from the car when replacing a module with a non-blank (non-green) one, so as to avoid what you hit.
The above applies to a lot more than just Jaguars.
If you've got the data, once you have a working PCM you can put the data in and be good to go.
One more thought: maybe the PCM has gone into a timed shutdown where it inserts a delay from key on to being willing to talk. That could be another anti-theft measure. You'd expect such a delay to get longer if it thinks further theft-type things have happened. Bob or anothe tech may know if this occurs. If so, you may just need to key on and wait a while before using IDS.
There are lots of warnings to provide external power in addition to the battery - even I've seen them and I don't reflash the things!
Jaguar and/or SPX surely offer courses for IDS/SDD and again I've seen the kind of stuff Bob mentions. For Fords, too, which again have VID blocks.
The lost comms is either a fault in wiring/etc, which sounds intermittent, or voltage dropped. If the programming was part way through I guess you could need a specialist fix. There are ECU repair companies which can probably sort it out (basically, initiate a lower level reflash).
The underlying thing is that there are chunks of replicated vehicle data scattered across several modules. That makes it more robust and assists with anti-theft (e.g. you can't just swap PCM and drive away). It also means you need to choose the IDS actions so that you keep previous data from the car when replacing a module with a non-blank (non-green) one, so as to avoid what you hit.
The above applies to a lot more than just Jaguars.
If you've got the data, once you have a working PCM you can put the data in and be good to go.
One more thought: maybe the PCM has gone into a timed shutdown where it inserts a delay from key on to being willing to talk. That could be another anti-theft measure. You'd expect such a delay to get longer if it thinks further theft-type things have happened. Bob or anothe tech may know if this occurs. If so, you may just need to key on and wait a while before using IDS.
The following users liked this post:
Panthro (03-30-2012)
#5
#6
Join Date: Oct 2007
Location: PHX some of the time
Posts: 117,545
Received 6,330 Likes
on
5,516 Posts
The following users liked this post:
bfsgross (02-02-2012)
#7
![Default](/forum/images/icons/icon1.gif)
I always reflash with a Snap-On "Computer Smart" battery charger connected, so I don't think low voltage level is the issue. I do have the VID block from a previous session. I am getting another used ECM today, and will be proceeding very cautiously. I will look at the mentioned bulletin before proceeding. Thanks for the replies, any more info will be welcomed.
The following users liked this post:
03Xtype (07-22-2015)
Trending Topics
#8
The following 2 users liked this post by Jagman1984:
03Xtype (07-22-2015),
Cash Jackson (02-24-2017)
#9
#10
![Default](/forum/images/icons/icon1.gif)
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
The following 13 users liked this post by Jagman1984:
03Xtype (02-02-2012),
Cash Jackson (02-24-2017),
dharry078 (04-15-2019),
Don B (03-19-2018),
dsetter (05-08-2015),
and 8 others liked this post.
#12
Join Date: Sep 2008
Location: Damon /Houston, Texas
Posts: 7,254
Received 2,193 Likes
on
1,359 Posts
![Default](/forum/images/icons/icon1.gif)
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
And to think there have been a few on here over the past couple years that call hard reboots BS and ficticious in fixing anything. But yet it is still more than ever a primary diagnositc and repair step from Jaguar and a step when doing FRED paperwork.
And 03Xtype. when modules crash like that, we dealers do know what recitifications steps are, reboots, and recovering corrupted vid blocks. Most ecu failures revolve around burned out/shorted/open drivers. there are few module failures at a dealership level. most notable are ABS, AC, security, and instrument pack modules. few ECU, or trans(TCM)
ABS-solder joints to power
AC-heater valve drivers
Security-revolve around older modules that control lighting and locking issues
Instrument packs-fuel level failures, gauge sticks, and sounders
these are most frequent and reason that I have seen over the years
Last edited by Brutal; 02-02-2012 at 08:57 PM.
#13
![Default](/forum/images/icons/icon1.gif)
Good to know about the 'connecting the cables together' procedure. I have not had a module "failure to communicate" but I have heard from guys at Jaguar training regarding horror stories about cars with that fault involving Jaguar field techs and the crazy steps to rectify.
It's a little easier when the factory Tech-line or FSE has your back for back and forth communication. It is GREAT when you figure it out on your own with some documents and logic!!!!!!!!!!!!!
Glad to hear it worked out.
bob gauff
It's a little easier when the factory Tech-line or FSE has your back for back and forth communication. It is GREAT when you figure it out on your own with some documents and logic!!!!!!!!!!!!!
Glad to hear it worked out.
bob gauff
The following users liked this post:
03Xtype (07-22-2015)
#14
#15
#16
#17
![Default](/forum/images/icons/icon1.gif)
03 s type is a bit funny when using anything past ids 117... been a few issues re flashing ecm and tcm, what level add or ids are you running, i haven't seen any issues after add 125 on... Im in Los Angeles and could offer you some help if you like..pm me if you have any further questions
The following users liked this post:
03Xtype (07-22-2015)
#18
![Default](/forum/images/icons/icon1.gif)
Hey JagV8, was looking back through my threads on this forum and realised that I didn't respond to your questions on the IDS. We have a one year subscription to the IDS/SDD that includes all updates. It was about $1000.
Although other people have successfully run the software on other laptops we had problems and ended up purchasing a used Panasonic Toughbook in order to conform the supported specifications in order to satisfy Jaguar support. If I had to do it again I would have purchased the unit from SPX so that I could have support from them too! The Mongoose JLR (J2534 tool) was reasonably priced from Drew Technologies and they have been somewhat helpful in examining logs that I have had to send on a recent car. Hope that answers your questions.
Although other people have successfully run the software on other laptops we had problems and ended up purchasing a used Panasonic Toughbook in order to conform the supported specifications in order to satisfy Jaguar support. If I had to do it again I would have purchased the unit from SPX so that I could have support from them too! The Mongoose JLR (J2534 tool) was reasonably priced from Drew Technologies and they have been somewhat helpful in examining logs that I have had to send on a recent car. Hope that answers your questions.
#19