View Single Post
Posts: 6 | Thanked: 17 times | Joined on Aug 2012 @ Ljubljana
#133
Originally Posted by wictor View Post
Hi,
First of all, I only have one DTC P0135, and that has been tested with "proper" diagnostic software with my bluetooth ELM327..
That verified info is very useful information.

Originally Posted by wictor View Post
Code:
Send: 0101
data: 41 01 81 07 61 21
Number of stored DTC:1 MIL: 1
Send: 03
DTC result:43 01 35 00 00 00 00
Send: 07
DTC freeze result:47 00 00 00 00 00 00
Value : P0309 Active Cylinder 9 Misfire Detected
Obviously PyOBD is calculating/decoding DTCs the wrong way. Checking by hand, DTC result from the car (01 35) is exactly P0135 (according to OBD2 PIDs Wiki - Mode 3).

At first glance in the code it seems to me that obd_io::decrypt_dtc_code does things the right way, but is not used anywhere in the code. Instead, obd_io::get_dtc is taking the wrong chunks (3+3 bits at a time, instead of 2+2+4+8 bits) for decoding codes.

I get my car back on saturday, so until then, I won't be much help about this. Perhaps @m750 will have the time to look into this.


Originally Posted by Crogge View Post
I tried the latest version with my Mercedes W203 today and had sadly only partial success. Other OBD applications (Android) work generally without problems. I'm using a normal ELM327 adapter.

Any idea why nothing happens after "Send command:atz"?
Could you check if your phone is connected to the right BT device? Before selecting "Connect to ECU", what device is listed at "BT dev" on the bottom of the Status page? It should be "ELM327" rather than "Andy's iPhone".



Calculating gears seems very easy and reliable (in higher gears at least). I used ROUND(Speed/RPM*160) for calculation. When shifting gears / holding the clutch, gear is higher (unfortunately I do not have 6th gear)
 

The Following 4 Users Say Thank You to GizmoXomziG For This Useful Post: