30 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH'99 OBDII Pinouts
Leading reported evidence
Check car's obd2 connector
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.
Leading evidence: 'Check car's obd2 connector' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Check car's obd2 connector' (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 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
Guess you would have to check the ECU 85/86 pin connectors.
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
Temporarily installing/testing my VBox Video Lite in my DD.
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
Being a C2 6-speed, you have DME5.2, which uses the CAN bus only for tiptronic.
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.
30 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: 20261026T165820Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I took the wiring diagram and followed the wires and came up with this spreadsheet
If somebody has more ideas or sees a correction, let me know and I'll modify.
Looks good. I would add these:
Pin 1 is switched 12v power
Pin 3 is the 2nd K-line that's connected to the ABS, Airbag, PSM, alarm, etc.
Pin 7 is the 1st K-line that's connected to the DME (via the alarm CU)
Pin 11 is the "Knock yes/no" output from the DME 5.2
I added in the OBDII standard Bus pins. The wiring diagram doesn't show anything connected to 2/10 or 6/14. So now it will take someone to drop the OBDII connector and see if there are any wires attached to 2/10 or 6/14.
Google/Images
OBDII pinouts - that came out with the industry standardized pinouts
then did a search on porsche OBDII pinouts - that came up with the second image with the Bus connectors
I really don't know if the 2/10 or 6/14 wires exist. Haven't been there. Let us know what you see.
Yes, post #5 applies to you so you have pin 11 (option M339 = C40).
No, there is no CAN bus access on our OBDII diagnostic port. The CAN bus is between the tiptronic, PSM, and DME and it's not exposed to the OBDII diagnostic port.
Slakker, what are you trying to do?
Temporarily installing/testing my VBox Video Lite in my DD. What was supposed to be my first race weekend this weekend is now a 3day DE since they still don't have the welded roll cage finished in my track car.
It can only access the ECU through the CAN BUS. I was hoping the OBDII port would be an easy place to tie in. I've got an OBDII splitter that I'm tapping into for power and was hoping CAN as well. Doesn't look like it will work though. Is there any other place that is "easy access" that I can get to the CAN?
Here's the pictures of my OBDII port on my '99 C2.
Only C4's have pin 11. Being a C2 6-speed, you have DME5.2, which uses the CAN bus only for tiptronic. So I don't think you will find the CAN bus for your purpose.
Hmmm. I'm kind of shocked by this. Almost as much as VBox not using the K-Line which is where my AIM dash will tie into.
Edit: I may have misstated and may be able to wire it into the K Line instead. Their recommendation was connecting to the CAN but not their only option.
Huh. Still don't know where you are going (what's a VBox?) but the CU DME wiring diagram shows this
I wonder if even though you have the 99 6 speed if the High/Low CAN terminals work? Guess you would have to check the ECU 85/86 pin connectors.
Video VBox is a video system with data acquisition and lap timing. Its kind of like Harry's Lap Timer but a lot more sophisticated on the video side. I double checked and it really does only read CAN or analog inputs.
Ok, so looks like I just need to trace out those wires off the ECU. I swear I looked at the diagram and didn't see those the first time.
It is 6 and 14.
Check your car's OBD2 connector. If there are no sockets in holes 6 and 14 there is no CAN at the connector.
For engine telemetry you will need something that communicates via ISO-9141-2 or KWP2000.
No wires in 6 and 14 on mine. The AIM dash i have has a KLine connection and a CAN output option that I will try and use to feed the VBox. It should be fun to play with.
Yes, but the device I was trying to hook up didn't support OBDII and was CAN only. Granted, there isn't much on the CAN, but I thought it was interesting that it had any data at all.
