What will vehicle diagnostics look like in the future?

Electronic vehicle architecture is constantly subject to technical innovations. To meet new requirements, such as autonomous driving, increasingly powerful control units are being installed in modern vehicles. These so-called HPCs (High Performance Computers) are taking on more and more responsibility. This change demands rapid innovation in vehicle diagnostics in order to maintain control over the growing complexity.

Challenge

HPCs in mordern E/E Architectures

Traditional Architecture

In traditional vehicle architectures, there was a high number of different control units that had individual "small" tasks. Today's vehicles are sometimes equipped with more than 100 control units, which are responsible, for example, for controlling the windows and doors or checking the tire pressure.

Translate dialects and central database

Modern E/E Architecture

In modern vehicles, which are equipped with increasingly comprehensive driver assistance systems, the ECUs are taking on more and more safety-relevant responsibilities. To cope with the increasingly complex software of the ECUs, more and more HPCs, which can combine the tasks of "small" ECUs, are finding their place in the vehicle.

HPCs offer new possibilities

More computing power than ever

In order to process big data streams from e.g. ADAS controllers or ECU clusters, high performance computers are vehicles new super brains.

Security & Safety critical

Being the main controller for ADAS, safety and security is crucial. Renowned solutions from other branches make their way into modern vehicles.

HPCs cluster several sub ECUs

High Performance computers combine several smaller ECUs into one big computer. Even some sub modules are often connected. HPCs are built on dynamic linux or android platforms to deal different static tratditional ECUs.

SOVD as the new standard diagnostic interface

The SOVD (Service Oriented Vehicle Diagnostics) standard is intended to simplify the world of diagnostics and prepare it for the challenges of the future. It is not a communication protocol in the classic sense, but rather an easy-to-understand interface (API) for all diagnostic accesses to the vehicle. It is specially tailored to the requirements of new HPC-based E/E architectures. However, the Classic Diagnostic Adapter (CDA) also makes it very easy to integrate the currently prevalent diagnostic protocols such as UDS.
With SOVD, already interpreted and thus human-readable data can be queried directly on the vehicle. The technological basis is formed by the common standards from web development.

Easy & Abstract Interface

SOVD simplifies the complexity of vehicle diagnostics and offers a standardized interface to request data from the vehicle.

Unifies the diagnostic world

SOVD integrates all the regular UDS based ECUs as well as the dynamic HPCs and combines it with state of the art web technologies.

Web-based technology

SOVD uses the web-based REST technology to introduce a self-describing and consistent API into vehicle. The external ODX descritpion does no longer need to be part of the tester.

vega.onboard as SOVD server

The full-stack of diagnostics in your vehicle

Our embedded ODX runtime allows generic remote diagnostics, software updates for your complete fleet.
With bidirectional communication and a complete diagnostic featureset, datacollection and remote updates aren‘t a task of the future anymore!

Integrates into your environment

The highly modular vega.onboard architecture allows easy and fast integration in a high variety of different embedded platforms and your complete OTA architectures as an SOVD Server.

vega.onboard as SOVD server

Interpreting the onboard message with the diagnostic core in the vehicle already, allows backendservices or off-baord testers to request readable data at the SOVD interface directly.