|
The LineSpi LEDs can be used to quickly identify the communication protocol.
The best way to identify the protocol is to set the scan tool up for LIVE DATA. This will result in a constant data stream between the scan tool and the vehicle. Next, locate the LED(s) that are flashing.
Pin 2
| • | VPW (Variable Pulse Width) |
| • | Signal decision point = +3.5v |
Pin 2 and Pin 10
| • | PWM (Pulse Width Modulated) |
Pin 6
| • | CAN (Controller Area Network) |
| • | Common to all US vehicles in 2008 |
Pin 7 (KWP and ISO)
| • | KWP2000 (Keyword Protocol 2000) |
| • | Common to European, Asian and some US. |
| • | Pin 15 L-line (optional) |
| • | Common to Chrysler, Asian, and European vehicles |
| • | Pin 15 L-line (optional) |
For example:
| • | Only LED 7 flashing: Protocol is either KWP or ISO 9141 |
| • | LED 2 and LED 10 flashing: Protocol is PWM |
NOTES:
| • | Just because the LEDs are flashing does not mean communication between the vehicle and the scanner has been established. For example, the scan tool initiates communication with the vehicle by toggling the different datalines. This results in the LEDs flashing. This is why it is important to use the LIVE DATA feature of your scan tool to identify the actual protocol. |
| • | Note that it is common for different combination of LEDs to be on regardless of the actual communication protocol. For example, a 2004 Mitsubishi Endeavor has a constant signal on the CAN lines (6 and 14) but the scan tool communicates via lines 7 and 15 (KWP/ISO). |
|