How to Make Your Check Engine Light Flash Code

Introduction: Why Your Check Engine Light Is Flashing (And What It Means)

You’re driving down the road, and suddenly—your check engine light starts blinking. Your heart skips a beat. Is it serious? Should you pull over? Or is it just a minor glitch?

Before you panic, know this: a flashing check engine light can actually be a helpful tool. On many older vehicles, especially those made before 1996, the onboard computer can communicate trouble codes by making the check engine light flash in specific patterns. This is called a “flash code” or “blink code” method.

In this guide, you’ll learn exactly how to make your check engine light flash code so you can read diagnostic trouble codes (DTCs) without spending money on an OBD scanner. Whether you’re a DIY car enthusiast, a budget-conscious driver, or just curious about how your car talks to you, this method puts powerful diagnostic info right at your fingertips.

We’ll walk you through everything: which cars support this feature, where to find the diagnostic port, how to trigger the flash sequence, and how to interpret the codes. By the end, you’ll be able to diagnose common engine issues like a pro—no fancy tools required.

What Is a Check Engine Light Flash Code?

Visual guide about How to Make Your Check Engine Light Flash Code

Image source: dodgecheckenginelight.com

Before we dive into the steps, let’s clarify what we mean by a “flash code.”

A flash code is a way your car’s onboard computer (ECU or engine control unit) communicates a problem. Instead of sending data to a scanner, it uses the check engine light to blink in a pattern that corresponds to a specific trouble code.

For example:
– One long flash, then two short flashes = Code 12
– Three long flashes, then four short flashes = Code 34

These codes follow a standard format: long flashes represent the tens digit, short flashes represent the ones digit. A pause separates each code, and the sequence usually repeats.

This system was common in OBD-I (On-Board Diagnostics Generation I) vehicles, which were used from the 1980s up to 1995. Some early OBD-II vehicles (1996 and newer) may also support this method, but most require an OBD-II scanner.

Important: Not all cars can display flash codes. This method works best on older domestic vehicles like GM, Ford, and Chrysler models from the 1980s and early 1990s. Japanese and European cars often use different systems.

Which Vehicles Support Flash Code Reading?

Not every car can flash its check engine light to show trouble codes. This method is mostly limited to older vehicles with OBD-I systems.

Here’s a quick breakdown:

GM Vehicles (Chevrolet, GMC, Buick, Cadillac)

Most GM cars and trucks from 1982 to 1995 support flash codes. You’ll need to access the ALDL (Assembly Line Diagnostic Link) connector, usually under the dashboard on the driver’s side.

Ford Vehicles

Ford used a similar system called the Self-Test Automatic Readout (STAR). You can trigger flash codes on many Ford models from the 1980s and early 1990s by bridging specific pins in the diagnostic connector.

Chrysler Vehicles

Chrysler vehicles from the 1980s and early 1990s also support flash codes. The diagnostic port is typically under the hood or near the fuse box.

Japanese and European Cars

Most Hondas, Toyotas, Nissans, BMWs, and Mercedes-Benz models from this era do not support flash codes via the check engine light. They often require a proprietary scanner or a different method.

Tip: If your car was made after 1996 and has an OBD-II port (a 16-pin connector under the dash), it likely requires a scanner. However, some early OBD-II vehicles (1996–1998) may still allow flash code reading on certain models—check your owner’s manual or online forums for confirmation.

Tools You’ll Need

The beauty of this method is that it requires very little equipment. Here’s what you’ll need:

• A paperclip or small jumper wire: This will bridge the diagnostic pins. A standard paperclip works fine—just straighten it out.
• Safety glasses: Always protect your eyes when working near the dashboard or under the hood.
• A flashlight: The diagnostic port is often in a dark area under the dash.
• Your vehicle’s service manual (optional but helpful): This can confirm pin locations and code meanings.

You don’t need a scanner, laptop, or special tools. Just a few household items and about 10 minutes of your time.

Step-by-Step Guide: How to Make Your Check Engine Light Flash Code

