ECUs and PIDs Discovered on the Prius

The name of the data item in the section heading is what I think the THHS might display.  The names are taken from Richard's post 5299, matched by guesswork to the filenames of data captures.  Some can be verified against pictures Richard took of the THHS screen.

Explanation of Table

Battery ECU, address = 0xD5, data rate 10.4 kbit/s

The table entry is the number of data items obtained via the PID (discovered so far).  The link takes you to what we know about the data items from Richard's August 2003 captures.  A dash indicates that it has been confirmed that the ECU does not respond to a request for this PID.  An empty box indicates work to be done.  A question mark indicates a valid PID, but we don't know what it does.

 

?0

?1

?2

?3

?4

?5

?6

?7

?8

?9

?A

?B

?C

?D

?E

?F

0?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

1?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

2?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

3?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

4?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

5?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

6?

 

 

?

?

?

 

 

 

 

 

 

 

 

 

 

 

7?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

8?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

9?

 

1

 

 

 

 

 

1

?

1

1

1

1

 

 

 

A?

 

 

 

1

2

2

2

2

2

2

2

2

2

1

2

2

B?

 

 

1

 

1

1

 

1

 

1

1

 

1

 

 

 

C?

 

1

3

?

 

 

 

 

 

 

4

4

4

4

3

 

D?

3

1

 

1

 

 

 

 

 

 

 

 

 

 

 

 

E?

 

?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

F?

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Items from Richard's post 5299 for which we don't yet have PIDs (Battery ECU):

In "ecupids.txt", Richard mentions these currently not understood PIDs:

62, 63, 64, 98, C3, E1

In "allpids.txt", Richard also tabulated responses at these PIDs:

00, 20 (but not 40) 60, 80, A0, C0, E0 (supported PID maps)
01, 1C, 61, 70, 71, 73, 74, 82, 84, 85, 87, 89, 8A, 8C, 90, EC (but no B?)

Aux Bat Volt, PID = 0xB7

ECU

PID

Size

Data

Format

Ver

D5

B7

1

1

divide by 12.8 -> volts

0.31

Richard gets 0xB1 (177) in capture "bat-aux-bat-volt-13.828v"
-> 13.828V (?? to three places ??) on THHS (no picture)

Batt Inside Air, PID = 0xB2

ECU

PID

Size

Data

Format

Ver

D5

B2

1

1

subtract 40 -> °C

0.31

Richard gets 0x47 (71) in capture "bat-bat-inside-air-31_c" -> 31°C on THHS (no picture)

Batt Temp 1, 2 and 3, PID = 0xD0

Richard says "The Bat Temp 1-3 seem to be the in order at Bat Ecu / Pid D0, i.e. the first byte is temp 1, second byte is temp 2, third is temp 3".
Batt Temp 1

ECU

PID

Size

Data

Format

Ver

D5

D0

3

1

subtract 40 -> °C

0.31

Richard gets 0x4C, 0x49, 0x49 (76, 73, 73) in capture "bat-ib-bat-temp-1-36_c" -> 36°C on THHS (no picture)

Batt Temp 2

ECU

PID

Size

Data

Format

Ver

D5

D0

3

2

subtract 40 -> °C

0.31

Richard gets 0x4C, 0x49, 0x49 (76, 73, 73) in capture "bat-bat-temp-2-33_c" -> 33°C on THHS (no picture)

Batt Temp 3

ECU

PID

Size

Data

Format

Ver

D5

D0

3

3

subtract 40 -> °C

0.31

Richard gets 0x4C, 0x49, 0x49 (76, 73, 73) in capture "bat-bat-temp-3-33_c" -> 33°C on THHS (no picture)

Batt Temp 4, PID = 0xD1

ECU

PID

Size

Data

Format

Ver

D5

D1

1

1

subtract 40 -> °C

0.31

Richard gets 0x47 (71) in capture "bat-bat-temp-4-31_c" -> 31°C on THHS (no picture)

Battery Lo Time, PID = 0x97

ECU

PID

Size

Data

Format

Ver

D5

97

2

????

???? -> ????

0.31

Richard gets 0x00, 0x00 in capture "bat-batter-lo-times-0" -> 0 on THHS (no picture)

Richard says "The battery lo times seems to be a simple counter (how many times was the battery soc too low; probably < 40% soc). educated guess."  See also Battery Too High#.

However, the name of the item given in Richard's post #5299, "Battery Lo Time", suggests that it might be a timer rather than a counter.  Also, the name "Battery Too Hi#" suggests a battery (block?) number.  Pictures of the THHS are not available for these items.

Battery Too Hi#, PID = 0xB4

ECU

PID

Size

Data

Format

Ver

D5

B4

2

????

???? -> ????

0.31

Richard gets 0x00, 0x00 in capture "bat-battery-too-hi-times" -> 0 on THHS (no picture)

Richard says "Same for battery too high times (>80% ?)" (refer to Battery Lo Times).

CCtl, EQC0 DF Relay, and EQTR Charge St PID = 0xC2

CCtl

ECU

PID

Size

Data

Format

Ver

D5

C2

1

1

???? -> ????

-

Richard gets 0x08 in capture "bat-cctl-on" -> "on" on THHS (no picture)

Richard says "CCTL On seems to be the bit 3 in Bat Ecu / Pid C2 - but this one is probably bit-mapped."

TO DO - Try to figure out what it means.  Cruise control?  Climate Control?

EQC0 DF Relay

ECU

PID

Size

Data

Format

Ver

D5

C2

1

?

?? bitmapped ?? -> ????

-

Richard gets 0x08 in capture "bat-eqc0-df-relay-off" -> "off" on THHS (no picture)

Richard says "the next two items are again bit-mapped in the Pid C2, but unless the Bat Ecu sees a need to equalize the chare, we will not find out, which bit is what".
EQTR Charge St

ECU

PID

Size

Data

Format

Ver

D5

C2

1

?

?? bitmapped ?? -> ????

-

Richard gets 0x08 in capture "bat-eqtr-charge-stat-off" -> "off" on THHS (no picture)

Richard says (see above).

cooling-fan-hi-cmd-on, PID = 0x??

ECU

PID

Size

Data

Format

Ver

D5

???? -> ????

-

Richard's capture "bat-cooling-fan-hi-cmd-on" contains many PIDs

Richard says "Cooling Fan Hi Cmd was a trace of the Command, sent from the THHS to the Car, to make the battery fan run in High Mode! When you do this with Thhs, it initially shows you again all the parameters screen, with one line at the bottom indicating if the fan was set to on or off - so the normal Mode 1 data can be ignored in that trace."

In among the mode 1 requests and responses, there are messages like this:
    0x84 0xD5 0xF1 0x30 0x81 0x08 0x08 0x0B
    0x82 0xF1 0xD5 0x70
0x81 0x39
It looks as if the THHS is sending two octets of data to PID 0x81 of the battery ECU.  Towards the beginning of the file, the second data octet is often 0x00.

Richard's post #5299 lists COOLING FAN LO, COOLING FAN MID and COOLING FAN HI.  Presumably, these are yet to be discovered.

DC Inhibit Time, PID = 0x99

ECU

PID

Size

Data

Format

Ver

D5

99

2

???? -> ????

-

Richard gets 0x00, 0x00 in capture "bat-dc-inhibit-times-0" -> 0 on THHS (no picture)

Richard says "DC inhibit times again is a counter. From what I've learned, if the Soc is too low, and the current drain from the battery too high, the DC / DC converter can be signalled to shut down to save a few amps".

Again, the name of the item given in Richard's post #5299, "DC Inhibit Time", suggests that it might be a timer rather than a counter.  Would it really be 16 bits if it were a counter?  Could someone run up a steep hill and figure this out?

Delta SoC, PID = 0xBC

ECU

PID

Size

Data

Format

Ver

D5

BC

1

1

divide by 2 -> percent

0.31

Richard gets 0x28 (40) in capture "bat-delta-soc-20" -> 20 on THHS (no picture)

TO DO - figure out what it means.  I always seem to get 40, just like Richard.

DTC, PID = 0x9C

ECU

PID

Size

Data

Format

Ver

D5

9C

2

???? -> ????

