Why do owners of old cars need an OBD1→OBD2 adapter?

If your car was manufactured before 1996 (and for some brands before 2001-2003), it is most likely equipped with a connector OBD1 - outdated diagnostic standard. Modern scanners, applications like Torque Pro or OBD Auto Doctor, as well as most diagnostic instruments in car service centers work only with OBD2. This is where the adapter comes in handy: it converts the old protocol signals into a format that new devices can understand.

But it's not that simple. Firstly, there is no universal OBD1→OBD2 adapter - each manufacturer used its own protocols (GM ALDL, Ford DCL, Toyota MUT, etc.). Secondly, even with an adapter, the diagnostic functionality will be limited: for example, you will not be able to read sensor parameters in real time if the car's ECU does not support such requests. In this article, we will look at how to choose an adapter for a specific brand, what errors occur when connecting, and whether it is possible to do without a soldering iron.

What's the difference between OBD1 and OBD2: why can't you just connect?

The main difference is in communication protocols and physical connector:

  • 🔌 OBD1 connector: Each brand has its own format (for example, GM I used a 12-pin rectangular connector, Toyota - round 22-pin). There is no single standard for either shape or pinout.
  • 📡 OBD1 protocol: data transmission occurs via analog signals (for example, ALDL at Chevrolet or ISO 9141 for European cars). The exchange speed is low, there are no unified commands.
  • 🔗 OBD2: standard 16-pin connector (J1962) and digital protocols (CAN, ISO 15765, KWP2000). Supports advanced diagnostics, including real-time parameter reading.

The adapter must not only physically connect the connectors, but also convert protocol. For example, for Honda 90s will require an adapter that converts the signals Honda DST in OBD2 PIDs. Without this, the scanner simply will not understand the data, even if the contacts are connected correctly.

📊 What car do you have with OBD1?
American (GM, Ford, Chrysler)
Japanese (Toyota, Honda, Nissan)
European (VW, BMW, Mercedes)
Other

Types of OBD1→OBD2 adapters: which one to choose?

All adapters are divided into three types according to the principle of operation:

Adapter type Example models Pros Cons
Passive (jack only) OBD1-to-OBD2 cable (for example, for Toyota 22-pin) Cheap (from 500 ₽), does not require power Does not convert protocols, only works with compatible ECUs
Active (with converter) STN1110, ELM327 with modified firmware Converts signals (for example, ALDL → CAN), supports most scanners Expensive (from 3,000 ₽), requires firmware configuration
Specialized (branded) VAG-KKL for VW/Audi, Honda OBD1→OBD2 Maximum compatibility with a specific ECU Only works with one brand, hard to find

Optimal for most owners active adapter based on STN1110 - it supports major OBD1 protocols (including ALDL, ISO 9141) and is compatible with popular scanners like ELM327. However, before purchasing, check to see if the description supports your brand! For example, for Ford before 1996 you need an adapter with support Ford DCL, and for Mitsubishi — MUT-I.

💡

If you buy an adapter on AliExpress, be sure to check with the seller whether it supports your ECU model. Often only popular protocols are indicated in the description, and for rare cars (for example, Subaru SVX) may require custom firmware.

Connection diagram: step-by-step instructions

Let's consider a universal algorithm for an active adapter (using the example STN1110):

  1. Find the OBD1 connector in the car. It is usually located under the driver's side dash or behind the glove compartment. B Toyota This is a round gray connector, in GM — rectangular black (ALDL).
  2. Connect the adapter to the OBD1 port. If the connector does not fit, use an adapter block (for example, GM 12-pin → OBD2).
  3. Connect the adapter to the OBD2 scanner (for example, ELM327 Bluetooth). Order: OBD1 → adapter → OBD2 scanner → phone/PC.
  4. Apply power. Some adapters require connection to a cigarette lighter or battery (check the instructions!).
  5. Run diagnostic software (for example, Torque Pro) and select the protocol manually (for example, ISO 9141-2 for European cars).

Make sure the adapter supports your ECU protocol|

Check the voltage at the OBD1 pins (should be 12V on power supply)|

Turn off the ignition before connecting |

Use only high-quality connectors (Chinese “disposable” ones can melt) -->

⚠️ Attention: If after connecting the scanner does not see the car, check:

  • 🔋 Power polarity (mixed “+” and “-” may burn the adapter).
  • 🔌 Quality of contacts (oxidation or poor soldering is a common cause of errors).
  • 📱 Scanner firmware compatibility (for example, ELM327 v1.5 does not support ALDL).

Common mistakes and how to avoid them

Even with the correct adapter, diagnostics may not work. Here are the most common problems and their solutions:

Error Reason Solution
NO DATA or UNABLE TO CONNECT Incorrect protocol in scanner settings Try manually specifying ISO 9141, KWP2000 or ALDL (depending on the car brand)
The scanner connects but shows no errors The ECU does not support standard OBD2 PIDs Use specialized software (for example, Tactrix OpenPort for Subaru)
The adapter gets hot or smokes Short circuit or power reverse Disconnect immediately! Check the connection diagram with a multimeter

