Automotive standards - from CAN through UDS to ODX and OTX
Today, the auto industry applies standards in many areas that are not subject to competition.
These standards come into being in a whole host of ways ranging from casual collaborations through European-based associations (e.g. ASAM) to large standardization organizations (e.g. ISO, SAE).
Using standards results in a large number of advantages, notably considerably shorter development and engineering times as well as much lower costs per unit.
Softing Automotive Electronics is an active member of associations and organizations that define market standards.
Standardized programming interfaces are defined with two specific aims in mind: first of all consistent runtime responses of test and diagnostic systems regardless of use and secondly the consistent integration of VCIs (Vehicle Communication Interfaces) in test systems regardless of OEM and test system manufacturer.
Data descriptions are always standardized when a large number of applications use the same information and several people in several companies exchange information. Similarly, if the information is to be further processed in different ways, it makes sense to apply standards in a structured form. This is the case, for example, when data from specification systems is used for runtime systems and for documentation purposes.
Protocols have always been standardized whenever different test systems (e.g. in brand and independent repair shops) are to access vehicles or different ECUs have to be integrated into subsystems – requirements that are in fact always demanded nowadays!
In addition to access to the vehicle via the diagnostic connector, defined by the legislator, other bus systems have also established themselves as standards in the vehicle. These always focus on special requirements, ranging from inexpensive implementation through high bandwidth to possible use in security-relevant distributed closed-loop control.