Now let’s get into the actual process. Follow these steps carefully to trigger and read the flash codes.

Step 1: Locate the Diagnostic Port

The first step is finding the right connector. This is usually called the ALDL (GM), DLC (Ford), or OBD-I port.

– GM vehicles: Look under the dashboard on the driver’s side. The ALDL connector is a 12-pin rectangular plug, often black or gray.
– Ford vehicles: The STAR connector is usually under the dashboard or near the fuse box. It has multiple pins and may be labeled.
– Chrysler vehicles: The diagnostic port is often under the hood, near the firewall or battery.

Use your flashlight to spot it. It may be tucked behind panels or covered with a cap.

Step 2: Identify the Correct Pins to Jump

Each manufacturer uses different pins to trigger the flash code sequence. Here’s how to find them:

GM Vehicles

In the ALDL connector, you need to bridge pins A and B. These are usually the two pins on the bottom row, farthest to the left and right.

– Pin A: Ground
– Pin B: Diagnostic enable

Use your paperclip to connect these two pins. Make sure the metal ends touch the pins securely.

Ford Vehicles

For Ford, you’ll typically bridge pins 2 and 6 in the STAR connector. These are often labeled or can be found in a service manual.

– Pin 2: Signal return (ground)
– Pin 6: Self-test input

Again, use a paperclip or jumper wire to connect them.

Chrysler Vehicles

Chrysler systems vary, but many use a single pin to ground. Look for a pin labeled “CCD” or “Diagnostic.” You may need to ground it to the chassis.

Tip: If you’re unsure, search online for “[your car make/model/year] ALDL pinout” to find a diagram.

Step 3: Prepare the Vehicle

Before triggering the codes, make sure the car is ready:

– Turn the ignition to the “ON” position (but don’t start the engine).
– Make sure all accessories (lights, radio, A/C) are off.
– Ensure the battery is fully charged—low voltage can affect the ECU.

Step 4: Trigger the Flash Code Sequence

Now it’s time to make the check engine light flash.

1. Insert the paperclip or jumper wire into the correct pins.
2. Turn the ignition to “ON.”
3. Wait 2–5 seconds.
4. The check engine light should begin flashing.

If nothing happens, double-check your pin connections. Make sure the wire is making solid contact.

Note: On some vehicles, you may need to cycle the ignition (OFF → ON → OFF → ON) while the pins are bridged.

Step 5: Read the Flash Patterns

Once the light starts flashing, count the flashes carefully.

– Long flashes = tens digit (each lasts about 1 second)
– Short flashes = ones digit (each lasts about 0.5 seconds)
– A pause separates each code
– The sequence usually repeats after a few seconds

For example:
– One long flash, then two short flashes = Code 12
– Four long flashes, then five short flashes = Code 45

Write down each code as it appears. Some vehicles display multiple codes in sequence.

Step 6: Interpret the Codes

Now that you have the codes, it’s time to figure out what they mean.

Here are some common OBD-I flash codes:

• Code 12: No RPM signal from the distributor. Could indicate a faulty sensor or wiring issue.
• Code 13: Oxygen sensor circuit malfunction. Check the O2 sensor and connections.
• Code 14: Coolant temperature sensor high voltage. Engine may be overheating or sensor is faulty.
• Code 15: Coolant temperature sensor low voltage. Sensor may be shorted.
• Code 21: Throttle position sensor (TPS) high voltage. Throttle may be stuck or sensor is bad.
• Code 22: TPS low voltage. Sensor may be out of range.
• Code 32: EGR system malfunction. Could be a clogged valve or vacuum leak.
• Code 34: MAP sensor high voltage. Manifold pressure sensor may be faulty.
• Code 42: Electronic spark timing (EST) circuit issue. Check ignition module.
• Code 43: Knock sensor circuit problem. Sensor may be loose or damaged.
• Code 44: Lean exhaust condition. Could be a vacuum leak or fuel delivery issue.
• Code 45: Rich exhaust condition. May indicate a bad fuel injector or sensor.
• Code 51: PROM error. The ECU’s memory chip may be corrupted.
• Code 52: Engine oil temperature sensor fault.
• Code 53: System voltage too high. Alternator may be overcharging.
• Code 54: Fuel pump circuit low voltage. Check fuel pump relay and wiring.
• Code 55: End of codes. The system has finished displaying all stored faults.

