The K-line is the single wire a tester uses to talk to a control unit that still speaks ISO 9141 or Keyword Protocol 2000. It idles near battery voltage, either end can pull it to ground, and a byte is a start bit, eight data bits with the least significant bit first, and a stop bit. The emissions session on that wire runs at 10.4 kbit/s. The services those bytes carry, and why that rate is not the sample rate of a log, are on the diagnostic communication protocols page. The pins in the 16-pin socket are on the diagnostic ports page.
The wire
A logic high is above 80 percent of the battery voltage at the control unit. A logic low is below 20 percent. The pull-up that holds the idle line high sits in the tester for a legislated session, so a control unit that is awake can still be silent and the line stays high. The K-line is bidirectional. The L-line, where the car has one, is a second wire the tester drives only while it is waking the control unit. It carries the same wake-up pattern. Once the session is running, the bytes are on the K-line.
The same electrical wire has been used for more than the emissions session. Manufacturer programming on K-line has been run faster than 10.4 kbit/s, including 115.2 kbit/s when the job is writing flash rather than reading legislated data. A proprietary byte stream on the same pin can add a parity bit or change the gaps. An emissions tool that only implements the three wake-ups below will not follow that stream, and a programming tool that jumps straight to a fast baud rate will not satisfy a control unit that is still waiting for a five-baud address.
Three ways to start
A legislated control unit implements one of three starts. They share the wire and they are separate sequences. ISO 14230-4 requires every emissions control unit on one vehicle to use either five-baud initialisation or fast initialisation. ISO 9141 is a third sequence, told apart from Keyword Protocol five-baud by the key bytes. California's OBD regulation allows the manufacturer one standardised protocol for that communication. A scan tool still has to discover which one this car is.
ISO 9141, five baud
The tester sends the address byte 33 hexadecimal at 5 bit/s. Each bit lasts 200 ms, so the start bit, the eight data bits and the stop bit occupy about two seconds. The line is idle high before that address. The control unit checks the address during W1, a window of 20 to 300 ms, then answers at 10.4 kbit/s with the synchronisation byte 55 hexadecimal. That byte is the pattern 01010101, and it is how the tester measures the real bit time. After W2, 5 to 20 ms, the control unit sends two key bytes, separated by W3, 0 to 20 ms. For ISO 9141 those key bytes are 08 08 or 94 94 hexadecimal. The pair tells the tester which minimum gap, P2, to keep. The tester waits W4, 25 to 50 ms, sends the second key byte inverted, waits another W4, and the control unit returns the address inverted. For the address 33 hexadecimal that inverted byte is CC hexadecimal. The session then uses 10.4 kbit/s.
Keyword Protocol, five baud
The bits on the wire follow the ISO 9141 start, including the two-second address and the 55 hexadecimal synchronisation byte. The key bytes differ. Keyword Protocol key bytes have the form 8F xx hexadecimal. Nineteen pairs are defined. Legislated OBD, in ISO 14230-4, allows four of them: 8F E9, 8F 6B, 8F 6D and 8F EF. Whichever of those four comes back, the tester uses the header rules that belong to 8F E9: a three-byte header, the length carried in the format byte, no extra length byte, and the normal timing set. One five-baud attempt is enough to tell ISO 9141 from Keyword Protocol, because the key bytes are the difference.
Keyword Protocol, fast initialisation
There is no five-baud address. The line must already have been idle. The tester then holds it low for 25 ms and lets it rise for 25 ms. That 50 ms pattern is the wake-up. Immediately afterwards, with no vehicle byte in between, the tester sends a StartCommunication request at 10.4 kbit/s. For a legislated functional wake-up the request is:
C1 33 F1 81 66
C1 hexadecimal is the format byte: functional addressing, and one data byte. 33 hexadecimal is the functional target. F1 hexadecimal is the tester. 81 hexadecimal is StartCommunication. 66 hexadecimal is the sum of the preceding bytes, modulo 256. The control unit answers within 50 ms. A positive answer has the shape:
83 F1 ss C1 yy zz cs
83 hexadecimal is a physical header with three data bytes. The target is the tester, F1. The source ss is that control unit's own address. C1 hexadecimal is the positive response, which is the request 81 hexadecimal plus 40 hexadecimal. yy zz are the key bytes. cs is the checksum. Nothing after this point is part of the wake-up. If that positive response never arrives, the fast initialisation has failed.
The first request
The first useful emissions request is service 01, parameter identifier 00, which asks which of the current-data identifiers this vehicle supports. The header has to match the key bytes just received.
| Key bytes | Service 01, identifier 00 |
|---|---|
| 08 08 or 94 94 | 68 6A F1 01 00 C4 |
| 8F E9, 8F 6B, 8F 6D or 8F EF | C2 33 F1 01 00 E7 |
68 6A F1 is the ISO 9141 emissions header. C2 33 F1 is the Keyword Protocol functional header with a two-byte payload, the service and the identifier. A fast-initialisation session may send this request only after the positive StartCommunication response. Sending it into the wake-up gap is a request the control unit is not yet ready for.
Legislated Keyword Protocol on this wire is the short form. The bit rate stays 10.4 kbit/s, the timing parameters stay at the normal set, the header always carries addresses, there is no separate length byte, and the data field stops at 7 bytes. The tester addresses a function, such as the powertrain at 33 hexadecimal. Each control unit answers with its own physical address. The longer Keyword Protocol message, up to a 255-byte data field, belongs to enhanced diagnostics on the same wire. That longer form is the one described on the protocols page. A legislated OBD request uses the short form above.
When the first try is ignored
SAE J1978 allows the protocol tests in any order, and in parallel where the pins allow it. One worked example in that document is J1850 pulse-width modulation, then J1850 variable pulse width, then ISO 9141-2, then ISO 14230-4, then ISO 15765-4. Those other buses are on the J1850 page and the CAN page.
A fast-initialisation low pulse wakes every control unit on the K-line, including one that only understands five baud. That control unit may spend the whole two-second address time, plus W1, deciding that the pulse was not a valid address. If the tester starts a five-baud address before that decision finishes, the control unit is still busy with the previous edge. It then treats the real address as another bad start, resets again, and the tester records a failure on a car that would have answered.
Two sequences keep the timings intact. Try five baud first, then fast initialisation. Or try fast initialisation first and, on silence, wait 2.6 seconds from the end of that attempt before the five-baud address: two seconds of address time, 300 ms of W1, and 300 ms of the tester's W5. A later retry on a line that may still be inside a session waits out P3 max first, so every control unit has left the previous exchange. Manufacturer quirks exist. They belong after these sequences have been tried.
Addresses, collisions, and a damaged reply
Neither ISO 9141 nor ISO 14230 assigns a physical address to an engine, a gearbox or an ABS unit. The manufacturer does. Annex material in ISO 14230-2 says the addresses are the vehicle maker's, and that a fast-initialisation address may follow the maker's five-baud map or the address style in SAE J2178. The tester address in the examples above is F1 hexadecimal. An engine that answers as 10 hexadecimal is common, and plenty of engines use another address, and plenty of other units use 10. The address is the manufacturer's label for that module.
Two control units can drive the wire at once after a functional request. The low level wins, in the same way a dominant bit wins on CAN, and a tester that sees a broken reply sends the original request again. The control units sort the collision out between themselves. The application can also refuse a request that arrived intact and still makes no sense to it: that answer is a negative response, with its own service identifier, rather than silence.
StartCommunication is 81 hexadecimal, StopCommunication is 82 hexadecimal, and AccessTimingParameter is 83 hexadecimal. Those three manage the link. A positive answer is the request plus 40 hexadecimal. Everything else in the data field is the diagnostic service, passed through to the control unit's application. On an emissions session the timing service is left at the normal set.
Sources
- ISO 9141-2. Five-baud initialisation, key bytes 08 08 and 94 94, and the W1 to W4 windows.
- ISO 14230-2. Keyword Protocol data link, fast initialisation, and manufacturer physical addresses.
- ISO 14230-4:2000. One initialisation method per vehicle, the four legislated key-byte pairs, and the 8F E9 header rules.
- SAE J1978. Protocol tests may run in any order. One worked example runs J1850 PWM, J1850 VPW, ISO 9141-2, ISO 14230-4, then ISO 15765-4.
- K-line communication description. OBD Clearinghouse. The three initialisation sequences, the service 01 requests, and the 2.6 second wait after a failed fast initialisation. Accessed 2026-11-12.