search

adamahani / android-obd-reader

Automatically exported from code.google.com/p/android-obd-reader
0 stars 0 forks source link

Trouble Code - Strange Results #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Running the trouble codes command 03 for a know MAF failure returns only 5 
bytes of data after the 43 response when it should return 6.

For example, I unplugged the maf on a 2008 Mazda3.  The codes set are P0102 and 
P0113  When I run the 03 command the response is:
43 02 01 02 01 13 \r\r

It should be:
43 01 02 01 13 00 00

Or something like:
43 01 02 01 02 01 13

ANy idea why it would do this?

Original issue reported on code.google.com by jm...@saveology.com on 23 Apr 2011 at 1:16

GoogleCodeExporter commented 9 years ago 
Will look into this after issue #10 is closed.

Original comment by pjpi...@gmail.com on 22 Sep 2011 at 6:40

GoogleCodeExporter commented 9 years ago 
where did you get the protocol to interpret the response?
is there a manual or something?

Original comment by federerc...@gmail.com on 19 Dec 2011 at 9:04

GoogleCodeExporter commented 9 years ago 
federerc...@gmail.com:
http://elmelectronics.com/DSheets/ELM327DS.pdf

Original comment by DragonxX...@gmail.com on 22 Dec 2011 at 6:07

GoogleCodeExporter commented 9 years ago 
seems i got inregular response from obd device.
when i send 01 0F to check the engine run time , i got this: 7F0112/r7F0112.
and the response won't change as the test goes.

Original comment by federerc...@gmail.com on 6 Jan 2012 at 6:20

GoogleCodeExporter commented 9 years ago 
This is a response from the ELM device and not a software bug, to my 
understanding.

Original comment by pjpi...@gmail.com on 24 Jul 2013 at 1:28