Question about 1995 GMC Jimmy

1 Answer

How do I get the trouble codes from a 1995 GMc Jimmy? I has the obdII connector but my code reader wont communicate.

Posted by on


1 Answer

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points

    Top Expert:

    An expert who has finished #1 on the weekly Top 10 Fixya Experts Leaderboard.


    An expert that got 20 achievements.


    An expert that got 10 achievements.

  • GMC Master
  • 14,534 Answers

Some code readers have problems reading the 94 -95 vehicles wasnt till 96 that it was required to have the 16 pin obdll system -but check the connection and try again if it still tells u cant communicate take truck to an auto store for a scan some such as auto zone/ advanced auto do it for free and also have ur scanner checked could have a bad wire connector

Posted on Nov 14, 2009


1 Suggested Answer

  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi there,
Save hours of searching online or wasting money on unnecessary repairs by talking to a 6YA Expert who can help you resolve this issue over the phone in a minute or two.

Best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.

Here's a link to this great service

Good luck!

Posted on Jan 02, 2017


Add Your Answer

Uploading: 0%


Complete. Click "Add" to insert your video. Add



Related Questions:

1 Answer

Where is the vsc switch on a 04 4runner?

If you suddenly have the "VSC TRAC" and "VSC OFF" lights in your dash, this post may help you fix the problem yourself. The information here applies to 4th gen 4Runners that use the ISO protocol rather than the newer CAN protocol for their OBDII interfaces to code readers, ECU programmers, hand-held testers, etc. The OBDII interface includes several different protocols (methods of digital communication) and they all use the same physical connector, though with some different pins. The connector is located at the bottom of the dash on the driver's side and in the 4Runner it's covered by a small black cap.

4Runners switched from ISO to CAN around 2005 though this information may also apply to newer 4Runners with some modification. That is, newer 4Runners may display trouble codes and reset sensor calibration values in response to the connection of different (than earlier 4Runners) pins together than the ones described below.

Several posters have discussed similar problems, described in several different threads. I'm reluctantly starting a new one, with a more specific title (including the exact name of the two trouble indicator lights), in the hope that searchers will more easily find a solution.

The specific behavior: On startup, the "VSC TRAC" and "VSC OFF" lights come on and stay on. The ABS light may or may not come on. On subsequent starts the lights will come on temporarily as usual (as a bulb check) and then go off. They come on again and stay on as soon as the 4Runner is moved. The "check engine" light does not come on. This behavior begins after the vehicle has been hooked to some sort of OBDII code reader or engine tester or data logger, etc. Though the lights are on, no standard OBDII problem codes are detected by a regular code reader.