Tip: Always refer to your vehicle’s service manual for the most accurate code definitions. Some codes vary by model and year.

Step 7: Clear the Codes (Optional)

After diagnosing the issue, you may want to clear the codes to see if the problem returns.

On most OBD-I systems, you can clear codes by:

– Disconnecting the battery for 10–15 minutes
– Or turning the ignition off and removing the paperclip/jumper wire

Note: Clearing codes won’t fix the underlying problem—it just resets the system. If the issue persists, the light will come back on.

Practical Tips for Success

To get the best results when reading flash codes, keep these tips in mind:

• Work in a well-lit area: It’s easier to see the diagnostic port and count flashes in good lighting.
• Have a helper: Ask someone to watch the check engine light while you handle the jumper wire. This makes counting easier.
• Use a notepad: Write down each code as it appears. Some sequences repeat, so you don’t want to miss one.
• Don’t rush: Take your time with each step. A mistake in pin connection can lead to incorrect readings.
• Check for multiple codes: Some vehicles store several trouble codes. Wait for the full sequence to complete.
• Verify with a scanner (if available): If you have access to an OBD-I scanner later, use it to confirm your findings.

Troubleshooting Common Issues

Even with careful steps, you might run into problems. Here’s how to fix the most common ones.

The Check Engine Light Doesn’t Flash

– Cause: Wrong pins, poor connection, or incompatible vehicle.
– Solution: Double-check the pinout diagram. Make sure the paperclip is making solid contact. Confirm your car supports flash codes.

Only One Code Appears (e.g., Code 12)

– Cause: Code 12 often means “no RPM signal,” which can happen if the engine isn’t running or the sensor is faulty.
– Solution: Try cranking the engine while the pins are bridged. If the light still doesn’t flash, the distributor or sensor may need inspection.

Codes Keep Repeating or Won’t Clear

– Cause: The underlying problem hasn’t been fixed.
– Solution: Address the root cause (e.g., replace a faulty sensor, fix a vacuum leak). Then clear the codes and test drive.

Battery Drains Quickly

– Cause: Leaving the ignition on with the pins bridged can drain the battery.
– Solution: Only keep the ignition on long enough to read the codes—usually 30–60 seconds.

When to See a Mechanic

While flash codes are helpful, they have limits. Here’s when you should seek professional help:

• Codes point to complex systems: Transmission, ABS, or emissions issues often require specialized tools.
• You’re unsure of the repair: If you don’t know how to fix a faulty sensor or wiring issue, don’t guess—get expert advice.
• The problem persists after repair: If you’ve fixed the issue but the light returns, there may be a deeper problem.
• Your vehicle is OBD-II (1996+): Most modern cars require a scanner for accurate diagnostics.

Remember: Flash codes are a starting point, not a complete diagnosis.

Conclusion: Empower Yourself with DIY Diagnostics

Learning how to make your check engine light flash code is a valuable skill that saves time, money, and stress. Instead of guessing what’s wrong with your car, you can get real data straight from the source.

This method puts the power of diagnostics in your hands—no expensive tools, no waiting at the mechanic. Whether you’re troubleshooting a rough idle, a failed emissions test, or just curious about your car’s health, flash codes give you a clear starting point.

Just remember: this technique works best on older vehicles. If you drive a newer car, invest in an OBD-II scanner for more accurate readings.

But for classic cars, project vehicles, or budget-friendly repairs, the flash code method is a game-changer. So grab a paperclip, locate that diagnostic port, and start listening to what your car is trying to tell you.

You’ve got this.