fullymatted.
Back to search
Porsche Club GB

Dashboard Warning Message

Add to repair workspace
Open repair workspace
Original source
26 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW

Discussion summary

YOUR RESEARCHDashboard Warning Message

Leading reported evidence

Check fuses - also ok - tried

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 checked all the fuses - also OK - tried disconnecting the battery for a while to give everything a chance to reset.

Dashboard Warning Message
Frequently discussed work

Check between pin 23

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

Probably easier to unplug Plug A from the alarm module, Plug A from the DME, and do a simple continuity check between pin 23 on the alarm plug and pin 3 on the DME plug.

Dashboard Warning Message
Read full discussion summary

Leading evidence: 'Check fuses - also ok - tried' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'bit late in the day' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check between pin 23' (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.

Read captured replies

1 matching discussions · 26 captured posts examined · 0 partial discussions

Compare 4 other evidence results

Check wet footwells and they are all dry

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've checked for wet footwells and they are all dry.

Dashboard Warning Message

Install dme (£ouch

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

Ninex fitted a new DME (£Ouch!) and had a bit of a battle getting the X50 unlocking code from Germany, but were persistent and got it sorted in the end - Thanks Andy!

Dashboard Warning Message

bit late in the day

Suggestion or failed attempt

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
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 suspect a cause
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.

Suspected cause · Original poster

Probably a bit late in the day to start dismantling, but I will give it a try as soon as I can.

Dashboard Warning Message

communication between the alarm module and the engine ecu

Suggestion or failed attempt

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
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 suspect a cause
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.

Suspected cause

I think the problem is communication between the alarm module and the engine ecu.

Dashboard Warning Message
Frequently discussed actions (10)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

Check between pin 23

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

Probably easier to unplug Plug A from the alarm module, Plug A from the DME, and do a simple continuity check between pin 23 on the alarm plug and pin 3 on the DME plug.

Dashboard Warning Message

Check cabling and ecu connections (i even

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 also opened up the real load space and checked the cabling and ECU connections (I even checked inside the ECU to see if there were signs of tuning chips or other mods).

Dashboard Warning Message

Check fuse c1

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

Did you check fuse C1 when you did your initial fuse checks?

Dashboard Warning Message

Check fuses - also ok - tried

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 checked all the fuses - also OK - tried disconnecting the battery for a while to give everything a chance to reset.

Dashboard Warning Message

Check inside the ecu

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 also opened up the real load space and checked the cabling and ECU connections (I even checked inside the ECU to see if there were signs of tuning chips or other mods).

Dashboard Warning Message

Check visible cable runs

No successful repair reported for this finding.

0
Reported fixes
1
Unsuccessful attempts
1
Discussions
Read evidence and context
Discussions that report an unsuccessful attempt
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.

Unsuccessful attempt · Original poster

I checked all visible cable runs for damage and re-made all connectors (with a squirt of contact cleaner) but no change.

Dashboard Warning Message

Check wet footwells and they are all dry

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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've checked for wet footwells and they are all dry.

Dashboard Warning Message

Disconnect battery

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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 checked all the fuses - also OK - tried disconnecting the battery for a while to give everything a chance to reset.

Dashboard Warning Message

Install dme (£ouch

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

Ninex fitted a new DME (£Ouch!) and had a bit of a battle getting the X50 unlocking code from Germany, but were persistent and got it sorted in the end - Thanks Andy!

Dashboard Warning Message

Run wire

No successful repair reported for this finding.

0
Reported fixes
0
Unsuccessful attempts
1
Discussions
Read evidence and context
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

You could try running a wire from the Alarm unit Plug A Pin 23 to the DME Plug A Pin 3, just in case there is a break in the wire somewhere.

Dashboard Warning Message
Reported and suspected causes (2)

These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.

bit late in the day

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect a cause
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.

Suspected cause · Original poster

Probably a bit late in the day to start dismantling, but I will give it a try as soon as I can.

Dashboard Warning Message

communication between the alarm module and the engine ecu

No successful repair reported for this finding.

0
Identified cause
1
Suspected cause
0
Reported fixes
Read evidence and context
Discussions that suspect a cause
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.

Suspected cause

I think the problem is communication between the alarm module and the engine ecu.

Dashboard Warning Message
Coverage and how to read this overview

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.

26 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.

  • Porsche Club GB: 1 discussions

0 evidence records excluded for query context · 0 excluded by outcome qualification · 0 adjusted by outcome qualification.

1 acknowledgements have no verified action link; they do not establish a repair result.

Outcome without a verified action link

However, it's still not totally straightforward to fix as the car has the X50 option pack, which means that it needs a special software map, which Ninex are currently in the process of obtaining from Germany.

No unique explicit quoted action; no causal link assigned

NEARBY ACTION · LINK UNVERIFIED

Probably easier to unplug Plug A from the alarm module, Plug A from the DME, and do a simple continuity check between pin 23 on the alarm plug and pin 3 on the DME plug.

Nearby source post

Generation: 20261026T220748Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources

POST 1 / ORIGINAL POSTEROriginal post

Hi Everyone, I have a 2002 996 TT (6 Spd), that has been "resting" for a few weeks while there was salt down on the roads. I tried to start it this afternoon only to be greeted by the rather cryptic "Failure Indicator" dashboard warning message pictured - The dashboard warning lights all came on as usual, but the starter would not turn! The battery is kept topped up with a trickle charger and that shows as being fully charged, so that should be OK. I checked all the fuses - also OK - tried disconnecting the battery for a while to give everything a chance to reset. Still no joy. I have also tried searching the Internet for clues, but have only found one reference that suggests that an accessory tuning chip might have become "unsoldered" in the ECU. At the moment, I can't move the car, so getting it to a garage won't be easy, so any suggestions as to what could be wrong would be welcomed. Thanks! Jeff

POST 2Original post

Was there any audible click from the engine bay? Solenoid on starter motor? You could try putting it gear and rocking the car, then try again in neutral. Obviously diagnostics would reveal fault.

POST 3Original post

Jeff! Does the voltmeter in the instrument cluster show 12V? Do you have another key you could try? (In case it is an immobiliser problem).

POST 4 / ORIGINAL POSTEROriginal post

Hi Everyone, Thanks for the suggestions! In answer to some of your points: The Voltmeter shows above 12V even when the key is turned There is no click from the Starter solenoid when I turn the key, nor is there any flickering or dimming of the lights I have tried a second key, with the same result I have also tried plugging in my EOBD Code reader which is "unable to communicate with the ECU" - worrying as normally it works OK with this car! Jeff

POST 5Original post

It does sound like an immobiliser issue (of sorts). The DME diagnostic line runs from the OBD2 port, via the alarm module, to the DME (on an aluminium platform under the carpet behind the rear seats). If there is a break in the line between the alarm module and the DME the immobiliser can't communicate. This would also explain why your code reader can't connect. I would start by unplugging the DME connector, and plugging it back in, as it may be a bad connection. There is also a large black 30-pin plug under the carpet in the rear passenger footwell. The diagnostic line runs through that connector, and I have known cases where the pins have corroded, giving a bad connection. It might also be a bad connection on the alarm module plug (under the left hand seat). Another thought. Is it damp under the passenger seat?

POST 6 / ORIGINAL POSTEROriginal post

Hi Richard, Thanks for the suggestion! Probably a bit late in the day to start dismantling, but I will give it a try as soon as I can. Jeff

POST 7 / ORIGINAL POSTEROriginal post

OK, I've checked for wet footwells and they are all dry. I have re-made all the electrical connections that I could find under seats and carpets. I also opened up the real load space and checked the cabling and ECU connections (I even checked inside the ECU to see if there were signs of tuning chips or other mods). There are a couple of non-porsche looking units under the ECU, but I would guess this was the Tracker? The bottom line is that none of the above has helped and the cryptic message still appears when I turn the key. Anyone know a good recovery service? Jeff

POST 8Original post

Not sure what those units are, but it looks a bit of a 'jiggle and dodge'. Most independents will have a recovery service they use. Where are you located?

POST 9 / ORIGINAL POSTEROriginal post

Hi Richard, Near Taplow (Maidenhead). I usually take it to RSJ Porsche in Slough, but they don't offer recovery. Just had RAC Homestart to take a look at it in the hope that they would have better diagnostic equipment than I do. Their diagnostic reader could talk to the ABS and the PCM1 but nothing from the ECU. I assume that ECU's are coded to the vehicle, so not easy to try a swap? All starting to sound expensive. Jeff

POST 10Original post

I think the problem is communication between the alarm module and the engine ecu. That is causing the immobiliser to inhibit starting. You could try NineX in Maidenhead, or would you like me to pop round and plug in my Porsche tester? If so, drop me a PM with your phone number.

POST 11Original post

Is the car manuel/ tiptronic I remember years ago about the inhibitor switch on auto gear boxes they did the same. When you try to start the car move the gear stick slightly back and forward. Only if it's auto.

POST 12Original post

It's a manual. No tiptronic display on the right hand gauge.

POST 13 / ORIGINAL POSTEROriginal post

Hi Richard, Thanks for the offer, but I suspect I would be wasting your time! So far three code readers have failed to get a response from the ECU and I know that my own reader has been able to communicate with it in the past, so sadly I think it may be an ECU fault (A wiring fault would be cheaper, but I am at a loss to know how to test for one) I will phone around next week and see if I can find someone who can take it in to have a look at it (You mention Ninex - they are local, so I'll see if they can help!) Jeff

POST 14Original post

The Porsche tester will be able to connect to the alarm module, which other readers won't. If it is an immobiliser issue, as I suspect, the alarm module will have a fault code stored and would confirm a lack of communication with the engine ecu. The offer stands, so if you want me to plug it in give me a call in the morning on 07860 561543.

POST 15Original post

Jeff if I were you I would take up Richards offer, he is extremely knowledgeable on these cars Richard once again you go over and above for members of the club. It is people like you that make the club ??

POST 16Original post

I visited Jeff yesterday, and the PIWIS confirmed that the W-Line (the diagnostic and immobiliser wire between the alarm module and DME) is open circuit. Hence the DME is not receiving the immobiliser signal from the alarm control unit. This also stops any diagnostic tester from communicating with the DME, because it uses the same line. My strong suspicion is that there is a bad connection at the plug and socket joint under the rear footwell carpet, and I let Jeff to decide to either tackle it himself, or have the car recovered for a specialist to do it. It is a bit of a grovel to access it, and not the best of weather conditions for working outside, so I wouldn't blame him if he decides on the easier way out.

POST 17 / ORIGINAL POSTEROriginal post

My job for this morning! (Now it's warmed up a bit!) And thanks again to Richard for taking the time to come over and help - much appreciated! Jeff

POST 18 / ORIGINAL POSTEROriginal post

Next step: I've removed the passenger seat and stripped back the carpet. The connector was actually on the pillar below the seatbelt reel, but still a pain to get to! I checked all visible cable runs for damage and re-made all connectors (with a squirt of contact cleaner) but no change. Very frustrating!

POST 19Original post

As you have disconnected the DME and re-connected it, the only other connection you can try is the plug on the alarm module under the passenger seat.

POST 20 / ORIGINAL POSTEROriginal post

Sorry, already tried that one! The wiring and connectors generally look to be in good condition, although there are signs that I wasn't the first person to pull up the carpets. I also checked each of the connectors in case any of the pins had been pushed back, but as I said, it all looks to be OK. Jeff

POST 21Original post

You could try running a wire from the Alarm unit Plug A Pin 23 to the DME Plug A Pin 3, just in case there is a break in the wire somewhere. Other than that, I think that maybe those additional boxes near the DME might be something to do with it. Can you see if they break in to a green wire (the W-Line) in the loom? If not, then perhaps the DME has failed, which would be highly unusual. Did you check fuse C1 when you did your initial fuse checks?

POST 22 / ORIGINAL POSTEROriginal post

Hi Richard, Thanks again - I'll give that a try! Question - Is it possible to test for a signal on that line at the DME with something like an oscilloscope? (or do I risk damaging the DME). Just a thought, as if it's a digital signal, it may be too high a frequency for a scope anyway?? Jeff

POST 23Original post

Probably easier to unplug Plug A from the alarm module, Plug A from the DME, and do a simple continuity check between pin 23 on the alarm plug and pin 3 on the DME plug. Also check that the wire doesn't go to ground.

POST 24 / ORIGINAL POSTEROriginal post

I had to put this on hold for a couple of weeks while I dealt with some other non-car related problems, but finally got around to it again. I eventually had to get the car collected by Ninex Motorsport and after testing, they diagnosed that it was indeed the DME that had failed! This is apparently a VERY rare occurrence and there is no indication of why it may have happened. However, it's still not totally straightforward to fix as the car has the X50 option pack, which means that it needs a special software map, which Ninex are currently in the process of obtaining from Germany. It's been a couple of months since I drove it last and now I can't wait to get the car back!

POST 25Original post

That's a bit of a shocker - very rare indeed. The fuel maps are stored on the PIWIS tester, but you need the security codes from Porsche to load them on the car. The X50 map also needs a special programming code to transfer it. I would have thought they should be able to get the codes from Porsche GB, but I'm sure NineX know what they are doing.

POST 26 / ORIGINAL POSTEROriginal post

Well, I finally have a running car again - Yayyy!!!!! Ninex fitted a new DME (£Ouch!) and had a bit of a battle getting the X50 unlocking code from Germany, but were persistent and got it sorted in the end - Thanks Andy! Still a few other jobs to be done on the car, but I'll drive it for a while and look at them later.

This is a source reference. Confirm exact model applicability in the original material.