ELM327: versions, clones, connection types and Windows setup

An ELM327 is a translator chip. Your software sends it a text line such as 0100, the adapter puts that request on the car diagnostic bus using the right protocol, and hands the module reply back as another text line. That is the entire job. Deciding which modules to interrogate and what a reply means belongs to the software on the PC - which is why so much of what people blame on the adapter is really a software limitation, and the other way round.

Elm Electronics, the Canadian company behind the part, shut down on 30 June 2022 and genuine silicon has not been made since. Everything on sale in 2026 is a clone, so the useful question is not whether yours is a clone but whether it is a complete one.

What the hardware can and cannot do

The original was built around a Microchip PIC18F2x8x core, and the datasheet reference circuit runs it from a 4 MHz crystal. Most good clones use a PIC18F25K80 at 16 MHz with reimplemented firmware. On the car side, the chip speaks every protocol the OBD-II connector allows; on the PC side it presents itself as a plain serial port over USB, Bluetooth SPP, BLE or WiFi.

Now the honest list of what an ELM327 will never do, whatever the sticker claims:

• No second bus. The chip is wired to pins 6 and 14 only. Ford and Mazda body modules on MS-CAN (pins 3 and 11) and GM body modules on single-wire CAN (pin 1) are physically out of reach. Those need an OBDLink on an STN chip: the MX+ covers both buses, the EX only MS-CAN.
• No coding, no flashing. It reads and clears, it does not write module configuration or reprogram firmware.
• No BMW dealer depth. Coding, service functions and full module access on a BMW need a K+DCAN cable or an ENET cable.
• Slow K-line. On pre-CAN cars the bus itself runs at 10.4 kbaud, so a full module sweep takes minutes, not seconds. That is physics, not the adapter.
• Patchy routine control. Actuator tests and UDS routines depend on the module accepting them, and clones with an incomplete header command set often cannot address the module at all.

The OBD-II connector, pin by pin

The socket is defined by SAE J1962: sixteen contacts, top row 1-8, bottom row 9-16, numbered left to right as you look at the socket in the car. Some pins are fixed by the standard, the rest are the manufacturer's to use.

Identifying your adapter properly

Forget the label and the chip marking: both come from the same people who wrote the firmware string. Identification is behavioral - work through this list in a terminal, or let Diagnost do it for you.

• ATZ - reset and banner. This is the string that gets quoted as the version, and it is a hard-coded text constant in every clone. Treat it as marketing, not evidence.
• ATI - the same identifier without a reset. If it disagrees with the banner, the firmware was patched carelessly.
• AT@1 - device description. Real firmware returns a meaningful string; thin clones return nothing or a question mark.
• ATRV - battery voltage at the connector. Compare it against a multimeter and watch it move when the engine starts. A constant 12.0V means there is no divider behind the number.
• ATPPS - programmable parameter summary. A complete board prints a table of hex values; a crippled one says it does not understand.
• ATAL, ATH1, ATSH, ATCRA - long messages, headers, custom header and receive filter. These four are what a module sweep is built on. If headers do not appear in replies after ATH1, that adapter will never read anything beyond generic engine codes.
• ATMA - monitor all traffic. Many fakes silently do nothing here, which is a well-known giveaway.

If you would rather not install anything first, the fastest test is the in-browser adapter check: it talks to an ELM327 over USB with Web Serial or over BLE with Web Bluetooth, straight from Chrome or Edge, and pulls engine codes in a few seconds. Windows and Android are supported, iOS is not.

Drivers and connection setup on Windows 10 and 11

USB

Inside a USB adapter sits a USB-to-serial bridge, most often a CH340, sometimes an FTDI FT232RL or a Prolific PL2303. Install the driver for the actual bridge: CH341SER for CH340, the CDM package from ftdichip.com for FTDI, and for PL2303 only the legacy driver, because current Prolific drivers deliberately refuse cloned chips. A healthy install shows up in Device Manager as a COM port with no warning icon.

On FTDI parts, open the port properties, go to the advanced port settings and drop the latency timer from its default of 16 ms to 1-4 ms. On a bus sweep with hundreds of short requests this is the difference between a brisk scan and a sluggish one.

Bluetooth SPP

Pair it in Windows settings with PIN 1234 or 0000. Windows then creates two virtual COM ports, outgoing and incoming, and software needs the outgoing one. Pairing is not connecting: the port only opens at the moment an application asks for it, which is why an adapter can sit in the device list looking paired and connected to nothing.

BLE

Bluetooth Low Energy models exist mainly because iOS does not let apps use SPP. Units such as the Vgate iCar Pro BLE are connected directly by the application through a GATT service and normally expose no COM port at all. On Windows this avoids the whole virtual-port mess, provided your software supports BLE - Diagnost and the browser check both do.

WiFi

A WiFi adapter runs its own access point. Factory defaults are almost always IP 192.168.0.10 and TCP port 35000, on an open network with no internet behind it. Join that network, point the software at that address, and expect the laptop to be offline until you disconnect.

What Diagnost reaches through an ELM327, by make and year

As of September 2026 the rule of thumb is simple: the newer the car, the more a cheap ELM327 gives you. On a CAN car from 2008 onward it is a full multi-module scanner in the hands of the right software; on a car from the late nineties it is an engine code reader and not much else.

Common connection failures

• Detected by Windows, no reply from the car. The PC-to-adapter half works and the adapter-to-car half does not. Ignition to ON, check ATRV for real battery voltage, then force the protocol instead of relying on ATSP0.
• Wrong COM port. Bluetooth pairing yields two ports and only the outgoing one works. Some older software also chokes on port numbers above COM9, which you can change in the driver properties.
• Wrong baud rate. 38400 is the factory value, 115200 appears on faster clones. At the wrong rate you get silence or garbage.
• Paired but not connected. Windows shows the device permanently, but the SPP channel only exists while an application holds the port open. Remove and re-pair if the port refuses to open.
• Replies truncated. Long multi-frame answers arriving in pieces is the signature failure of cut-down clones, and no setting fixes it - replace the adapter.
• WiFi joined, no data. Confirm the software is aimed at 192.168.0.10:35000 and that Windows has not silently switched back to a network with internet.

When to buy something else

An ELM327 is the right first adapter for almost everyone: cheap, universal, and enough for one owner and one car. Move up in three situations. For a BMW or Mini where you want coding, service resets and every module, buy a K+DCAN cable for E series and early F cars or an ENET cable for G and I series - around $10 each. For Ford, Mazda or GM body work, only an OBDLink MX+ (or an EX for Ford MS-CAN) reaches the second bus. For a pre-2005 car that never answers on CAN, you need K-line: a VAG KKL cable at about $5, or the same K+DCAN.

J2534 pass-through devices such as Mini-VCI, Mongoose, Scanmatik and Openport are a separate category: Diagnost drives them as a virtual ELM327 through the vendor driver, support was added in version 3.1.12 and is still being verified on real devices. They are not a BMW solution.

What the software does with any of these is on the Diagnost download page and the ELM327 software page; code explanations live in the code reference, for example P0420.