8 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHInstrument Cluster 'Error Bordcomputer'
Leading reported evidence
Replace c2 instrument cluster
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
My C2 instrument cluster was replaced by a C4S cluster by the previous owner.
Leading evidence: 'Replace c2 instrument cluster' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'problem is within your cluster' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Check of the inner connections' (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
I bought a used Turbo instrument cluster when I manual swapped my car and had the mileage reprogrammed to match.
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
So we changed the instrument cluster with a set of working from a 996.2, and they worked fine.
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
The clocks were swapped with a set from a 996.2 Tiptronic, and those worked perfectly with no faults.
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
Based upon your description, I suspect the problem is within your cluster.
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
While the OP says the cluster/clock was working prior to the leak repair, I wonder if the systems were working with RAM until there was a reset and then reverted to ROM.
Outcome qualification: Negation, uncertainty or missing explicit repair resolution overrides the raw extraction signal.
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.
8 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 · 1 adjusted by outcome qualification.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T130754Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I have a 2001 996 Turbo Tiptronic that�s recently had the engine and gearbox removed to fix a leak between the gearbox and transfer case. Since everything was refitted, the instrument cluster has been showing some very strange faults, and both the specialist and I are a bit stuck.
When turning the ignition on, the display shows
�Error Bordcomputer�
, followed by
�Selector lever not engaged.�
Once the car is started, it returns to �
Error Bordcomputer
�. The reverse light flashes while in P, and when moving the selector to D it shows both first and reverse at the same time.
Despite this, the car drives normally and shifts through all gears without issue.
The clocks were swapped with a set from a 996.2 Tiptronic, and those worked perfectly with no faults.
Has anyone come across this before or got any ideas what might be causing it?
Part numbers:
Turbo clocks:
996 641 218 01
70C
Non-turbo clocks:
996 641 228 20
70C
Any help would be greatly appreciated - thanks in advance.
*Note ,there are no fault codes on the car and the live data is showing the correct position of the gear lever, but the instrument cluster is not*
Before engine started.
After engine started
Based upon your description, I suspect the problem is within your cluster. You say you replaced the clock? I'm guessing the whole sub-board? Not just the LED screen? I would start with the cluster. Either swap with a known good cluster or open it up and check all of the inner connections.
I looked through the workshop manual. Can't find any references there to assist you. Not even a reference to "error Bordcomputer"
Maybe with clocks you mean the instrument cluster, or did you actually fiddled with the instrument cluster?
It may be a reprogramming issue. This is a good article to follow but you need PIWIS and the codes.
https://www.pelicanparts.com/techart...h2HkUYM4Q50Y4q
Lol. Two nations divided by a common language?
I still think the OP should focus on the cluster/clock. While the OP says the cluster/clock was working prior to the leak repair, I wonder if the systems were working with RAM until there was a reset and then reverted to ROM. Hence the recent wonkiness.
I'd confirm compatibility between the clusters and then confirm the programming. btw, the Pelican article points out that clusters are USA or ROW but the Porsche manual says there are other choices such as UK, Japan, etc. I pulled up my coding and there seems to be about 10 different codes (more than shown in the photo) No idea what most of them are but I suspect they all do something. The only way I know to change them is to extract the coding from the original cluster and then over-write the new one (I don't think that'll update the mileage.)
Sorry for the confusion I caused by changing my terminology half way through my post. Clocks is a lazy term from instrument cluster in the UK, but obviously the instrument cluster has a clock in it, so I appreciate I made that a little bit harder than it had to be.
And thank you for your help so far.
So we changed the instrument cluster with a set of working from a 996.2, and they worked fine. I understand there is always a first, but these cars are 20 plus years old now and in all the years that these cars have been built, I can not find one reference to an instrument cluster failure in this manner on any forum.
So I suppose my question is given the donor instrument cluster is from a Carrara 4 Tiptroinc with a different part number, can have complete confidence that it isn't the car and the fault lies within my turbo instrument cluster?
Thank you
That is a good assumption. Perhaps you can find a shop to repair the instrument cluster?
I bought a used Turbo instrument cluster when I manual swapped my car and had the mileage reprogrammed to match. Just note that 2001 has a different programming than 2002-2005; so I have been told.
You should not need to spend $5000 for a new cluster at the dealet.
My C2 instrument cluster was replaced by a C4S cluster by the previous owner. Fuel gauge was totally out of place, due to the different way of the fuel tank. I had to use PIWIS to recalibrate it. Keep your fuel gauge in mind... Better to repair your original cluster
This is a source reference. Confirm exact model applicability in the original material.
