PDA

View Full Version : DTC HOLDEN VS



vsboost
October 13th, 2005, 12:11 PM
HI all, just ran into something interesting during the week, i logged a DTC on my 1996 VS calais S/C, however efilive does not display what fault code it is using the vsv6.xml, but it does show that its trigged a DTC, the DTC tab goes red, and status flag shows 1 for "malf". If i load the VTV6, or VYV6.XML, and load my saved log then click the DTC's it shows a CODE 21 TPS HIGH. I didnt extract the code using the pin 5 6 on the connector as i cleared the code from efilive (should of done it) im trying to get the car to do the same fault.

Short desciption of fault,

1) Crusing at approx 60kph, revs suddenly drop to about 300 and CEL comes on then fixed itself up within 2 sec

2) Was idling at a set of traffic lights suddenly revs drop to about 300 (almost stall) then pick up again

So yea twice this fault, cant get it to happen again.

Blacky
October 13th, 2005, 02:39 PM
Were you logging the macro: "DATADTC" or just "DATA".

If you log just DATA then you won't see the actual DTC codes
If you log DATADTC you will see the DTC codes.

If you were logging DATADTC and the code did not show up, send the log file and I will extract the code manually and tell you what it was.

Regards
Paul

vsboost
October 13th, 2005, 05:01 PM
email sent to efilive@blacky.co.nz hope thats right, if so the log is of the second time it happend, the spikes you see in the log are when the fan comes in and out, seems to cause stress to the data at those points, at the end is when it happend and it stopped recording.

Cheers

Blacky
October 13th, 2005, 05:12 PM
email sent to efilive@blacky.co.nz hope thats right, if so the log is of the second time it happend, the spikes you see in the log are when the fan comes in and out, seems to cause stress to the data at those points, at the end is when it happend and it stopped recording.

Cheers

I've got the file - thanks. I'll let you know what I find tomorrow.
Paul

Blacky
October 14th, 2005, 03:24 PM
For the sake of other readers...

Trouble code 65 is set in that log file. It doesn't show up because it is listed as "Unused".
To make the "Unused" codes show up in cases like this, just change the Unused text to be something other than Unused, for example Unknown. That way it will show up and you will see the code. However, it doesn't tell you what the code means.

I looked up the trouble codes in the VT (next model) since newer codes are usually available in the later model definitions. However, there is no guarantee that the codes in the VT are the same as the VS (but they usually are).

65: Left Hand O2 Sensor Rich
66: Left Hand O2 Sensor Lean
67: Left Hand O2 Sensor Open

Regards
Paul