-

Richard gets 0x00, 0x34 in capture "bat-dtc-cnt-0" -> 0 on THHS (no picture)

Richard says "DTC Cnt is also just a counter of how many DTC are stored in the Bat Ecu, and can be retrieved by a Mode 3 request".

Ok, the count might be the first octet?  So, what's the second octet?

ECU Code, PID = 0xD3

ECU

PID

Size

Data

Format

Ver

D5

D3

6

1-6

read directly as ASCII characters

-

Richard gets 0x34, 0x37, 0x30, 0x33, 0x30, 0x41 in capture "bat-ecu-code-47030A" -> 47030A on THHS (no picture)

Et Off Chr Hr, PID = 0x9A

ECU

PID

Size

Data

Format

Ver

D5

9A

1

1

???? -> ????

-

Richard gets 0x00 in capture "bat-et-off-chr-hr-0.00hr" -> 0.00hr on THHS (no picture)

Richard says "Et Off Chr Hr is most likely directly coded the hours, a off-board charger is charging the battery".

IB Main Battery, PID = 0xA3

ECU

PID

Size

Data

Format

Ver

D5

A3

2

1,2

subtract 12800 and divide by 100 -> amps

0.10

Richard gets 0x32, 0x9F to 0x32, 0xA3 in capture "bat-ib-main-bat-1.54" -> 1.54 on THHS (no picture)

Ig Off Hour, PID = 0x9B

ECU

PID

Size

Data

Format

Ver

D5

9B

2

???? -> ????

-

Richard gets 0x00, 0x07 in capture "bat-ig-off-7hr" -> 7hr on THHS (no picture)

Richard says "Ig Off is the number of hours, the car was parked".

Need to park for a couple of weeks to find out if this is 8 bits or 16 bits.  Where is Ig On Hour?

off-av-cg-relay-cmd, PID = 0x??

ECU

PID

Size

Data

Format

Ver

D5

???? -> ????

-

Richard's capture "bat-off-av-cg-relay-cmd" contains many PIDs (no picture).

Perhaps it was a command from the THHS to the car.  The capture contains this:
    0x84 0xD5 0xF1 0x30 0x83 0x01 0x01 0xFF
    0x82 0xF1 0xD5 0x70
0x83 0x3B
The second octet is zero at the beginning of the file.

Sblw Fan St Rqs, PID = 0xC1

ECU

PID

Size

Data

Format

Ver

D5

C1

1

1

???? -> ????

-

Richard gets 0x00 in capture "bat-sblw-fan-stat-rqs-off" -> "off" on THHS (no picture)

Vmf Fan Voltage, PID = 0xB5

ECU

PID

Size

Data

Format

Ver

D5

B5

1

1

???? -> ????

-

Richard gets 0x00 and 0x82 to 0xB2 (130 to 178) in capture "bat-vmf-fan-voltage-10v-13v-0v-3-digits" -> "10v-13v-0v-3-digits" on THHS (no picture).

Richard says "Vmf-fan-voltage was shown on the thhs with 2 or 3 digits; the scaling again seems to be a divide by 12,8".

WIn, PID = 0xB9

ECU

PID

Size

Data

Format

Ver

D5

B9

1

1

???? -> ????

-

Richard gets 0x32 (50) in capture "bat-wIn--20.0kW" -> -20.0kW on THHS (no picture)

WOut, PID = 0xBA

ECU

PID

Size

Data

Format

Ver

D5

BA

1

1

???? -> ????

-

Richard gets 0x69 (105) in capture "bat-wOut-21.0kW" -> 21.0kW on THHS (no picture)

Engine ECU, address = 0x10, data rate 10.4 kbit/s

ac-clutch-sig, PID = 0xEF

ECU

PID

Size

Data

Format

Ver

10

EF

3

 

???? -> ????

-

Richard gets various in capture -> ???? on THHS

cyl1, 2, 3 and 4 PID = 0xE9

cyl1

ECU

PID

Size

Data

Format

Ver

10

E9

4

???? -> ????

-

Richard gets 0x00, 0x00, 0x00, 0x00 in capture -> ???? on THHS