⚠️ Attention: If your car is equipped immobilizer (for example, VW Immo2 or Toyota Transponder), connecting a non-original adapter may cause an error Anti-Theft System and block the engine from starting. In this case, you will need to reset the ECU through dealer software or chip tuning.

What to do if the adapter is not detected by the computer?

1. Check the drivers for the adapter (for example, for STN1110 needed FTDI).

2. Try a different USB port or cable (especially important for cheap Chinese adapters).

3. Disable your antivirus - it may be blocking access to the COM port.

4. B Device Manager Check if the adapter is detected as a virtual COM port. If not, the device is faulty.

Not all programs work with OBD1 via an adapter. Here is the compatibility table:

Scanner/Application OBD1 support Notes
Torque Pro Partial Works only with adapters ELM327 or STN1110. You need to manually select the protocol
OBD Auto Doctor Yes (with plugins) Supports ALDL and ISO 9141 via additional modules
ScanTool OBDLink Yes Best choice for GM and Ford (supports ALDL and DCL)
Launch X431 No Requires original adapters for OBD1 (for example, Launch OBD1 Cable)

For maximum functionality we recommend using specialized software for your brand. For example:

  • 🚗 For Toyota/Lexus: Techstream (requires adapter Mini VCI).
  • 🚘 For VW/Audi: VCDS (VAG-COM) with cable KKL.
  • 🚙 For GM (Chevrolet, Opel): TunerPro with plugin ALDL.
💡

If you need not only diagnostics, but also chip tuning (for example, removing the speed limit), a regular OBD1→OBD2 adapter will not work. You will need professional equipment like OpenPort 2.0 or Kess V2 with support for older ECUs.

Is it possible to make an adapter yourself?

Yes, but this will require soldering skills and knowledge of circuit design. Here's what you'll need:

  • 🔧 OBD1 connector for your brand (eg GM ALDL 12-pin).
  • 🔌 OBD2 connector (J1962) - can be taken from a faulty scanner.
  • 📶 Converter chip: STN1110, ELM327 (with flashing) or FT232RL (for USB connection).
  • 🔋 Power stabilizer (for example, LM7805 for 5V).

The connection diagram depends on the protocol. For example, for Toyota MUT need to connect:



OBD1 (22-pin) → STN1110 → OBD2 (16-pin)


Pin 4 (TE1)  → RX (STN1110)


Pin 5 (TE2)  → TX (STN1110)


Pin 16 (+12V) → VCC (via stabilizer)


Pin 8 (GND)  → GND

⚠️ Attention: Self-assembly of the adapter is fraught with risks:

  • 🔥 A short circuit can burn out the car's ECU (repair cost - from 15,000 ₽).
  • 📵 Incorrect firmware of the microcircuit will lead to a lack of communication.
  • ⚡ Static electricity can damage the ECU inputs (use an antistatic wrist strap!).

If you are not confident in your abilities, it is better to buy a ready-made adapter. For example, for Honda 90's will do Hondata S300 (about 10,000 ₽), and for GM — ALDL-to-OBD2 from Moates (about 5,000 ₽).

FAQ: Frequently asked questions about OBD1→OBD2 adapters

Is it possible to flash the ECU through an adapter?

Theoretically yes, but in practice it is risky. Most adapters do not support writing data to the ECU - only reading. To flash the firmware you need a specialized tool (for example, OpenPort 2.0 for Subaru or Galletto for EDC15/16). In addition, incorrect firmware can “kill” the ECU, and you will have to resolder it or buy a new one.

Why does the scanner show the "Link Error" error?

This error means that the adapter cannot communicate with the ECU. Reasons:

  1. Invalid protocol (try ISO 9141 instead of CAN).
  2. Poor contact in the OBD1 connector (move the adapter or clean the contacts).
  3. The ECU does not support diagnostics via OBD1 (rare, but happens with some BMW 80s).

Solution: check the voltage on the OBD1 pins with a multimeter (should be 12V on the power line and 5V on the data line).

Does the adapter work with iPhone?

Yes, but with reservations:

  • iPhone does not support ELM327 Bluetooth (you need a Wi-Fi adapter, for example, OBDLink MX+).
  • Applications like DashCommand or OBD Fusion work with OBD1 only through specialized adapters (for example, STN1110).
  • For Android The choice is wider - you can use any Bluetooth adapters.
Can the adapter be used to diagnose diesel cars?

Yes, but with nuances:

  • Diesel engines (eg Mercedes OM606 or VW 1.9 TDI) often use the protocol KWP2000, which most adapters support.
  • However, some parameters (for example, fuel rail pressure) may not be read due to limitations of the old ECU.
  • For trucks (eg MAN or Scania) adapters for specific protocols will be required (J1939, J1708).
Where to buy an adapter for a rare brand (for example, Saab 900 or Alfa Romeo 164)?

For rare cars, adapters are usually made to order. Options:

  1. Order at AliExpress from sellers who offer “custom solutions” (for example, OBD1 Custom Adapter Store).
  2. Contact chip tuning communities (for example, forum ECU Tuning or DigitalKaos).
  3. Buy a universal adapter at STN1110 and reflash it to the desired protocol (you will need a soldering iron and a programmer).

The cost of a custom adapter is from 8,000 to 20,000 rubles.