Has anyone figured out the PID code to collect Mode data, specifically the OBD monitor rate data (In-use Performance Tracking values)? I normally use a SilverScan (DiagRA) tool or sometimes Ease Diagnostics but needed something more portable and this seems to fill the bill. I just need to know what PIDs to ask for and how to ask using Torque.

If someone has already done a custom plug-in that would be great.

Have you looked at the pushbutton
display (send cmnd) in test mode?

It will send an obdii command and
you can review the response in test
mode. The elm data is returned in
hex.

Edit:

If you create a custom pid for each of
the items in your response layout you
should be able to extract the desired
byte(s) of info with using the appropriate
variable(s). Torque assigns A,B,C…,AA,AB… etc.
to data bytes (not including the header).

Torgue will display the value in decimal
according to your equation.

0x7E8 ECU responding (7E0+8)
0x49 (09+40) mode response
0x08 pid
0x14 # of data items returned in response

0x00 data byte A (0)
0xC8 data byte B (200)
Equation: (A*256)+B = 200

0x03 data byte C (03)
0x86 data byte D (134)
Equation: (C*256)+D = 902

etc.

Here is what I get as the decoded info:

+000265ms INFORMATION: ECU ID: 0x7E8
+000000ms INFORMATION: INF SIZE: 0x14 (20 data items)

+000015ms INFORMATION: OBDCOND = 200 (A*256)+B
+000000ms INFORMATION: IGNCNTR = 902 (C*256)+D
+000016ms INFORMATION: CATCOMP1 = 142 (E*256)+F
+000000ms INFORMATION: CATCOND1 = 200 (G*256)+H
+000000ms INFORMATION: CATCOMP2 = 142 (I*256)+J
+000000ms INFORMATION: CATCOND2 = 200 (K*256)+L
+000000ms INFORMATION: O2SCOMP1 = 118 (M*256)+N
+000000ms INFORMATION: O2SCOND1 = 200 (O*256)+P
+000016ms INFORMATION: O2SCOMP2 = 118 (Q*256)+R
+000000ms INFORMATION: O2SCOND2 = 200 (S*256)+T
+000000ms INFORMATION: EGRCOMP = 191 (U*256)+V
+000000ms INFORMATION: EGRCOND = 200 (W*256)+X
+000000ms INFORMATION: AIRCOMP = 0 (Y*256)+Z
+000000ms INFORMATION: AIRCOND = 0 (AA*256)+AB
+000000ms INFORMATION: EVAPCOMP = 19 (AC*256)+AD
+000000ms INFORMATION: EVAPCOND = 39 (AE*256)+AF
+000000ms INFORMATION: SO2SCOMP1 = 96 (AG*256)+AH
+000015ms INFORMATION: SO2SCOND1 = 200 (AI*256)+AJ
+000000ms INFORMATION: SO2SCOMP2 = 96 (AK*256)+AL
+000000ms INFORMATION: SO2SCOND2 = 200 (AM*256)+AN

If the custom displays work you can
add the pids to your vehicle file logging
which can then be imported into a
Windows program where you will have
to create the report from the raw data.

The data is stored on your phone
as comma separated values file (.csv).
You should be able to share this file to
email. Again, it will only contain the
raw data. You can import into Excel
or Word to create a formatted report
using the data.

The +xxxxxxms value looks like a calculated
timing value from your special reporting software
which will not be available from Torque.

Alternately,

You could create dashboard displays with
your pids and take a snapshot of the screens
which then can be emailed as pictures. (Using
digital display types).

Would be interesting to know what all that
data represents to a lay person

Edit:

OBDCOND
OBDCOND
Header: 7DF
Mode/Pid: 0908
Equation: (A*256)+B
Units: Counts

IGNCNTR
IGNCNTR
Header: 7DF
Mode/Pid: 0908
Equation: (C*256)+D
Units: Counts

etc.

FYI… each pid will poll 0908 independent
of the other pids. Hopefully this will not
cause issues with your reports.

I believe others are using services like
dropbox, photobucket etc. to store their
images then copying the public or img
link to the Torque forum post.

Can you copy and paste the text from
your different response?

I’m guessing the protocol maybe the
difference?

Look under the adapter status icon
to see protocol being used.

Edit:

Setting the unit type to Counts is
recommended. It will show in the
displays.

