For on-board diagnostics, the OBD-2 standard defines the exchange of specific vehicle parameters. The client makes a request on the connected control units (ECUs) in the vehicle to which one or several ECUs are answering. As part of OBD-2, the ISO 15765-4 standard describes the CAN bus as a transmission option.
The PCAN-OBD-2 API implements the functionality of the standard on the basis of 15 functions. They are categorized in Tester Allocation, Configuration, Information, Services, and Communication.
According to ISO 15765-4, OBD-2 is based on UDS. Analog to this, PCAN-OBD-2 uses the PCAN-UDS programming interface for the exchange of diagnostic data.
- Implementation of the OBD-2 protocol (ISO 15765-4) as on-board diagnostics standard
- Windows® DLLs for the development of 32-bit and 64-bit applications
- Thread-safe API
- Physical communication via CAN using a CAN interface of the PCAN series
- Uses the PCAN-Basic programming interface to access the CAN hardware in the computer
- Uses the PCAN-ISO-TP programming interface (ISO 15765-2) for the transfer of data packages up to 4095 bytes via the CAN bus
- Uses the PCAN-UDS programming interface (ISO 14229-1) for the communication with control units
- Windows® 10, 8.1, 7 (32/64-bit)
- At least 2 GB RAM and 1.5 GHz CPU
- For the CAN bus connection: PC CAN interface from PEAK-System
- PCAN-Basic API
- PCAN-ISO-TP API
- PCAN-UDS API
|PCAN-OBD-2 API documentation|
|API Documentation in PDF Format|
|API for the vehicle diagnostics according to OBD-2 (ISO 15765-4)|
|API for the development of applications with CAN and CAN FD connections for Windows® 10, 8.1, 7 (32/64-Bit)|
|API for the transfer of data packages according to ISO-TP (ISO 15765-2)|
|API to communicate with control devices according to UDS (ISO 14229-1)|