Take a screenshot of this PID test

Here are a few screenshots. Took a bit longer to get them due to being out of town.

In the profile settings, write the initialization string
atsp7\natshda1df1
Take again the screenshots of the test PID and screenshots two devices near
1 Coolant
2 Trans Temp

I can’t add a screenshot right now but I did add the initialization string. That didn’t seem to make a difference in the output, still stayed at -1 but I did get this response when testing the pid:

Start Diagnostic Response:
OK
OK

I tried to pull up the files that were linked earlier in the page but it looks like they disappeared. However I did look at things after a cold start and after a 25 minute highway drive.

Cold Start:
Car sat all night
57.2F Coolant Temp
The HEX value in the 4th row that was 79 in the screenshot converted using the formula: 51.8F
The HEX value in the 5th row that was 61 in the screenshot converted using the formula: 55.4F

After the 25 minute drive:
The HEX value in the 4th row that was 79 in the screenshot converted using the formula: 183.2F
The HEX value in the 5th row that was 61 in the screenshot converted using the formula: 147.2F

I went through all other locations in the screenshot and none of the others stuck out as a good fit.

My speculation is the 4th row that had a 79 is probably the correct value for transmission temp. However, I don’t know how the locations are defined so that I can pull that into the formula. Can someone explain how the hex locations are defined?

Does A start in the 2nd row and correspond to 02 in the screenshot?

I may not be following correctly but I am thinking it is:

2nd row
A=02
B=CF
C=00

4th Row
K=32
..
N=79

5th Row
R=61
..
T=61

However, you recommend U and V which is different than the N or T that I would try based on my understanding.

I did some troubleshooting and it looks like it is pulling values much later than what is being explained. Basically I can only choose the last 4 values by using A, B, C or D. anything I can adjust to pull earlier values? Anything beyond D returns a -1, must be due to it going past the end of the data.

Rx or Nx didn’t seem to work either. Rx didn’t seem to be pulling relevant data that I could tell from anywhere in the stream. Nx matched up with the other method (N0=A…N3=D).

What would it mean if I am dealing with an ATH1/0 or ATCAF1/0 issue? I tried to look around at various settings and didn’t see anything that resembled that.

Thanks for the help so far!

Sorry, forgot to upload those yesterday. I didn’t notice much different with the revised string. I’m not sure if I captured what you wanted for two devices near coolant temp and trans temp. If there is something additional needed let me know.

Quote from cintakc on May 9, 2017
in this screenshot no device “Oil temperature A/T”

Not sure I follow the request. Do you want me to create a gauge for the custom transmission temp PID and include a screenshot of that? I can add a gauge for the custom transmission temp PID but I would expect it to stay at -41.8. The PID test screenshot was taken when the engine was running.

I also looked for the “Oil Temperature A/T” and didn’t see it in the list. I did see two other standard (not custom) PID options for transmission temp PIDs to add to the display. However, neither of those worked and one just appeared to be exactly the same value as coolant temp.

Still curious if you tried what I suggested in
previous post…

ATH0
ATCAF1

It looks to me that Torque is parsing the
format shown on page [1] but not yours.
The message data looks similar for both
of you.

Based upon my readings CAN Auto formating
uses the x: layout.

I believe…

You are talking to the vehicle with the correct
protocol and baud rate, you are getting a proper
response from your desired pid, the layout presented
back seems to be the source of the Torque parsing
issue.

Torque has a history of not reading some users
CAN 29 Bit protocols but has worked for others
like the OP. I’m starting to believe its related to
how the CAN Auto Formating is set and the way
the multiframe data is presented to Torque.

My two cents and as always could be wrong.