On a 1996–2001 XJ you can read engine trouble codes two ways: plug a cheap OBD-II scanner into the port under the dash, or skip the tool entirely and flash the codes through the odometer with the key. Both get you a "P" code — a pointer to which circuit is unhappy, not a verdict on which part is bad.
When the Check Engine Light comes on, the first move is to find out what the PCM is complaining about before you spend a dime on parts. The 1996-and-up XJ runs standardized OBD-II, so any basic code reader works — and the truck will even hand you the codes with no tool at all if you know the key sequence. A code names a circuit. The sensor, its wiring, its connector, and its ground are all suspects until you test them. This guide covers where the port is, the free odometer method, how to read and clear codes, and the handful of codes XJ owners see most.
The cutoff is 1996, but it's not perfectly clean. Every XJ from 1997 on is OBD-II. Most 1996 trucks are OBD-II, but a few very early 1996 builds left the factory with the older OBD-I system on the 4.0L. If your scanner powers up but reports "no communication," or there's no 16-pin port under the dash, you may have one of those transitional trucks — read OBD-I codes with the key-dance flash method instead (see "Reading OBD-I Codes on the XJ"). The quickest tell is the port itself: a 16-pin trapezoidal connector under the dash means OBD-II.
The OBD-II data link connector is under the dash, to the left of the steering column, usually right above the pedals near the lower edge of the dash panel. It's a 16-pin trapezoidal socket. On most XJs it hangs free or clips to a bracket — you may have to duck your head under the wheel to see it. The port is powered through a fuse; if a scanner won't light up at all when plugged in, check the fuse feeding the connector before assuming the tool or the truck is dead.
Chrysler built a code-flash routine into the cluster, so you can pull P-codes with nothing but the key:
This won't give you live sensor data or let you clear codes, but for a quick "what's the light about?" in a parking lot, it costs nothing and needs no hardware.
A note on scanners and the XJ: Chrysler used the ISO 9141-2 protocol on these trucks, not the GM-style J1850. A bargain-bin reader built only for GM/Ford protocols may connect to your buddy's truck and refuse to talk to your XJ. Any scanner that lists ISO 9141 support — which covers nearly all modern universal readers and Bluetooth dongles — will work. If a tool won't link, suspect protocol support or the port fuse before the PCM.
Most scan tools have an Erase Codes function that clears the stored code and turns the light off. Clear a code only after you've actually fixed the underlying fault — erasing it doesn't repair anything, and if the problem is still there the light comes back, often within a drive cycle or two. Clearing also wipes the readiness monitors, which matters if you're heading to an emissions test: the truck needs a few drive cycles to re-run its self-tests before it'll pass. The odometer method can't clear codes; you need a tool for that.
A code is a starting point, not an answer. P0138 means the rear O2 circuit is reading high — that's almost always the sensor, but it can also be wiring or an exhaust leak near the sensor. Test before you buy.
Some parts links are Amazon affiliate links — if you buy through them Trail Manual may earn a small commission at no extra cost to you. We only list parts we’d run on our own rig, and never on safety-critical pages.
| Part | Vendor | Est. price |
|---|---|---|
| Basic plug-in OBD-II code reader (Innova 3030 / Autel AL319 class) | auto parts store / Amazon | ~$35 |
| Bluetooth OBD-II dongle with phone app (BlueDriver or ELM327 class — confirm ISO 9141 support) | Amazon | ~$60 |
Written and maintained by an AZ wheeler and driveway wrencher. Always cross-reference your factory service manual — modifications affect vehicle safety and warranty. Work at your own risk.
Trail Manual · About · Privacy · Terms · Database