Richard says "What Cyl 1-4 really code for I don't know, but the data again is most likely Data 1 - Cyl 1, ... Data 4 - Cyl 4".
cyl2-4, PID = 0xE9 (should this be three separate items?)

ECU

PID

Size

Data

Format

Ver

10

E9

4

???? -> ????

-

Richard gets 0x00, 0x00, 0x00, 0x00 in capture -> ???? on THHS

etcs-mag-clutch, PID = 0xB3

ECU

PID

Size

Data

Format

Ver

10

B3

6

???? -> ????

-

Richard gets 0x05, 0x00, 0x1F, 0x00, 0x0?, 0x00 in capture -> ???? on THHS

evap-vsv, PID = 0xEF

ECU

PID

Size

Data

Format

Ver

10

EF

3

???? -> ????

-

Richard gets (various) in capture -> ???? on THHS

fuel-pump, PID = 0xEF

ECU

PID

Size

Data

Format

Ver

10

EF

3

???? -> ????

-

Richard gets (various) in capture -> ???? on THHS

Richard says "For the Bit-Mapped Pid EF see my text file; during the trace I engaged the engine, so the fuel pump cycled from off to on; on is a "1" bit, off "0".

ign-advance, PID = 0x0E

ECU

PID

Size

Data

Format

Ver

10

0E

1

1

subtract 128, then divide by 2 -> degrees

0.10

Richard gets 0x96 to 0x98 in capture -> (not recorded) on THHS

ignition-cnt, PID = 0xEB

ECU

PID

Size

Data

Format

Ver

10

EB

2

???? -> ????

-

Richard gets (various) in capture -> (not recorded) on THHS

Richard says "Ignition Cnt again a simple counter".

injector, PID = 0xE4

ECU

PID

Size

Data

Format

Ver

10

E4

1

1

divide by 8 -> ms

0.31

Richard gets 0x0C and 0x21 to 0x25 (12 and 33 to 37) in capture -> 1.5_4.2-4.6ms on THHS

mil-on-run-dist, PID = 0x21

ECU

PID

Size

Data

Format

Ver

10

21

2

???? -> ????

-

Richard gets 0x00, 0x00 in capture -> (not recorded) on THHS

Richard says "Mil-On-Run-Dist is a default parameter - counting the miles since the MIL lampe turned on".

misfire-load-g_rev, PID = 0xE2

ECU

PID

Size

Data

Format

Ver

10

E2

2

???? -> ????

-

Richard gets 0x00, 0x00 in capture -> (not recorded) on THHS

Richard says "Since I never expirienced any misfires, the misfire pid will be hard to decode for me".

misfire-rpm, PID = 0xE2

ECU

PID

Size

Data

Format

Ver

10

E2

2

???? -> ????

-

Richard gets 0x00, 0x00 in capture -> (not recorded) on THHS

o2_rl_b1_s2, PID = 0xF2

ECU

PID

Size

Data

Format

Ver

10

F2

4

???? -> ????

-

Richard gets 0x00, 0x00, 0x00, 0x00 in capture -> (not recorded) on THHS

Richard says "The O2 RL B1 S2 probably coded like the "normal" O2 sensor data, but i don't know"

throttle-close-duty, PID = 0xB2

ECU

PID

Size

Data

Format

Ver

10

B2

6

???? -> ????

-

Richard gets various, for example 0x00 0x00 0x8? 0x2? 0x?? 0x00, in capture -> 0% on THHS

throttle-motor-on, PID = 0xB3

ECU

PID

Size

Data

Format

Ver

10

B3

6

???? -> ????

-

Richard gets 0x05 0x00 0x1F 0x00 0x0? 0x00  in capture -> (not recorded) on THHS

throttle-open-duty, PID = 0xB2

ECU

PID

Size

Data

Format

Ver

10

B2

6

? 5 ?

???? -> ????

-

Richard gets various, for example 0x00 0x00 0x8? 0x2? 0x08 0x00, in capture -> 8-14% on THHS

Throttle Pos, PID = 0x11

ECU

PID

Size

Data

Format

Ver

10

11

1

1

divide by 2.56 -> %

0.10

