Documents
Documents
| Features | Details |
|---|---|
| OBD2 |
|
| Supported Platforms | A comprehensive interface to configure, monitor, and manage all 8 NXP i.MX 9 Application Processor NXP i.MX 8 Application Processor NXP i.MX 6 Application Processor Other ARM-based platforms |
| OBD2 Stack Solution Package | C-based stack designed for compatibility with Linux OS. APIs for seamless communication with vehicle ECUs for diagnostics. Supports communication through CAN (ISO 11898-1 & ISO 15765 4). Fully customizable and scalable for various automotive use cases. |
| Value Proposition | Supports on various ARM processors Robust API’s which are easy to integrate Porting support for newer version of the software MISRA C compliant End to End solution offering |


Diagnostics Service With the increasing complexity of modern vehicles, efficient diagnostics are essential for identifying and resolving issues. On-Board Diagnostics (OBD2) is the standardized automotive protocol that enables real-time vehicle diagnostics and monitoring. Defined under ISO 15031-5, OBD2 is widely adopted by automobile manufacturers to provide a universal system for diagnosing vehicles across different brands.
The OBD2 system provides access to both emission-related and other vehicle data. It helps meet environmental rules and track performance. By reading Diagnostic Trouble Codes (DTCs), users can quickly find problems, check vehicle health, and perform maintenance to prevent bigger issues.
OBD2 Data Communication
The OBD2 protocol follows a structured communication model where the vehicle acts as a Server, and the diagnostic device (scanner, telematics unit, or mobile app) acts as a Client. The protocol enables communication over CAN (ISO 15765-4) and other transport layers, allowing seamless data exchange for vehicle diagnostics.
OBD2 stack provides a robust and efficient way to request and retrieve vehicle diagnostic data, including engine parameters, sensor values, and fault codes. The communication process allows clients to:
- Read real-time vehicle data (e.g., engine RPM, speed, fuel consumption)
- Retrieve Diagnostic Trouble Codes (DTCs) for fault detection
- Monitor vehicle health using live sensor readings
- Request vehicle status and control specific components
- Access memory and stored vehicle data



