23 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHsomething cool for everyone
Leading reported evidence
Use by examining the obd ii connector
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
On 1996 and later vehicles, you can tell which protocol is used by examining the OBD II connector:
Leading evidence: 'Use by examining the obd ii connector' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, The most frequently discussed action is 'Reset airbags' (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.
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 use Torque (Android app) which let's you enter any PID you want to query and a formula as well to interprete the returned value I think.
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
Besides code reading it can do more specific things like resetting the airbags which was the main draw for me.
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
Even if it's just so much as resetting the service light.
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
using the regular OBDII cable which don't use pin 3 but may still have some hope on getting DME non-OBDII real-tmie values from pin 7 (e.g., oil temp).....*IF* Porsche uses similar protocol to retrieve those.
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.
23 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.
How about full Durametric data, on your IPhone, for about $20. Is that cool? Yes it is. Very cool. Just one problem ... I NEED PIDs! I'm talking Porsche specific OBD2 Parameter IDs. I know a Rennlister out there somewhere must have stayed curled up all night with her Durametric and trusty logic analyzer.
I have been using the EngineLink WiFi based ELM327 OBD reader software for IPhone. This beasty will take a user generated PID file, so if we can get the non-standard PIDs (over-revs, misfires, etc.) I will configure them for the software and make that available to the community. If anyone is willing to share this data please PM me (or whatever your comfortable with ... email, carrier pigeon, wikileaks.) It will be greatly appreciated!
This is a fantastic idea; the community sorely needs some reasonably priced options for this. Even if it's just so much as resetting the service light.
I just got the knockoff for $20 and called it a day. Besides code reading it can do more specific things like resetting the airbags which was the main draw for me. I know this isn't the most popular choice among some people but it works for me. My$.02
Why not work in-conjunction with Durametric?
I would think they would love to have IOS and Android mini versions of their software. Seems like a win-win to me.
Send an email or call Duram - certainly worth a discussion?
You know, honestly, I NEVER should have used the word "Durametric." It's not Durametric data in any way, shape or form, thats just a sort of short-hand for the Porsche community. All I'm really looking for is mis-fires, over-revs and maybe turning off the airbag light. And no, Durametric ain't gonna help. The guys who can help make this super easy all live in Stuttgart.
Yeah, it certainly would have prevented people tossing out words like "retainer."
How's the project progressing? Any luck? If I can help, I'll get off my **** and do so. PM me if there's something I can do with my laptop, scantool, or rhymes-with-pleuratetric to contribute.
I'm an Android Software Engineer with Garmin. Although I did not work on the
Garmin Mechanic
app, I could probably track down the electrical engineers that worked with the OBDII spec, and using my vehicle, see if we could find where in the stream, the info for the overrevs, etc. are. Were you thinking about writing an app from scratch? Perhaps I could talk w/ some folks to see if some new features could be added to the app (it's been over a year since the last update). Kicker is, the bluetooth protocol, for communicating the data from the Bluetooth device, to the Android device, is proprietary, so that means purchasing Garmin's Bluetooth OBDII dongle. But hey, it could be a win/win for both parties.
The views expressed herein are my own and do not necessarily represent the views of Garmin International or any other individual.
You might drop Harry from
HarrysLapTimer
an email or drop in on his product forums... I don't know if you've seen his iPhone app, but it is a super cool track timer/video capture system and also reads OBD PID info for overlay on the videos...
On his forums there was discussion about getting additional Porsche specific PID info, what data was available in the datastream, etc. He might be willing to share what he learned for a non-competing product.
Hi Doug, no I'm not writing this from scratch. I'm using the EngineLink app for IPhone. EngineLink takes a user generated input parameter file for non-generic (factory) parameter IDs. This would be a GOOD THING to add to the Garmin app (I have no relationship with the EngineLink developer.)
I think I've got mis-fires worked out (mode 6 data.) Still looking for over-revs and airbag light.
I'll be interested in this info as well. I use Torque (Android app) which let's you enter any PID you want to query and a formula as well to interprete the returned value I think. Never tried it yet.
On 1996 and later vehicles, you can tell which protocol is used by examining the OBD II connector:
J1850 VPW --The connector should have metallic contacts in pins 2, 4, 5, and 16, but not 10.
ISO 9141-2/KWP2000 --The connector should have metallic contacts in pins 4, 5, 7, 15, and 16.
J1850 PWM --The connector should have metallic contacts in pins 2, 4, 5, 10, and 16.
CAN --The connector should have metallic contacts in pins 4, 5, 6, 14 and 16.
source:
http://www.obdii.com/connector.html
Can someone confirm 996 is using protocol
ISO 9141-2
?
Yes, it does.
I think LordVicious is looking for the PID and formula definitions specific to Porshce similar to this link for Prius
http://priuschat.com/threads/gen2-pr...ormulas.95370/
Once we build this spreadsheet, Torque and EngineLink could just import the spreadsheet.
That's exactly right Ahsai. Unfortunately it looks like the software cannot deal with mode 6 yet. The Prius guys were kind enough to provide much of the electrical system information via mode 21 which is non-standard but works exactly like mode 1/2 (given correct ECU header offsets etc.) The Porsche guys have not been so, uhm, I'll use the word "industrious."
Porsche also uses pin 3 as the second K-line to communicate with all modules except the DME, which uses the regular K-line on pin 7. See
here
. So I think we are out of luck with ABS/Airbag stuff etc. using the regular OBDII cable which don't use pin 3 but may still have some hope on getting DME non-OBDII real-tmie values from pin 7 (e.g., oil temp).....*IF* Porsche uses similar protocol to retrieve those. However, it's not clear to me Porsche uses OBDII-like protocol to retrieve those info on the K-line on pin 7.
Ex-Developer over here... Two thumbs up for using the Torque App rather than developing something new... Torque seems to be the most popular App for this stuff.
This is a source reference. Confirm exact model applicability in the original material.
