Three different datastream definitions for the L05 use the same chart of A/D to CTS values and based on the values it appears that inverted CTS is output on the ALDL. Is this how the conversion is set up for the scanner part of TP? If not, then the values you see when testing may not be correct. If you're monitoring events using ALDL data and you're unsure of the temp conversion, use the hex values.
The ALDL end is all documented in ALDL.ds charts, but I went to double check my work. Temps in ALDL datastream have always been correct from startup (ambient) to warmed up (T stat temp), data coming in is raw and goes to a lookup table.
Code:
5 COOLANT TEMPERATURE SEE TABLE 1
Value of coolant X sent to lookup table, look up mode is Interpolate.
TABLE 1 --- COOLANT TEMPERATURE
A/D DEGREES
COUNTS C
------- -------
255 -40
251 -30
250 -25
247 -20
245 -15
241 -10
237 - 5
231 0
225 5
218 10
209 15
199 20
189 25
177 30
165 35
152 40
139 45
126 50
114 55
102 60
92 65
81 70
72 75
64 80
56 85
50 90
44 95
39 100
34 105
30 110
26 115
23 120
21 125
18 130
16 135
14 140
13 145
12 150
0 200
So I believe ALDL temp data for comparing what is happening is accurate.
Since I see the same remarks in disassembly I'm wondering if this is where they got the info? And one parameter already has been proven to not need this, it was not marked 1KPUP, but had a conversion, take out conversion and it is accurate in hex compared to data stream Coolant temp.
But in TunerPro XDF looking at:
LD299 FCB 64 ; xxC COOL, Min for CLS LP Enable
Hex is 40h, TP shows in calculated view as 64d. Is it as simple as the decimal value shown for hex is Celcius?
Then I'll try and find a 1k pup one to test...
Bookmarks