L-line

From OpenGK
Revision as of 00:06, 1 November 2026 by Dante383 (talk | contribs) (Created page with "L-Line on the Tiburon has nothing to do with L-Line described in ISO 9141-2. It isn't a separate communication line and it does not require receiving 5 baud init wakeup packets to wake up the ECU. It's simply connected to the relay inside of the BCM that steers K-Line traffic. If L-line is grounded, K-Line traffic goes to the BCM. If it's released, K-Line traffic goes to the ECU. While using [https://github.c...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

L-Line on the Tiburon has nothing to do with L-Line described in ISO 9141-2.

It isn't a separate communication line and it does not require receiving 5 baud init wakeup packets to wake up the ECU.

It's simply connected to the relay inside of the BCM that steers K-Line traffic. If L-line is grounded, K-Line traffic goes to the BCM. If it's released, K-Line traffic goes to the ECU.

While using GKFlasher or other tools at high baudrate, it's possible to hear a rapid ticking of said relay. Hearing this relay being constantly activated means that your OBD2 adapter tries to send wakeup packets over L-Line. By trying to do so, it constantly flips the relay, causing you to drop frames on K-Line. If this happens to you, it is recommended to physically unconnect L-Line from your adapter.

Retrieved from "https://opengk.org:443/index.php?title=L-line&oldid=1038"