Richard gets 0x28 to 0x30 (40 to 48) in capture -> 18-to-14% on THHS

throttle-pos2, PID = 0xB2

ECU

PID

Size

Data

Format

Ver

10

B2

6

???? -> ????

-

Richard gets (various) in capture -> 2.90_2.76_2.70-2.92v on THHS

throttle-target, PID = 0xB2

ECU

PID

Size

Data

Format

Ver

10

B2

6

???? -> ????

-

Richard gets (various) in capture -> 0.76-0.82v on THHS

vvt-ctrl-b1, PID = 0xEF

ECU

PID

Size

Data

Format

Ver

10

EF

3

???? -> ????

-

Richard gets (various) in capture -> (not recorded) on THHS

Hybrid Vehicle ECU, address = 0x16, data rate 10.4 kbit/s

Acc Sensor Main, PID = 0xD5

ECU

PID

Size

Data

Format

Ver

16

D5

2

1

subtract 1, then multiply by 50 -> volts

0.10

Richard gets 0x24 in capture -> 0.70 volts on THHS

Acc Sensor Sub, PID = 0xD5

ECU

PID

Size

Data

Format

Ver

16

D5

2

2

subtract 1, then multiply by 50 -> volts

0.10

Richard gets 0x4A/0x4B in capture -> 1.47 volts on THHS

Aux Bat, PID = 0xD8

ECU

PID

Size

Data

Format

Ver

16

D8

1

1

???? -> volts

Richard gets 0xAE (174) in capture -> 13.64 volts on THHS (no picture)

Richard says "Aux Bat was reading there slightly different than from the Bat ecu... but I have no idea on the true scaling".

† Mini-Scanner gets this data from the Battery ECU, PID 0xB7.

Cell Temp Max, PID = 0xD6

ECU

PID

Size

Data

Format

Ver

16

D6

2

1

read directly as °C

-

Richard gets 0x26 (38) in capture -> 38 on THHS (no picture)

Cell Temp Min, PID = 0xD6

ECU

PID

Size

Data

Format

Ver

16

D6

2

2

read directly as °C

-

Richard gets 0x22 (34) in capture -> 34 on THHS (no picture)

Coolant Temp, PID = 0x05

ECU

PID

Size

Data

Format

Ver

16

05

1

1

subtract 40 -> °C

Richard gets 0x7E (126) in capture -> 86°C on THHS (IMG_0853.JPG)

† Mini-Scanner gets this data from the Engine ECU, PID 0x05.

Dchg Rqsr SoC, PID = 0xCB

ECU

PID

Size

Data

Format

Ver

16

CB

2

1,2

???? -> ????

-

Richard gets 0x00, 0x00 in capture "hv-dchg-rqst-soc-0W" -> 0W on THHS (IMG_0862.JPG)

Richard says "Dchg Rqst Soc will probably only be seen when the Charge level is really high (>80%) I would believe! Just sitting on a parking lot will most likely not change that parameter.".

Drive Condition, PID = 0xCC

ECU

PID

Size

Data

Format

Ver

16

CC

1

1

???? -> ????

-

Richard gets 0x00 in capture -> 0 on THHS (IMG_0862.JPG)

Richard says "Drive Condition: I also saw number "5" with the thhs (when I didn't capture data, unfortunately). I believe this parameter is again simply decimal coded, and changes with P, R, N, D, B _and_ the external conditions, like climbing a hill with high-output power from the ICE, coasting down a hill (no power from ice), speed...".

ECU Type HV, PID = 0xFE

ECU

PID

Size

Data

Format

Ver

16

FE

1

1

???? -> ????

-

Richard gets 0x01 in capture -> unknown on THHS (no picture)

Engine Spd, PID = 0xC7

ECU

PID

Size

Data

Format

Ver

16

C7

2

1,2

read directly as r.p.m.

Richard gets values around 0x05, 0xA0 in capture -> 1440 on THHS (no picture)

† Mini-Scanner gets this data from the Engine ECU.

Intake Air, PID = 0x0F

ECU

PID

Size

Data

Format

Ver

16

0F

1

1

subtract 40 -> °C

