Request Message Format
The Request Message is a message sent from a personal computer to the Multiplex Engineering interface that is 15 bytes long. The request message either instructs the interface to send a message to the vehicle with the data included, or it requests information from the interface itself. The message sent to the vehicle or information requested from the interface depends on the Command sent in the message.
The Format for a request message is:
(Destination), (Command), (Byte Count), (Data 1), …, (Data 11), (Sum check)
All bytes in the message including the command number are in hexadecimal format.
Destination
The destination address can be different for different interfaces. Specific destination addresses are assigned to different customers. You must send your destination address to your interface or the interface will not allow any communications.
Command
This is the command byte. The Commands that the diagnostic interface will respond to are described in Request Message Commands.
Byte Count
This is the number of bytes that will be sent over the automobile data bus. This does not include the error detection byte sent on the automobile data bus. (The interface will generate the error detection byte.) The byte count is not used in some commands. Please refer to the specific command format to see its structure.
Data
These are the actual data bytes of the message that will be sent on the automobile data bus. The first byte sent to the vehicle is the most significant byte in the message for the vehicle.
Sum check
The sum check is the lower 8 bits of the sum of the Command byte through the last data byte. The Destination byte is not included in the Sum check.
Request Message Format – Byte Description:
1. Destination
2. Command
3. Byte Count
4. 1st (most significant) byte of the message to be sent to the automobile
5. 2nd byte of the message to be sent to the automobile
6. 3rd byte of the message to be sent to the automobile
7. 4th byte of the message to be sent to the automobile
8. 5th byte of the message to be sent to the automobile
9. 6th byte of the message to be sent to the automobile
10. 7th byte of the message to be sent to the automobile
11. 8th byte of the message to be sent to the automobile
12. 9th byte of the message to be sent to the automobile
13. 10th byte of the message to be sent to the automobile
14. 11th byte of the message to be sent to the automobile
15. Sum check
Request Message Commands
Request message commands are used to instruct the interface what to do with the message it receives. The interface first reads the command and then performs the corresponding action with the data included in the request message. The command messages are detailed below.
Legacy Buses Commands
01 = Send message on ISO-9141-2 with initialization
Command Usage
Command 01 is used as the first message sent over ISO 9141 to initialize the connection. The initialization takes place at 5 bits/sec, because of this and other bytes sent it can require up to 2 seconds to complete the initialization. After the bus is initialized, you will need to send a command at least every 5 seconds according to the specifications to keep the connection active. However, we recommend you send a 10 command every 3 seconds to keep the connections alive.
Request Message Format
1. Destination Address
2. 01
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
02 = Send message on J1850 VPW [details]
Command Usage
Command 02 is used to send the message contained in the Data Bytes 1-11 over J1850 VPW.
Request Message Format
1. Destination Address
2. 02
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 102
14. Data Byte 11
15. Sum Check
04 = Send message on J1850 PWM without IFR [details]
Command Usage
Command 04 is used to send the message contained in the Data Bytes 1-11 over J1850 VPW without In Frame Response (IFR). In Frame Response is an internal handshake used by Ford vehicles. We do not recommend sending PWM message to Ford vehicles without IFR.
Request Message Format
1. Destination Address
2. 04
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
10 = Send message on ISO-9141-2 without initialization [details]
Command Usage
Command 10 is used to send the message contained in the Data Bytes 1-11 over IS0 9141. The connection needs to have already been established with the 01 command to use the 10 command.
Request Message Format
1. Destination Address
2. 10
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
When bit 5 of the Byte Count is set to a 1 the interface will be configured for receive of one long response message.
When bit 6 of the Byte Count is set to a 1 the ISO request message will be sent but the interface will not wait to receive the response message.
When bit 7 of the Byte Count is set to a 1the ISO request message will be sent with out a checksum byte.
20 = VW Intelligent Pass-through Mode with 5 baud init and baud rate detect. (Not available in USB) [details]
Command Usage
Command is an old way of communicating with VW cars. While this feature is still in our RS232 interfaces we do not recommend using it.
A Brief Over Of How The VW Intelligent Pass-through Mode Works
1. Command 20 is sent with the desired controller address.
2. The interface sends the desired controller address at exactly 5 baud on both the K and L lines.
3. The interface observes the sync byte (55) from the ECU and determines the period of baud rate used by the ECU.
4. The interface responds with an RS232 message that contains the vehicle’s ISO baud rate.
5. The PC must then receive KW1 and KW2, and send the KW2 inverted to the ECU. All future messages are in pass-through mode unless 5 seconds passes without any ISO bus activity. After 5 seconds, the interface returns to normal mode.
Request Message Format
1. Destination Address
2. 20
3. 1
4. Controller Address
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
40 = VW Intelligent Pass-through Mode without 5 baud init. (Not available in USB) [details]
Command Usage
Command 40 functions the same as command 20 except it allows a direct transition to pass-through mode. The 5 baud init and the baud rate detection of the sync byte are skipped. The response message is therefore empty. See Command 20 details for more information.
Request Message Format
1. Destination Address
2. 40
3. 1
4. Controller Address
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
41 = Send a VPW message and ignore VPW responses 1-8, report responses 9-16 [details]
Command Usage
Command 41 sends the message contained in Data Bytes 1-11 over VPW and stores responses 9-16 from the request message. Responses 1-8 are ignored.
Request Message Format
1. Destination Address
2. 41
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
42 = Send a VPW message and ignore VPW responses 1-16, report responses 17-24 [details]
Command Usage
Command 42 sends the message contained in Data Bytes 1-11 over VPW and stores responses 17-24 from the request message. Responses 1-16 are ignored.
Request Message Format
Request Message Format
1. Destination Address
2. 42
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
43 = Send a VPW message and ignore VPW responses 1-24, report responses 25-32 [details]
Command Usage
Command 43 sends the message contained in Data Bytes 1-11 over VPW and stores responses 25-32 from the request message. Responses 1-24 are ignored.
Request Message Format
1. Destination Address
2. 43
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
44 = Send a VPW message and ignore VPW responses 1-32, report responses 33-40 [details]
Command Usage
Command 44 sends the message contained in Data Bytes 1-11 over VPW and stores responses 33-40 from the request message. Responses 1-32 are ignored.
Request Message Format
1. Destination Address
2. 44
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
45 = J1850 VPW set up for monitor mode, for use with J2190 mode 21 [details]
Command Usage
Command 45 is not recommended for most users. Please contact one of our engineers for more information on this command.
46 = J1850 VPW send, but do not wait for responses [details]
Command Usage
Command 46 sends the message contained in Data Byte 11-1 over VPW but dose not wait for a response from the vehicle. A normal response message for J1850 VPW will be reported as soon as the request message is sent on the J1850 VPW bus.
Request Message Format
1. Destination Address
2. 46
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
47 = J1850 VPW send, and enter monitor mode [details]
Command Usage
Command 47 is not recommended for most users. Please contact one of our engineers for more information on this command.
48 = Intelligent Pass-through mode with 5 baud init (Not available on USB interfaces) [details]
Command Usage
Command 48 enters Intelligent Pass-through mode with a 5 baud init. Pass-through mode is an old way of doing communications. While this feature is still available in our RS232 interfaces we do not recommend using this feature.
Request Message Format
1. Destination Address
2. 48
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
49 = VPW send, but do not report FE and FF [details]
Command Usage
Command 49 sends a VPW request message and ignores responses from addresses FE and FF. This command is useful because some vehicles use source addresses FF and FE for non diagnostic purposes. In this case the data from these address is not useful to the user.
Request Message Format
1. Destination Address
2. 49
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
4A = PWM send, but do not report FE and FF [details]
Command Usage
Command 4A sends a PWM request message and ignores responses from addresses FE and FF. This command is useful because some vehicles use source addresses FF and FE for non diagnostic purposes. In this case the data from these address is not useful to the user.
Request Message Format
1. Destination Address
2. 4A
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
4B = ISO send, but do not report FE and FF [details]
Command Usage
Command 4B sends a ISO request message and ignores responses from addresses FE and FF. This command is useful because some vehicles use source addresses FF and FE for non diagnostic purposes. In this case the data from these address is not useful to the user.
Request Message Format
1. Destination Address
2. 4B
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
4C = KWP send, but do not report FE and FF [details]
Command Usage
Command 4C sends a KWP request message and ignores responses from addresses FE and FF. This command is useful because some vehicles use source addresses FF and FE for non diagnostic purposes. In this case the data from these address is not useful to the user.
Request Message Format
1. Destination Address
2. 4C
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
4D = Reserved For Multiplex Engineering Use
4E = J1850 VPW send, with aggressive arbitration (version 47 and later) [details]
Command Usage
Command 4E will send the request message on the J1850 VPW bus with aggressive arbitration for use with the J1850 bus. This command waits the bare minimum time after the end of a J1850 VPW message, before attempting to send the J1850 VPW request message from the interface. This reduces the amount of time the interface waits before getting onto the bus to send its message. The reason to have this new command is to allow diagnostic messages to get through, even if the J1850 VPW bus traffic is happening at close to the maximum throughput. The normal J1850 VPW command (Command 02) was intentionally done with a long wait after the previous J1850 VPW message. This was done to avoid the risk of diagnostic messages overloading the J1850 VPW bus and causing operational errors. Due to the J1850 VPW bus loading on GM vehicles, this command is recommended.
Request Message Format
1. Destination Address
2. 4E
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
4F = ISO send, with 5 baud, user-programmable 5 baud address [details]
Command Usage
Command 4F sends and ISO request message with a custom 5 baud address. The custom 5 baud address is stored in Request Byte 14. This means the longest data message that can be sent with this command is 10 bytes long instead of the normal 11 byte maximum.
Request Message Format
1. Destination Address
2. 4F
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Byte to be sent as 5 Baud ISO Address
15. Sum Check
80 = Send message on J1850 PWM with IFR (recommended for Ford) [details]
Command Usage
Command 80 sends a message on J1859 PWM with In Frame Response (IFR). In Frame Response is a internal handshake used by Ford vehicles. This is why we recommend using command 80 instead of command 04 when communicating with Ford vehicles.
Request Message Format
1. Destination Address
2. 80
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
Note: setting the most significant bit in the byte count will cause the skip of sending the PWM request message and cause a receive only mode. An example request message for receive only is FF 80 85 68 6A 01 00 00 00 00 00 00 00 00 D8
81 = Send message on ISO-9141-2, receive only 1st response [details]
Command Usage
Command 81 sends a message on ISO-9141-2. The interface only stores and sends back to the user the first response from the vehicle. All other responses from the vehicle are ignored.
Request Message Format
1. Destination Address
2. 81
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
82 = Send message on J1850 VPW, receive only 1st response [details]
Command Usage
Command 82 sends a message on J1850 VPW. The interface only stores and sends back to the user the first response from the vehicle. All other responses from the vehicle are ignored.
Request Message Format
1. Destination Address
2. 82
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
83 = Read car battery voltage [details]
Command Usage
Command 83 sends a message to the interface that asks it to read the voltage of the car battery. This voltage is converted from analog to digital and stored into the 3rd most significant byte in the response message. To get the value, convert the 3rd byte to decimal and multiply by 0.23.
Request Message Format
1. Destination Address
2. 83
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
Note that the legacy commands will be turned off and that part of the interface will be put to “SLEEP” if a command 83 with a byte count of FF is sent. The interface must be disconnected from the car or the reset line (hardware) activated to recover from this command. This feature is used to reduce power consumption.
84 = J1850 PWM send command, receive only 1st response [details]
Command Usage
Command 84 sends a message to J1850 PWM. The interface only stores and sends back to the user the first response from the vehicle. All other responses from the vehicle are ignored.
Request Message Format
1. Destination Address
2. 84
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10br> 14. Data Byte 11
15. Sum Check
85 = KWP send, with 5 baud initialization [details]
Command Usage
Command 85 sends a message with Key Word Protocol and performs 5 baud initialization.
Request Message Format
1. Destination Address
2. 85
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
When bit 4 of the Byte Count is set to a 1 the response message reported will be one long response of 96 bytes. Some cars require this for proprietary mode communications.
When bit 5 of the Byte Count is set to a 1 the baud rate of the KWP messages will be 9600 baud. The interface will remain in 9600 baud mode until a message is sent with command 87 KWP Fast Init. Some cars require this for proprietary mode communications.
When bit 6 of the Byte Count is set to a 1 the interface transmits the request but does not wait to receive a response.
When bit 7 of the Byte Count is set to a 1 the interface will not calculate the KWP checksum byte and it will not transmit the KWP checksum byte. This allows the user to calculate a checksum byte and add it to the message. Some cars require a different type of checksum when operating in a proprietary mode.
86 = KWP report KW1 and KW2. Must do command 85 first. [details]
Command Usage
Command 86 sends a message with Key Word Protocol (KWP) that reports Key Word 1(KW1) and Key Word 2(KW2). KW1 and KW2 are sent back in a single response message. KW1 is stored in the second byte of the response message. KW2 is stored in the third byte of the response message. Command 85 must be sent before 86 can be used.
Request Message Format
1. Destination Address
2. 86
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
Response Message Format
1. Command
2. KW1
3. KW2
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. Sum Check
87 = KWP send, with fast initialization [details]
Command Usage
Command 87 sends a message with Key Word Protocol with fast initialization.
Request Message Format
1. Destination Address
2. 87
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
When bit 4 of the Byte Count is set to a 1 the response message reported will be one long response of 96 bytes. Some cars require this for proprietary mode communications.
When bit 5 of the Byte Count is set to a 1 the baud rate of the KWP messages will be 9600 baud. The interface will remain in 9600 baud mode until a message is sent with command 87 KWP Fast Init. Some cars require this for proprietary mode communications.
When bit 6 of the Byte Count is set to a 1 the interface transmits the request but does not wait to receive a response.
When bit 7 of the Byte Count is set to a 1 the interface will not calculate the KWP checksum byte and it will not transmit the KWP checksum byte. This allows the user to calculate a checksum byte and add it to the message. Some cars require a different type of checksum when operating in a proprietary mode.
88 = KWP send, without initialization [details]
Command Usage
Command 88 sends a message to KWP without initialization. The baud rate that is used is determined by the previous 5 baud initialization. If no 5 baud initialization has been preformed then the baud rate defaults back to 10.4Kbps.
Request Message Format
1. Destination Address
2. 88
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
When bit 4 of the Byte Count is set to a 1 the response message reported will be one long response of 96 bytes. Some cars require this for proprietary mode communications.
When bit 5 of the Byte Count is set to a 1 the baud rate of the KWP messages will be 9600 baud. The interface will remain in 9600 baud mode until a message is sent with command 87 KWP Fast Init. Some cars require this for proprietary mode communications.
When bit 6 of the Byte Count is set to a 1 the interface transmits the request but does not wait to receive a response.
When bit 7 of the Byte Count is set to a 1 the interface will not calculate the KWP checksum byte and it will not transmit the KWP checksum byte. This allows the user to calculate a checksum byte and add it to the message. Some cars require a different type of checksum when operating in a proprietary mode.
89 through 8E = Reserved
8F = Toyota Propritary KWP [details]
Command Usage
Command 89 sends a message to KWP with a special fast initialization. The baud rate is then set to 9600 baud. This command is intended for use with Toyota proprietary type communications.
Request Message Format
1. Destination Address
2. 8F
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
90 = Bosch Propritary KWP [details]
Command Usage
Command 90 sends a message to KWP without initialization. One 96 byte long response message will be reported. This command does special low level features and is not suitable for normal KWP use.
Request Message Format
1. Destination Address
2. 90
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
91 through 9F = RESERVED
CAN Bus Commands
08 = Send message on CAN without flow control. [details]
Command Usage
Command 08 sends the message contained in Data Bytes 1-11 over CAN without flow control. This is not recommend for most applications. Instead, we recommend using Command A0.
Request Message Format
1. Destination Address
2. 08
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
A0 = CAN send, with flow control. [details]
Command Usage
Command A0 sends the message contained in Data Bytes 1-11 over CAN with flow control. This command is recommend for most CAN applications.
Request Message Format
1. Destination Address
2. A0
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
A1 = CAN configuration command, changes flow control message default values.(Version F or later) [details]
Command Usage
Command A1 allows the user to change the default control flow message for CAN. It also allows the user to change some timing values. Please contact one of our engineers for more information on this command.
A2 = Set the 11 bit SID address and switch to SID addressing mode. [details]
Command Usage
Command A2 sets the 11 bit SID address for transmitting equal to the address stored in third and fourth bytes of the request message. It then puts the interface into SID mode. Please note that SID bits 2:0 are in the following format in the forth byte of the request message (SID2, SID1, SID0, x, x, x, x, x).
Please read the tutorial on EID and SID addressing for more information and examples on how to use this command.
Request Message Format
1. Destination Address
2. A2
3. SID address 10:3
4. SID address 2:0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
A3 = Set the 29 bit EID address and switch to EID addressing mode. [details]
Command Usage
Command A3 sets the 29 bit EID address for transmitting equal to the address stored in third, forth, fifth and sixth bytes of the request message. It then puts the interface into EID mode. Please note that EID address bits 20:16 are in the following byte format (EID20, EID19, EID18, x, x, x, EID17, EID16).
Please read the tutorial on EID and SID addressing for more information and examples on how to use this command.
Request Message Format
1. Destination Address
2. A3
3. EID address 28:21
4. EID address 20:16
5. EID address 15:8
6. EID address 7:0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
A4 = Send one CAN message, wait for responses, saving response SID information. [details]
Command Usage
Command A4 sends one CAN message and then waits for responses until another command is sent from the user. The interface will create a response message right away to indicate that the CAN message was sent. The interface will then wait forever (if needed), gathering responses until another command is received from the user.
The A4 command also reports the 11 bit SID CAN addresses of the responses. The address is stored in the first 3 data bytes of the response message. This shifts the data from the message over by three bytes as well (See the response message format below).
To retrieve the messages stored by a command A4 the user must send a command A9.
Request Message Format
1. Destination Address
2. A4
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
Response Message Format
1. Destination Address of user
2. 88
3. 00
4. SID address 10:8 (0,0,0,0,0,SID10,SID9,SID8)
5. SID address 7:0
6. Data Byte 1
7. Data Byte 2
8. Data Byte 3
9. Data Byte 4
10. Data Byte 5
11. Data Byte 6
12. Data Byte 7
13. Data Byte 8
14. Data Byte 9
15. Sum Check
A5 = Send one CAN message, wait for responses, saving response EID information. [details]
Command Usage
Command A5 sends one CAN message and then waits for responses until another command is sent from the user. The interface will create a response message right away to indicate that the CAN message was sent. The interface will then wait forever (if needed), gathering responses until another command is received from the user.
The A5 command also reports the 29 bit EID CAN addresses of the responses. The address is stored in the first 3 data bytes of the response message. Only the lower 24 bits of the EID address are stored in the message. The Upper 5 bits are ignored. This shifts the data from the message over by three bytes as well (See the response message format below).
To retrieve the messages stored by a command A5 the user must send a command A9.
Request Message Format
1. Destination Address
2. A5
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
Response Message Format
1. Destination Address of user
2. 88
3. EID address 23:16
4. EID address 15:8
5. EID address 7:0
6. Data Byte 1
7. Data Byte 2
8. Data Byte 3
9. Data Byte 4
10. Data Byte 5
11. Data Byte 6
12. Data Byte 7
13. Data Byte 8
14. Data Byte 9
15. Sum Check
A6 = Set the SID acceptance mask and filter for receiving. [details]
Command A6 sets the SID acceptance mask and filter, and puts the interface into SID mode for receiving. A bit in the incoming address is accepted regardless of its value if the corresponding bit in the mask is 0. A bit in the incoming address must be equal to the corresponding bit in the filter address if the corresponding bit in the mask is 1. If you want to receive all messages from addresses 0x7E0 through 0x7EF you would set the filter to 0x7E0 with a mask of 0xFF0. This mask will make the interface only accept messages whose upper 2 address bytes match the filter; the lowest byte is ignored when filtering the incoming messages.
Please note that the bits of Mask 2:0 are in the following format (MASK2, MASK1, MASK0, x, x, x, x, x).
Also note that the bits of Filter 2:0 are in the following format (FILTER2, FILTER1, FILTER0, x, x, x, x, x). It is recommended to use 0 for x.
Please read the tutorial on EID and SID addressing for more information and examples on how to use this command.
Request Message Format
1. Destination Address
2. A6
3. SID Mask bits 10:3
4. SID Mask bits 2:0
5. SID Filter bits 10:3
6. SID Filter bits 2:0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
A7 = Set the EID acceptance mask and filter for receiving. [details]
A7: Configuration Command for EID Receive Mode
This command writes the EID acceptance mask and filter, and puts the interface into EID mode for receiving. A bit in the incoming address is accepted regardless of its value if the corresponding bit in the mask is 0. A bit in the incoming address must be equal to the corresponding bit in the filter address if the corresponding bit in the mask is 1. If you want to receive all messages from addresses 0x18DAF100 through 0x18DAF1FF, you would set the filter to 0x18DAF100 with a mask of 0xFFFFFF00. This mask will make the interface only accept messages whose upper 6 address bytes match the filter; the lower 2 bytes are ignored when filtering the incoming messages.
Please note that the bits of MASK 20:16 are in the following format (MASK20, MASK19, MASK18, x, x, x, MASK17, MASK16).
Also note that the bits of FILTER 20:16 are in the following format (FILTER20, FILTER19, FILTER18, x, 1, x, FILTER17, FILTER16). It is recommended to use 0 for x. The 1 in between the two don’t cares in the Filter is to enable EID mode in older version (Ver E or older) of our CAN enabled interface. Newer versions do not need to worry about this setting this bit to one, since it is treated as a don’t care.
Please read the tutorial on EID and SID addressing for more information and examples on how to use this command.
Request Message Format
1. Destination Address
2. A7
3. EID Mask bits 28:21
4. EID Mask bits 20:16
5. EID Mask bits 15:8
6. EID Mask bits 7:0
7. EID Filter bits 28:21
8. EID Filter bits 20:16
9. EID Filter bits 15:8
10. EID Filter bits 7:0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
A8 = Send one CAN message and wait for responses. [details]
Command Usage
Command A8 sends the CAN message contained in Data Bytes 1-11 and saves the response messages from this message in a buffer that can be read out with the A9 command.
Request Message Format
1. Destination Address
2. A8
3. BYTE COUNT
4. Data Byte 1
5. Data Byte 2
6. Data Byte 3
7. Data Byte 4
8. Data Byte 5
9. Data Byte 6
10. Data Byte 7
11. Data Byte 8
12. Data Byte 9
13. Data Byte 10
14. Data Byte 11
15. Sum Check
A9 = Read CAN buffer to get responses from A8 command [details]
Command Usage
Command A9 gets the responses from command A8, A4 or A5. Command A8, A4 or A5 must be sent prior to using Command A9.
Request Message Format
1. Destination Address
2. A9
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
AA = Change CAN baud rate [details]
Command Usage
Command AA changes the CAN baud rate. The lower 5 bits, of the third byte in the request message contain the CAN baud rate. The valid values for the baud rate are defined as:
0x00 = 500 Kbaud
0x01 = 250 Kbaud
0x02 = 166.6666… Kbaud
0x03 = 125 Kbaud
Request Message Format
1. Destination Address
2. AA
3. Baud Rate
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
AB = Reserved
AC = Reserved
AD = Go into reprogram mode. [details]
Command Usage
Command AD puts the interface into reprogramming mode. Please contact one of our engineers for more information on this command.
AE = Send “core” commands used in reprogramming. [details]
Command Usage
Command AE sends the core commands used in reprogramming. Please contact one of our engineers for more information on this command.
AF = Return from reprogram mode. [details]
Command Usage
Command AF brings the interface out of reprogramming mode. Please contact one of our engineers for more information on this command.
USB Only Commands
F1 = Get the first response message. [details]
Command Usage
Command F1 tells the interface to send out the first response message stored in the interface from the most recent request message.
Request Message Format
1. Destination Address
2. F1
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
F2 = Get the second response message. [details]
Command Usage
Command F2 tells the interface to send out the second response message stored in the interface from the most recent request message.
Request Message Format
1. Destination Address
2. F2
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
F3 = Get the third response message. [details]
Command Usage
Command F3 tells the interface to send out the third response message stored in the interface from the most recent request message.
Request Message Format
1. Destination Address
2. F3
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
F4 = Get the fourth response message. [details]
Command Usage
Command F4 tells the interface to send out the forth response message stored in the interface from the most recent request message.
Request Message Format
1. Destination Address
2. F4
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
F5 = Get the fifth response message. [details]
Command Usage
Command F5 tells the interface to send out the fifth response message stored in the interface from the most recent request message.
Request Message Format
1. Destination Address
2. F5
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
F6 = Get the sixth response message. [details]
Command Usage
Command F6 tells the interface to send out the sixth response message stored in the interface from the most recent request message.
Request Message Format
1. Destination Address
2. F6
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
F7 = Get the seventh response message. [details]
Command Usage
Command F7 tells the interface to send out the seventh response message stored in the interface from the most recent request message.
Request Message Format
1. Destination Address
2. F7
3. 0
4. 0
5. 0
6. 0
7. 0
8. 0
9. 0
10. 0
11. 0
12. 0
13. 0
14. 0
15. Sum Check
F8 = Get the eighth response message. [details]