1. Manuals
  2. Brands
  3. AVT Manuals
  4. Recording Equipment
  5. 84 Series
  6. Manual

AVT 84 Series Manual

Multiple interface
Hide thumbs
Table of Contents

Advertisement

Quick Links

ADVANCED VEHICLE TECHNOLOGIES, Inc.
J1850 VPW
CAN0: 2-wire (high speed)
CAN4: Single Wire CAN (SWC)
CAN ISO 15765 support
K-Line communications
LIN communications
1509 Manor View Road, Davidsonville, MD
AVT - 841 & 842 & 843
Multiple Interface
Volume 1
+1-410-798-4038 (voice)
www.AVT-HQ.com
AVT-841:
Hardware revision "B1"
AVT-842:
Hardware revision "A1"
AVT-843:
Hardware revision "A2"
Firmware Version "4.4"
27 February 2018
21035
support@AVT-HQ.com
USA

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 84 Series and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for AVT 84 Series

Summary of Contents for AVT 84 Series

  • Page 1 ADVANCED VEHICLE TECHNOLOGIES, Inc. AVT - 841 & 842 & 843 Multiple Interface Volume 1 J1850 VPW CAN0: 2-wire (high speed) CAN4: Single Wire CAN (SWC) CAN ISO 15765 support K-Line communications LIN communications AVT-841: Hardware revision “B1” AVT-842: Hardware revision “A1”...

  • Page 2: Table Of Contents

    ..........................7 OMMANDS AND ESPONSES GLOSSARY ................................7 AVT-84X OPERATION ............................8 HOST COMPUTER CONNECTION........................8 AVT-841 C ......................9 ONNECTION TO OMPUTER 4.1.1 AVT-841 Baud Rate to Host Computer......................9 AVT-842 C ......................9 ONNECTION TO OMPUTER AVT-843 C .......................10 ONNECTION TO OMPUTER 4.3.1 Ethernet Setup..............................11 4.3.2...
  • Page 3 AVT-84x Multiple Interface 7.10.5 ID/Mask Example #2 ...........................26 7.10.6 ID/Mask Example #3 ...........................26 7.10.7 ID/Mask Example #4 ...........................27 7.10.8 ID/Mask Example #5 ...........................27 7.10.9 Summary..............................28 7.11 ......................28 ETTING UP A CHANNEL FOR OPERATION 7.11.1 Communications Example ...........................28 7.12 ..............................29 HANNEL CTIVITY 7.13...
  • Page 4 AVT-84x Multiple Interface 9.3.3 Fast Transmit..............................57 ..........................57 ERIODIC ESSAGE UPPORT 9.4.1 Organization of Periodic Messages.........................57 9.4.2 Periodic Message Master Timer ........................57 9.4.3 Type1 Periodic Messages ..........................57 9.4.4 Type2 Periodic Messages ..........................59 9.4.5 Periodic Message Commands..........................60 VPW MODE ...............................60 10.1 JP3 ................................60 UMPER 10.2...
  • Page 5 AVT-84x Multiple Interface LIN OPERATIONS IN CAN MODE - COMMANDS .................108 15.1 ....................111 OPERATIONS IN MODE ESPONSES KWP OPERATIONS IN CAN MODE - COMMANDS ................117 16.1 CAN M ....................120 OPERATIONS IN ESPONSES VPW MODE - COMMANDS .........................126 17.1 VPW M ...........................131...

  • Page 6: Introduction

    1. Introduction This document describes the AVT-841, AVT-842, and AVT-843 hardware and firmware. The AVT-841, 842, and 843 are nearly identical units. The only difference is the means by which they connect to and communicate with the host computer. AVT-841: RS-232 serial communications with host computer.

  • Page 7: Firmware

    1.3 Firmware The firmware version stands at “4.3”. Refer to our web site for the most up-to-date information about AVT-84x firmware versions: www.AVT-HQ.com/841_asm.htm 1.3.1 Determining Firmware Version Perform the following to determine the version of firmware in your unit.

  • Page 8: Avt-84X Operation

    Bit-wise logical exclusive ‘OR’. 3. AVT-84x Operation The AVT-84x does not have a power switch. The unit powers up and begins operations as soon as it is plugged into a vehicle or other power source is applied. On power-up, the interface will, almost immediately, report to the host computer: $91 $12 and $92 $04 $xx (where “xx”...

  • Page 9: Connection To Host Computer

    AVT-84x Multiple Interface 4.1 AVT-841 Connection to Host Computer The AVT-841 serial connection to the host computer com port is standard RS-232. It should be mated to a host computer using a straight through wired 9-pin cable (NOT a null modem cable).

  • Page 10: Connection To Host Computer

    AVT-84x Multiple Interface Note that the USB side of the AVT-842 is USB bus powered. You can connect the AVT-842 to your host computer and it will be ‘discovered’ by the host and the port will be enumerated. USB driver software is provided by FTDI (from their web site). AVT has tested and recommends using the FTDI Virtual Com Port (VCP) drivers for communications between the user application and the AVT-842 board.

  • Page 11: Ethernet Setup

    4.3.1.2 Hardware or MAC Address The hardware or MAC address of the AVT-843 can be found on the serial number sticker on the XPort device - which looks like an RJ-45 connector. The MAC address will start with: “00-20-4A” for Lantronix.

  • Page 12: Ethernet Ip Addressing Modes

    Setting the AVT-843 IP address to 0.0.0.0 will enable DHCP (Dynamic Host Configuration Protocol) function. In this mode, the AVT-843 XPort will, on power-up, search for a DHCP server. If one is found it will obtain its IP address, gateway address, and subnet mask from the DHCP server.

  • Page 13: Autoip Addressing

    DHCP server.” [Quoted from Lantronix XPort User Manual, revision A 3/03, page 3-4.] AutoIP addressing is only enabled if the AVT-843 XPort IP address is set to 0.0.0.0 and no DHCP server is found.

  • Page 14: Vehicle Connection

    = is the receive status byte (indicates if any error were detected, etc.) ss tt vv = actual message from the network. Additional information about the AVT protocol is available at the beginning of the “Master Commands and Responses” document available from our web site at: www.AVT-HQ.com/download.htm#Notes...

  • Page 15: Power Requirements

    K-line network: VPW network: JP3. Note that AVT-841 revision “A” boards do not have JP3. The VPW network line is always connected to pin #2 of P3 - the DA-15P “Vehicle” connector. 6. ADC Connection The four position screw terminal block is used to access the three Analog to Digital Converter (ADC) channels.

  • Page 16: Adc Readings

    The report $83 11 04 00 indicates that CAN channel 4 is disabled. The report $91 19 indicates that LIN mode of operation is active. The AVT-84x supports operations of two simultaneous CAN channels and one LIN or KWP channel when in CAN mode.

  • Page 17: Can Secondary Operational Modes

    AU5790 transceiver. The SWC signal is routed through jumper JP1 to the D-15 network connector pin The factory default for jumper JP1 is OFF (to prevent possible damage in the event the AVT-84x is connected to a vehicle that does not have the SWC signal on pin #1).

  • Page 18: Jumper Jp1

    AVT-84x Multiple Interface 7.3.1 Jumper JP1 Jumper JP1 on the AVT-84x board connects / disconnects the Single Wire CAN (SWC) line from pin #1 of P3; the DA-15P “Vehicle” connector. Usually, the factory default position of JP1 is installed. 7.4 CAN0 Channel Number CAN0 is designated channel “0”.

  • Page 19: Listen Only

    AVT-84x Multiple Interface the acceptance ID according to the mask and associated rules, are passed to the host. Refer to Section 7.5 for a discussion. The CAN channel can transmit messages. Command: 73 11 0x 01 Status report: 83 11 0x 01 7.8.3 Listen Only...
  • Page 20 When ISO 15765 is enabled, maximum is 4095 data bytes. 7.8.4.5 Pacing Note 1 The AVT-84x will process a transmit command from the host as quickly as possible. It is possible that the host can send transmit commands to the AVT-84x so quickly that the transmitted CAN frames cause problems for the downstream module.

  • Page 21: Receive Response

    (the 7x 35 command). 7.8.5 Receive Response When the AVT-84x interface receives a CAN message from the CAN network the message is reformatted and sent to the host computer. There are three possible forms of the receive response. The number of bytes in the receive response determines the format used by the AVT-84x interface.

  • Page 22: Time Stamps

    AVT-84x Multiple Interface 11 pp rr ss xy tt vv ww zz mm nn ... : count of bytes to follow rr ss: time stamp [optional] 11-bit ID 29-bit ID normal frame RTR true, remote transmit request Channel number: 0, 4, 5, 6...
  • Page 23 AVT-84x Multiple Interface The 52 08 01 command enables time stamps where the time stamp clock is separate for each CAN channel and separate from the LIN channel. In this case the time stamp is a 16-bit free running counter that is driven by the baud clock for that channel.

  • Page 24: Acceptance Id And Mask Configuration

    ...: data field. 7.9 Acceptance ID and Mask Configuration Each CAN channel of the AVT-84x is independent of the other channel. Each CAN channel of the AVT-84x has three ID/Mask modes: Mode 2. The CAN channel has two 32-bit acceptance IDs and two corresponding 32-bit masks.

  • Page 25: Id/Mask Mode = 2

    AVT-84x Multiple Interface For modes 2 and 4, when setting up the acceptance ID, the user must specify in the command if the desired message ID is 11-bit or 29-bit. Refer to the CAN Commands and Responses later in this document;...

  • Page 26: Id/Mask Example #2

    AVT-84x Multiple Interface RTR bit is 0 (do not receive RTR frames). The following commands are used. ; set CAN0, ID/mask mode to 2 73 2B 00 02 ; set CAN0, acceptance ID0, 29-bit, RTR=0 77 2A 80 00 12 34 56 78 ;...

  • Page 27: Id/Mask Example #4

    AVT-84x Multiple Interface The following commands are used. ; set CAN4, ID/mask mode to 4 73 2B 04 04 ; set CAN4, acceptance ID2, 11-bit, RTR=0 75 2A 04 02 07 E0 ; set CAN4, Mask2, low order 4 bits are “don’t care,” all other bits are “must match.”...

  • Page 28: Summary

    AVT-84x Multiple Interface RTR bit is “don’t care.” (Will receive both non-RTR and RTR frames.) Send the following commands. ; set CAN0, ID/mask mode to 8 73 2B 00 08 ; set CAN0, acceptance ID6 74 2A 00 06 A5 ;...

  • Page 29: Channel Activity

    $FF. The counter will not rollover and will not automatically reset. The host computer can query for network activity on that CAN channel at any time. The AVT-84x will issue a response with the number of CAN frames received (up to the maximum of $FF) since the last query and then the counter is immediately reset.

  • Page 30: Organization Of Periodic Messages

    AVT-84x Multiple Interface 7.13.1 Organization of Periodic Messages Each CAN channel (0 and 4) has available two groups (1 and 2) of periodic messages with sixteen messages in each group. For each CAN channel, the periodic messages are numbered from $01 to $20.

  • Page 31: Type2 Periodic Messages

    AVT-84x Multiple Interface 4. ; Set the master timer to 98.30 msec 52 63 01 5. ; Define periodic message #01, ID = 0246, data = 03 A3 B4 C5 79 18 01 00 02 46 03 A3 B4 C5 6.

  • Page 32: Periodic Message Commands

    AVT-84x Multiple Interface 2. ; Set CAN4 baud rate to 33.333 kbps 73 0A 04 0A 3. ; Enable CAN4 normal operations 73 11 04 01 4. ; Enable CAN4 SWC transceiver for normal operations 72 12 03 5. ; Set the master timer to 98.30 msec 52 63 01 6.

  • Page 33: Iso 15765 Support

    AVT-84x Multiple Interface • 7x 1C Disable all periodic messages Disable all groups 7.14 ISO 15765 Support This may also be known as: Multi-Frame Messaging (MFM) Segmented Messages Keyword Protocol over CAN This protocol is often used in diagnostic modes for all messages and is particularly useful when moving large blocks of data.

  • Page 34: Receive Operations - General Notes

    PCI byte to the host, unless an error is encountered. When receiving a multi-frame message, the AVT-84x will automatically compose and send a Flow Control frame. The AVT-84x will never send a transmit ack (02 0x 0y) to the host when a Flow Control frame is transmitted.

  • Page 35: Receive Operations - Mode0

    If the CAN message is a single frame, the frame is sent to the host (PCI byte omitted). If the CAN message(s) are part of a multi-frame sequence, the AVT-84x will save the ID, save the AE byte (if enabled), remove the PCI bytes, remove any pad bytes, and buffer the inbound data. The AVT- 84x handles all handshaking with the downstream module.

  • Page 36: Transmit Operations

    AVT-84x Multiple Interface 84x handles all handshaking with the downstream module. When the complete message is received, the AVT-84x forwards the ID and block of data to the host using the usual ‘packet’ convention: 0x rr ss tt vv mm nn ...
  • Page 37 If the downstream module responds with a flow control separation time of ‘00’ the AVT-84x will transmit frames as fast as it can. It’s possible an AVT-84x can transmit frames too quickly.

  • Page 38: Operation Examples

    Enable the CAN channel. 73 11 0x 01 7.14.9.1 Example #1 (Mode1) The user wants to set up the AVT-84x to exchange ISO 15765 formatted messages with a CAN module. The specifics are: • 2-wire CAN at 500k baud. • 11-bit message IDs.
  • Page 39 CAN network. 7.14.9.2 Example #2 (Mode2) The user wants to set up the AVT-84x to receive all CAN network messages but only specified IDs are to be treated as ISO 15765 formatted. The specifics are: • 2-wire CAN at 500k baud.
  • Page 40 CAN network. 7.14.9.3 Example #3 (Mode1) The user wants to set up the AVT-84x to exchange ISO 15765 formatted messages with a CAN module. The specifics are: • Single Wire CAN (SWC) at 33.333 kbaud.

  • Page 41: Iso 15765 Questions And Engineering Support

    7.14.10 ISO 15765 Questions and Engineering Support Some may find the ISO 15765 protocol and its implementation in the AVT-84x to be confusing and difficult. It needn’t be. Contact the factory if you have questions - we will do our best to help.

  • Page 42: Command Descriptions (Non-Volatile Parameters)

    CAN frames. A ‘loop’ is the time it takes the AVT-84x firmware to make a complete loop in the firmware, in CAN mode. This time is variable, but empirical measurements in a lightly loaded environment reveal the ‘loop’...
  • Page 43 29-bit ID, right justified 7.15.2.3 ABX Data 76 38 This command queries for or stores the CAN frame data. All of this data is stored in the AVT-84x unit in non-volatile FLASH space. The address range is $0000 thru $7FFF (16 KBytes = 32 768 bytes).
  • Page 44 $ kk ll specifies how many bytes the host computer will send immediately following the command ($ kk ll valid range is $0001 to $0200) After the AVT-84x receives the command and all expected data bytes, the AVT-84x will respond with: 86 38 01 ss tt kk ll 7.15.2.4 ABX Byte Count...

  • Page 45: Command Description (Control)

    Remember that all parameters and data are stored in non-volatile memory on the AVT-84x unit. Thus, once an AVT-84x unit has been initialized, the user can start an Auto Block Transmit operation at any time. There is no need to re-initialize the ABX parameters just because the AVT-84x unit has been reset or power cycled.

  • Page 46: Operation Example

    20 milliseconds store some data total data count to 100 bytes Then I will set the AVT-84x unit, as noted here, and transmit the block. CAN0 at 500 kbaud do not receive any CAN frames enable CAN0 for operations.

  • Page 47: Lin Operations - In Can Mode

    LIN mode uses the AVT-84x K-line for communications. LIN mode can be disabled with the 52 69 00 command. 8.1 Jumper JP2 Jumper JP2 on the AVT-84x board connects / disconnects the K-line (LIN bus) from pin #7 of P3; the DA-15P “Vehicle” connector. 8.2 Communications Unless otherwise commanded, the AVT-84x will passively receive all messages from the LIN bus.

  • Page 48: Checksum

    The “52 66 01” command causes the AVT-84x to notify the host that an ID byte only message was received and report the ID byte. The format of the notification is (time stamps disabled):...

  • Page 49: Time Stamp

    AVT-84x Multiple Interface ; act as a Master without data -- this elicits a response from a Slave node 03 05 01 25 0 indicates “to” the network 3 count of bytes to follow 05 channel 5 - LIN 01 master node 25 message ID ;...

  • Page 50: Periodic Message Support

    40 status byte, bit 5 set, indicates “from this node”. 8.3 Periodic Message Support When LIN mode is active, the AVT-84x has the ability to transmit as many as ten ($0A) messages automatically. The operator defines and sets up the desired periodic messages, enables them, and the AVT-84x unit will then transmit those messages, at the defined interval, without any operator intervention.

  • Page 51: Organization Of Periodic Messages

    AVT-84x Multiple Interface 8.3.2 Organization of Periodic Messages In LIN mode there is only one group of periodic messages: Group1. All ten periodic messages are in Group1. All ten periodic messages can be set to operate in Type1 or Type2 mode.

  • Page 52: Type2 Periodic Message

    AVT-84x Multiple Interface 1. ; LIN mode is only available in CAN mode ; Enter CAN mode E1 99 2. ; Enable LIN operations (this is the default condition) 52 69 01 3. ; Set the master timer to 98.30 msec 52 63 01 4.

  • Page 53: Slave Periodic Message

    AVT-84x Multiple Interface A periodic message designated as a Slave will be qued for transmission when its timer expires. However, it will not be transmitted until a matching ID byte is received from the LIN bus. The message will stay queued until then and thus prevent other periodic messages from being transmitted.

  • Page 54: Periodic Message Commands

    AVT-84x Multiple Interface When a Slave periodic message is enabled for ‘Slave periodic message’ operations (the 7x 1A command) it operates independently of a timer. Every time an ID byte is received from the LIN bus, all periodic messages are searched. If a periodic message is enabled for ‘Slave periodic’ operations, and if its ID byte matches that just received from the LIN bus, then that message is immediately transmitted into the data field of the LIN frame in progress.

  • Page 55: Kwp Operations - In Can Mode

    KWP mode is now operational. 9.1 Jumper JP2 Jumper JP2 on the AVT-84x board connects / disconnects the K-line from pin #7 of P3; the DA-15P “Vehicle” connector. 9.2 Communications Unless otherwise commanded, the AVT-84x will passively receive all messages from the K-line.

  • Page 56: Time Stamp

    AVT-84x Multiple Interface 9.3.2 Time Stamp Time stamps for both the transmit ack and received messages can be disabled or enabled using the 5x 08 command. Transmit ack: the time stamp is a two byte value immediately after the packet header byte(s); but before the KWP channel number (06).

  • Page 57: Fast Transmit

    “52 27 00” command. However, due to internal processing, even when this value is set to zero, the AVT-84x unit still inserts a small delay between transmitted bytes. For some applications this (small) delay is unacceptable.
  • Page 58 AVT-84x Multiple Interface When Type1 operations are enabled, each enabled message in that group operates according to its own interval count. The message is set up. The interval count is defined. The message is enabled. The group is enabled for Type1 operations.

  • Page 59: Type2 Periodic Messages

    AVT-84x Multiple Interface 9.4.4 Type2 Periodic Messages Type2 periodic messages are transmitted in sequence, within the group. When more than one message in a group is defined and enabled, and the group operating mode is set for Type2 operations (7x 0C command) then those messages will be transmitted, in sequence, using the interval count of the first message in the group (regardless if that first message is used or not).

  • Page 60: Periodic Message Commands

    • Transmit acks are enabled and consist of the bytes “01 60.” 10.1 Jumper JP3 Jumper JP3 on the AVT-84x board connects / disconnects the VPW network from pin #2 of P3; the DA-15P “Vehicle” connector. Usually, the factory default position of JP3 is installed.

  • Page 61: Communications Example - Not Block Transfer

    68 is the priority / type byte 6A is the destination address (functional, in this case) F1 is the source address (an OBD-II tool, the AVT-84x, in this case) 01 is the mode 0C is the PID, which is a request for engine RPM ;...

  • Page 62: Time Stamp

    AVT-84x Multiple Interface 10.2.2 Time Stamp Time stamps for both the transmit ack and received messages can be disabled or enabled using the 5x 08 command. Transmit ack: the time stamp is a two byte value immediately after the packet header byte(s); but before the status byte.

  • Page 63: Example Network Message

    • “ss” is the source. (It is always a physical address.) • “mm nn rr ...” are the remaining bytes of the message. The AVT-84x firmware permits the host computer to specify one or two filter or match bytes, one for the destination byte and one for the source byte.

  • Page 64: Example #2

    Only messages with source byte equal to $20 will be passed to the host. If the message above is received from the network, the AVT-84x will determine that the source bytes do not match and will throw out the message. The host will not receive anything.

  • Page 65: Command Summary

    At this point, if any message passes by that has the byte sequence “AA BB CC DD EE” (or longer), and it must be an exact match, the command “C1 01” will be issued that will cause the AVT-84x to switch to 4X mode.

  • Page 66: Organization Of Periodic Messages

    A common use for this capability is for the “Tester Present” message that some ECUs (Electronic Control Units) require when in diagnostic mode. Another use would be in a simulation scenario. The AVT-84x will not generate a transmit ack when a periodic message is transmitted, unless transmit forwarding (52 06 01) is enabled.

  • Page 67: Type2 Periodic Messages

    AVT-84x Multiple Interface 2. ; Set the master timer to 98.30 msec 52 63 01 3. ; Define periodic message #01. (The message is: 68 6A F1 3F.) 76 18 01 68 6A F1 3F 4. ; Set periodic message #01 for an interval count of 10, actual interval = 0.983 msec 73 1B 01 0A 5.

  • Page 68: Periodic Message Commands

    Disable all groups 10.6 Block Transmit Example The AVT-84x supports transmitting VPW messages in block mode. The maximum message length supported is 4112 bytes = 4096 + 16 bytes. The hex equivalent is: $1010. The following is an example of transmitting a maximum length message in block mode.

  • Page 69: Block Receive Example

    VPW Responses, Section 17.1. The AVT-84x waits 3 seconds for the entire message to be received from the host. The message is buffered before being sent to the network.

  • Page 70: Jumper Jp2

    [An alternate configuration for the pull-up resistors is available. A second 1 K ohm resistor can be installed in parallel for an equivalent pull-up resistance of 500 ohms.] 11.1 Jumper JP2 Jumper JP2 on the AVT-84x board connects / disconnects the K-line from pin #7 of P3; the DA-15P “Vehicle” connector. 11.2 Communications K-line messages, according to ISO 14230 have a maximum length of 259 bytes (including checksum byte).

  • Page 71: Time Stamp

    AVT-84x Multiple Interface 6A is the destination address (functional, in this case) F1 is the source address (an OBD-II tool, the AVT-84x, in this case) 01 is the mode 0C is the PID, which is a request for engine RPM ;...

  • Page 72: Initialization

    Depending on the particular application, K-line communications with a vehicle and/or module may require initialization. Initialization is essentially a logical function. The AVT-84x unit (also known as the off-board tester) announces itself to the module it wishes to communicate with, requests a communications session, and, if successful, communicates with that module.

  • Page 73: Fast Initialization

    The user can query for the keyword, or two key bytes, using the “51 2C” command. If the initialization attempt fails, the AVT-84x will respond with a “22 54 xx” error code and then the 71 00 initialization attempt failure report.

  • Page 74: Organization Of Periodic Messages

    A common use for this capability is for the “Tester Present” message that some ECUs (Electronic Control Units) require when in diagnostic mode. Another use would be in a simulation scenario. The AVT-84x will not generate a transmit ack when a periodic message is transmitted, unless transmit forwarding (52 06 01) is enabled.

  • Page 75: Type2 Periodic Messages

    AVT-84x Multiple Interface 24. ; Set the master timer to 98.30 msec 52 63 01 25. ; Define periodic message #01. (The message is: 68 6A F1 3F.) 76 18 01 68 6A F1 3F 26. ; Set periodic message #01 for an interval count of 10, actual interval = 0.983 msec 73 1B 01 0A 27.

  • Page 76: Periodic Message Commands

    All AVT-84x units can be reFLASHed in the field to permit updating the unit operating firmware. 12.1 AVT-84x reFLASHing - AVT Provided Application AVT can provide stand alone applications for a host PC to reFLASH an AVT-841, 842, or 843 unit. Host operating systems supported are: WIN98, WIN-NT, WIN-XP, WIN2000.
  • Page 77 Double click on the executable (.exe) to launch the application. Running the application should be self explanatory. The AVT-84x firmware is likely to be released with the following naming convention. The “XX” in the name will be the version number.

  • Page 78: Idle Mode - Commands

    E1 DD: Switch to KWP mode. Model Query and Reset Query for model number. F1 A5: Restart the AVT-84x (a form of software reset). 13.1 Idle Mode - Responses Error reports. 22 34 xx: Command time-out. header byte of offending command.
  • Page 79 AVT-84x Multiple Interface Idle mode 21 70: Backdoor is disabled. 21 71: Backdoor access attempt failed. 21 84: Command buffer mode fault. Advanced Vehicle Technologies, Inc. Page 79...

  • Page 80: Can Mode - Commands

    AVT-84x Multiple Interface CAN mode 14. CAN Mode - Commands High nibble, bits b7 - b4: Command type. Packet for message to be transmitted to the network. Format “0x” 0p xy tt vv ww zz mm nn ... : count of bytes to follow.
  • Page 81 AVT-84x Multiple Interface CAN mode RTR true, remote transmit request. Channel number: 0, 4, 5, 6. tt vv: 11-bit ID, right justified. tt vv ww zz: 29-bit ID, right justified. mm nn ...: data. Data byte count limitations When ISO 15765 is disabled, maximum is 8 data bytes.
  • Page 82 AVT-84x Multiple Interface CAN mode 52 58 01: Read ADC channel #1 (terminal #1). 52 58 02: Read ADC channel #2 (terminal #2). 52 58 03: Read ADC channel #3 (terminal #3). -------------------- 51 59: Query for status of periodic ADC reports.
  • Page 83 AVT-84x Multiple Interface CAN mode CAN configuration. 71 0A: Request baud rate settings for all CAN channels. 72 0A 0x: Request baud rate setting for CAN channel. CAN channel, 0 or 4. 73 0A 0x yy: Set baud rate for CAN channel.
  • Page 84 AVT-84x Multiple Interface CAN mode Type2 enabled. -------------------- 71 0E: Outbound flow control separation time query; both channels. 72 0E 0r: Outbound flow control separation time query. CAN channel, 0 or 4. 73 0E 0r ss: Set outbound flow control separation time.
  • Page 85 AVT-84x Multiple Interface CAN mode 72 12 0x: Set SWC transceiver mode. CAN4 only. Sleep mode. High speed mode. Wake up mode. Normal mode. [Default.] -------------------- 71 17: Single Wire CAN (SWC) transceiver status request. CAN0 only. 72 17 0y: Set SWC transceiver mode.
  • Page 86 AVT-84x Multiple Interface CAN mode ‘normal’ mode enabled. ‘slave’ mode enabled. both modes enabled. -------------------- 73 1B 0x yy: Periodic message interval count status query. Channel number: 0, 4, 5, 6. Message number, $01 to $20. 74 1B 0x yy vv: Periodic message interval count command.
  • Page 87 AVT-84x Multiple Interface CAN mode 73 2A 0x 0z: Report specified acceptance ID. CAN channel, 0 or 4. Acceptance ID number; from 00 on up. Number depends on ID/Mask mode. 7x 2A xy 0z rr ss tt vv: Set acceptance ID.
  • Page 88 AVT-84x Multiple Interface CAN mode must match. don’t care. CAN channel, 0 or 4. Mask number; from 00 on up. Number depends on ID/Mask mode. Mask value when ID/Mask mode = 8. rr ss: Mask value when ID/Mask mode = 4.
  • Page 89 AVT-84x Multiple Interface CAN mode x: CAN channel 0 or 4. y: Data field length, 4 to 8. -------------------- 71 33: Query for CAN I5P receive buffer time-out value. 72 33 xx: Set CAN I5P receive buffer time-out value. Time is in 174.8 msec increments.
  • Page 90 AVT-84x Multiple Interface CAN mode nn rr: 11-bit ID, right justified. (IDE = 0). nn rr ss tt: 29-bit ID, right justified. (IDE = 1). -------------------- 76 38 0r ss tt kk ll: ABX data, read or store. r = 1: store the data into FLASH.

  • Page 91: Can Mode - Responses

    When ISO15765 processing is enabled, a non-zero value in the block size field of a flow control frame will result in the ’22 5F 3B’ or ’22 5F 7B’ error response from the AVT-84x to the host. This command will suppress those error responses.
  • Page 92 AVT-84x Multiple Interface CAN mode count of bytes to follow. rr ss: time stamp. [Optional.] IDE. 11-bit ID. 29-bit ID. RTR. normal frame. RTR true, remote transmit request. Channel number: 0, 4, 5, 6. tt vv: 11-bit ID, right justified.
  • Page 93 AVT-84x Multiple Interface CAN mode 21 35: Time out reading bytes from 12 xx yy command (less than 12 bytes). [3 seconds.] -------------------- 21 5B: Time out trying to send received block to host. [3 seconds.] -------------------- 22 5F xx CAN ISO 15765 processing error.
  • Page 94 AVT-84x Multiple Interface CAN mode CAN0; Command too long, 11/12, command flushed. CAN0; Transmitter not available, command flushed. CAN0; Ran out of data on first frame, command flushed. CAN0; Invalid separation time received ($80 to $F0). CAN0; Invalid separation time received ($FA to $FF).
  • Page 95 AVT-84x Multiple Interface CAN mode CAN4; Command too short. (0x xmt cmd, no AE, 11-bit) CAN4; Command too short. (0x xmt cmd, with AE, 11-bit) CAN4; Command too short. (0x xmt cmd, no AE, 29-bit) CAN4; Command too short. (0x xmt cmd, with AE, 29-bit) CAN4;...
  • Page 96 AVT-84x Multiple Interface CAN mode CAN0; 0x transmit processing error. CAN4; 0x transmit processing error. Invalid CAN channel number. CAN0; channel not configured to transmit. CAN0; non-I5P transmit command too short, 11-bit. CAN0; non-I5P transmit command too long, 11-bit. CAN0; non-I5P transmit command too short, 29-bit.
  • Page 97 AVT-84x Multiple Interface CAN mode CAN4; time out reading 11/12 transmit command. CAN0; mask mode not equal mask status, 7x_2B. CAN4; mask mode not equal mask status, 7x_2B. Mask mode not equal mask status, 7x_2B. Invalid id mode in CAN_rpt_all_ids.
  • Page 98 AVT-84x Multiple Interface CAN mode DLC > 8 in ISO 15765 receive manager DLC > 8 in 7x_18 routine DLC > 8 in non-ISO 15765 receive manager CAN error interrupt Copy of CAN0 rflg register. wake up interrupt flag. CAN status change interrupt flag.
  • Page 99 AVT-84x Multiple Interface CAN mode CAN status change interrupt flag. receiver status bit 1. receiver status bit 0. transmitter status bit 1. transmitter status bit 0. overrun interrupt flag. receive buffer full flag. -------------------- 21 84: Command buffer mode fault.
  • Page 100 AVT-84x Multiple Interface CAN mode -------------------- 64 58 xx yy zz: Periodic ADC report. xx = ADC channel #1 reading. yy = ADC channel #2 reading. zz = ADC channel #3 reading. -------------------- 62 59 00: Periodic ADC reports are disabled. [Default] 62 59 xx: Periodic ADC reports are enabled.
  • Page 101 AVT-84x Multiple Interface CAN mode User specified using 74 0B 0x rr ss command. 1 Mbps. 500 Kbps. [Default for CAN0.] 250 Kbps. 125 Kbps. 33.333 Kbps. [Default for CAN4]. 83.333 Kbps. -------------------- 84 0B 0x rr ss: Bit Timing Registers (BTR) for CAN channel.
  • Page 102 AVT-84x Multiple Interface CAN mode AE byte. -------------------- 83 11 0x 0y: Operational mode for CAN channel. CAN channel, 0 or 4. Disabled. [Default for CAN0 and CAN4.] Enabled for normal operations. Enabled for listen only operations. -------------------- 82 12 0x: Set SWC transceiver mode.
  • Page 103 AVT-84x Multiple Interface CAN mode Message number, $01 to $20. disabled. ‘normal’ mode enabled. ‘slave’ mode enabled. both modes enabled. -------------------- 84 1B 0x yy vv: Periodic message interval count. CAN channel, 0 or 4. Message number, $01 to $20.
  • Page 104 AVT-84x Multiple Interface CAN mode Acceptance ID value when ID/Mask mode = 8. rr ss: Acceptance ID value when ID/Mask mode = 4. rr ss: Acceptance ID value when ID/Mask mode = 2. and IDE = 0 (11-bit). rr ss tt vv: Acceptance ID value when ID/Mask mode = 2 and IDE = 1 (29-bit).
  • Page 105 AVT-84x Multiple Interface CAN mode -------------------- 83 30 0s 0t: “AE” byte; disable / enable status report. CAN channel, 0 or 4. disabled. enabled. -------------------- 83 32 0x 0y: First frame data field length. x: CAN channel 0 or 4.
  • Page 106 AVT-84x Multiple Interface CAN mode nn rr ss tt: 29-bit ID, right justified. (IDE = 1). -------------------- 86 38 02 ss tt kk ll: ABX data, read from FLASH. ss tt: start address. kk ll: number of bytes to follow.
  • Page 107 AVT-84x Multiple Interface CAN mode 91 0C: FIFO reset. 91 0F: KWP operations. 91 10: CAN operations. 91 19: LIN operations. 91 24: CAN0 reset. 91 25: CAN4 reset. Advanced Vehicle Technologies, Inc. Page 107...

  • Page 108: Lin Operations In Can Mode - Commands

    AVT-84x Multiple Interface LIN operations in CAN mode 15. LIN operations in CAN mode - Commands High nibble, bits b7 - b4: Command type. Note: Only LIN unique commands are listed. Some CAN mode commands may be applicable. Refer to the CAN mode section for additional commands, responses, and information.
  • Page 109 AVT-84x Multiple Interface LIN operations in CAN mode ABIC = 15 control LIN: 00 = slave; 01 = master ABIC = count of expected response bytes from ABIC ss tt: message bytes All forms are equal in ascending order. 0x = 11 0x = 12 00 0x...
  • Page 110 Disable receive buffer auto-termination function. 52 3C 01: Enable receive buffer auto-termination function. [Default] (Auto-terminate function only applies to the receive function of network messages being transmitted by the AVT-84x. e.g. reception of the echo.) -------------------- 51 50: Query for LIN bus baud rate.

  • Page 111: Lin Operations In Can Mode - Responses

    AVT-84x Multiple Interface LIN operations in CAN mode Periodic messages are supported for LIN operations. Refer to the CAN commands Section 14 for command information. 15.1 LIN operations in CAN mode - Responses High nibble, bits b7 - b4: Response type.
  • Page 112 AVT-84x Multiple Interface LIN operations in CAN mode receive message too long buffer closed by break buffer opened without break synch byte error receive message too short or actual length not equal to expected length checksum error message ID rr ss tt ...
  • Page 113 AVT-84x Multiple Interface LIN operations in CAN mode received sync not equal transmitted transmitted state unknown unknown command byte transmitted processing return code error state watchdog timeout echo error in tm6 echo error in tm6 transmit length error in tm6...
  • Page 114 AVT-84x Multiple Interface LIN operations in CAN mode received a zero length message error decoding length bits, receive manager #2 master mode is unknown receive byte not equal transmit byte (slave) slave mode error lin_m_state time-out transmit data register empty.
  • Page 115 AVT-84x Multiple Interface LIN operations in CAN mode -------------------- 62 24 00: Do not receive any network messages. 62 24 01: Receive network messages. [Default.] -------------------- 62 27 xx: P4 time, transmit message inter-byte time. “xx” is in increments of approximately 30 microseconds.
  • Page 116 AVT-84x Multiple Interface LIN operations in CAN mode Advanced Vehicle Technologies, Inc. Page 116...

  • Page 117: Kwp Operations In Can Mode - Commands

    AVT-84x Multiple Interface KWP operations in CAN mode 16. KWP operations in CAN mode - Commands High nibble, bits b7 - b4: Command type. Note: Only KWP unique commands are listed. Some CAN mode commands may be applicable. Some KWP mode commands may be applicable.
  • Page 118 AVT-84x Multiple Interface KWP operations in CAN mode Example: for K-line bus baud rate = 10400; xxyy = $00 90 (hex) = 144 (decimal) -------------------- 51 06: Request transmit message echo status. 52 06 00: Do not echo transmitted messages. [Default] 52 06 01: Echo transmitted messages.
  • Page 119 AVT-84x Multiple Interface KWP operations in CAN mode 51 48: Query for FAST initialization high time. 52 48 xx: Set FAST initialization high time to “xx” milliseconds. [Default = 25] -------------------- 51 4B: Query for status of type of transmit checksum.

  • Page 120: Kwp Operations In Can Mode - Responses

    AVT-84x Multiple Interface KWP operations in CAN mode 16.1 KWP operations in CAN Mode - Responses High nibble, bits b7 - b4: Response type. Note: Only KWP unique responses are listed. Some CAN mode responses may be applicable. Some KWP mode responses may be applicable.
  • Page 121 AVT-84x Multiple Interface KWP operations in CAN mode Alternate form #2 for long messages (blocks). 12 xx yy 06 pp rr ss tt ... xx yy: count of bytes to follow. the channel number message status byte, as defined above.
  • Page 122 AVT-84x Multiple Interface KWP operations in CAN mode K-line not high during rest of T_high. Time out waiting for rest of T_high. -------------------- 24 85 xx yy zz: KWP error. short to ground detected. periodic message error. zero length periodic message found.
  • Page 123 AVT-84x Multiple Interface KWP operations in CAN mode Configuration reports. 62 01 00: Send received checksum to host disabled. [Default] 62 01 01: Send received checksum to host enabled. -------------------- 63 03 xx yy: Baud rate divisor is “xx yy”.
  • Page 124 AVT-84x Multiple Interface KWP operations in CAN mode 62 4B 01: Transmit checksum is 2’s complement. -------------------- 62 57 xx: Parity type and frame length. All are one start bit and one stop bit. 01 – 8 data bits, no parity (frame length = 10). [Default] 02 –...
  • Page 125 AVT-84x Multiple Interface KWP operations in CAN mode Advanced Vehicle Technologies, Inc. Page 125...

  • Page 126: Vpw Mode - Commands

    AVT-84x Multiple Interface VPW mode 17. VPW Mode - Commands High nibble, bits b7 - b4: Command type. Packet for transmission to the network. 0x yy zz ... : x is message length; yy zz ... message bytes. Alternate header formats, packet for transmission to the network.
  • Page 127 AVT-84x Multiple Interface VPW mode 53 35 xx yy: Direct communication with DLC. xx - Transmit Data or Configuration byte. yy - Command byte. -------------------- 51 40: Transmit acks query. 52 40 00: Do not send transmit acks to host.
  • Page 128 AVT-84x Multiple Interface VPW mode 52 67 01: Set host baud rate to 19.2 kbaud. 52 67 02: Set host baud rate to 38.4 kbaud. 52 67 03: Set host baud rate to 57.6 kbaud. 52 67 04: Set host baud rate to 115.2 kbaud.
  • Page 129 AVT-84x Multiple Interface VPW mode 71 0C: Periodic message group operational control. Status query; Group1 is reported. 72 0C 0x: Status query 1 = Group1 (only). 73 0C 0x 0y: Periodic message group operational control command. 1 = Group1 (only).
  • Page 130 Switch to VPW mode. E1 99: Switch to CAN mode. E1 DD: Switch to KWP mode. Model Query and Reset Query for model number. F1 A5: Restart the AVT-84x (a form of software reset). Advanced Vehicle Technologies, Inc. Page 130...

  • Page 131: Vpw Mode - Responses

    AVT-84x Multiple Interface VPW mode 17.1 VPW Mode - Responses High nibble, bits b7 - b4: Response type. Valid message packet received from the network. 0x pp rr ss tt ... count of bytes to follow. message status byte; bit map, bit set indicates: CRC error.
  • Page 132 AVT-84x Multiple Interface VPW mode -------------------- 21 34: Time out reading bytes from 11 xx command (less than 12 bytes). [3 seconds.] -------------------- 22 34 xx: Command time-out. header byte of offending command. [0.5 seconds.] -------------------- 21 35: Time out reading bytes from 12 xx yy command (less than 12 bytes).
  • Page 133 AVT-84x Multiple Interface VPW mode byte count to sum = $0000. checksums are not equal. -------------------- 21 79: No instruction trap. -------------------- 21 7A: COP fail reset. -------------------- 21 7B: Clock monitor reset. -------------------- 23 83 xx yy: VPW error.
  • Page 134 AVT-84x Multiple Interface VPW mode Configuration reports. 62 06 00: Echo of transmitted messages disabled. [Default.] 62 06 01: Echo of transmitted messages enabled. -------------------- 62 08 00: Time stamps are disabled. [Default] 62 08 01: Time stamps are enabled.
  • Page 135 AVT-84x Multiple Interface VPW mode 62 5C xx: Source filter byte is set to value “xx”. [Default = 00, disabled.] -------------------- 62 63 xx: Master timer setting. 98.30 msec. 49.15 msec. 20.48 msec. 10.24 msec. 5.12 msec. -------------------- 62 67 01: Host baud rate is set for 19.2 kbaud.
  • Page 136 AVT-84x Multiple Interface VPW mode 83 0C 0x 0y: Periodic message group operation status. Group, 1 or 2. Mode. Disabled. Type1 enabled. Type2 enabled. -------------------- 8x 18 xx mm nn pp... Periodic message setup. Message number, $01 to $0A. mm nn pp ...: The message.
  • Page 137 AVT-84x Multiple Interface VPW mode C1 01: High speed (4X) mode selected. F3 pp rr ss Block transmit acknowledgement count of bytes to follow. message status byte; bit map, bit set indicates: Bad message, bad status, or receive block too big.

  • Page 138: Kwp Mode - Commands

    AVT-84x Multiple Interface KWP mode 18. KWP Mode - Commands High nibble, bits b7 - b4: Command type. Packet for transmission to the network. 0x yy zz ... : x is message length; yy zz ... message bytes. Alternate header formats, packet for transmission to the network.
  • Page 139 AVT-84x Multiple Interface KWP mode -------------------- 51 08: Request time stamp status. 52 08 00: Disable time stamps. [Default] 52 08 01: Enable time stamps. The time stamp is 1 millisecond resolution. -------------------- 51 13: Query for 5-baud address. 52 13 xx: Set 5-baud address to $xx.
  • Page 140 AVT-84x Multiple Interface KWP mode -------------------- 51 48: Query for FAST initialization high time. 52 48 xx: Set FAST initialization high time to “xx” milliseconds. [Default = 25] -------------------- 51 4B: Query for status of type of transmit checksum. 52 4B 00: Transmit checksum is “normal”...
  • Page 141 Note: This delay is in addition to the P4 inter-byte time (5x 27 command). This delay is in “xx” main loop counts. For example, if the P4 time is set to 00, but the AVT-84x is then transmitting too fast, you can add a small amount of delay using this command.
  • Page 142 AVT-84x Multiple Interface KWP mode Mode. Disabled. Type1 enabled. Type2 enabled. -------------------- 72 18 xx: Periodic message setup query. Message number, $01 to $0A. 7x 18 xx mm nn pp ... Periodic message setup command. Message number, $01 to $0A.

  • Page 143: Kwp Mode - Responses

    Switch to KWP mode. Model Query and Reset Query for model number. F1 A5: Restart the AVT-84x (a form of software reset). 18.1 KWP Mode - Responses High nibble, bits b7 - b4: Response type. Valid message packet received from the network.
  • Page 144 AVT-84x Multiple Interface KWP mode -------------------- 22 2C xx: Serial comms with host error. transmit data register empty. transmit complete. receive data register full. idle. overrun. noise flag. framing error. parity fault. -------------------- 22 34 xx: Command time-out. header byte of offending command.
  • Page 145 AVT-84x Multiple Interface KWP mode Inverted address byte received in error, not equal to expected. Unknown return code from initialization attempt. 5-baud start bit error. 5-baud, sending “0” bit error. 5-baud, sending “1” bit error. 5-baud sending stop bit error.
  • Page 146 AVT-84x Multiple Interface KWP mode short to ground detected. periodic message error. zero length periodic message found. zero length periodic message found. transmit watchdog time out. no receive buffers available. zz: SCI1_error transmit date register empty. transmit complete. receive data register full.
  • Page 147 AVT-84x Multiple Interface KWP mode -------------------- 62 06 00: Echo of transmitted messages disabled. [Default.] 62 06 01: Echo of transmitted messages enabled. -------------------- 62 08 00: Time stamps are disabled. [Default] 62 08 01: Time stamps are enabled. -------------------- 62 13 xx: 5-baud address is “xx”.
  • Page 148 AVT-84x Multiple Interface KWP mode 62 4B 01: Transmit checksum is 2’s complement. -------------------- 62 4C xx: Command processing delay. Delay is ‘xx’ timer ticks (5x 63 command). -------------------- 62 57 xx: Parity type and frame length. All are one start bit and one stop bit.
  • Page 149 AVT-84x Multiple Interface KWP mode 00 = red LED off. xx = red LED blink rate; interval is 174.8 msec. FF = red LED on. -------------------- 62 6C 00: “Fast Transmit” disabled. 62 6C 01: “Fast Transmit” enabled. -------------------- 62 6D xx: Transmit inter-byte delay is set to “xx”...
  • Page 150 AVT-84x Multiple Interface KWP mode 81 1C: All periodic messages disabled. Board status information. 92 04 xx: Firmware version report. Firmware version is ‘xx’. 91 07: VPW operations. 91 08: DLC initialization complete. 91 0C: FIFO reset. 91 0F: KWP operations.
  • Page 151 8 Exit without save 9 Save and exit Your choice ? If you do not make a selection, but instead just hit <Enter> the AVT-843 XPort module will display the full unit configuration. An example listing is below (3 sections down). ======================================== At the menu prompt, select "0"...
  • Page 152 When you select <9> and hit <Enter> the AVT-843 XPort will save the configuration and reboot - that will terminate the telnet session. Wait at least 20 seconds for the AVT-843 XPort unit to finish saving and rebooting before trying to establish a connection to the AVT-843 unit.
  • Page 153 AVT-84x Multiple Interface Appendix A 3 E-mail 5 Expert 6 Security 7 Factory defaults 8 Exit without save 9 Save and exit Your choice ? *** basic parameters Hardware: Ethernet TPI IP addr 192.168.1.70, no gateway set, netmask 255.255.255.000 *** Security...
  • Page 154 Re-notification interval : 0 s ======================================== 20. Appendix B A listing of the AVT-843 XPort device, setup web page, factory default settings are provided in this appendix. [Please see the notes at the end of this Section.] To log into the AVT-843 XPort to view and/or change the configuration, use a web browser and...
  • Page 155 Disconnect Mode: Flush Mode: Pack Control: UDP Datagram Type: [Not used] Server Properties Page Select the button to view and change the AVT-843 XPort properties. Factory “Server Properties” default settings are shown here. Server Properties IP Address: 192.168.1.70 Subnet Mask: 255.255.255.0...
  • Page 156 AVT-84x Multiple Interface Appendix A UDP Datagram Type: [blank] Incoming Connection: Accept unconditional Response: Nothing (quiet) Startup: No Active Connection Startup Dedicated Connection Remote IP Address: [blank] Remote Port: [blank] Local Port: 10001 Flush Mode Input Buffer (Line to Network)

  • Page 157: Questions

    Appendix A Notes: I tried several different versions of web browsers to try and access the web page of the AVT-843 XPort. Only one worked. Your results will likely differ. (Both browsers and the embedded web page in the Xport have been updated and changed. The last time I checked, things are working much better using the browser interface of the Xport.)

  • Page 158: Bit Map For Ids, Masks, Commands, Etc

    AVT-84x Multiple Interface Appendix A 22. Bit Map for IDs, Masks, Commands, etc. A worksheet that may help in determining acceptance IDs, masks, and command values is on the next page. Advanced Vehicle Technologies, Inc. Page 158...
  • Page 159 bit # 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 mask mask mask mask mask Bit map form...

This manual is also suitable for:

841842843

Table of Contents