Richard gets 0x6A in capture -> 66 on THHS (but IMG_0847.JPG shows 62°C)

† Mini-Scanner gets this data from the Engine ECU.

Inverter Temp MG1 and MG2, PID = 0xCD

Inverter Temp MG1

ECU

PID

Size

Data

Format

Ver

16

CD

2

1

subtract 50 -> °C

0.31

Richard gets 0x6D-0x6E (109-110) in capture -> 59-60 on THHS (but IMG_0862.JPG shows 58°C)

Richard says "The inverter temperatures were taken individually, and with the all-params (where the images were taken). During the individual traces I caused the temperature to climb significantly; the scaling (-50 -> °C) is correct.".
Inverter Temp MG2

ECU

PID

Size

Data

Format

Ver

16

CD

2

2

subtract 50 -> °C

0.31

Richard gets 0x68-0x81 (104-129) in capture -> 59-79 on THHS (but IMG_0862.JPG shows 55°C)

Mcyl Ctrl Prw, PID = 0xC8

ECU

PID

Size

Data

Format

Ver

16

C8

2

1,2

multiply by 4 -> N.m

-

Richard gets 0x00,0x00 to 0xFF,0x84 in capture -> -496 N.m on THHS (no picture)

MG1 Curr V, PID = 0xD0

ECU

PID

Size

Data

Format

Ver

16

D0

4

???? -> ????

-

Richard gets ??? in capture -> ???? on THHS

Richard says "As to the [MG] currents, I think the scaling is 1,46 A / digit".

I have not been able to get steady readings from these items and suspect that they are the instantaneous currents and not rectified and smoothed values.  TO DO - check when MG2 is stalled (stationary car).

MG1 Curr W, PID = 0xD0

ECU

PID

Size

Data

Format

Ver

16

D0

4

???? -> ????

-

Richard gets ??? in capture -> ???? on THHS

MG1 Rev, PID = 0xC4

ECU

PID

Size

Data

Format

Ver

16

C4

4

1,2

read directly as r.p.m.

0.10

Richard gets 0x10,0x52 - 0x11,0x43 (4178-4419) in capture -> ~4300 on THHS (no picture)

MG1 Trq, PID = 0xC4

ECU

PID

Size

Data

Format

Ver

16

C4

4

3,4

divide by 10 -> N.m

0.10

Richard gets 0xFF,0xDB - 0xFF,0xEB (-37  to -21) in capture -> ~-4.00 N.m on THHS (no picture)

MG2 Curr V, PID = 0xCF

ECU

PID

Size

Data

Format

Ver

16

CF

4

???? -> ????

-

Richard gets ??? in capture -> ???? on THHS

MG2 Curr W, PID = 0xCF

ECU

PID

Size

Data

Format

Ver

16

CF

4

???? -> ????

-

Richard gets ??? in capture -> ???? on THHS

MG2 Rev, PID = 0xC2

ECU

PID

Size

Data

Format

Ver

16

C2

4

1,2

read directly as r.p.m.

0.10

Richard gets 0xFF,0xFE - 0x00,0x02 (-1 to +2) in capture -> ±2 r.p.m. on THHS (no picture)

MG2 Trq, PID = 0xC2

ECU

PID

Size

Data

Format

Ver

16

C2

4

3,4

divide by 10 -> N.m

0.10

Richard gets 0xFF,0x98 - 0xFF,0xCC (-104  to -52) in capture -> ~-10.00 N.m on THHS (no picture)

Power Rqst, PID = 0xC5

ECU

PID

Size

Data

Format

Ver

16

C5

2

1,2

multiply by 10 -> watts

0.31

Richard gets 0x01, 0x0C (268) in capture -> 2680W on THHS (no picture ???)

Pwr Resource IB, PID = 0xD2

ECU

PID

Size

Data

Format

Ver

16

D2

2

???? -> ????

-

Richard gets 0x00,0x00 to 0x00,0x03 in capture -> 0 to 6A on THHS

Richard says "Pwr Resource seems to be another Current Sensor, this time from the Inverter
at the Bat connector side, with a resolution of only 2 A / digit".

So, why 16 bits?  Is first octet used for something else?

