Integrating with In-Dash AVN or In-Vehicle Infotainment Systems

An in-vehicle infotainment is a combination of vehicle systems designed for the delivery of entertainment and information to the driver and the passengers, using audio and video interfaces. The IVI architecture is composed of a HMI layer, an application layer, a middleware layer, an operating system layer, and a hardware layer. Integrating navigation software with an in-vehicle infotainment, therefore, is a challenging task for many of our competitors.

Polstar is the Best Partner for navigation on the In-Vehicle Infotainment 


As your navigation partner, we provide A-to-Z supports, throughout your product development cycle, with a dedicated team following our quality assurance standards.

Our core navigation engine has gone through road tests by numerous automotive hardware manufacturers in nearly 100 countries for more than 15 years.

Our engineering and PM teams have in-depth experience of delivering projects in areas of Heads-up Display, Tablet Computer, Telematics, In-Dash AVN, and In-Vehicle Infotainment.

Our navigation software is highly compatible with 3D Gyro, HUD, LBS, POI Advertising, Real-time traffic, LDWS/ FCWS/ AR, TPMS, CAN, VR (Voice Recognition), and Cloud Computing.

Our navigation software can be smoothly operated on different system including, but not limited to, Android, iOS, WinCE, Linux, and QNX.

  

Q&As for Our Software Integration with the In-Vehicle Infotainment Systems 

Polstar prefers to have the following information:

  • Operating System: Android, Win CE, Linux, etc.

  • CPU: ARM, X86, SH4, etc.

  • Screen Resolution

  • GPS com port and baud rate

  • OpenGL enabled or not

  • RAM size

  • Storage: SD card or internal FLASH

  • The way navigation software to be installed and updated

  • The way software license to be activated

Yes, the Linux-based in-dash system is more diversified. Polstar needs to know:

  • The Code Development Environment for hardware/firmware, Software SDK and/or tool chain, Debugging tool.

  • The way Simple Direct Media Layer works.

  • The way system message is exchanged, message queue or D-bus, etc.

  • Technical documents for the exchange of system message.

Information from the CAN Bus is helpful for navigation. When the GPS signal is lost in the tunnel or among high-rise buildings, our navigation software switches to adopt the speed and direction of the automobile keeping the navigation workable. Also, the day/night mode of the navigation display can be connected to the CAN Bus for automatic changeup.

Yes, whether opening a widget or splitting the screen is workable. Polstar accumulated intensive such experiences on platforms of Win CE, Android, and Linux.

A HUD can be connected to the in-vehicle infotainment by way of Bluetooth, Wi-Fi, or a USB cable. Brief symbols such as turn arrows and distance to turn are the information most often chosen by manufactures who adopt the Bluetooth solution. The bandwidth of Wi-Fi and USB cable, on the other hand, allows much more alternative from projecting the whole map to something in between. 

Internet connected information such as real-time traffic, real-time parking, and real-time weather along the way can be well integrated with our software. Other functions such as cloud-based voice recognition and vehicle monitoring can be enabled also. 

Yes, we can manage to adjust the display refreshing rate, remove insignificant map information, simplify text presentation, and remodel the routing algorithm to relieve the CPU loading. Also, we can further compress the map data, reduce the icon pixels, and simplify the road classification to meet the limitation of smaller RAM size.  

Polstar makes use of diversified routes such as MAC address, serial number, or SD card UUID as license references. License keys can be delivered in a way to facilitate the production of the manufacturers. 

Before the completion of each project, our Quality Assurance Handbook requires us to go through the six-step verifications procedures. They are 

  1. one-by-one functional tests

  2. overall performance tests

  3. map data sampling tests

  4. 72-hour burn-in tests

  5. dynamic navigation tests

  6. real road tests.

NMEA logs from field tests are of extremely importance for the trouble shooting. NMEA and relevant information gathered from field tests make it possible for our QA team to reproduce the to-be resolved issues and speculate possible causes. Departments of navigation engine, algorithm, or map data will be assigned to do further analysis respectively and solve their own problems from the root causes.