HPC – The Transformation of the Automotive vehicle electrical system
Here’s how a connector overcomes this challenge
Increased electrical complexity, driven by the shift toward e-mobility, autonomous driving, and infotainment systems with 4K HD resolution, requires new in-vehicle E/E architectures in automotive engineering. The traditional decentralized vehicle electrical system-Architektur is reaching its limits due to its complexity and the required high-speed capabilities. ept offers the right board-to-board connector for these challenges.
Definition of “vehicle electrical system”: Decentralized, domain- and zone-based architecture
The classic decentralized architecture in automobiles consists of up to 100 ECUs (ECU), with each ECU assigned a specific function: engine control, airbag, ABS/ESP, seat adjustment, climate control, and much more. Each ECU operates independently and communicates with other ECUs via gateways.
Over the past decades, the decentralized architecture has undergone historical growth, with each new functionality requiring the addition of another ECU. Today, however, it is reaching its limits: Increasing functionality significantly raises the installation and wiring costs within the vehicle.
In domain-based architecture, the ECUs are grouped into different functional areas. Each domain is responsible for a specific area of the vehicle, such as powertrain, infotainment, or safety. The overarching control of a domain is handled by a standalone high-performance computer (HPC). This HPC coordinates the ECUs within its domain. For the safety functional area, for example, these would include ECUs for driver assistance systems, ABS/ESP, and steering systems.
Compared to decentralized architecture, the smaller number of installed ECUs reduces wiring and installation effort. The domain architecture can thus also effectively contribute to cost and weight reduction compared to decentralized architecture. Additionally, new functions can be integrated later with minimal effort.
In zone architecture (zonal architecture), the structure is not based on domains but on local zones. For example, multiple functionalities are bundled within a single zone in a vehicle. Accordingly, functions such as the powertrain and infotainment can certainly be combined and processed within a single zone controller. The various zone controller are managed by a central HPC. The advantage is clear: a reduction in the number of ECUs and their wiring by up to 50 percent.
Over the past decades, the decentralized architecture has undergone historical growth, with each new functionality requiring the addition of another ECU. Today, however, it is reaching its limits: Increasing functionality significantly raises the installation and wiring costs within the vehicle.
In domain-based architecture, the ECUs are grouped into different functional areas. Each domain is responsible for a specific area of the vehicle, such as powertrain, infotainment, or safety. The overarching control of a domain is handled by a standalone high-performance computer (HPC). This HPC coordinates the ECUs within its domain. For the safety functional area, for example, these would include ECUs for driver assistance systems, ABS/ESP, and steering systems.
Compared to decentralized architecture, the smaller number of installed ECUs reduces wiring and installation effort. The domain architecture can thus also effectively contribute to cost and weight reduction compared to decentralized architecture. Additionally, new functions can be integrated later with minimal effort.
In zone architecture (zonal architecture), the structure is not based on domains but on local zones. For example, multiple functionalities are bundled within a single zone in a vehicle. Accordingly, functions such as the powertrain and infotainment can certainly be combined and processed within a single zone controller. The various zone controller are managed by a central HPC. The advantage is clear: a reduction in the number of ECUs and their wiring by up to 50 percent.
Requirements for the HPC and its connector
The resulting demands placed on an HPC are significant: Not least, the processing of imaging data in the infotainment sector or in camera systems for autonomous driving requires secure, high-speed data transmission with low latency. At the same time, signal transmission must not fail under any circumstances—its reliability must be guaranteed at all times.
High performance, fast, and above all, reliable data transmission—sometimes under adverse environmental conditions—are therefore also requirements placed on the installed connector.
High performance, fast, and above all, reliable data transmission—sometimes under adverse environmental conditions—are therefore also requirements placed on the installed connector.
What should you consider when choosing the right connector for HPC?
Ensure the "readability" of a signal, for example, using an eye diagram. This indicates whether a transmitted signal can be unambiguously assigned to the digital states 1 or 0 at the receiver.
Pay special attention to the signal protection of your high-speed signals. A connector can act as both a source of interference and a sink. For this reason, signal protection using a shield plate is recommended to shield sensitive signals from external influences.
For example, use the coupling inductance (mutual inductance) to select the appropriate connector (connector) based on its electromagnetic compatibility (EMC), thereby avoiding costly and time-consuming trial-and-error testing in the EMC-Labor.
Choose uninterrupted signal transmission even under extreme environmental conditions such as vibrations and shocks. In this context, contact design, contact systems, and connection technology (termination technology) play a decisive role.
Free white paper with a detailed guide to selecting the right connector for HPC
How does the “eye diagram” work in detail, and how is it used in practice?
What do you need to consider when shielding a connector? What exactly is mutual inductance, and how does it help in selecting the right connector for HPC?
Which contact design, contact system, and connection technology ensures reliable data transmission under the most adverse environmental conditions, and what factors must be considered?
You’ll find the answers to these questions—along with detailed explanations and practical examples—in our free white paper!
Download the white paper »
What do you need to consider when shielding a connector? What exactly is mutual inductance, and how does it help in selecting the right connector for HPC?
Which contact design, contact system, and connection technology ensures reliable data transmission under the most adverse environmental conditions, and what factors must be considered?
You’ll find the answers to these questions—along with detailed explanations and practical examples—in our free white paper!
Download the white paper »
Conclusion
Current developments in the automotive industry are constantly placing new demands on the connectors (connector) used in vehicles. At first glance, the role of these connectors seems to be fading into the background due to the reduced number of ECUs. Upon closer inspection, however, it becomes clear that their role is actually gaining importance precisely because of this shift toward central data processing via HPC: reliability in signal transmission has never been more important than it is today.
Are you looking for the right connector?
product list
Any questions?
Then please contact us!
Submit an inquiry via the form
+1 (806) 304-0402
sales@eptusa.com
Then please contact us!
Submit an inquiry via the form
+1 (806) 304-0402
sales@eptusa.com