The EE architecture has developed from domain centralization to domain integration. Different OEMs have begun to try cross-domain integration among the five classic domains (cabin domain, intelligent driving domain, power domain, chassis domain, and body domain) based on their own understanding. Cabin Driving one body came into being.
From a hardware perspective, "cabin and driver integration" can improve the reuse rate of sensors , chips and other hardware and reduce costs; from a software perspective, the "cabin and driver integration" integrated system drives the iteration of the overall software architecture to obtain more functions Or a better functional experience.
Although "cabin-driving integration" has many benefits, its implementation also faces various difficulties.
On the afternoon of September 24, Jiuzhang Zhijia and the China Automobile Industry Training Base jointly held a small offline salon event with the theme of "Integrated cabin and driving, is it a real demand or a fake demand?", inviting guests from OEMs, autonomous driving solution providers, Nearly 20 smart driving related personnel including chip suppliers (positions include smart driving strategic planning manager, electronic and electrical architecture manager, sales manager, product manager, project manager, software and hardware engineer , etc.) participated.
Is the integrated cabin and driver a real demand or a false demand?
The theme of this event centered on "Demands and Changing Trends of the Integrated Cabin-Driving Market and Technology", with exchanges and discussions as the main form, discussing "What are the core advantages of the integrated cabin-driving solution" and "In the long run, whether the integrated cabin-driving solution Can it really achieve the effect of cost reduction?", "What is the evolution path of the cabin-berthing integrated solution, the cabin-parking integrated solution and the cabin-driving integrated solution", "What are the landing time points, challenges and difficulties of cabin-driving integration", "Cabin-driving integrated solution" What impact will the integrated solution have on the cooperation model between OEMs and suppliers?" and other related issues.
Summary of some opinions of the salon
In this discussion, the guests raised:
The electronic and electrical architecture design of most OEMs involves the planning of cabin-driving integration, but it has not been implemented into specific projects. The core reason is that the cost reduction and functional experience improvement of cabin-driving integration are uncertain.
The benefits and difficulties of "cabin-driving integration", as well as issues such as landing form and time points, can all be attributed to cost considerations. If the cost drops enough, it may even be possible to abandon the integration of cabin and driver and directly switch to a more integrated central computing architecture.
"Cabin-driving integration" can significantly reduce hardware costs and supply chain management costs, but it still needs to consider the increase in software development costs, vehicle-level verification costs, and organizational structure integration costs.
in:
Explicit cost reduction:
(1) Regardless of the one box/one board/one chip solution, compared with the current two box and two chips solution in the smart driving domain and cockpit domain, it reduces the investment in domain control and chips in terms of hardware, and reduces the number of wire harnesses between domains. Hardware costs have declined;
(2) From managing multiple domain controllers and chip suppliers to centrally managing a small number of suppliers, the management cost of the supply chain is reduced;
Hidden costs rise:
(1) The migration of the upper-layer ecology and the complexity and difficulty of software adaptation will increase significantly with the increase in the integration of the intelligent driving domain and the cockpit domain, and the development cost will increase;
(2) The smart driving domain and the cockpit domain have different functional safety requirements, leading to an increase in the cost of meeting vehicle regulatory requirements;
(3) Cabin-driving integration needs to gradually open up the department walls between the smart driving domain and the cockpit domain, and promote the integration of organizational structures to improve efficiency, but the time cost is high;
(4) It is difficult to achieve platformization, standardization, and scale in the short term. It cannot cover all high-end, high-end, and low-end models, and it is difficult to amortize costs.
Therefore, combining the demands of reducing costs and improving functional experience, the guests believed that the integration of travel and parking is the best solution in the short term, and it is expected to be implemented on a large scale in 2024~2025. The integration of cabin and driving will reduce the cost in the comprehensive dimension and bring more to users. , On the premise of better user experience, it can be first implemented on high-end models, and then gradually expand to mid- and low-end models, which is expected to be as early as 2026.
At the same time, a few guests also proposed that based on the considerations of product definition, system consideration, cost reduction, mass production delivery, and organizational structure integration, we should abandon one box and one board and focus on the one chip solution to integrate cabin and driving.
If its R&D costs and other hidden costs are equal to those of a more integrated central computing architecture, it will consider directly abandoning the integration of cabin and driving and directly switching to a more integrated central computing architecture.
Jiuzhang Zhijia has organized many high-quality small-scale offline closed-door meetings (salon activities), such as "Who will be the winner in the battle for large computing power chips ?", "Analysis of basic software trends for autonomous driving", " The implementation of the BEV perception model, how different players can deeply participate in and promote it, etc. We carefully selected and invited senior executives and technical backbones from OEMs and intelligent driving technology companies to participate, which was highly recognized by the participating guests.
Previous article:ADAS research of local car companies: The NOA popularization storm has begun. How will the OEMs respond?
Next article:Pure visual ability PK Tesla FSD, Baidu’s era of “asking the world” has finally arrived
- Popular Resources
- Popular amplifiers
- A new chapter in Great Wall Motors R&D: solid-state battery technology leads the future
- Naxin Micro provides full-scenario GaN driver IC solutions
- Interpreting Huawei’s new solid-state battery patent, will it challenge CATL in 2030?
- Are pure electric/plug-in hybrid vehicles going crazy? A Chinese company has launched the world's first -40℃ dischargeable hybrid battery that is not afraid of cold
- How much do you know about intelligent driving domain control: low-end and mid-end models are accelerating their introduction, with integrated driving and parking solutions accounting for the majority
- Foresight Launches Six Advanced Stereo Sensor Suite to Revolutionize Industrial and Automotive 3D Perception
- OPTIMA launches new ORANGETOP QH6 lithium battery to adapt to extreme temperature conditions
- Allegro MicroSystems Introduces Advanced Magnetic and Inductive Position Sensing Solutions
- TDK launches second generation 6-axis IMU for automotive safety applications
- LED chemical incompatibility test to see which chemicals LEDs can be used with
- Application of ARM9 hardware coprocessor on WinCE embedded motherboard
- What are the key points for selecting rotor flowmeter?
- LM317 high power charger circuit
- A brief analysis of Embest's application and development of embedded medical devices
- Single-phase RC protection circuit
- stm32 PVD programmable voltage monitor
- Introduction and measurement of edge trigger and level trigger of 51 single chip microcomputer
- Improved design of Linux system software shell protection technology
- What to do if the ABB robot protection device stops
- Detailed explanation of intelligent car body perception system
- How to solve the problem that the servo drive is not enabled
- Why does the servo drive not power on?
- What point should I connect to when the servo is turned on?
- How to turn on the internal enable of Panasonic servo drive?
- What is the rigidity setting of Panasonic servo drive?
- How to change the inertia ratio of Panasonic servo drive
- What is the inertia ratio of the servo motor?
- Is it better for the motor to have a large or small moment of inertia?
- What is the difference between low inertia and high inertia of servo motors?
- Analysis of the design steps of RS-485 bus interface circuit
-
[NXP Rapid IoT Review] +
NXP Rapid IoT Online IDE Air Quality Test - How to remotely control a two-wheeled balancing vehicle via the Internet?
- How to get the most out of your low noise amplifier solution?
- 【GD32E503 Review】 Unboxing and Powering on the Machine
- JHIHAI APM32E103VET6 Review: External Interrupt (EINT)
- PYPL Programming Language Popularity Index, September 2022
- I don't quite understand this thermal imager resolution comparison chart
- Where can I buy an LCD that works with the STM32F429IGT6?
- [TI recommended course] #Amplifier design in test and measurement#