Search Results

Model based architecture methods for designing and optimizing electrical and electronic systems of vehicles are becoming more and more popular. However, there is still no standard on the models which are vital for design and description of architectures. Most methods and tools begin with a functional abstraction. The functional elements are mapped to electronic control units [ECU] which are connected through bus systems and supplied with electrical power via clamps. An open, unanswered question is the determination of specific control unit numbers and location in a vehicle platform. To do so, a new model layer is proposed: the “technological model” with so called “technological building blocks”. It sits in-between the “functional model” and the “communication model” and describes the necessary constraints for designing the optimum number and position for electronic control units.

In order to master the increasing complexity of electrical/electronic (E/E) systems in vehicles, E/E architecture design has become an established discipline. The task of the E/E architecture design is to come up with solutions to challenging and often contradictory requirements such as reduced cost and increased flexibility / scalability. One way to optimize the E/E architecture in terms of cost (electronics & wiring harness) is to integrate functions. This can be done by either combining functions from multiple ECUs into a single ECU or by introducing Domain Control Units. Domain Control Units provide the main software functionality for a vehicle domain, while relegating the basic functions of actuator control to connected intelligent actuators. Depending on the different market segments (low price, volume and premium) and the different vehicle domains, the actual usage of Domain Control Units can be quite different and sometimes questionable.