14 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCH996 Live Data Export
Reported or suspected cause
finding the porsche-specific info
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
The problem is finding the Porsche-specific info to translate the data, unless it's in a useful format like JSON (English, not binary).
Leading evidence: 'finding the porsche-specific info' (1 discussions report identifying this cause; no attributable repair resolution). Across 1 matching discussions, the most frequently mentioned possible cause is 'finding the porsche-specific info' (1 discussions; 1 report identifying it and 0 suggest it). The most frequently discussed action is 'Use slower data rate than newer cars' (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 · Original poster
I think that, for the 2001 cars, they're using a slower data rate than newer cars.
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.
14 eligible posts · 0 unverified posts · 1 discussions match the subject in their title or opening post.
911uk: 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: 20261026T150451Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
I am attempting to record live data, specifically TipTronic data on my 2001 996 C4. It's surprisingly complicated. I want to be able to record all the shift points, selected gear, input/ output speed, etc. The data is available but....
Autel MK905BT
Allows at least summer of the data to be recorded
No obvious way to export the data even by reading the embedded disk directly
Foxwell NT510 Schwaben (loaner)
Allows all the data to be recorded
Easy to get started
Can't seem to find how to export the data even by reading the removable micro SD card directly
Durametric Enthusiast
No live data for the 2001 tip on this or pro version
Porsche PIWIS 3 clone
Seems to limit the number of data elements to 5
Still haven't figured out how to export the data
Thoughts? I'd but yet another scanner if I found one that could do this.
I've Google a lot. There's a metric tonne of noise so it's very possible I missed the needle in the haystack.
I also looked at the Foxwell, Durametric, and Autel manuals and/or websites as well as contacting tech support for Autel and Durametric, but no joy so far. Autel didn't respond. Durametric did, badly.
I was considering buying their pro version, but it's unlikely to do live data for the TipTronic in my year and "Tech Support" just pointed me to a vague website.
The owner of the Foxwell is also trying to figure it out for his device for me.
I was hoping to connect with somebody who had fo you d the needle.
@MisterCorn
, I'm too new to send a DM. From what I read in another thread, I need a certain number of posts before I can DM.
If you are willing to advise, please either DM me or respond to this thread.
I haven't used Durametric on a Tip car, but from knowing how the 996.1 data works I can imagine that a lot less data is available than on a car with CAN. If it is a 996.2 I can help with CAN data. I have a Durametric Pro which I'm happy to plug in and see what we can get from it is you are anywhere near Nottingham.
MC
I would love to come visit, but getting my car across the ocean would be expensive. I'm in Kentucky, land of bourbon and horses.
Are you fluent in CAN bus? If I can't find a better option, I can look for open source to get me started and write my own data capture and export tool. But, I haven't slung bits in a while so it would take me longer to get that going. The problem is finding the Porsche-specific info to translate the data, unless it's in a useful format like JSON (English, not binary).
I can see the location being an issue
I will have the full CAN bus data for the tiptronic in the 996.2, which could well be the same as used in the 996.1 I'll see which messages are on there and post some info. It will be Monday now as info is at the office. I do a lot of work with CAN for my day job.
MC
I haven't done much with CAN, but am a retired director of firmware, ASIC development, and electronics. Before having my brain and spine removed for that role, I was an electronics and firmware engineer. Actually, in my various management roles, I spent countless hours with experts on any number of related topics, so I have been exposed to a lot of different thing but we never had reason to explore the CAN protocol.
If you can get to the CAN bus, you might well see messages 0x440, 0x530 from the gearbox. These contain gear position, ATF temperature, transfer function, and torque limit requirement. There are a few messages which are received by the gearbox module, but I don't know which are transmitted from the ECU, as there might be many more transmitted than required, since they are defined in the protocol. If you can get a list of message and what you want to view I tell you where the two overlap.
MC
I'm interested in playing with the CAN bus, but found a way to get data pretty easily. My friend had loaned me his Foxwell NT510 and I couldn't find any documentation or method to extract the data after capture. But then he gave me his copy of the SW and it's very easy to put it in a spreadsheet now!
I have to recalibrate the gas gauge before I drive it again. Tow trucks aren't fun.
@MisterCorn
Unforunately, the Foxwell 510 can only record 4 data items at a time. I think the PIWIS has a limitation of 5 or 6. I think that, for the 2001 cars, they're using a slower data rate than newer cars. So maybe that's why only limited data can be saved?
I may eventually have to resort to writing code, which has been a hot minute. If it's a data rate issues, I'd want to look for a change in the requested gear, then change what data I'm requesting accordingly. I don't need to worry about gears 3,4, and 5 when I"m shifting from 1 to 2, for example. Failing that, I suppose I can just focu on one gear issue at a time.
What do you use to get the data out (what dongle, etc)?
What packages do you use to obtain and parse the data stream from said dongle?
My priority is getting this car whole, but....
This is a source reference. Confirm exact model applicability in the original material.