The following is a multi-line response used
by the protocol. The first portion are the 29 bit
header bytes followed by a control byte for
assembling the message.

Note the characters after the header portion
10, 21, 22, 23, 24, 25 set the assembly order
of the message. (PCI byte).

0x23 # bytes following in the response. (35) padded with zeros afterwards to complete frame.

0x49 (09+40) mode response
0x08 pid
0x10 # data items returned (16)

Torque should still only use the data bytes
for its variables.

……………………………………..A…B…C
18DAF110 10 23 49 08 10 00 6E 00

……………………D…E…F…G…H…I… J
18DAF110 21 D2 00 62 00 6E 00 00

……………………K…L…M…N…O…P…Q
18DAF110 22 00 00 00 5D 00 6E 00

……………………R…S…T…U…V…W…X
18DAF110 23 00 00 00 00 A7 00 6E

……………………Y…Z…AA.AB.AC.AD.AE
18DAF110 24 00 00 00 00 00 1D 00

…………………..AF
18DAF110 25 32 00 00 00 00 00 00

You may have to specify a header in
the pid editor to get a valid response.

DA10F1 ?

0xDA is message type (physical addressing)
0x10 is ecu
0xF1 is tester

0x18 is a priority byte automatically added by elm
to the front of the message.

A message encapsulated in a message.

OBDCNTR
OBDCNTR
Header: DA10F1
Mode/Pid: 0908
Equation: (A*256)+B
Units: Counts

Does this respond?

Quote from lefarmerjr on March 5, 2014
Capp777,

thanks for all your help so far. I tried the header you suggested and still got results = 0.0. I then tried several other combinations and none yielded the desired values. Some even just said no data available. I must be missing something.

I wish I could find a way to just take a screen shot of what I see and post it here. That would be a really valuable feature. It won’t even let me paste something I copy from elsewhere other than pure text.

Is there anything needed in the Diagnostic Start or Stop fields? How about the Header = Auto instead of the one on the testing data screen. By the way, the actual header is as follows: 18DAF110 with the first line then being 1023490810 before the first data byte and the subsequent lines are then just 21, 22, 23 24 and 25 before beginning the data bytes. What should the header be? Blank doesnt work I know.

End Quote.

I was finally able to post a pic using dropbox following the
advice of MJ:

Create a public folder in dropbox using laptop.

Move the desired pic into that folder.

Using the laptop copy public link.

In Torque post click the pic icon to insert special fields.

Click between the two fields for insertion point.

Paste the public link between the two fields.

Suggest you size the picture to no larger than 4″ to fit
nicely in Torque post before adding to post.

Header:

By all means try Auto and see if Torque will use
the correct header.

A special elm command may be needed to set the
priority byte. (The elm should use 18 as a default).

If your point is the F110 are reversed… in a response
the role of receiver/transmitter are reversed as the
ecu is “transmitting” back to the “receiving” scan tool.

The diagnostic start/stop command fields are new
to the pid editor. They should not be used.

Capp777

I tired this again today with creating a PID using the data we have and then ran the Test function. I get data back that is useable but it is still in HEX format and the formula does not return any results.

Here are two pictures I took of the screen showing the PID setup and then the Test result.

I hope this comes out OK.

Use the links in my last post while
logged in from your desktop web
browser.

The links above allow you to enable
the public folder for your account
which has been disabled by default
for newer accounts.

After completing the steps successfully
dropbox will create a public folder
in your account.

Posting a pic works but only with a public link.

The copy public link function appears to
only be available for pictures in your
public folder while logged in the desktop
web browser version of the software.

The copy public link function is not available
in the phone app.

My first pic is on page 11 of Trans Temp, IAT
and MAP thread and I just subscribed to dropbox
less than a month ago.

You are getting a valid response but it looks
like Torque is not parsing it correctly.

Ian will need to sort out why.

Can you tell me what protocol is reported under
your adapter status as being used? (Ian will need
that info to troubleshoot I believe).

I am surprised that your header is working as it
doesn’t match the order from what I have read
about 29-bit CAN headers. Back to the books
for me… my understanding must be wrong.

Is this vehicle fully OBDII compliant?

The top picture shows actual data
is being returned but the equation is
returning 0.0 (not the values as shown
in the response string).

A = 0x00
B = 0x74

(A*256)+B = 116

Supposedly DA10F1 returns zero as well
according to the previous posts. (9-10
posts up).