With the popularization and development of autonomous driving and infotainment systems, more and more demand for information display has been generated, and the importance of the resulting HMI has also been highlighted.
Most automakers have the following four most basic requirements for AR-HUDs.
- A complete and intuitive GUI that gives the end user a cool experience and can be displayed in accordance with various driving scenarios.
- Customizable, easy to modify, and easy to get started software solutions.
- End-user safety tests such as driver distraction must be passed.
- Design that does not adversely affect any driving scenario (safety hazard).
The HMI design of the future AR-HUD can be roughly divided into three blocks: near field, far field and side.
We can see from the AR-HUD of the TFT and DLP solutions that the close focus is basically the information of alternative instruments such as vehicle speed; the far focus is the information related to ADAS safety. There is not much information that can be displayed now, mainly navigation arrows, ACC, lane markings, vehicle lane changes, place names, etc. In the future, when the AR engine can be more mature, the combination of ADAS and AR-HUD can display more information and be more intuitive.
Also in the side display area, because of the current AR-HUD FoV limitations, we have not considered too much. In fact, if the future is too much to holographic technology, when FoV is not a problem, information such as the power information of some electric vehicles, V2X information, auxiliary navigation screens, POI and telephones can be displayed to the area.
At present, the HMI in AR-HUD is related to AR rendering, and many companies in the film and television and game industries have entered the field. As mentioned last time when talking about AR engines, the software part that is good at front-end ADAS information fusion and processing may not be good at AR rendering, so a better AR-HUD software solution usually requires the participation of both companies.
For example, in the DLP solution of the Mercedes-Benz S-Class, most people know that the hardware supplier is Japanese Seiki, and the software part is Elektrobit and Unity. In fact, Nissei has its own AR engine solution, and he previously acquired Alpine's AR engine business. However, mercedes-benz this project is estimated to be a software solution provider designated by Mercedes-Benz. Elektrobit is responsible for ADAS information processing and Unity is responsible for the HMI part. Unity, which many people may be familiar with, is developed for 3D and AR for the film and video and game industries.
In addition, the optical hardware supplier of AR-HUD of the Volkswagen ID series is LG, the ADAS information part is also developed by LG itself, and the HMI part is cooperated with The Austrian Cadera.
Finland's Rightware has also recently ventured into the AR-HUD space, and he has a Kanzi UI solution that has been adopted by the instruments of mass-produced models, and is said to have recently developed a solution for AR-HUD.
Now in order to pursue the cooler effect of HMI, car companies have begun to test the water game engine. For example, electric Hummer uses Epic Games' game engine, and game engines may also be a trend in the future.
Search public number: Zhiche Tribe
Get more industry profiles