PREEvision Features and Functions Described in Expert Essays and Technical Articles
PREEvision product managers introduce workflows and describe specific use cases, processes and team support features in detail. Download for free!
Communication Paradigms in the Vehicle of the Future: Service-Oriented, Data-Centric or RESTful?
Middleware protocols in the automobile
These days, users want to adapt their vehicle to their personal preferences, expand it with functions and provide it with regular updates, just as they do with their mobile devices. One building block for technically implementing these desired properties is Internet Protocol (‘IP’) based communication; IP opens the way for new design patterns, because it enables the use of higher-layer protocols. These “middleware” protocols should be examined in greater detail. What are their defining characteristics? And which ones can be considered for use in the automotive environment?
Model-Based Development of Vehicle Functions for Modern E/E Architectures
How can the extended design space be mastered and converted to added customer value?
Today’s Electric/Electronic (E/E) architectures differ from previous architectures in many ways. Inside the vehicle, available tools – in addition to conventional ECUs with limited resources – include high-performance computers with very significant computing power. At the same time, the E/E architecture extends beyond vehicle limits all the way to the IT backend and to mobile end devices. Along with the practice-proven AUTOSAR Classic software platform, AUTOSAR Adaptive and other software platforms will also be used in the future. Unlike in the past, system and functional designers have access to a design space that has been expanded to an extreme level. The challenge is to exploit new degrees of freedom to develop vehicle functions for more customer value. At the same time, growing complexity must also be overcome.
Vehicle Diagnostics as Part of a Contemporary E/E Development Process
How to efficiently acquire, specify and implement diagnostic data in software
In typical automotive development processes, not only are diagnostic descriptions and their software implementations handled by different people, in different roles, but they are also supported by different authoring tools. The consistency between the two sets of data must be verified manually, and this process can be both complicated and susceptible to errors. An integrated, model-driven approach to development makes it possible to describe diagnostics within a vehicle E/E system, including the relationships with the implementation software.
Bridging the gap between AUTOSAR Classic and Adaptive systems
AUTOSAR Adaptive can be introduced successfully if the hardware and software that is based on AUTOSAR Adaptive works well with the existing AUTOSAR Classic system components. Full implementation throughout the system – including when implementation takes place on different platforms – will be one of the next major challenges in E/E development. Service-oriented architectures can bridge the gap between two worlds.
Product Lines and Variant Management in E/E Development
Modeling a product line with PREEvision illustrated by an example from the field of powertrain
Practically all electrical/electronic (E/E) developments in the automotive industry now use a product line approach. The development object is not just a certain vehicle model but a whole vehicle family with many different drive, body and equipment variants; This is why one often hears the terms E/E toolbox or E/E platform being used to describe the development object, or product line. Starting with this type of E/E product line, it is necessary to support the different vehicle models as variants and allocate systems and components to them. Efficient variant management is therefore vitally important for development.
Developing diagnostic communications for E/E systems
The electronically controlled systems of modern vehicles are networked with one another to a high degree, and they execute many complex functions. The communications protocol DoIP (Diagnostics over Internet Protocol) – which is supported by AUTOSAR – enables flexible and powerful diagnostics of systems over Ethernet, WLAN and mobile data connections: both offboard in the workshop as well as onboard and via remote access during the drive. The same applies to flashing of ECUs in manufacturing, in the workshop or over-the-air. For this to work properly, it is necessary to define the communication paths between the diagnostic tester and the specific diagnostic object (device under test or DUT) of the vehicle network precisely. It is essential to use the right tools to find optimal paths in a modern vehicle’s complex Electrical/Electronic (E/E) network.
Model-based E/E development conforming to ISO 26262
Electrification, automation and vehicle networking demand maximum requirements for the functionalsafety of vehicles. The electronic systems for new vehicle functions are networked to a high degree, which makes a safety analysis on the level of the complete system necessary. In addition, technical trends such as automotive Ethernet and AUTOSAR Adaptive need to be considered. Model-based engineering environments support engineers in overcoming these challenges.
The Next Stage in the Evolution of Requirements Engineering
Integrated requirements management for E/E systems
Electric-electronic architectures (E/E) in vehicles – What’s the first thing that comes to mind? Complex systems which have been becoming increasingly more extensive for years? Where an ever-greater number of components build upon one another and are dependent on one another? Where the individual components are subject to continual adjustment and expansion during development? And that it’s becoming increasingly difficult to maintain an overview for recognizing correlations and dependencies? If so, you should take a closer look at the advantages of an integrated development tool and requirement management.
Towards Data Centers on Wheels with Model-Based Methods
Service-oriented architectures and Ethernet in vehicles
Service-oriented architectures (‘SOAs’) have been used for years in the IT industry to describe and structure distributed systems. However, service-oriented design is also becoming extremely significant in the automobile industry: how else can customers’ increasingly urgent demand to adapt the scope of functions of the automobile, similar to the possibilities of today’s smartphones, be met reliably? It is also necessary to handle additional requirements from model maintenance and to introduce technology such as autonomous driving and vehicle-to-X communication.
Integrated Development of a Complete E/E Architecture
Reaching goals reliably with a consistent model-based approach
Specification and modeling tools for subtasks in the development of electric/electronic systems are widely used today. This is not due in small part to the fact that their use is what enables today's complex development processes to be controlled. Abstraction allows for transparency in domain concepts and systematically avoids repeated maintenance, which increases development speed significantly. Integrated, model-based system development for the entire E/E architecture still seems like a far-off dream, though.
The development of modern electric/electronic (E/E) architectures is a challenge today more than ever. Numerous development criteria must be taken into account, and classic vehicle domains need to be linked to new functions in the areas of driver assistance and autonomous driving. Completely new functions that are no longer limited to just the vehicle, but are also provided as services in the “IT backend” outside the vehicle, are emerging here. The introduction of serviceoriented architectures and powerful domain computers, Ethernet to on-board communication, connectivity gateways and, last but not least, increasing safety and security requirements represent profound and radical changes for every development organization. To master these complex development tasks successfully as a team, a development platform and E/E database, which can be implemented in different ways, are required.
AUTHORS: DR. THOMAS BECK｜DR.-ING. CLEMENS REICHMANN｜JÖRG SCHÄUFFELE ORIGINALLY PUBLISHED IN ATZ ELEKTRONIK 6-2016
PREEvision as model-based tool for the next generation of E/E systems
Design and optimization of modern electric/electronic architectures is more than ever a task for specialists. They must take into account numerous design criteria and connect classic vehicle domains with new requirements and trends: the introduction of domain computers, Ethernet for onboard communication, connectivity gateways and, last but not least, the increasing requirements for functional safety and information security. To master these complex tasks, model-based development tools such as PREEvision with versatile engineering functions are needed.
Why consistent implementation of the AUTOSAR system view is worth it
Started thirteen years ago, the AUTOSAR standards enables efficient electric/electronic development today. Besides continuous additions in recent years, the systems thinking remains a mainstay of the standard. Rather than focusing on the individual ECU or on a communication bus, AUTOSAR always looks at the whole system. This system view is playing a more and more important role in the digitization of the automotive industry and, together with the “Adaptive Platform”, is paving the way for the next generation of vehicle electronic systems.
Controlling Complexity in the Vehicle Wiring System
Model-based wiring harness development
Handwritten corrections on printouts, giant spreadsheets, and countless tool changeovers: these and similar approaches are used in an effort to keep a handle on the development of a vehicle wiring system. More efficient approaches are needed to control the complexity of modern electrical distribution systems in the long run. The model-based development methods already in successful use in many industrial sectors provide the needed tool for this.