Power Resource VM, PID = 0xD1

ECU

PID

Size

Data

Format

Ver

16

D1

1

1

multiply by 2 -> volts

-

Richard gets 0x98 to 0x9B in capture -> 304 to 306V on THHS

Regen Exec Trq, PID = 0xC3

ECU

PID

Size

Data

Format

Ver

16

C3

2

1

read directly as N.m

0.20

Richard gets 0x00 in capture -> 0.00 N.m on THHS

Regen Rqst Trq, PID = 0xC3

ECU

PID

Size

Data

Format

Ver

16

C3

2

2

multiply by 4 -> N.m

0.20

Richard gets 0x00 in capture -> 0.00 N.m on THHS

Shift Sensor 1, PID = 0xD4

ECU

PID

Size

Data

Format

Ver

16

D4

1

1

???? -> ????

0.10

Richard gets 0x01 in capture -> prndbu? on THHS

Richard says "I didn't look at the shift sensor 1 data, but i cycled through the PRNDB modes and also saw the corresponding mode on the thhs; with a U(unknown) during the shift.".

This item has been supported and documented since Mini-Scanner firmware version 0.10.

Shift Sensor 2, PID = 0xD3

ECU

PID

Size

Data

Format

Ver

16

D3

2

1,2

divide by 50 -> volts

0.10

Richard did not capture, but this item has been supported since Mini-Scanner firmware version 0.10.  Of course, I don't know that the offset and scaling are correct, especially since the accelerator pedal sensors apparently have an offset of 1, so you need to subtract one before dividing by 50.

SoC, PID = 0xC9

ECU

PID

Size

Data

Format

Ver

16

C9

1

1

???? -> ????

Richard gets 0x90 to 0x8F in capture "hv-soc-56.05" -> 56.05 on THHS.

Richard says "For the HV ECU Soc (C9) try dividing by 2,55 (i.e. 0... 0%, FF... 100%)."

† Mini-Scanner gets this data from the Battery ECU and divides by 2.

Tachometer, PID = 0x

ECU

PID

Size

Data

Format

Ver

16

???? -> ????

-

Richard did not capture.

Target Engine Spd, PID = 0xC6

ECU

PID

Size

Data

Format

Ver

16

C6

2

1,2

read directly as r.p.m.

-

Richard gets up to 0x07, 0x4B in capture -> ~1700 r.p.m. on THHS

Temp MG1, PID = 0xCE

ECU

PID

Size

Data

Format

Ver

16

CE

2

1

subtract 50 -> °C

0.31

Richard gets 0x6C (108) in capture -> 58 on THHS (but IMG_0862.JPG shows 60°C)

Temp MG2, PID = 0xCE

ECU

PID

Size

Data

Format

Ver

16

CE

2

2

subtract 50 -> °C

0.31

Richard gets 0x6C-0x6D (108-109) in capture -> 58-59 on THHS (but IMG_0862.JPG shows 57°C)

Vehicle Speed, PID = 0xD7

ECU

PID

Size

Data

Format

Ver

16

D7

1

1

read directly as m.p.h. (!?!?!)

Richard gets 0xFF to 0x00 in capture -> -1 to 0 m.p.h. on THHS (IMG_0847.JPG)

Richard says "I believe Vehicle speed is given in SI units (km/h) instead of mph!.".

† Mini-Scanner gets this data in km/hr using PID 0x0D.

WIn Ctrl Pwr, PID = 0xCA

ECU

PID

Size

Data

Format

Ver

16

CA

2

????

???? -> ????

-

Richard gets 0x83 in capture -> 20000W on THHS (no picture)

WOut Ctrl Pwr, PID = 0xCA

ECU

PID

Size

Data

Format

Ver

16

CA

2

????

???? -> ????

-

Richard gets 0x83 in capture -> 20960W on THHS (no picture)

XTest Sw Sig, PID = 0xEC

ECU

PID

Size

Data

Format

Ver

16

EC

1

1

???? -> ????

-

Richard gets 0x00 in capture -> "normal" on THHS (no picture)


Last edited August 4, 2003.  All material Copyright © 2003 Graham Davies.  No liability accepted.