Putting Remote ECU Diagnostics in the Fast Lane
Modern vehicles have an increasingly higher vulnerability due to a gamut of electronic and software components. Thus, remote diagnostics and ECU flashing assume far more importance. DoIP makes ECU diagnostics faster and more reliable with Ethernet as the communication medium.
Diagnostics over Internet Protocol (DoIP) is an extremely important piece of protocol software with respect to modern automobiles.
It opens up an entirely new ECU diagnostics paradigm that works on Ethernet, a faster and more reliable communication channel.
On the OSI reference model, DoIP is specified for Transport protocol and network layer services (ISO 13400-2) and data link layer (ISO 13400-3).
Embitel offers a ready-to-deploy DoIP protocol software package defined by ISO 13400 standard. With our DoIP stack, you can implement remote vehicle diagnostics capabilities in your production programs in no time.
We can configure the required diagnostics services and provide other customizations as per your specific requirements.
Know more about our DoIP protocol software business model, features, use-cases, and technical specifications.
Implement remote diagnostics with these features of our DoIP protocol software:
- Our DoIP protocol stack has a modular architecture making it simpler to integrate to your existing automotive system and hardware.
- DoIP protocol software can be integrated with both server side (ECU) as well as client side (external diagnostics tool).
- Unit, Integration and Functional testing of DoIP with relevant tools are performed and test reports are shared with the customer.
- DoIP software code comply to MISRA C standards.
- We offer our industry recognized DoIP protocol software under a one-time licensing fee model.
- Terms & conditions regarding IP rights and source code ownership are completely transparent and fully aligned with the customer’s requirements and vision.
- Our DoIP stack finds applications in implementation of diagnostics system for all kinds of vehicle ECU and external diagnostic device.
- Enablement of remote vehicle diagnostics capabilities and remote ECU flashing are some of the most common use-cases.
A Closer Look at Our DoIP Stack Architecture
- DoIP Transport Layer (ISO 13400-2) is equipped with features to establish and maintain connection between external tester device and DoIP gateway inside the vehicle.
- UDS application layer (ISO 14229-5) is the application profile that implements UDS on IP.
Embitel’s Service Offerings for DoIP Software and its Integration
DoIP Based Vehicle Diagnostic Implementation (ISO 13400-2 and ISO 14229-5)
- DoIP implementation for ECU (server side) and Diagnostic tester (Client side)
- DoIP gateway development
- Support for configuration of DoIP services
Design and Development of DoIP Based Tooling Solution
- DoIP based tooling applications for vehicle diagnostics at the service centre
- Remote Diagnostics with DoIP protocol
- End of line ECU reprogramming
- Fault Code Memory (FCM) Configuration
DoIP Protocol Software Maintenance and Support Services
Testing Services:
- Unit testing and Integration Testing
- Functional Testing
Documentation Services:
- Creation of High-Level Design Document (HLDD) and Low Level Design Document (LLDD)
- Design of Module Test Plan, Integration Test Plan, and Functional Test Plan
- MISRA Report Creation
Ethernet Device Driver Development and Integration Support
- Integration of DoIP Protocol Stack with Ethernet MAC
- Driver development for MAC IC (Transceiver) to facilitate LAN and Microcontroller communication
- Integration of MAC IC
- Implement Seed and Key algorithm for security access
- Customized bootloader sequence as per customer requirement
Embitel’s Advantage
Industry-wide Recognized
- We have integrated DoIP stack for several production programs across the globe.
- The extensive experience gives us an edge in the implementation of vehicle diagnostics through DoIP and UDS.
Configuration & Integration Support
- Our DoIP stack is designed to be fully configurable as per diagnostics specifications.
- We provide support for configuration of desired diagnostics services using automation tools.
Tooling solution development support
- DoIP software can be integrated to both server and client side.
- We provide support for development of tooling solutions you might require for your project.
Support & Maintenance
- Our DoIP stack integration service comes with a well-defined support and maintenance process.
- The post- integration support begins as soon as we integrate the DoIP stack with your projects.
DoIP Protocol Software Integration and Tool Development Services
Our DoIP protocol solution as a standard software package supports following services:
| SID | DoIP Services | Description |
|---|---|---|
| 0x10 | Diagnostic Session Control | Enable several diagnostics sessions within ECU |
| 0x11 | ECU Reset | Resetting the ECU back to default session |
| 0x27 | Security Access | Limit access to data and services to prevent unauthorized access |
| 0x3E | Tester Present | Alert the ECU(s) that client is still connected so that diagnostic sessions remain active |
| 0x22 | Read Data By Identifier | Request data from ECU(s) |
| 0x2E | Write Data By Identifier | Write data onto ECU(s) |
| 0x14 | Clear Diagnostic Information | Clear diagnostic trouble codes (DTC) stored in the ECU |
| 0x19 | Read DTC Information | Read DTC from the ECU |
| 0x2F | Input Output Control By Identifier | Control the input/output signals through the diagnostic interface |
| 0x31 | Routine Control | Control all the routine services (erasing memory, testing routines etc.) |
| 0x34 | Request Download | Request ECU to initiate download session based on request from the tester |
| 0x36 | Transfer Data | Manage actual transmission ( upload and download) of data |
| 0x37 | Request Transfer Exit | Terminate and exit data transfer |
| 0x28 | Communication Control | Manage the exchange of messages in the ECUs |
| 0x85 | Control DTC Setting | Enable/disable updating of DTC settings in ECU |
| 0x87 | Link Control | Control the ECU- client (tester) communication to gain bus bandwidth for diagnostic purposes. |
| 0x23 | Read Memory By Address | Read memory data from the memory address provided |
| 0x24 | Read Scaling Data By Identifier | Read scaling data stored in the server using data identifier. |
| 0x3D | Write Memory By Address | Write information into the server memory location |
| 0x35 | Request Upload | Request ECU to upload data |
Ans. DoIP is a vehicle diagnostics and communication standard defined in ISO 13400-2 document.
DoIP stands for Diagnostics over Internet Protocol. As the name suggests, this software standard enables remote diagnostics of the vehicle over an internet protocol.
DoIP standard leverages Ethernet as the physical layer for the communication. Hence, a DoIP software solution can support the data transfer rate of up to 100 Mbps.
Due to its high speed, DoIP protocol stack is best suited for applications like ADAS, since these applications work with real-time data and require faster response time.
Ans. Our Diagnostics over IP software stack can be customized to include DoIP services defined as per the ISO 13400-2 standard.
The following SIDs/services are included in our DoIP protocol stack as a standard software package. Additional DoIP diagnostics services can be included as per your project requirements.
Ans. Depending on your business requirements, we can provide end-to-end support for the integration of the DoIP stack with your hardware platform and software application.
Following is the snapshot of some of our service offerings that our team can support you with:
- Integration of the DoIP stack with your hardware platform
- Integration of DoIP solution with target application
- Development of bootloader software based on DoIP standard
- Development of device driver modules for MAC
Ans. The services that support the bootloader functionality comes included in the software stack. Additionally, we provide the integration support for ECU reprogramming through DoIP.
This includes the following software development services:
- Segregating the memory as boot and application area
- Implementing boot loader logic in both boot and application
- CRC checks, Flash driver development and more
Ans. No, our DoIP software solution is mostly hardware independent. However, as the DoIP works over Ethernet, the hardware must have an Ethernet port.
Ans. The DoIP software stack is complaint with ISO 13400-2 and ISO 14229-5 standards. The software source code is developed using Embedded C in compliance with MISRA-C standard.
The quality control best practices as mandated for CMMI level 3 companies are strictly followed across our organization for all software and hardware development projects. We also follow the functional safety guidelines as mandated in ISO 26262 Standard.
A separate QA team works in close association with the embedded software and hardware development teams to ensure the compliance.
Ans. Yes, in the last 11 years, we have partnered with many global automotive OEMs and suppliers for deployment and configuration of DoIP protocol solution.
The team of automotive software developers and testers has been providing key solutions for integration and support for DoIP protocol solution across multiple platforms.
Ans. The DoIP stack integration service comes with a well-defined support and maintenance process. The post production support begins as soon as we integrate the DoIP stack with your projects.
Ans. Our engagement model is designed as a one-time licensing offering. This lets our customers to get access to the DoIP software stack IP rights as well as the source code.
The IP rights help the customers reuse the software code across multiple projects and product lines. We can modify the business model depending on the requirements of the customers
Ans. Yes, we provide conformance testing services after the software stack is integrated to the automotive ECU. Our development and testing team offers complete support and en-of-the-line testing in the production environment.
Our teams have considerable experience of integration and conformance testing in compliance with ISO 13400-2 standard.
Ans. The DoIP protocol stack can be implemented both as a server (ECU side) and client (Tool Side). It implies that we can either integrate it into an automotive control unit or in an external tool like a scanner or telematics unit.
Blogs Related to DoIP Protocol: Learn More about UDS on IP (Diagnostics over IP) v/s UDS on CAN
Knowledge Bytes
What is Diagnostics over Internet Protocol (DoIP)?
- The era of Connected Cars, Infotainment and ADAS (Advanced Driver Assistance System) systems can be associated with explosion of ‘Big Data’ in the Automotive Industry.
- In-vehicle networking and communication between vehicles and road infrastructure, call for huge amount of data to be transferred at a very fast speed.
- In this new ecosystem, there is a strong business case for high-speed vehicle diagnostics and ECU reprogramming solutions.
- DoIP is the vehicle diagnostics solution that perfectly fits the bill! DoIP comes into picture as a supplementary to the existing network (mostly CAN) in a vehicle. However, it outsmarts CAN network by the virtue of its high-speed data rate (100 mbps)
- Simply put, DoIP is the set of diagnostic services made available on Ethernet data-frames. It is mostly used in combination of UDS (ISO 14229) based vehicle diagnostics protocol.
- Using DoIP, a diagnostic tester tool can communicate with a vehicle ECU over internet protocol. This ensures higher bandwidth as compared to a default vehicle network.
What is the role of DoIP software stack in the new-age vehicle diagnostics and communication?
-
- Diagnostics over IP is a high-speed solution and supports remote vehicle inspection and repair. Due to several advantages offered by DoIP protocol stack, it is popularly deployed for the following automotive applications:
- ECU Re-programming
- Remote vehicle diagnostics
- Measurement reading
- Online data streaming to and from the vehicle
- Diagnostics over IP is a high-speed solution and supports remote vehicle inspection and repair. Due to several advantages offered by DoIP protocol stack, it is popularly deployed for the following automotive applications:
- Using DoIP protocol helps in saving time in ECU reprogramming as it is capable of handling huge data volumes. As it uses standardized communication protocol like UDS (ISO 14229), DoIP (ISO 13400) is quite flexible. Also its future-proof technologies enables DoIP to be deployed in various automotive use cases.
