Error Message Byte Description
When the interface cannot perform the requested command, it returns a response message that’s Type byte is 80. The message includes the error code of the error that occurred. In this case, the description of the bytes for the response message is as follows.
1. Destination Address. (This is the address of the PC that sent the request message. It is normally 0x40)
2. Type. (In this case it is Error, 0x80)
3. Version code of interface
4. Error Code. (See Error Code Description below)
5. Interface Capabilities (Multiplex Engineering Use Only)
6. 00 Reserved. May be used for special features.
14. Sum check
Description of Error Codes
00 = Request Message command not implemented in this interface.
01 = Request Message command is not used.
02 = Request Message sum check error.
03 = ISO or KWP – No sync or incorrect sync.
04 = Incorrect ISO inverted address received.
05 = No ISO response to the request message.
06 = J1850 message received was not a diagnostic message.
07 = No J1850 response to the request message.
08 = ISO checksum error detected in response message.
09 = J1850 CRC error detected in response message.
0A = Unused
0B = KWP baud rate too slow
0C = No KWP response to the request message.
0D = KWP incorrect inverted address returned by car
0E = PWM pulse width is too long
0F = Incorrect variable response counter
10 = ISO not enabled
11 = J1850 VPW not enabled
12 = J1850 PWM not enabled
13 = KWP not enabled
14 = VW Pass-through mode not enabled
15 = Repeated arbitration errors
16 = CAN did not respond to request
17 = CAN core command had a bad command count
18 through 1F = Unused
20 = CAN destination address byte error
21 = CAN command byte error
22 = CAN byte count byte error
23 = CAN sum check byte error
24 = CAN RS232 receive message – 100ms timeout error
25 = CAN Configuration command address error
26 = CAN stop bit error
27 = CAN transmit message – 100ms timeout error
28 = CAN transmit error
29 = CAN transmit lost arbitration
2A = CAN receive message – 100ms timeout error
2B = CAN Mode Request – 100ms timeout error
2C = CAN invalid CAN byte count error
F1 = Unimplemented USB command attempted
F2 = Legacy (Non CAN) bus hardware did not respond to USB request
F3 = CAN hardware did not respond to USB request
Note 1. The interface automatically generates the error correction bytes for the messages.
Note 2. If a request message is sent, and no response is received from the car, an error Response Message will be sent by the interface.