Torque is using A-40 °C for its GM TFT PIDs.

Byte A=3C which equals 60 decimal…

60-40= 20°C which equals 68°F in previous
posts.

Ok, managed to check a few more things today. Was hoping to get TorqueScan results – I did get them on the phone, but could not email them. Got a message something like “Could not attach empty file”.

Using the Test option in the PID editor I came up with the following:

(First with the ‘atz’ (Very Advanced – ELM327 custom configuration string) under Vehicle Profile:

Testing PID with atz

Result for equation: 42

Command:
221940

Start Diagnostic Response:
3E00
7F 3E 00 11

Variables used in equation:
A=82(hex=52, binary=01010010)

Equation steps:
‘=A-40

Next with the ‘atz’ setting removed:

Testing PID without atz

Result for equation: 43

Command:
221940

Start Diagnostic Response:
6CF1187F3E001171

Response:
6CF1187F22194012F6

Variables used in equation:
A=83(hex=53, binary=01010011)

Equation steps:
‘=A-40

Quote from Capp777 on March 12, 2017
The 7Fxxxxxx responses are failed responses
from the TCM.

Did you ever test the 3F version of tester present
from earlier posts?

You didn’t give the response to the working
version of command using ATZ.

@Capp777, I stayed away from the 3F versions as there was mention about them possibly messing with the ECU, and I am not smart enough about all this to understand the possible impacts.

I don’t think there was a response from the setup with ‘atz’ entered, unless it was the ‘7F 3E 00 11’ info.

Here are the results showing the PID setup and the PID testing status. 2 PIDs were used – Transmission Fluid Temperature (GM Method 1 and 2).

First batch is the GM Method1 –
PID setup:
ODB2 Mode and PID without atz
221940
Long Name
Transmission Fluid Temp (GM Method 1)
Short name
TFT-GM1
Min Value
0.0
Max value
300.0
Scale Factor
x1
Unit type
°C
Equation:
A-40
OBD Header to use
6c18f1
Diagnostic start command
3E00

PID Test:
Testing PID without atz

Result for equation: 24

Start Diagnostic Response:
6CF1187F3E001171

Command:
221940

Response:
6CF1187F22194012F6

Variables used in equation:
A=64 (hex=40 , binary=01000000 )
{display read 75.2)
Equation steps:
‘=A-40

========================================================
Now the same thing but with the ‘atz’ setting in Vehicle Profile.

PID test with ‘atz’:

Testing PID with atz

Result for equation: 35.0

Start Diagnostic Response:
3E00
7F 3E 00 11
Command:
221940

Response:
229140
7F 22 19 40 12
Variables used in equation:
A=76 (hex=4C , binary=01001100)

Equation steps:
‘=A-40

Next post will have the info for (GM Method 2)

Quote from Capp777 on March 12, 2017
An after thought… if ATZ is getting your
custom pids to work, you might try creating
your own OBDII pids using 686AF1 as their
headers.

Engine Coolant example:

Header: 686AF1
Mode/Pid: 0105
Equation: A-40
Units: °C

Engine Oil Temperature:

Header: 686AF1
Mode/Pid: 015C
Equation: A-40
Units: °C

Engine RPMs:

Header: 686AF1
Mode/Pid: 010C
Equation: ((A*256)+B)/4
Units: RPM

Your long names must be unique and
different than what Torque uses.

7F3E0011 means failed response to
3E00… mode not supported. Ian had
mentioned this in earlier post.

Do this mean to leave the ‘atz’ setting, and then create PIDs as above for the non-working ones to create a complete setup?

BTW, thanks to all for the help, greatly appreciated.

Quote from Capp777 on March 13, 2017
That’s what I was thinking…trying to get
the OBDII pids working with your ATZ
solution.

Please note that 07E0 and 07E2 are CAN
Header addresses… NOT VPW commands that
your vehicle recognizes.

I suggest leaving the diagnostic commands
blank.

Edited.

Excellent – I’ll give that a try the next time I have a chance to mess with the settings.

Thanks,