Car IF Vaibhav Jain
Car IF Vaibhav Jain
Bachelor of Technology
in
Computer Science and Engineering
by
Vaibhav Jain
r.
Kumar
Shivam
Project
Manage
r,
LGSI)
1
GLA
Universi
ty
Mathur
a-
281406,
INDIA
December 2023
2
Declaration
Vaibhav Jain
3
CERTIFICATE
Signature of Supervisor:
4
ACKNOWLEDGEMENT
Thanking You
Vaibhav Jain
5
ABSTRACT
This project aims to develop a middleware platform managed by LG Soft that seamlessly
connects the car's Human-Machine Interface (HMI) with the Volkswagen (VW)
ecosystem. This middleware will act as a bridge, facilitating communication and data
exchange between the car's internal systems and VW's external services.
It is designed to enhance the integration and communication between these two critical
components, the middleware plays a crucial role in optimizing the user experience
and functionality within modern automotive interfaces.
The project addresses the complexity of connecting diverse HMI elements, ranging from
touchscreens and voice recognition to gesture controls, with the intricate systems
embedded in Volkswagen vehicles. LG Soft's middleware acts as a unifying layer,
facilitating seamless data exchange and interaction protocols between the HMI and VW,
thereby ensuring a harmonious and responsive interface.
The Car Interface Middleware Project by LG Soft emerges as a critical enabler for
enhancing the synergy between HMI and Volkswagen systems. By providing a robust,
customizable, and secure middleware solution, LG Soft contributes to the evolution of
advanced, user-centric automotive interfaces, promising an enriched driving experience
for consumers.
6
Table of Contents
Declaration ii
Certificate iii
Acknowledgement iv
Abstract v
CHAPTER 1: Introduction 1
1.1 Overview and Motivation
1.2 Objective
1.3 Summary of similar Application
CHAPTER 2: Software Requirement Analysis 13
2.1 Requirement Analysis
2.2 Modules and Functionalities
7
CHAPTER 1
INTRODUCTION
The car interface, once a simple dashboard of analog gauges and physical buttons, has
undergone a dramatic transformation in recent years. Driven by technological
advancements and evolving consumer expectations, the car interior is now evolving
into a sophisticated digital ecosystem, blurring the lines between vehicle and mobile
device. This shift towards a more integrated and connected experience presents
exciting possibilities for both drivers and manufacturers, promising to revolutionize
the way we interact with our automobiles.
This paper delves into the changing landscape of the car interface, exploring the key
trends, challenges, and opportunities shaping its future. We will examine the transition
from traditional dashboards to digital displays, the increasing role of voice and gesture
control, and the integration of advanced technologies like artificial intelligence and
augmented reality. Additionally, we will discuss the evolving role of the interface in
enhancing safety, comfort, and convenience for drivers and passengers alike.
Overview:
8
The Car Interface Project represents a comprehensive endeavor aimed at
revolutionizing the automotive experience by redefining the interface through
which drivers and passengers interact with their vehicles. In an era of
technological innovation, this project goes beyond traditional dashboard
controls and enters the realm of advanced Human-Machine Interface (HMI)
technologies. The primary goal is to seamlessly integrate and enhance the
communication between users and their vehicles, creating an intuitive,
interactive, and user-friendly interface.
Motivation:
The motivation behind undertaking a project focused on advancing the car
interface stems from the recognition of the pivotal role that interfaces play in
shaping the modern automotive experience.
The primary motivation is to create a more user-centric and intuitive driving
experience. Recognizing that drivers and passengers increasingly expect
seamless interaction with their vehicles, the project aims to design interfaces
that are not only easy to use but also enhance overall satisfaction and
convenience.
1. 2 Objective:
The objectives of a car interface project are typically multifaceted, addressing various
aspects related to user experience, technology integration, safety, and overall
innovation in the automotive domain. Below are common objectives that a car
interface project might aim to achieve:
10
technologically advanced, user-centric, and safe driving experience that sets
new standards in the automotive industry.
In recent years, a surge of innovation has characterized the automotive industry, with
numerous projects dedicated to advancing car interfaces. These projects collectively
aim to redefine the driving experience by introducing cutting-edge technologies and
user-centric design principles.
11
CHAPTER 2
SOFTWARE
REQUIREMENT
12
An example of the green board. (1)
13
An example of the board setup containing (from left) a green board stack to
power the main board and a red board. (2)
14
2.2 MODULES AND FUNCTIONALITIES
Ambient Light
It is also known as internal light
Ambient light in a car refers to the strategic use of subtle lighting
inside the cabin. It differs from the primary lighting sources like
headlights and interior dome lights, which are used for
illumination. Instead, ambient light focuses on creating a specific
atmosphere and enhancing the overall driving experience.
Ambient light can add a touch of elegance and sophistication to the
car's interior. It can be used to highlight specific design elements,
create a sense of space, and personalize the driving environment
Different colors and intensities of ambient light can evoke different
emotions. For example, warm colors like red and orange can create
a cozy and inviting atmosphere, while cooler colors like blue and
green can promote a sense of calm and relaxation.
Ambient light can be automatically adjusted based on the time of
day or the driving conditions. This can help to reduce fatigue and
improve driver comfort.
15
Exterior Light
In a car's Human-Machine Interface (HMI), the control and
display system for various vehicle functions, including exterior
lights, provides a user-friendly interface for drivers to manage
and customize the car's lighting features
Headlights Control:
o On/Off: Allows the driver to manually turn the headlights on or
off.
o Automatic Mode: Enables an automatic mode where the headlights
are controlled by ambient light conditions or the vehicle's sensors.
o High Beam/Low Beam Control: Enables switching between high
and low beam headlights for optimal visibility under different
driving conditions.
Head Up Display
16
unintentionally drifts out of its lane without using the turn
signal.
Forward Collision Warning: Warns the driver of an imminent
collision with the vehicle in front, often using sensors and
cameras.
Seats
The specific functionalities of seat controls accessible through
the Human-Machine Interface (HMI) in a VW car can vary
depending on the model, year, and trim level.
Seat Adjustment Controls:
o Driver's Seat: Typically, the HMI allows the driver to
control the position of their seat, including adjustments for
seat height, fore/aft position, recline, and lumbar support.
o Passenger's Seat: Similar controls are often available for
the front passenger seat, allowing occupants to find a
comfortable seating position.
Memory Settings:
o Seat Memory Profiles: If the car has memory seats, the
HMI may allow users to save and recall preferred seat
positions for different drivers. This is especially common
in higher-end models.
Massage and Ventilation:
o Massage Functions: In premium models, the HMI might
include controls for activating seat massage functions,
allowing occupants to choose different massage programs
and intensity levels.
o Seat Ventilation/Heating: Some cars offer seat ventilation
and heating controls through the HMI, allowing occupants
to adjust the temperature of the seats for added comfort.
17
Tyres
18
CHAPTER 3
SOFTWARE DESIGN
19
layers is well-defined. The software design is also flexible
and scalable. New layers can be added to the design without
affecting the existing layers.
20
USER INTERFACE
The user interface (UI) plays a crucial role in interacting with
car functions through the HMI screen. It should be designed
to be intuitive, safe, and user-friendly, allowing drivers to
control various features without compromising their focus on
the road.
Here are some key aspects of the UI for car functions on the
HMI screen:
1. Layout and Organization:
Clear and logical layout: Information should be presented in
a way that is easy to scan and navigate. Grouping related
functions together and using consistent iconography can
improve usability.
Hierarchical structure: Complex functions can be organized
into submenus or layers to avoid cluttering the main screen.
Contextual awareness: The UI should adapt to the current
driving context, highlighting relevant functions and
minimizing distractions.
2. Visual Design and Accessibility:
Minimalist and uncluttered: Avoid overloading the screen
with unnecessary information or graphics.
High contrast and readability: Use fonts and colors that are
easily readable in different lighting conditions.
Accessibility features: Consider features like voice control,
large icons, and haptic feedback to cater to users with diverse
needs.
3. Interaction and Navigation:
Touch-friendly interface: Buttons and icons should be large
enough for easy touch interaction.
21
Intuitive gestures: Allow users to perform common actions
like swiping or pinching to navigate through menus.
Minimal text input: Minimize the need for typing while
driving by utilizing voice commands or pre-defined options.
Confirmation prompts: Implement confirmation prompts for
critical actions to prevent accidental activation.
4. Feedback and Information Display:
Clear and concise feedback: Provide visual, auditory, or
haptic feedback to confirm user actions.
Real-time information: Display relevant information about
the car's status and active functions.
Alerts and warnings: Use clear and unambiguous alerts to
notify the driver about potential issues.
5. Customization:
Adjustable settings: Allow users to personalize the UI layout,
color schemes, and accessibility features.
Profile management: Enable saving and switching between
different user profiles with personalized settings.
22
contacts, and listen to messages.
Driver assistance systems: Activate and adjust settings
for features like lane departure warning and adaptive
cruise control.
Vehicle information: Check fuel level, tire pressure,
and engine diagnostics.
23
CHAPTER 4
INSTALLATION & SETUP
1. Preparation:
Gather the following:
New hardware patch
Installation tools as specified in the patch documentation
Car interface unit
Access to a safe and clean workspace
Backup of existing software and configuration (optional, depending on
patch nature)
Review the patch installation instructions carefully.
Identify the hardware component requiring the patch.
2. Patch Installation:
Power down the car interface unit and disconnect all peripherals.
Open the car interface unit according to the manufacturer's instructions.
Locate the hardware component requiring the patch.
Carefully remove the existing version of the hardware component (if
applicable).
Prepare the new patch for installation, ensuring correct orientation and
alignment.
Install the new patch according to the provided instructions.
Securely close the car interface unit.
24
5. Safety Precautions:
After the setup is complete the IP address of the board is taken and an SSH
connection is established, here MobaXterm is used for this process, PuTTY
is an alternative to this software, post the connection establishment, we
mount the binary image file on the board. During the mounting process
following operations will be involved:
1. Stopping the previously running service
2. Mounting the image file from our local server onto the board.
3. Providing read/write permissions to the mounted binary file.
4. Restart the service.
5. Run the Luna command to verify the changes made to the module.
25
We go to session tab of MobaXterm, then click on serial connection and
choose the COM port in which the serial USB is connected.
We then run certain commands to flash the bin file generated from arm-gcc-
compiler.
Example of MobaXTerm
26
CHAPTER 5
IMPLEMENTATION AND USER
INTERFACE
Software Implementation:
1. Communication Protocols:
1.1 HMI Communication: CarIF uses standardized protocols like
CAN, LIN, and Bluetooth to communicate with the HMI
system. This allows for compatibility with various HMI
implementations and car models.
1.2 VW Communication: Communication with VW's cloud-
based services and vehicle systems utilizes APIs and
protocols like REST and MQTT. This ensures secure and
efficient data exchange with VW infrastructure.
27
3. Feature Integration and Services:
3.1Custom Feature Development: The software allows for the development
of customized features and services tailored to specific user needs and
preferences. This can include innovative applications for fleet management,
carsharing, and other emerging mobility concepts.
6. Software Architecture:
6.1 Modular Design: CarIF is designed with a modular architecture,
allowing for flexibility, scalability, and ease of maintenance.
6.2 Microservices Architecture: The software can be implemented as a
collection of microservices, each focusing on a specific functionality.
This improves scalability and fault tolerance.
6.3 Open-source libraries and frameworks: Leverage open-source
libraries and frameworks to accelerate development, reduce costs, and
promote community collaboration.
7. Programming Languages & Technologies:
The choice of programming languages and technologies depends on the
specific requirements and target platform.
Common choices include Python, C++, Java, and JavaScript for backend
28
development.
HMI development might utilize technologies like Qt, HTML5, and
JavaScript frameworks.
Cloud-based services might leverage platforms like AWS, Azure, or
Google Cloud Platform.
Hardware Implementation:
2. Communication Hardware
Wireless communication module: Enables communication with the
HMI system and VW's cloud services through technologies like
Wi-Fi, Bluetooth, or cellular networks.
Gateway controller: Processes data received from various sources
and transmits it to the appropriate recipient systems.
29
3. Processing Hardware:
Microcontroller or embedded computer: Performs data
processing, communication protocol handling, and
application logic execution.
Memory storage: Stores software programs, configuration
data, and collected data.
4. Additional Hardware:
Display: Depending on the project's design, a dedicated
display might be used to present information to the driver or
passengers.
Control buttons: Dedicated buttons can be implemented for
specific functions like voice command activation or
emergency calls.
5. Hardware Integration:
The hardware components should be securely mounted
within the car and connected to the vehicle's electrical
system.
Proper cable management and shielding are essential to
ensure reliable communication and prevent interference.
Software drivers and configuration settings need to be
tailored to the specific hardware components used.
30
CHAPTER 6
SOFTWARE TESTING
The software testing of the Car IF module in a car is an essential step in ensuring that
the module works as intended and meets the required quality standards. Here are some
of the software tests that can be performed on the Car IF module:
1. Unit Testing: This test involves testing individual software components of the
Bluetooth audio module to ensure that they work as intended. This test helps
detect any bugs or errors early in the development process and ensures that the
individual components function correctly.
3. Functional Testing: This test involves testing the functionality of the Bluetooth
audio module to ensure that it meets the required specifications. This test
includes testing features such as device discovery, pairing, authentication,
volume control, and equalizer settings to ensure that they work as intended.
5. User Acceptance Testing: This test involves testing the Bluetooth audio module
from the user's perspective to ensure that it meets the required usability
standards. This test includes testing the user interface, user experience, and ease
31
of use of the module.
In conclusion, the software testing of the Car IF audio module in a Car is a critical
step in ensuring that the module works as intended and meets the required quality
standards. Different software tests, such as unit testing, integration testing, functional
testing, performance testing, user acceptance testing, and regression testing, can be
performed to ensure that the module meets the required specifications and provides a
seamless and enjoyable drive experience to the users.
32
CHAPTER 7
RESULTS AND CONCLUSION
SUMMARY
33
The middleware project aimed to seamlessly integrate Human-Machine
Interface (HMI) elements with Volkswagen (VW) systems, achieving a
unified and responsive car interface. By establishing standardized
communication protocols, implementing advanced interaction methods,
and ensuring adaptability to VW system specifications, the middleware
successfully bridged the gap between diverse HMI components and
intricate VW functionalities. The project's outcome delivers an enriched
driving experience through intuitive touchscreens, voice recognition, and
gesture controls. Notably, robust security measures were implemented to
safeguard sensitive data, while configuration flexibility empowers
developers and integrators to customize functionalities. This collaborative
effort sets a standard for the future of car interfaces, emphasizing seamless
integration, security, and adaptability, marking a significant milestone in
the evolution of intelligent and user-centric automotive systems..
34
BIBLIOGRAPHY
35
APPENDICES
Appendix B: Glossary
Bluetooth: A wireless communication technology used for short-range communication
between devices.
A2DP: A Bluetooth profile used for streaming high-quality audio from one device to
another.
AVRCP: A Bluetooth profile used for controlling audio/video playback on remote
devices.
Device Discovery: The process of searching for and identifying nearby Bluetooth-
enabled devices.
Pairing: The process of establishing a connection between two Bluetooth-enabled
devices.
Authentication: The process of verifying the identity of a device during the pairing
process.
Codec: A software or hardware component that encodes or decodes digital audio data.
User Interface: The interface through which users interact with the Bluetooth audio
module.
Firmware: Software that is embedded in the Bluetooth audio module's hardware and
controls its operation.
API: A set of software tools and protocols used for building software applications.
36
1. Pairing Test Case
Objective: To ensure that the module can pair with a Bluetooth-enabled device.
Steps: Put the device into pairing mode and search for it on the TV. Follow the on-
screen instructions to pair the device.
Expected Result: The device should be successfully paired with the TV.
Audio Playback Test Case
Objective: To ensure that the module can stream high-quality audio from a
Bluetooth-enabled device to the TV.
Steps: Stream audio from a Bluetooth-enabled device to the TV and test the audio
quality, volume, and stability of the connection.
Expected Result: The audio should be of high quality, the volume should be
adjustable, and the connection should be stable.
2. Compatibility Test Case
Objective: To ensure that the Bluetooth audio module is compatible with the TV.
Steps: Check the TV's specifications and ensure that it supports the necessary
Bluetooth profiles, such as A2DP and AVRCP.
Expected Result: The Bluetooth audio module should be compatible with the TV.
37