http://torquebhp.wikia.com/wiki/How_to_add_extended_PIDs

Thanks. That's exactly what I was looking for.

Do you know if enumerations are supported?

For example, can I convert a data value of 1 to display "P", 2 to display "R", 3 to display "N" etc?

Not at this time. Torque can do bit examinations
for ON/OFF displays if this would help in the
meantime...

{A:7} MSB
{A:0} LSB

Thanks for the info. I'll just have to display numbers for now.

I can't get the extended PID to work. Here's the message I'm trying to get:

1F5 03 03 00 06

The PRNDL data is in the last data byte(value of 06 in this example)

Here's what I put in the csv file:

"Transmission Shift Lever Position", "PRNDL", "01F5", "C&120", 0, 9, "", ""

Am I doing something wrong?

I verified that the message is being transmitted periodically and on change via the telnet terminal pass-thru of the Torque Scan plugin.

Thanks

I think I figured out part of it. I need to use a mode 22 physical request for the data. I tried this:

“Transmission Shift Lever Position”, “PRNDL”, “2201F5", “C&120", 0, 9, “”, “”
I get:
Command:2201f5
Response: 7E 0A 03 7F 22 31, which I think means PID is not supported by that controller.

So I tried:
“Transmission Shift Lever Position”, “PRNDL”, “2201F5", “C&120", 0, 9, “”, “TCM”
I get:
Command 2201f5
Response:NO DATA

So I tried:
“Transmission Shift Lever Position”, “PRNDL”, “2201F5", “C&120", 0, 9, “”, “7E0”
I get:
Command 2201f5
Response:7E E8 03 7F 22 31, PID not supported

So I tried:
“Transmission Shift Lever Position”, “PRNDL”, “2201F5", “C&120", 0, 9, “”, “7E1”
I get:
Command 2201f5
Response:NO DATA

I went through all the rest of the controller numbers(7E2 through 7E7, and they all come back with a response of PID not supported.

I'm guessing the TCM is 7E1. Do you know why it doesn't respond?

Is there a way to just grab the CAN bus data that is already being broadcast periodically for this PID instead of requesting it??

no you can just pickup the data that is broadcast
i asked for that in the past
it's not an option

i just don't know if you would ask the request 8 below the broadcast adress if it would see it as an answer

i haven't tried that

and sometime it's better to look for the info in test mode

since it show you the full response not only the result of the calculation

if it's no data it's the same but like in my case the result
were on 5 lines so it took me 2,3 test before catching the right variable i think was O and P in my case

and i was wondering what you were talking about with the CSV i didn't know you could do that

Quote from trindywest on February 27, 2015
I can't get the extended PID to work. Here's the message I'm trying to get:
1F5 03 03 00 06
The PRNDL data is in the last data byte(value of 06 in this example)
Here's what I put in the csv file:
"Transmission Shift Lever Position", "PRNDL", "01F5", "C&120", 0, 9, "", ""
Am I doing something wrong?
I verified that the message is being transmitted periodically and on change via the telnet terminal pass-thru of the Torque Scan plugin.
Thanks

You can create separate devices 9 for this case
for example
https://yadi.sk/i/lWHOUuubevc8F

Thanks moreause.

Yes, capturing the periodic broadcast message data would be nice. I'll submit that as a feature request, too.

I believe the periodic broadcast messages are referred to as functional messages, while the mode 22 PID requests are referred to as physical messages.

I did finally get this to work. I was trying to request the functional PID number that contains the PRNDL info instead of the physical PID number for that info.

Here's the mode 22 physical PID setup that works on this vehicle:

"Transmission Shift Lever Position", "PRNDL", "22194F", "A", 0, 128, "", ""

You can create a .csv file and put it in the sdcard/.torque/extendedpids directory on your android device. Then go to settings in torque, then Manage extra PIDs/Sensors, then add predefined set, then select the .csv file to import all the PIDs at once.

Thanks, cintakc.

I may do that to display each gear. The enumeration feature would be really nice, though.