OBD II stack solutions and services
Business Model for OBD II Stack Solution
Leverage the benefits of one-time licensing fee model for this stable, pre-tested and industry recognized OBD II protocol stack.
Under this business model, we offer IP rights and the complete source code of the OBD II stack. This facilitates our customers to integrate the stack across different projects and/or product lines.
OBD II stack design and development services:
Stack Development for automotive ECU and tooling applications
Implementation of physical layers (CAN, J1850. K-Line and more) as per the project requirement
Implementation of OBD modes and PID (Parameter IDs’) implementation
OBD II stack Integration with automotive ECU application software
Fault code memory implementation
Vehicle Data collection solutions
Consulting workshops to understand the vehicle data collection requirements
Complete design and functional audit of the existing/legacy system (if any)
OBD II stack design and development services for data collection from on-road vehicles
Solution design for after-market automotive products
OBD II stack integration, design and development services for after-market automotive products/solutions
Support for access to vehicle parameters, data collection and processing
Development, testing and maintenance support for Telematics, ADAS, Remote Vehicle Diagnostics, Driver Behavior Analysis
OBD II stack implementation on physical layers
Support for implementation on all automotive physical layers – CAN, K-Line, ISO9141, PWM and VPW (J1850)
Meet Our Automotive Leaders
OBD2 software stack Factsheet:
Refer this handbook to know the details of our ready-to-deploy OBD2 stack for diagnostic and emissions control in passenger vehicles.
Download this OBD2 PDF to get following information:
- OBD2 license fee, engagement model, and overview
- Benefits of IP rights and OBD2 source code
- OBD2 Features, platform details, OS compatibility and memory requirements
- OBD2 software stack Development, testing, support and maintenance services
Refer to the OBD2 FAQ sections for more details.
Advantages of integrating the OBD II stack:
- OBD II stack supports all physical layers – CAN, K-Line, ISO9141, PWM and VPW (J1850)
- Pre-tested software stack: OBD II stack has been tested for integration in both automotive control units and tooling applications
- This OBD II stack is designed to support all OBD modes
- Platform independent – OBD II stack can be integrated with Non-OS, RTOS, and Linux environments
- This automotive software stack has been pre-tested for integrations with multiple embedded platforms – Freescale, Renesas, PIC, Fujitsu and more.
- This stack has been designed to ensure reduction in time to market and development costs for the customers
FAQs about OBD2 stack solution
Q. What is OBD II Stack?
A. OBD II (On-Board Diagnostics) stack, designed and developed by our expert automotive developers, is a set of embedded software services implemented in compliance with ISO 15031 standards for automotive.
This pre-tested and pre-packaged stack can be readily integrated with your diagnostic application for emissions control and monitoring of major engine components.
This stack is best suited for passenger cars and light commercial vehicles. We also have expertise and experience to support OBD/OBD II implementation over various physical network layers.
Q. What is included in the OBD2 stack as a software package?
Ans. When you purchase OBD2 software stack from us, following pre-tested OBD modules and drivers are included in a standard package:
- ISO 15031 standard complaint OBD services
- ISO 15765 standard complaint OBD over CAN module (CAN TP Layer)
- VPW/PWM drivers to support OBD over J1850
- ISO 14230 complaint UART/K-Line drivers to support OBD over K-Line
- ISO 9141-2 complaint UART drivers to support OBD over ISO9141-2
Q. Do you also provide OBD2 stack integration services in addition to software stack package?
Ans. In addition to our software package, we also offer integration support which includes integration of the stack to your hardware.
Our automotive team will provide end-to-end support for customization and integration of the OBD II stack as per the business need of your target application.
Q. What are the testing services that you provide ?
Ans. Verification and validation is being done post integration of the stack with your target application.
Q. Is your OBD2 software solution a master or a slave?
Ans. The OBD II stack solution, designed by our embedded software developers, can be implemented either as master or slave as per your project/application requirement.
We can either integrate it into an automotive control unit as a master or in an external tool like a scanner or telematics unit as a slave.
Q. Does your stack have any dependency on the underlying hardware platform?
Ans. No. Our OBD2 solution is hardware platform independent.
Our software development team has designed OBD services (ISO 15031) and OBD Over CAN module (ISO15765) as platform agnostic software
Q. Is the source code of your OBD 2 stack complaint to a proven standard?
Ans. Yes. Embedded C based software code has been developed in complaince with MISRA-C standard for automotive applications.
We are a CMMI Level 3 organization. We follow industry complaint project management and software development best practice.
The OBD2 source code has also been tested using the third party tools.
Q. Have you partnered with customers to integrate OBD2 solution for end-of-line testing and/or production programs?
Ans. With more than 10 years of business experience and automotive domain expertise, we have partnered with Global OEMs’ and Automotive Suppliers for multiple projects of OBD (and other automotive stacks) integration projects
Our team has collaborated for end-of-line testing and OBD2 implementations across multiple OEM platforms and tooling applications.
Q. Please share details about your support and maintenance services
Ans. We provide post-production support for a specific period of time.
The SLA, warranty period and number of months of support is included in the contract based on the discussions with customer’s team and project requirements.
Q. Please share details regarding business model and license policy
Ans. We work on the business model of one-time licensing that provides the customer with source code and IP rights.
With IP rights, customers can implement/re-use the OBD2 stack for multiple projects or platforms.
Q. Can the licensing agreement be customized?
Ans. Yes, a customized contract can be drafted based on your business requirements and budget allocated to the project.
OBD II stack design implementation: hardware and software expertise
|OBD over CAN
||CAN support in microcontroller
||ISO15765 (CAN TP layer)
|OBD over J1850 (VPW/PWM)
||PWM support in microcontroller
VPW/PWM driver based on J1850 standard
|OBD over K-Line
||UART support in microcontroller
K-Line driver (based on ISO14230)
|OBD over ISO9141-2
||UART support in microcontroller
Why partner with us for OBD/OBD II stack integration project:
- Leverage our automotive domain expertise and project experience in OBD II stack integration to reduce time-to-market and application development costs
- We are a CMMi Level 3 and ISO 9001:2008 & ISO 27001:2013 certified organization
- Robust project management processes based on EmbiQ – an engagement model. This model is built on three critical pillars - People, Process and Technology.
OBD II stack business impact: customer success story
Business Challenge: Design, development and testing of OBD II stack for Engine Control Unit
Our team of automotive embedded developers designed following OBD modules after the initial requirement gathering workshop with the automotive customer:
- Diagnostic System Manager (DSM) with Fault Code Memory: DSM modules collects test results reported by the monitoring functions. Current fault states and derived error memory entries are stored in standard form and is readily accessible to the application software and Tester communication.
- OBD Diagnostics Services: This module provides external access to fault code memory and other emission relevant data. A generic OBD scan tool can be connected to the ECU to read emission related data.
For more details about the OBD implementation and tools and technology deployed for this project, please refer to the entire case-study here.