I need to program a custom PID, anyone have any experience, or know someone?

I'm trying to add a custom PID to my OBDLINK LX to display the oil temp. I'm a developer by trade but I've never coded OBD before. Can anyone help or point me in a direction? Here's the info from the OBD database for the Oil temp: 5C 92 1 Engine oil temperature -40 210 �C Formula is A - 40 The folks at OBDLINK sent me this: https://obdsoftware.my.site.com/s/ar...r-defined-pids

Not possible, at least from everything I've read. Oil temp and pressure wasn't even reported on the can until the 997 generation. If you want to log them it must be with external sensors.

The oil temperature is not reported on the CANBUS (OBD2). It's only reported by the DME on the K-line which is a different protocol and not compatible with OBD2 dongles. Previously covered in this thread: https://rennlist.com/forums/996-foru...l#post13459799

Quotes source posts: 19042959, 13459799

Ok. I have a durametric pro and a icarsoft POR v1.0 that both can read the oil temperature in real time. I didn't know that value was not being reported via the CANBUS. Thanks for the info, saved me a lot of time. I guess I'll just leave the icarsoft hooked up and after a run check the oil temp, or mount it to the dashboard and watch it live!

Two good options https://rennlist.com/forums/996-foru...emp-gauge.html https://rennlist.com/forums/996-foru...ispreloading=1

k-line does actually seem to be supported by some variants of the elm327 chip, I think its just the software side (eg torque) isn't coded to use that interface.

Quotes source post: 19042996

I have the @Coopduc gauge -- the first link. I love it. I think I'd use the Durametric if I wanted to record values.

The plot thickens, hooked up my bluetooth scanner to my manual 2000 (no can bus at all from my understanding), the adapter reports it's communicating via iso-9141-2 aka K line. Did a quick pid scan but its all hex values, I've also got Coopduc's oil temp gauge so I'll try to get a bunch of readings and see if any of the discovered pids match up?

Quotes source post: 19043125

Here is what you can get ECU_1 OBDII_RPM RPM ECU_2 OBDII_SPEED Speed ECU_3 OBDII_ECT Engine coolant temperature ECU_4 OBDII_TPS Throttle position sensor ECU_5 OBDII_IAT Intake air temperature ECU_6 OBDII_MAP Manifold air pressure ECU_7 OBDII_MAF Manifold air flow ECU_8 OBDII_FUEL_LEV Fuel level ECU_9 OBDII_PPS Pedal position sensor

The DME's in the 996's can send out two different data streams on the K-Line.. Which data stream it sends depends on which query/request/Protocol it receives from the interface tool.. If the DME receives the generic OBDII Protocol over the K-line it will send the data steam that Hdunn posted above... If the DME receives the Porsche specific Protocol over the K-line, it will send out the more detailed Porsche Manufactures data stream that includes the oil temp and much much more data and programming capabilities and drive link functions and more.. The "Porsche specific Protocol" is hard to get and is why not many interfaces have this feature.. The "generic OBDII Protocol" is GOV mandated and free to anyone to use by law..

I picked up an icarsoft to try and dig a little deeper into what's happening here, at least on my 2000 c2 dme values seem like they should be coming in on the pin 7 k line, vs pin 3 for the other accessory systems. The readings are matching up fine with coop's gauge, however when I took the car out for a spin to graph the warmup temps above a certain speed the measured value would not update, bringing the car to a stop at a stoplight would then jump the value to the current correct temperature. Sasilverbullet (or anyone else with a scanner), does this happen to you as well? If the DME stops reporting oil temp once it thinks you're actually driving that's pretty much game over, if there's just extra traffic on the k line when the car is driving then maybe its my scanner failing to keep up with traffic.