kctrey, this post sat idle for a couple of months. I hope you’ve made some progress.

I’m after the same data with a 2001 Toyota Sequoia (SUV built on Tundra frame & powertrain 2UZ-FE).

I won’t post the Toyota extended PID list (pre-2005 & pre-CAN). I will suggest a Google search for:

"68 6A F1 01 A0 CS"

From that list, F8 “State” might take some detective work. However, the F9 address request might be more fruitful.

F9 - BIT IS 1 = BYTE 3(b1) - Shift Position Switch in L
F9 - BIT IS 1 = BYTE 3(b2) - Shift Position Switch in 2ND
F9 - BIT IS 1 = BYTE 3(b3) - Shift Position Switch in R
F9 - BIT IS 1 = BYTE 4(b1) - Shift Position Switch in 3RD
F9 - BIT IS 1 = BYTE 4(b2) - Shift Position Switch in 4th/Drive 

We can probably interpret a bit rather than a bitmap.

I haven’t tried this out yet. My concern is that “Shift Position Switch” will give what is selected on the steering column and not what is selected in transmission. For example, select “D” and the transmission is in 1st gear, but the F9 BYTE 4(b2)is “1”.

I’ll update this when I get a chance.

Third byte, first bit (if I’m reading that correctly)

The equation parser can deal with ‘bits’. However I’ve not tested it…..

If you get a readings for ‘C’ (third byte) and want to get the ‘bit’ for use with the on/off gauge, try the entirely untested:

Equation: C & 256

(edit: the above was 10000000, but that was wrong, it should be a ^2 figure – ie: 1, 2, 4, 8, 16, 32, 64, 128, 256)

Note: it may not work, it may work, it’s untested. It won’t work if C doesn’t come back with a value when the equation is just ‘C’ – you’ll need to get that working first.

Also, you may need to specifically set the header to: 686AF1 instead of ‘auto’

Possibly, but the scanner doesn’t touch mode1 PIDs at the moment, only the upper mode 21/22 ones. I might sort that out when I get round to updating that plugin

Don’t need to donate to paypal have a look at the torque widgets app if you feel like donating – you get something for it then!

Ok. Now I am puzzled. What equation would I use to get the value A (or AC) from the third line? Am I approaching this all wrong?

Command: 2141 response:
015
0:61412F672851
1:2800002CB32851
2:28782823000D0B
3:AC000000000000

Some updates and questions on my Toyota PID quest:

I now understand why many ODB-II products do not support Toyota enhanced PID’s. My experience, so far, indicates there is notable variation in PID support from model to model during the same “Toyota PID Protocol Era” (TPPE). For example, the suggested google search above for enhanced PID’s is for a 2004 Camry. My ’01 Sequoia is from the same TPPE (roughly 1996 – 2005) ISO 9141-2. My sample test efforts to get more data from my Sequoia’s ECU have been futile. The ECU responds with 0.0 ( and not “No Data”) when those PID’s are requested. I infer that to mean the ECU supports those PID addresses, but there is 0.0 assigned to them. I speculate Toyota ECU’s from the same TPPE are standardized PID’s, but which data is actually collected varies considerably among the models. Effectively, google-fu and trial and error can lead you to the point of “Oh, I guess my car/truck doesn’t gather that information.” This is disappointing when you’re able to see all the data the Prius community is able to collect from their ECU’s.

It’s extremely difficult to brick an ECU, the message is mostly for indemnity…

Telnet is okay (it can be a bit tempermental so you may have to restart it if it stops responding).

686AF1 <- that’s your header – you won’t usually need to type this

If you did ’01A0′, then that /should/ give you the list of PIDs for that range for Mode 01 requests.

Quote from zantets on August 10, 2013
hi this works on my 2002 toyota corolla:

PID: 01F8
Short name: Shift
Long name: Gear Position
Min: 0
Max: 255
Scale factor: x1
Unit: Gear
Equation: A
Header: auto

I’m looking for these display to my Toyota Corolla Xei 2003 A/T(Brazil). I’ll test this custom PID tonight in my car.

You might try equation of A&7.