SAE: PassThru¶
Vendor information
Vendor |
Web page |
Product name |
Version |
|---|---|---|---|
SAE International |
SAE J2534 PassThru API |
04.04 |
Categories
MDL 🛈 |
APL 🛈 |
BAN 🛈 |
BMA 🛈 |
SVC 🛈 |
DGN 🛈 |
FIU 🛈 |
EES 🛈 |
FCT 🛈 |
DBG 🛈 |
IMG 🛈 |
AUDIO 🛈 |
ENVSIM 🛈 |
ENVCOM 🛈 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
✓ |
✓ |
✓ |
✓ |
✓ |
Signal recordings 🛈
File format |
Comment |
|---|---|
*.asc |
|
*.mf4 |
BUSACCESS - CAN(-FD) ports support MDF4 bus logging only. XCP ports support signal-based MDF4 recording. |
*.pcapng |
BUSACCESS - CAN(-FD) ports will use linktype=227. The resulting files cannot be processed by trace analysis. |
Platform
Operating system |
Support |
|---|---|
Windows |
✓ |
Linux |
Ports¶
Info
Ports marked with ✦ are part of the Add-on ecu.test calibration (subject to a separate license)
Specifics¶
This interface allows, by means of hardware, direct CAN bus access for all devices for which an SAE J2534 pass-thru driver (64 Bit) is installed. It supports the test steps read signal, read/write signal group as well as monitor and supports signal recording, Raw diagnostics with KWP2000 over ISO-TP, the Mini residual bus simulation and Additional functions of the close-to-hardware bus connections. For CAN-FD both the official SAE J2534-2-2019 and the proprietary GMW17753 standard are supported.
Tested hardware:
Intrepid ValueCAN4-2
PEAK PCAN PassThru
Kvaser (only with a virtual device)
Vector VN8970
Note
The exact range of functionality depends very much on the type and vendor of the hardware used. Some vendors might not implement certain options (e.g. ISO-TP extended addressing) or restrict the possible number or combination of controller instances (e.g. only CAN or diagnostics with native ISO-TP but not both).
If there are problems configuring or using the tool, please check the manufacturer information and leave unsupported parameters in ecu.test at their default values.
Properties 🛈¶
Name |
Available if |
Default value |
Valid values |
Type |
Description |
|---|---|---|---|---|---|
Hardware |
[‘<online query>’, ‘<no toollib start>’] |
string |
Choose the hardware which should be used |
||
Device name |
string |
Device to use |
|||
Timeout for tool call ❲in sec.❳ |
‘600’ |
string |
Timeout after which a tool call is aborted. |