In the field of on-board diagnostics, the OBD-2 standard governs the exchange of vehicle-specific parameters. Clients send requests to the control units connected to the vehicle, which respond with the requested data. Within OBD-2, the ISO-15765-4 standard designates the CAN bus as a transmission option.
The PCAN-OBD-2 API implements the diagnostic standard's functionality through 15 functions, divided into categories: Tester Allocation, Configuration, Information, Services, and Communication. According to ISO-15765-4, OBD-2 is based on the UDS protocol. Accordingly, PCAN-OBD-2 uses the PCAN-UDS API for diagnostic data exchange.
Features
- Implementation of the OBD-2 standard (ISO 15765-4) as an automotive diagnostic protocol
- Windows® DLL for developing applications for the Windows® 11 (x64/ARM64) and 10 (x86/x64) platforms
- API supporting multitasking
- Physical communication via the CAN bus through a CAN interface from the PCAN range
- Uses the PCAN-Basic API to access the connected CAN hardware
- Uses the PCAN-ISO-TP API (ISO 15765-2) to transfer packets of up to 4095 bytes of data over the CAN bus
- Uses the PCAN-UDS API (ISO 14229-1) for communication with control units
System requirements
- Windows® 11 (x64/ARM64), 10 (x64)
- For CAN bus connection: a PEAK-System PC CAN interface
- PCAN-Basic API
- PCAN-ISO-TP API
- PCAN-UDS API
Scope of delivery
- DLLs d'interface (x86/x64/ARM64)
- Examples and header files for all common programming languages
- Documentation in PDF format
| Protocol | OBD-2 (ISO 15765-4) |
|---|---|
| Transport | ISO-TP (ISO 15765-2) via PCAN-UDS (ISO 14229-1) |
| Max packet size | 4095 octets |
| Number of API functions | 15 |
| Function categories | ['Tester Allocation', 'Configuration', 'Information', 'Services', 'Communication'] |
| Dependencies | ['PCAN-Basic API', 'PCAN-ISO-TP API', 'PCAN-UDS API'] |
