21 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHIntermittent no crank frustration
Reported or suspected cause
(currently)
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.
Reported cause · Original poster
I�m happy to say this problem is (currently) resolved- big relief!
Leading evidence: '(currently)' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is '(currently)' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Check than some problems' (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 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.
Reported cause · Original poster
Turned out to be a poor connection to the abs ecu, so basically as my error code suggested- so up and running again with no outlay.
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
Don't think its the ground lead - engine casing measures full voltage, have cleaned the chassis end but not the casing end
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
Awesome good to know, thats a way easier thing to check than some problems!
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
I would replace/rebuild the two CAN wires from DME to TCU and see if that fixes the intermittent issue, if not a new TCU may be in order..I have had to replace a few TCU's due to no start and sometimes the selector LED's will flash when the fault occurs
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
I would replace/rebuild the two CAN wires from DME to TCU and see if that fixes the intermittent issue, if not a new TCU may be in order..I have had to replace a few TCU's due to no start and sometimes the selector LED's will flash when the fault occurs
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
I would replace/rebuild the two CAN wires from DME to TCU and see if that fixes the intermittent issue, if not a new TCU may be in order..I have had to replace a few TCU's due to no start and sometimes the selector LED's will flash when the fault occurs
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.
21 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.
1 acknowledgements have no verified action link; they do not establish a repair result.
Outcome without a verified action link
Changing from Drive to Neutral makes no difference as to whether it starts or not.
Hi, I'm looking for some advice as I've come to a dead end using up all the info gained from other threads out there.
My recently purchased 996 tiptronic (which has been standing for most of the last 10 years) is starting about 50% of the time, the rest of the time there is no crank, everything appears normal, just no crank! It may start in 10 minutes or 10 hours, but will start again at some point. It's pretty random, the only continuity is that if it has been running for a while after I leave it for a minute or two it wont start (no crank). Error code 5284 (electrical connection between TC and DME) is present when the non starting fault is present and not when its starting ok - this is all I have to go on now but don't know what to try. Maybe there's another ground lead I could test?
What else I know -
Its not the battery - new one measuring 13v, not exact spec but slightly higher Amp hours.
Its not the starter - bridging the relay will make it start
Its not the relay - have swapped them about, but when the problem exists there is less than a volt going to the relay, else full voltage
Don't think its the ground lead - engine casing measures full voltage, have cleaned the chassis end but not the casing end
Not the ignition switch - replaced that
Don't think its the tiptronic selector not being in park - its displayed on the instrument cluster
Don't think its the immobiliser - no error code and alarm light on dash goes off when key is turned in ignition after manual locking
Any knowledgeable advice gratefully received TIA
Code 5284 is a communication error between the engine control unit and the transmission control unit..
The engine control unit will not allow the car to start unless it gets a communication from the transmission control unit telling that the transmission is in park/neutral and starting is safe/OK..
High and Low CAN wires in the trans conector are pin 85 and 86..
I would replace/rebuild the two CAN wires from DME to TCU and see if that fixes the intermittent issue, if not a new TCU may be in order..I have had to replace a few TCU's due to no start and sometimes the selector LED's will flash when the fault occurs
Excellent! Thanks Porschtech3, makes sense - I was stumped as I thought TC was for traction control. The error code showed up under the ABS check. This means I can make some progress, I'll check out the wires and connections - do you know which pins they connect to in the DME?
This is the error that I came up with from my Google search - definitely listed as an ABS / Traction control Issue? Or is there something I'm not understanding?
also..... had a thought. When I picked up the car I had to jump start it at a service station in a bit of a panic - just hooked it up to the battery - could this have fried the ECU?
and..... The TC indicator light on the button is illuminated when I switch the ignition on - is this normal?
No, jump startimg as described hasn't fried the ecu.
Illuminated upon ignition on but should extinguish after a couple of seconds.
If it lights up after having reached a speed of 4-5mph there is a wheel speed sensor related problem and the ABS Amber light should appear too.
I have tested the CAN wires connecting pins 86 and 85 and there is continuity, I would replace them as a precaution, but pretty sure I don't have the right kit to make a good job of it.
I unplugged the ABS module and the error 5284 went away though the car still won't start - would it ever start with the ABS module unplugged?
Maybe its still the Trans control module, though I have no error relating to this.....
What's this?
I should add - my remote key has failed / never worked. If the alarm / immobiliser is on I just make sure I turn the key in the ignition before the alarm goes off (the pill in the key seems to cancel them as it should)
I�m happy to say this problem is (currently) resolved- big relief! Turned out to be a poor connection to the abs ecu, so basically as my error code suggested- so up and running again with no outlay. Loads more to spend my money on mind