Dante383: 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..."

2026-11-01T00:06:09Z

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..."

New page

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 [[Body Control Module|BCM]] that steers [[K-Line]] traffic. If L-line is grounded, [[K-Line]] traffic goes to the [[Body Control Module|BCM]]. If it's released, [[K-Line]] traffic goes to the ECU.

While using [https://github.com/dante383/GKFlasher 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.

L-line - Revision history