Hi All,

I bought a cheap ELM327 OBD-II adapter (https://www.amazon.co.uk/gp/product/B01A...UTF8&psc=1) for my car (Pug Partner 2007, 1.6HDi, no dpf/fap).
I also got the Torque Pro app (android phone) and it works without a problem, but the app cannot obtain data from several sensors. I am mainly interested in the % EGR. I know the data are supplied via the OBD-II, as PP2000/Lexia displays these values.

The torque app allows for custom PIDs (hex code), but does anyone know what are the PID values for the various sensors? Alternatively, does anyone know how to get the PIDs that Lexia is using for say the EGR or other sensors?

Cheers,
saskak

Sorry it is not possible because that engine ecu is using k-line and KWP
protocol to communicate and send info about sensors.
Some sensors readings are "converted/transcoded" to OBD standard,
just to comply to OBD nothing more...
For OBD standard you can get some sensors over PID but for ERG
you have to go into KWP protocol and get info.

Here is good starting point : https://github.com/iwanders/OBD9141

Best regards,
brajomobil

(17-12-2018, 07:38 AM)brajomobil Wrote:  Sorry it is not possible because that engine ecu is using k-line and KWP
protocol to communicate and send info about sensors.
Some sensors readings are "converted/transcoded" to OBD standard,
just to comply to OBD nothing more...
For OBD standard you can get some sensors over PID but for ERG
you have to go into KWP protocol and get info.

Here is good starting point : https://github.com/iwanders/OBD9141

Best regards,
brajomobil

Many thanks Brajo. It is indeed KWP fast, rather than CAN bus.
The Class seems that can be incorporated into an Arduino Uno, which I have but will see if I have enough time to do something about it.

Many thanks again for the info.

I am somewhat confused about these extended PIDs. If Brajo is correct that I can only get PIDs tapping into the K-line, then I should not be able to get additional PIDs from Torque Pro, but I do.

I only managed a quick full scan of extended PIDs (2x15min running) and get a few additional PIDs that are not the standard EOBD. I will need to fully charge the battery or have a long run and wait for the scan to complete. I get a few PID hex starting with 21 and 22. As far as I understand these are the manufacturer specific PIDs. See photos attached. Figuring out the equation and what they represent might be problematic though.

   
   

Cheers,
Saskak

One of the problems you're having may be that different ECU's talk on different OBD connector pins with only 'basic' OBD compliance info coming via the 'standard' OBD pin.

https://mhhauto.com/Thread-Looking-for-2...or-Pinouts

(18-12-2018, 10:44 AM)cancunia Wrote:  One of the problems you're having may be that different ECU's talk on different OBD connector pins with only 'basic' OBD compliance info coming via the 'standard' OBD pin.

https://mhhauto.com/Thread-Looking-for-2...or-Pinouts

Thanks for the info, but how basic is 'basic' compliance. I assume that basic compliance is byte A + byte B, perhaps C and D, but these should be enough to get the sensor values. Anything else is probably manufacturer specific and no way of knowing what it represents.
My car was manufactured Sep 2007, but I doubt it is CAN.

I'm guessing that there's a minimum / basic OBD compliance spec somewhere & that perhaps EGR & other values are not included in that spec, or maybe were not included at the time of M59 manufacture. For Lexia or PP2000 to display EGR etc, maybe they're encoded and/or come via one of the other K-Line pins. AFAIK all of the M59's are VAN rather than CAN-BUS, mine is April '08 and is the same as my '04 in that respect so far as I can see.

(18-12-2018, 11:22 AM)cancunia Wrote:  I'm guessing that there's a minimum / basic OBD compliance spec somewhere & that perhaps EGR & other values are not included in that spec, or maybe were not included at the time of M59 manufacture. For Lexia or PP2000 to display EGR etc, maybe they're encoded and/or come via one of the other K-Line pins. AFAIK all of the M59's are VAN rather than CAN-BUS, mine is April '08 and is the same as my '04 in that respect so far as I can see.

I might have to read a bit more on the obd queries and responses. From the short PID scan, it seems that some are returning 4 bytes as expected under obd-ii/eobd, but others return quite a few more bytes, including multiple ECUs.

Cheers

Interesting, would be good to see what you find out.

(18-12-2018, 11:40 AM)cancunia Wrote:  Interesting, would be good to see what you find out.

I will post any results that are of any worth.