The OBDonUDS standard (SAE J1979-2) describes communication between on-board vehicle diagnostic systems and corresponding test equipment. OBDonUDS was designed to succeed the OBD-2 standard, which has reached its limits given the growing complexity of on-board diagnostics.
Based on the existing UDS standard (ISO 14229-1), OBDonUDS creates structures and features to improve vehicle diagnostics and monitoring. More DTC fault codes are possible and more detailed data is captured for each error.
The free PCAN-OBDonUDS API provides the services of the OBDonUDS standard along with its functions. Diagnostic data is exchanged via CAN using the underlying PCAN-UDS API.
Features
- Implementation of the OBDonUDS standard (SAE J1979-2, ISO 14229-1, ISO 15765-4:2021) 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 CAN hardware
- Uses the PCAN-ISO-TP API (ISO 15765-2) to transfer packets of up to 4095 bytes of data
- 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 | OBDonUDS (SAE J1979-2) |
|---|---|
| Related standards | ['ISO 14229-1 (UDS)', 'ISO 15765-4:2021', 'ISO 15765-2 (ISO-TP)'] |
| Max packet size | 4095 octets |
| Dependencies | ['PCAN-Basic API', 'PCAN-ISO-TP API', 'PCAN-UDS API'] |
| Successor of | OBD-2 |
