is torque pro extended pids toyota 4runner

At first look I believe once Torque gets the answer it was seeking it remembers the format for the duration of that session but not further. Then Torque adds the '01' to the end of the PID, as in this case would be 22162B01, and bingo, the PCM answers with the data requested on the first request, speeding up the original startup at least. Torque sends the same request again and is again rejected. When set to 'Auto' (CasE sEnSiTiVe) Torque first sends the PID as entered in the extended PID definition and with many of the PIDs the PCM essentially rejects the request. I snooped the Class 2 bus while using Torque and found that with the 'header' left blank many extended pids fail. Since that other post I have discovered that if one adds an '01' the the end of these extended PIDs the Torque app will receive the data quicker from the PCM as Torque won't need to cycle through formats seeking an answer from the PCM. Header should be set to 'Auto' (cAsE sEnSiTiVe) and the equation is 'A * 16'. 22 being the mode or service and 162B the actual PID. So as posted elsewhere the PID for Fan Speed to enter into Torque extended PIDs is 22162B (I confirmed only on a 2002 4.2). I have been spending a great deal of time fiddling with these PIDs of late and have additional informations that I will post on this thread. It is possible that this is my first original post! It was properly suggested by MRRSM that I repost that information here so here I am. A short time ago I posted a new pid I discovered for the Fan Speed of a 4.2 in a 2002 Trailblazer.

Is torque pro extended pids toyota 4runner