Cause: The code reader or other OBDII device has attempted to communicate with the 4Runner using the CAN protocol (involving pin #14) and this has caused the 4Runner to erase the "zero point calibration" numbers in its memory. Without these numbers it can't get accurate information from the yaw rate and deceleration sensors (in the center console near the gearshift) and so it disables traction and stability control functions.

The fix: Perform the "zero point calibration" procedure as described in TSB BR001-04. This procedure can be performed without special equipment such as a hand-held tester or OBDII reader. You only need the equivalent of a jumper wire to short together two pins of the OBDII connector at the right time and the right number of times between switching the 4Runner on and off. More detail is included below, leveraged from my other posts.

Why this doesn't happen every time a code reader is used: The code readers usually use the pins and protocol of the OBDII connector in a specific sequence, trying first to establish communication with the vehicle using the oldest protocol. They then try the pins and protocol of newer protocol standards. Usually the code reader would be successful in its first try at establishing contact with the 4Runner using the ISO 9141-2 protocol, and there would be no problem. However these communications schemes are not foolproof and occasionally the ISO protocol attempt fails. Then the code reader tries newer protocols including CAN (controller area network). It's this CAN attempt, which toggles pin #14 (the CAN data pin) that accidentally tells the 4Runner to erase the existing zero point calibration data. Since the 4Runner (this vintage anyway) can't communicate by CAN protocol the tester re-tries the older protocols again and eventually succeeds in setting up communication by the right ISO protocol. But by then the calibration data has been erased.

The calibration, by the way, is simply a matter of telling the 4Runner VSC/TRAC computer "your yaw rate and deceleration rate are currently zero" and to save the associated values. Then the output from the sensors can be interpreted correctly.

Detail (may be helpful if you're going to do the calibration procedure yourself): The SST (special service tool #09843-18040) specified in the service manual appears to be essentially a Y-shaped test lead and is variously called a "jumper wire" or "diagnostic check wire." It's used in this case to repeatedly connect and disconnect the chassis ground (CG, pin #4) and Ts (pin #14) terminals of the OBDII connector (referred to as DLC3 in Toyota-speak). The connection/disconnection sequence and timing are described in the service manual and in several TSBs. OBDII connector diagram and pin descriptions are in TSB BR005-03.

Since the OBDII connector is at the lower edge of the dash and pointing down (right above your left foot when you're sitting in the driver's seat) it's rather tough to reach in and do the shorting to the appropriate terminals of the OBDII connector with a test lead. Especially since you're supposed to avoid moving or shaking the vehicle when you're doing this. BTW, the OBDII connector usually has a black snap-on cover over it to keep out grit, etc.

Therefore I took a couple of pieces of insulated wire about 24" long each and taped them alongside each other, and stripped both ends. To make the wire fit securely in the (female) terminals of the OBDII connector I soldered a 3/8" length of metal (cut from a heavy paper clip) to one end of each of the wires. I chose a pin size so that would fit securely in the female terminals of the OBDII connector but wouldn't distort them. I used some heat shrink tubing around the solder joint to reduce any chance of accidental shorting.

After plugging the two pins into the OBDII connector (with the other ends held apart) I was able to hold the other ends of the two wires in my hands and touch them together at the appropriate times to connect the pins of the OBDII connector. I had a helper in the passenger seat to read the instructions from the TSB to me in sequence.

This is not very hard to do, and one need only be careful. It's easier to do with the Toyota OBDII tester, of course, and would only take 5 minutes. You might be able to get your dealer to do it gratis, but you might also be charged some minimum labor hour rate.

BTW #1: Doing the sulfur TSB or others that require the replacement or reprogramming of the engine computer or the VSC computer will also require this calibration.

BTW #2: I verified that when the lights are on the VSC and traction control are indeed inoperative. ABS is working, though.

BTW #3: Shorting other pins (such as #13 Tc) at the right time can cause the appropriate dash indicators to blink in sequence to reveal trouble codes other than the OBDII ones. A generic OBDII code reader won't give you this data, and you need the service manual (physical or online) to make sense of it. I believe there is a specific code to tell you that the zero point calibration data has been lost, but I didn't look for it.

BTW #4: In the 4Runner of this vintage the OBDII connector pins populated are 4, 5, 7, 9, 13, 14, 15, 16

Dec 19, 2011 | 2004 Toyota 4Runner

1 Answer

I have a 95 gmc jimmy i replaced the fuel pump and changed the wires plugs rotor and cap now it wont start

Hi, Were the parts replaced due to a no start condition? Is there a trouble code stored in the PCM or an engine light on? How many miles are on the truck?

Oct 05, 2011 | 1995 GMC Jimmy

2 Answers

Where on the 93 Dodge Dakota do I find the spot for the code reader? under hood or engine compartment?

That is an OBD1 System

Your code reader won't work

You need OBD1 capable reader or
the adapter for an older scan tool

The connector is in the engine compartment

If you need to know where, I will look in my
1992 manual as I departed with my Dakota
june last year.

If you get code I will look them up for you
or tell me the problem your having.

I think the connector is hanging near the
A/C expansion valve on pass side

Jun 27, 2011 | 1993 Dodge Dakota

1 Answer

97 Jetta GL 2.0 –connected a Code Reader (OBDII compatible) but unable to establish any communication-everything else works as normal- Is there a main fuse which protects the diagnostic link thanks for...

This is what I do, first is to connect my OBDII reader, pull ashtray out, on right side of ashtray, slide front panel out, connect OBDII reader, turn ignition to on, do not start, press read on OBDII, should be able to establish communication. If not then probably connection is bad somewhere from connector to the Digifant Control Unit (brain), there is no fuse in between.

Nov 28, 2010 | 1997 Volkswagen Jetta

1 Answer

Service engine light was on, truck kept wanting to stall then finally did then wouldnt start back up

Get an OBDII code reader and find out the code. It could be anything at this point.

Apr 15, 2010 | 1997 GMC Jimmy

2 Answers

Wont start pulled a code of p1351 wanna know what it is

what code reader did you ues? i need the make and model of the reader itself.

Dec 15, 2009 | 2000 GMC Jimmy

1 Answer

My jimmy 95 stall sometimes, when I stop strong, and when start run at 2250 rpm and then go down at 250 and sometimes stall, then reestart and run normal, but is danger than motosa stall in freeway. Thanks...

i would take it to a nearby parts store and ask to use the OBDII -code reader it plugs into the drivers side under the dash ...once connected turn the key to the on position and when is says communicating with vehicle let it continue on after a few minutes it will give you codes as well as a readout of issues that it has found ...any parts you may need will be there and you will have an option to clear all codes after the fix ..but it could be a few things going on such as a failing fuel-pump cracked plugs /wires or a wire that is grounding out on the block because the wires run close to the motor area ...hope this helps you

Oct 25, 2009 | 1995 GMC Jimmy

2 Answers

97 gmc jimmy codes

try cycling the key off and on three times ... with the final motion on.... count the times the check engine light flashes (if it does).... those are your codes.... if you can't get your codes that way and happen to live in the states... go to your local autozone.... my understanding is that they will read them for free


Jan 04, 2009 | 1997 GMC Jimmy

Not finding what you are looking for?
1995 GMC Jimmy Logo

Related Topics:

495 people viewed this question

Ask a Question

Usually answered in minutes!

Top GMC Experts


Level 3 Expert

79865 Answers

Colin Stickland
Colin Stickland

Level 3 Expert

22326 Answers

Ronny Bennett Sr.
Ronny Bennett Sr.

Level 3 Expert

6927 Answers

Are you a GMC Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides