Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J2534-2/13_0500: Adding Ethernet to Pass-Thru Vehicle Diagnostics
Note: This standard is part of the SAE J2534-2 extended feature set, designed to support Diagnostics over IP (DoIP) as per ISO 13400, and is fully compatible with SAE J2534-1_0500 API version 05.00.
Rationale and Scope
Modern vehicle architectures increasingly rely on Ethernet networks for diagnostic communication. SAE J2534-2/13_0500 addresses this shift by defining how to implement Ethernet within the SAE J2534 Pass-Thru API framework. The recommended practice must be used together with SAE J2534-2/BA_0500 and SAE J2534-2/RE_0500 documents, and only the Ethernet-specific changes are detailed here—everything else remains as defined in SAE J2534-1_0500.
Key Technical Requirements and API Changes
The standard specifies protocol requirements, pin usage, and error handling for Ethernet-based pass-thru interfaces. New IOCTL commands allow configuration and diagnostics over the Ethernet link. The following table summarizes the most important IOCTL additions:
| IOCTL Command | Description |
|---|---|
| GET_CONFIG / SET_CONFIG | Read or write Ethernet configuration parameters (e.g., speed, duplex, VLAN). |
| SET_MAC_ADDRESS | Assign a MAC address to the pass-thru device. |
| GET_MAC_ADDRESS | Retrieve the currently assigned MAC address. |
| ETH_ACTIVATION_PULLUP | Control the activation pull-up circuit required for Ethernet line wake-up. |
🛠️ Engineering Design Insight: To ensure reliable operation, the standard follows the OSI seven-layer model for its Ethernet stack and enables simultaneous communication on multiple protocols. This allows a single pass-thru device to handle DoIP, CAN, and other protocols concurrently without interference.
⚠️ Common Mistakes: Incorrect pin usage (see Table 3 in the standard) can cause link failures. Always check network errors using the codes defined in Table 4. Many implementations also skip the discovery mechanism, leading to hardcoded parameters—use GET_DEVICE_INFO, GET_PROTOCOL_INFO, and GET_RESOURCE_INFO to maintain flexibility.
Discovery Mechanism and Best Practices
The discovery mechanism is a cornerstone of the Ethernet extension. Using the WIN32 API IOCTL calls, software can query the device, protocol, and resource information dynamically. This avoids configuration errors and simplifies integration across different pass-thru devices. For example, GET_DEVICE_INFO provides vendor and firmware details, while GET_PROTOCOL_INFO lists all supported protocols and their capabilities.
🔍 When designing a client application, always start with discovery to ensure the attached pass-thru device supports the required Ethernet features and API version 05.00. This practice reduces runtime failures and improves user experience.
Frequently Asked Questions
- What are the API function changes for Ethernet support?
- New IOCTL commands for Ethernet configuration and MAC address handling have been added. Existing functions like
PassThruConnect,PassThruSelect, andPassThruIoctlnow accept Ethernet-specific parameters. - How to handle network errors in Pass-Thru?
- Refer to Table 4 in the standard for specific network error codes. Proper error checking ensures reliable communication and quick fault isolation.
- What is the required connector/pin combination for Ethernet?
- Table 3 specifies the required connector and pin combinations for Ethernet pass-thru devices, ensuring mechanical compatibility with vehicle diagnostic connectors (e.g., SAE J1962).
- How to perform device discovery?
- Use the
GET_DEVICE_INFO,GET_PROTOCOL_INFO, andGET_RESOURCE_INFOIOCTLs to discover device capabilities, supported protocols, and available resources dynamically.
