Admin, would you confirm if any x-gage code starting with 07E1 means this PID could not be handled by Torque Pro?

Bump.. 🙂

Dont know if this applies to your question.. try searching "7E1". Some info
on 7E1 in header field.

Thanks for that..

I've tried 7e1 instead of the Auto for the header.

Strange I'm getting changing erratic values, not indicating temperature.

Though the same 21d9 code is reading ATF temperature on the XGauge.

Try equation (A)-40 for your info..

Edit:

Also found...

7E0 2182

A * (9/5) - 40

Units: °F

or...

7E0 21D9

((A*256)+B)*10*(7/100)-400

Units: °F

Hi,

For 2182 no data.

For 21D9, Header 7E1 (or blank), A-38:

I'm reading values like -29 on P, then -17 on N, then -11 on R, then -19 on D.

I could reach the correct formula if I was receiving values which are consistent with the temperature.

If it is changing values as such, am I reading the right positions?

Were you able to try the equations i listed to see if
they gave reasonable values?

Note the 7E0.

Value may be x10.

Actually just tested the A to see if it will be consistent in readings..

Will try the whole formula today and let you know.

Thanks for the 7E0 note. Meaning will leave the Header value blank?

I believe Torque selects it by default but
setting the header to 7E0 should eliminate
the guessing.

OK, here are the results:

2182 No response (whether 07E0 or 07E1)

21D9 (Does not matter if I input to the header 07E0 or 07E1) It reads the same.

Readings for 21D9.

There are two double words being read in the test mode.

After observing both double words over time, the values changing consistently up and down with time reflecting temperature are in the second double word, bytes number 3 and 4.

Which formula parameters represent those bytes?

Second DWord:

1234 5678 90AB CDEF
0 1 2 3 4 5 6 7

As for variable addressing... you can try changing the variables
to match position in the response.

Quote from admin on June 17, 2011
A represents the first sequence of bytes in the reply from the vehicle, so it's basically the first 'Value'.

Data comes through in pairs of hex bytes (0-F) and is converted to decimal for ease of use, so the first 0x00 is A, the second 0x00 is B, etc.

Excellent, now I receive two values in the form of

001122334455
and
6677889900

A= 00
B= 11
C= 22
..
..
G= 66 ?

After converting the values to decimal..

Am I correct in the G value above?

If the response string is long your pairing would
be correct (A to Z then AA, AB ... AZ, BA ... etc. )
Just a matter of extracting the bytes of interest.
I believe the header bytes are not included just
the data bytes following.

Managed to extract the right bytes for both temp sensors.

the are E and F for sensor 1, G and H for sensor 2

44C0 is equivalent to 28 degrees celcius.

Any idea what the equation could be?

Do you know what these values are
After heating up and their corresponding
°C?

Have the highest recorded value as 7260 (think would have been in the 90's or ealy 100's celcius). Probably need to borrow a scangauge to test this.

Not sure if this will work but here we go...

Based on

Variable E F G H
44 C0 44 C0 @ 28°C

72 60 72 60 @ 100°C

Equation

(((E*256)+F)*0.00616)-80.5
(((G*256)+H)*0.00616)-80.5

Dont forget to try (E)-40 if all else
fails.

Thanks Cap.. will do some further testing, consult a scangauge and come back with a definitive answer. Might take a few days though, for the scangauge.

Quick question for those who have experience with ATF temp.

Does it change very quickly? Like up or down 5 degrees celcius in like 15 seconds?

The E-40 formula exhibits more stability.. like up or down 2 degrees per minute or so. It is also more realistic, like in the range of 70 degrees at normal load and speed, while the 0.00616 formula runs at 100-110 celcius.

Have yet to install scangauge to confirm which of the two formulas is the right one, or maybe none.