17 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHP0605 code
Leading reported evidence
Clean contacts
Performed · outcome unconfirmed
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
I also cleaned all the contacts for the Computer under the seat and DME although they looked clean with no corrosion.
Leading evidence: 'Clean contacts' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check are the ground cable connection in the engine bay' (1 discussions). For that action, 0 discussions report a resolution and 0 report an unsuccessful attempt. No action has an explicit, attributable resolution report under the current rules. These are forum reports and suggestions, not a confirmed diagnosis.
Source reports, not a diagnosis or a success probability. Counts refer to discussions and can overlap.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed · Original poster
Again, car runs like a champ and no issues other than this code which first appeared after a very slow start with an old (now replaced) battery.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that performed work without a confirmed outcome
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Performed · outcome unconfirmed
U can also check the normal used sources like ebay.
Check are the ground cable connection in the engine bay
Suggestion or failed attempt
No successful repair reported for this finding.
0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
Things that it seems I need to check are the ground cable connection in the engine bay.
Explicit resolution reports before identified causes, performed actions and suggestions. Within each level, matching component labels precede direct query mentions and inherited thread context; successful versus unsuccessful discussion counts, owner confirmations and independent discussion support determine order. This is not a probability of success.
Discussions that contain suggestions
1
0 original-poster resolution reports. Counts can overlap; they are not unique people or a success rate.
0 discussions have direct query context; 0 report a fix in that context. Other evidence may inherit the discussion’s subject.
Suggestion · Original poster
I will pull the connectors off the dme and check for corrosion.
Counts describe captured discussions, not unique people or a diagnosis. Author identities are not reliably stored. Exact duplicate evidence is counted once across matching discussions; one discussion counts at most once per action/state. Multiple repairs reported together remain a combination. Suggestions and failed attempts do not establish a fix. Matches cover whole discussions and can include related faults, model variants and incomplete threads.
17 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
Rennlist: 1 discussions
0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.
3 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
I deleted them both, took the car on a test drive and after a few miles and 2 starts both codes returned.
Hello all, I made it about 10 months post cam shaft dev project before I had a hiccup which isnt too bad right? haha
1999 C4 Cab
My battery was starting to get old. I could tell that it didn't have quite the oomph it once had starting even though I store on trickle charger . Last week it had a particularly lackluster crank when starting the car but the car did start and then it threw the code P0605.
Doing some digging and one of the culprits is a tired battery. Easy enough. Went and got a new battery. Now sounds healthy and happy starting and the code disappeared so I thought I was good to go. 2 days later and the code is back. (Starter is new as of the cam job last fall and sounds much happier with the new battery)
There are no running issues whatsoever or other codes.
Things that it seems I need to check are the ground cable connection in the engine bay. I have the cab in service mode. I will pull the connectors off the dme and check for corrosion.
What else do you guys think before I contact and ECU repair place. Again, car runs like a champ and no issues other than this code which first appeared after a very slow start with an old (now replaced) battery.
Thanks for any and all input.
I did a little more testing. The battery tested at 13.9v when starting so the alternator seems to have adequate output.
I scanned each individual module with my foxwell and got these below codes. The P0605 Control Unit Faulty (ROM) as well as 21 W Lead (DME Modilizer).
I deleted them both, took the car on a test drive and after a few miles and 2 starts both codes returned. My next step I think is to pull the driver seat and look at the imobilizer but it does seem that I have some kind of ECU/IMOBILZER issue ???
When you cleared the codes with your Foxwell, did you go into both the DME
and
the Alarm/Immobilizer modules separately to clear them, or just do a standard engine clear?
I cleared them separately within each module. They both returned.
I will order a Y cable as they aren�t too expensive but curious if it�s my issue or not
Well, you guys have once again come through for me. I replaced the Y Cable (man that would have been much easier with the engine out! lol)
I also cleaned all the contacts for the Computer under the seat and DME although they looked clean with no corrosion.
took it on a few spirited laps of the local area and did 4 start cycles and the code has not reappeared.
I was quite surprised at the audible difference with the new cable. Starter is spinning faster for sure with this cable.
every day I learn more! I�ll drive for a few more weeks and this squeaky things needs a suspension job.
thanks all!
Well....I guess the cable did not fix the problem.
The check engine light came on. Scanned with foxwell and got the same two codes....
P0605 Control Unit Faulty (ROM)
and
21 W Lead (DME Immobilizer)
The car has no issues...other than it seems to think there is an issue. At this point it seem the next step is to send off the DME/Immobilizer to an ECU Specialist.
What are the recommendations from the group? Specialized ECU Repair/ECU Doctor is what shows up most during my searches.
I received the report back from ECU Dr that there is an issue with the circuit board that isn�t repairable�.they are closed now but I�m wondering what my next step is. Do I need to source and ECU to send to them to program? Monumentally bummed and not sure what this is going to cost�.
very kind of you and I appreciate the offer!
I just got off the phone with ECU folks and they are selling me a reman ECU and programming everything. Total was $1228 shipped with a 5 year warranty. Can�t really complain about that and I�m really happy about the warranty. Thx all
This is a source reference. Confirm exact model applicability in the original material.
