17 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996 owners in Toronto area
Leading reported evidence
Check people in background
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
^^^ he already did check the people in background on the video.
Leading evidence: 'Check people in background' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check people in background' (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.
Repair damages in the unlikely event something does go wrong
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
who will be responsible for the cost of repairing the damages in the unlikely event something does go wrong?
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 testing the unit you have with another Rennlister's 996, I have been involved with enough electronic projects for work and for myself in the past to know how quickly things can go wrong, so personally I cannot afford to risk anything in my car getting messed up during the "test".
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 testing the unit you have with another Rennlister's 996, I have been involved with enough electronic projects for work and for myself in the past to know how quickly things can go wrong, so personally I cannot afford to risk anything in my car getting messed up during the "test".
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 testing the unit you have with another Rennlister's 996, I have been involved with enough electronic projects for work and for myself in the past to know how quickly things can go wrong, so personally I cannot afford to risk anything in my car getting messed up during the "test".
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 testing the unit you have with another Rennlister's 996, I have been involved with enough electronic projects for work and for myself in the past to know how quickly things can go wrong, so personally I cannot afford to risk anything in my car getting messed up during the "test".
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.
0 acknowledgements have no verified action link; they do not establish a repair result.
Generation: 20261026T194705Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
okay didn't spot the Ontario section on here!
North York is fairly close. Is your car still out?? You might even like the gauge...with its 996 integral mount
Yep, still out until the snows on the ground.....I'm around most weekdays if there's something you need help with.
Just curious why you need 996 to test, is there a specific parameter your looking for?
Okay great .....I do need a 996 to just verify communication with the ECU. The Digital gauge is designed to work with the 996 and has dedicated console mount for it. It might be something you would be interested in.....I put it in a 986 and it times out before establishing communication and have been told that this may be due 986 differences...
I want to make sure that it works with a 996..You can tell in seconds just after hooking it up. Other wise it is back to the manufacturer for a return rather than waiting for a 986 timing change
It's very similar to a scan gauge
Yes that is what I thought but I will go through and test it out. I am told there is a difference between the ECU programs that could affect things. The gauge could be faulty
Well, FWIW, I bought an Innova 3030 OBD-II reader from Canadian Tire today, it took almost two minutes before the Porsche returning the no-fault status, where my 2005 Accord took less than 30 seconds to return the no-fault status, maybe this is the difference.
As for testing the unit you have with another Rennlister's 996, I have been involved with enough electronic projects for work and for myself in the past to know how quickly things can go wrong, so personally I cannot afford to risk anything in my car getting messed up during the "test".
Perhaps another local Rennlister is more brave than I am.
Ahhhh i understand your fears. I have tested it on two 986s already...and they did not colapse. It is made to display ecu parameters just like your Canadian tire gauge....i am surprised you plugged that in!!!!
I don't have as much concern with the unit from CT since it is a well known brand, and not known to have caused any issues, else CT would have recalled it as CT does from time to time with any products CT sell that later are reported with safety or other undesirable consequences.
As well I have a significant recourse with CT if the gauge I bought from CT blew the electronics in my car when plugged in, it's my cross to bear if that does happen and I will go after CT for compensation, it will be ugly and lengthy since CT will likely try to fight against the claim.
You have provided very little info about this item you want to try out on someone else's car other than it's an OBD-II gauge which timed out when connecting to your car, unfortunately that's a risk for that "someone else", i.e. who will be responsible for the cost of repairing the damages in the unlikely event something does go wrong? Are you, or the manufacturer of the item going to be responsible?
Maybe others will be inclined to assist if you can provide more details such as brand, website etc. for them to assess themselves, however this is just more risk for me than I am willing to take.
Sorry.
Dgauge from Brockway engineering .....Brockway engineering would be the website
It's a common 996 component a few people have them on here as I recall. Is it is specifically made for the 996
