3 captured repliesDiscussion pagination complete · Source accounts, not a confirmed diagnosis
THIS DISCUSSION / SOURCE-DERIVED OVERVIEW
Discussion summary
YOUR RESEARCHTo Piwis or durametric, OIL temp. Cheapest opt.?
Leading reported evidence
Check every 5 degrees
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
I checked every 5 degrees from 140F to 320F (which is as high as the DME can read).
Leading evidence: 'Check every 5 degrees' (no explicit attributable resolution; this is a reported action or suggestion). Across 1 matching discussions, the most frequently mentioned possible cause is 'cheapest way' (1 discussions; 0 report identifying it and 1 suggest it). The most frequently discussed action is 'Adjust oil temp' (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
Then I graphed the data and used excel to compute a regression function.
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
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
To continue, what I did was to use a potentiometer to simulate the oil temp sensor.
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 used the potentiometer to adjust the oil temp to every 5 degree increment as read by my Durametric, then measured the voltage at the DME.
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.
3 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: 20261026T161109Z · outcome-qualification-6. Deterministic extraction; no AI model inference. How we use sources
Hi all,
So I am currently in the progress of making an oil temp guage kit for the 996.1/2, 986.
You Tube
I of course have a friendly mechanic that would allow me to use his piwis (sounds terrible i know).
I would like to be able to connect to the 996 to be able to view OIL temp and recreate a voltage curve based on that. OBD will not display such information.
Similarly I would like to check timing and deveation respectively for the 97/96, to be able diagnose timing guides etc... I will also be installing some mode and would love to be able to clear codes.
In general, I am looking for the cheapest option to do the above.
Thanks!
When I did this I used a Durametric. That's probably the cheapest way to read oil temperature. Other ways are: (1) I have a Cobb Accessport that reads oil temp; (2) Some have said, unconfirmed, that the Icarsoft devices can read oil temp.
To continue, what I did was to use a potentiometer to simulate the oil temp sensor. This let me set the oil temp anywhere I wanted it. I used the potentiometer to adjust the oil temp to every 5 degree increment as read by my Durametric, then measured the voltage at the DME. I checked every 5 degrees from 140F to 320F (which is as high as the DME can read). Then I graphed the data and used excel to compute a regression function.
I also did this for the 722.6 Tiptronic, except Durametric can't read any values from the TCU. I found the temperature/voltage curve of the temp sensor on a Mercedes forum and validated it using an infrared thermometer. Again I used excel to compute a regression function.
I build a lot of equipment based on the Analog Devices ADUC843 CPU, which conveniently has a bunch of ADC's and two very accurate delta-sigma DAC's for output. So I took a scrap board and rewired it to signal condition the two voltages and present them to the ADC's. I wrote the software to interpret the ADC inputs into temperatures, then to output the temperatures to the DAC's so I can read them on little digital voltmeters - one for oil temp and one for ATF temp.
It works fabulously! My next generation device will use an RS485 network to link sensors together to a master display. I want to add a bunch of sensors for things like brake temperature, intake air temp, fuel pressure, boost pressure, suspension position, who knows what else.
