Hello, I've been using Torque for some time, but I've just recently decided to add extended PIDs. I was able to add several ECU PIDS, and the values reported are correct, except that each PID periodically displays a bad value. This happens about once per second, but it is somewhat random. During some sessions, the values would drop to zero (or -64 for my A-64 PID), but I've also seen the values be much higher than the expected number. It happens to every extended PID, but none of the standard PIDs. When I run the OBDLink application (similar to Torque, less functionality), the extended PIDs work without issue.

I have a 2012 Jeep JK with a 11-bit CAN ECU. My OBD adapter is the ScanTool OBDlink LX. My extended PIDs are all mode 22, and the header for each is 7E0. I think 'auto' header also works. I have signed and unsigned words and bytes, and it happens to all of them. My equations all use 'A' or 'A & B' The issue is present whether the engine is running or not (ignition on, of course). I tried the 'fast communication' on/off, 'disable ELM327 auto timing' on/off, and the 'use alt OBD header' on/off; they did not fix the issue.

I searched the forum and found only one similar description by someone who had the USB version of my same adapter (May 2, 2014). In that case, Ian said it was due to a bug which he then corrected.

Anyone have any ideas?

thanks, Craig