Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
Implementing TP1.6 Vehicle Diagnostic Protocol on SAE J2534 Pass-Thru Devices
The TP1.6 vehicle diagnostic protocol, defined in SAE J3054, is a proprietary communication protocol used in certain Volkswagen of America and Audi of America vehicles. This standard provides the requirements for implementing TP1.6 on SAE J2534 pass-thru interfaces, enabling diagnostic tools to communicate with ECUs that support this protocol. Below, we break down the key aspects: CAN message format, transport protocol rules, and error handling, along with practical insights for engineers.
Protocol Overview and CAN Message Format
TP1.6 relies on specific CAN telegram structures for channel setup, acknowledgment, and data transfer. The protocol uses 11-bit CAN identifiers and a fixed data length of 8 bytes. Channel setup involves a two-step handshake: the tester sends a Channel Setup (ChS) request, and the ECU responds with a Channel Acknowledge (ChA) message. The following static parameters apply:
| Parameter | Value |
|---|---|
| Baud rate | 500 kbps |
| CAN identifier type | 11-bit |
| Data length code | 8 |
| Channel ID range (ChS) | 0x000 – 0xFFF |
| Channel ID range (ChA) | 0x000 – 0xFFF (same as request) |
Proper assignment of channel identifiers and adherence to these static parameters are critical for establishing a valid channel. The standard specifies distinct source identifiers for the tester and ECU to avoid conflicts.
Transport Protocol Rules and Error Handling
Once a channel is established, data exchange follows a transport protocol with built-in acknowledgment, block size management, and timeout handling. Key timings include T1 (wait for acknowledgment) and T2 (inter-block timeout). The protocol supports flow control via Acknowledge Request (AR) and Ready/Not Ready responses. Engineers must handle retransmissions gracefully when acknowledgments are missing or when the receiver is not ready.
🛠️ Design Insight: The static parameters and predefined CAN identifiers simplify implementation, but strict timing compliance is essential. Missing even a single acknowledgment can cause the diagnostic session to hang. Always validate timeout values against the standard.
⚠️ Common Mistake: Confusing the channel setup acknowledge with transport protocol acknowledges. Ensure your state machine correctly transitions between channel establishment and data transfer phases.
Error handling procedures in the standard cover scenarios like missing acknowledges, retransmission of previous blocks, and direction changes (e.g., from sending to receiving). Reference the examples in SAE J3054 for precise message sequences.
Frequently Asked Questions
- What vehicles use TP1.6?
- Some Volkswagen of America and Audi of America vehicles with ECUs that support this proprietary protocol. Consult the vehicle’s diagnostic documentation to confirm.
- How does TP1.6 relate to SAE J2534?
- SAE J2534-2 defines the pass-thru interface requirements; SAE J3054 (TP1.6) specifies how to implement this particular protocol on such interfaces for VW/Audi diagnostics.
- What are the key CAN telegram parameters for channel setup?
- The static parameters include 500 kbps baud rate, 11-bit CAN IDs, 8 data bytes, and specific channel ID ranges (0x000–0xFFF) for both request and acknowledge.
- How are timeouts handled in the transport protocol?
- T1 defines the maximum wait time for an acknowledgment after sending a message, while T2 governs the inter-block interval. If these timeouts expire, the protocol triggers error handling, such as retransmission or session disconnection.
