I recently purchased the Torque Pro app, first let me say awesome app !

I’m using the lower cost bluetooth adapter elm327 mini (small blue device)

The vehicle I’m using this on is a 2002 Dodge RAM 2500 pickup, with the cummings 5.9l engine with manual transmission, app is running on a HTC Thunderbolt.

Before purchased I tried the Torque lite and the gauges I’m interested all worked very well, RPM, Engine Coolant, Intake air temp, Intake Manifold Pressure, Boost (was off by 14.7 in lite app), Speed obd, Speed Diff gps vs obd, voltage at adapter.

With torque pro, Engine Coolant Temp, Boost, Intake air temp and Intake Manifold pressure don’t work. Meaning sometimes the data comes threw sometimes it does not, in most cases does not.

I have tried 2 other generic ODB lite reader programs in the play store, both read engine coolant temp, iat, map pressure fine. So I’m thinking my odb2 blue-tooth adapter is ok.

One thing I discovered, my truck appears to have multiple ecu’s, when I used one of the other odb lite reader programs, one of them detected 2 ecu’s and asked me which one to use, it said I have an ecu with address of D1 or 15, if I choose 15 everything works, if I choose D1 then same issue engine coolant etc no data.

So could it be that torque needs to be told to use the ecu with address 15 ? If so how does one do that in torque ?

At this point I’m not using custom PID’s just whatever comes with the Torque Pro app. I do have Torque scan installed and it shows the same thing “no data”.

Thanks in advance,

Tony

Quote from Capp777 on September 23, 2013

You might try adding one of your
mode 1 pids to the custom pids
and test to see the response(s).

If you know the correct header
for the ecu you will be able to add
it in the custom pid.

Capp777

I do not know pid or header, does the torque app provide this being engine coolant etc, is build into the app ? Otherwise I’m assuming it’s internet search time, so far Dodge 2002 Diesel pids seem to be under tight lock and key.

Thanks for the link.

Yep the 2002 is odb2, but within standard PIDS supports a small subset, not so sure on extended codes. In time I’d like to decipher them but getting information on the protocols, is ruff, unless one has lot’s money to spend on the publications.

From what I can tell the truck uses the ISO9141-2, I get how the pid is created mode/pid. How is the header created ? Then how does one specify a different ECU in the header ? In the sample header you provided what does each hex byte mean etc. or doc’s that explain it I can review.

I tried the engine temp 0105, with a blank header and I got data :). Going to try the other 01/xx pids in a bit.

Thanks

I’ve tried the alternate odb header no luck.

The raw data a when adding a custom pid, scrolls by so fast, I can see at times there is 2 response or more but I can only see 1

On way home from work I tried torque to test the pids I added, torque connected and the built in pids (pids that come with torque) they worked as well as the custom one’s I added.

Again once I re-conected the build in pids stopped working and the custom kept working.

So for now any pid I’d like to monitor (for now mode 1), I have to add as custom and works all the time, the built in pids work every xth time torque connects.

Seems to me this should work better, just not sure what else to try.

I was able to figure the header bytes out, curious minds want to know lol.

So the plus I can get the basic data I’m looking for but I have to do any PID I want data on from ECU 15, as custom PID (custom PID seems to be using ecu 15 with functional addressing based on the returned header, and of course I figure header out correctly). I have to duplicate in most cases, for example torque has engine coolant temp (ect) 05, if I add a custom pid for 0105 I get ect data), data from ECU D1 (which is not much). Torque does fine.

Basically torque on my truck is unable to get data from ECU 15, now on the flip side every xth time when torque connects it is able to get data from ECU 15.

I’m not sure which PID’s are calculated from data and/or pulled from the android device, I was thinking that perhaps most of the ff12xx pids are. None of those work :(, have not tried them when torque is able to get data from ECU 15.

To summarize I get data from ECU D1 fine, any data from ECU 15 has to be custom pid (talking mode 1 standard pids nothing special) when torque connects and gets data from ECU 15 all works ok, meaning custom pids not needed, appears none of the calculated pids (ff12xx) work (perhaps missing data prevents
this ?)

My truck must speak a strange language, need C3PO lol

Thanks for the tips :), think it’s working

Success at this point, I’ve been able to get torque to connect several times in a row, and pull in data, including getting a good amount of the ff12xx pids.

I tried the physical addressing (6C15F1, not sure if I was using the correct priority or not, I took 68 turned on physical addressing bit and came up with 6C) it worked once but, custom pids seem to be confusing it so I delete all custom pids I added. Re-connect then same issue.

I used the header you provided earlier 686AF1, which I believe is functional addressing (again if I have header figure out correct). Using the functional group Legislated Diagnostics (6A I think), Finally it works 5 times in a row connected with no glitches. I will test and observer behavior as I drive to ensure it works ok.

The short I deleted all the custom pids I added, then in the vehicle profile added atsh686af1

Quote from tonyjsan on September 25, 2013
Thanks for the tips :), think it’s working

Success at this point, I’ve been able to get torque to connect several times in a row, and pull in data, including getting a good amount of the ff12xx pids.

I tried the physical addressing (6C15F1, not sure if I was using the correct priority or not, I took 68 turned on physical addressing bit and came up with 6C) it worked once but, custom pids seem to be confusing it so I delete all custom pids I added. Re-connect then same issue.

I used the header you provided earlier 686AF1, which I believe is functional addressing (again if I have header figure out correct). Using the functional group Legislated Diagnostics (6A I think), Finally it works 5 times in a row connected with no glitches. I will test and observer behavior as I drive to ensure it works ok.

The short I deleted all the custom pids I added, then in the vehicle profile added atsh686af1

Did this work as a complete fix for you? I am still trying to figure it out. I have a 2007 5.9 Cummins.