3 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHSuddenly I have a computer and a misfire!
Reported or suspected cause
ignition coils
Reported cause
No successful repair reported for this finding.
1
Identified cause
0
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 report identifying 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.
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
As for the misfire - I seem to recall yours is pre-eGas (M620 option code), so you could try resetting the DME by disconnecting the battery for a couple of minutes.
Leading evidence: 'ignition coils' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'ignition coils' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Disconnect battery' (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
The OBC is built in to the instrument cluster, but not activated at the factory unless the stalk is fitted (as an option).
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
As for the misfire - I seem to recall yours is pre-eGas (M620 option code), so you could try resetting the DME by disconnecting the battery for a couple of minutes.
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
As for the misfire - I seem to recall yours is pre-eGas (M620 option code), so you could try resetting the DME by disconnecting the battery for a couple of minutes.
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'm going to take it for another run later to see whether it has cleared itself.
These are separate views of the same evidence. Frequency alone does not establish a fix, and these counts must not be added together.
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
As for the misfire - I seem to recall yours is pre-eGas (M620 option code), so you could try resetting the DME by disconnecting the battery for a couple of minutes.
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
As for the misfire - I seem to recall yours is pre-eGas (M620 option code), so you could try resetting the DME by disconnecting the battery for a couple of minutes.
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.
3 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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T152433Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Filled up with petrol this morning and two odd things happened.
Firstly I noticed that now instead of having outside temp displayed I have miles to re-fuelling - which is odd since I don't have a computer fitted and, as there's no stalk to control it, no way to scroll it back to temp.
Presumably the software is on all the cars but isn't activated without the stalk. (It's a '98 996 3.4)
Secondly, and much more concerning is that I've had a major misfire ever since. Peculiar co-incidence but actually I think it's unrelated, it's not like it's changed to a different ecu map or something as it's too inconsistent.
I've just phoned the petrol station and they're saying that no-one else has called with any problems. I had let the level drop further than it's ever been before and I suspect I've stirred up some muck from the bottom of the tank.
Went for a run to see what happened if warmed it through - had a patch of suddenly getting a lot worse (and the emissions warning light came on and stuck on at this point). But having stopped and restarted it seemed a lot better as I limped home.
If it is muck what's the chance of it clearing itself? Not sure whether I need to get it in the garage first thing in the morning or whether later in the week will suffice. I'm going to take it for another run later to see whether it has cleared itself.
Any thoughts on either issue??
Apologies if anyone has also seen this on Pistonheads but I'm not getting a lot of joy there.
The OBC is built in to the instrument cluster, but not activated at the factory unless the stalk is fitted (as an option). The cluster can be coded for OBC afterwards, and this causes the outside air temperature to display (the default setting). Someone has obviously coded it after it left the factory. It is strange that it has changed to the 'range' setting of it's own free will - it must have had some kind of blip or power loss to the cluster. You won't get the OAT reading back without fitting a stalk or simple switch, as it stays on the setting last used.
As for the misfire - I seem to recall yours is pre-eGas (M620 option code), so you could try resetting the DME by disconnecting the battery for a couple of minutes. Don't forget to switch the ignition on first, to stop the alarm siren going off. If it doesn't cure it, then you need to get the fault codes read.
Personally, I think the two are likely to be related, but that's just a hunch.
Turned out to be a ignition coil on cylinder 6.
I am developing a hot start problem that can cause a momentary loss of electrics - although I didn't notice this yesterday (usually it sets the alarm off) I suspect this is what caused the computer blip.
This is a source reference. Confirm exact model applicability in the original material.
