GESTURE CONTROL ROBOT USING

ACCELEROMETER AND MICRO CONTROLLER

Submitted for the partial fulfillment of the requirements for the award
of the Bachelor’s degree by

JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY

GURAJADA VIZIANAGARAM
In the Department of

ELECTRONICS AND COMMUNICATION ENGINEERING

Submitted by

P.SANJIVA REDDY 22NT5A0432

P. HARI KRISHNA 22NT5A0428

M. ROHIT KUMAR 22NT5A0422
M. DHANA LASKHMI 22NT5A0424
I.V.V.L. BHARATI 21NT1A0424

Under the esteemed guidance of

DR. KAUSAR JAHAN, M. TECH, PH. D
ASSISTANT PROFESSOR

VISAKHA INSTITUTE OF ENGINEERING &TECHNOLOGY

(Approved by A.I.C.T.E, New Delhi &Affiliated to JNTUGV,Vizianagaram)
NAAC ‘A’ ACCREDITED INSTITUTE
88th Division, Narava, GVMC, Visakhapatnam -530027, A.P.
2024-2025

i
 CERTIFICATE

This is to certify that the project report entitled“Gesture Control Robot Using
Accelerometer And Micro Controller” is being submitted by P. Sanjiva Reddy
(22NT5A0432), P. Hari Krishna (22NT5A0428), M. Rohit Kumar (22NT5A0422), M.Dhana
Lakshmi (22NT5A0424), I.V.V.L. Bharati (21NT1A0424) in partial fulfillment for the award of
Bachelor degree in ELECTRONICS AND COMMUNICATION ENGINEERING to the
JAWAHARLAL NEHRU TECHNOLOGICAL UNIVERSITY, GURAJADA
VIZIANAGARAM is a record of bonafide work carried out by them under the guidance and
supervision.

The results embodied in this project report have not been submitted to any other university
or institute for the award of any degree as per best of my knowledge.

Signature of the Guide: Signature of the HOD:

Dr. Kausar Jahan MTech, PH.D Mr.B.Jeevana Rao, M.Tech PH.D
Assistant Professor Assistant Professor

Department of E.C.E Department of

EXTERNAL EXAMINER

ii
 ACKNOWLEDGEMENT
The successful completion of any task is not possible without proper suggestion, guidance
and environment. Combination of these three factors acts like backbone to our project titled
“GESTURE CONTROL ROBOT USING ACCELEROMETER AND MICRO
CONTROLLER”. It is intended with a great sense of pleasure and immense sense of gratitude
that we acknowledge the help of these individuals.

We express our sincere thanks to our Guide Dr. Kausar jahan, M. Tech, Ph.d, Electronics
and communication engineering, VISAKHA INSTITUTE OF ENGINEERING AND
TECHNOLOGY , JNTU-GV University for his valuable guidance and co-operation throughout
our project work.

We express my sincere thanks to our Head of the Department Mr. JEEVANA RAO,
M.Tech, Ph.d, Electronics and communication engineering, VISAKHA INSTITUTE OF
ENGINEERING AND TECHNOLOGY, JNTU-GV University for his valuable guidance and co-
operation throughout my seminar work.

We would like to thank my principal Dr. G VIDYA PRADEEP VARMA, M.Tech., Ph.D.
for providing his support and simulating environment.

We would like to express our gratitude to the management of VISAKHA INSTITUTE OF

ENGINEERING AND TECHNOLOGY, for providing a pleasant environment and excellent
laboratory facilities.

We were thankful to all teaching and non-teaching staff and management of the department
of Electronics and communication engineering for the co-operation given for the successful
completion of the seminar.

P.SANJIVA REDDY ( 22NT5A0432)

P. HARI KRISHNA (22NT5A0428)

M.ROHIT KUMAR (22NT5A0422)

M.DHANA LASKHMI (22NT5A0424)

I.V.V.L. BHARATI (21NT1A0424)

iii
 DECLERATION

We hereby declare that the project report entitled “GESTURE CONTROL ROBOT USING
ACCELEROMETER AND MICRO CONTROLLER” originalwork done in the Department of
Electronics and Communication Engineering, Visakha institute of engineering and technology,
Visakhapatnam, submitted in partial fulfillment of the requirements for the award of the degree of
Bachelor of Technology in Electronics and Communication.

P.SANJIVA REDDY (22NT5A0432)

P. HARI KRISHNA (22NT5A0428)

M. ROHIT KUMAR (22NT5A0422)

M. DHANA LASKHMI (22NT5A0424)

I.V.V.L. BHARATI (21NT1A0424)

iv
 CONTENTS
ACKNOWLEDGEMENT ......................................................................................................................... iii
CONTENTS................................................................................................................................................ v
LIST OF TABLES ................................................................................................................................... viii
CHAPTER 1 ................................................................................................................................................ 1
OVERVIEW OF THE PROJECT........................................................................................... 1
1.1 Introduction ................................................................................................................................... 1
1.2 Project Objectives ......................................................................................................................... 2
1.3 Project Methodology ..................................................................................................................... 5
1.3.1 Requirements Gathering and Analysis .................................................................................... 5
1.3.2 System Design and Architecture ............................................................................................... 5
1.3.3 Component Integration and Development............................................................................... 6
1.3.4 Testing and Debugging .............................................................................................................. 7
1.3.5 System Optimization .................................................................................................................. 8
1.3.6 Deployment and Documentation .............................................................................................. 8
1.3.7 Evaluation and Conclusion ..................................................................................................... 9
1.4 Organization Of The Project ..................................................................................................... 10
LITERATURE REVIEW ....................................................................................................... 15
2.1 Gesture Recognition Systems ..................................................................................................... 15
2.1.1 Accelerometer-Based Gesture Recognition ........................................................................... 15
2.1.2 Vision-Based Gesture Recognition ......................................................................................... 16
2.1.3 Challenges In Gesture Recognition ........................................................................................ 16
2.2 Wireless Communication And Iot Integration ......................................................................... 16
2.2.1 Iot In Robotics .......................................................................................................................... 17
2.2.2 Remote Control Of Robots Via Iot ......................................................................................... 17
2.3 Robot Control And Actuators .................................................................................................... 17
2.3.1 Motor Control Using Arduino ................................................................................................ 18
2.3.2 Challenges in Motor Control .................................................................................................. 18
2.4 Applications of Gesture-Controlled Robots.............................................................................. 18
CHAPTER 3 .............................................................................................................................................. 19
PROJECT DESCRIPTION ................................................................................................... 19
3.1 Block Diagram ............................................................................................................................. 19
3.2 Proposed Methodology ............................................................................................................... 23

v
 3.2.1 Methodology For Communication Signal .............................................................................. 23
3.2.2Transmitter Module .................................................................................................................. 23
3.2.3 Receiver Module....................................................................................................................... 24
3.2.4 Methodology For Motion Control .......................................................................................... 24
3.3 Circuit Diagram .......................................................................................................................... 26
3.3.1 Transmitter ............................................................................................................................... 26
3.3.2 Receiver ..................................................................................................................................... 27
3.4: Hardware Components ............................................................................................................. 29
3.4.1 nodemcu : .................................................................................................................................. 29
3.4.2 ESP8266 Microcontroller: ....................................................................................................... 30
3.4.3 GPIO Pins: ................................................................................................................................ 30
3.4.2 Bluetooth Module ..................................................................................................................... 32
3.4.4 Applications in the Hand Gesture-Controlled Robot Car .................................................... 34
3.5 Nrf24l01 Wireless Transceiver: ................................................................................................. 35
3.6 Nfc Module .................................................................................................................................. 37
3.7 Introduction To Sensors ............................................................................................................. 38
3.8 Accelerometer For Gesture Control .......................................................................................... 39
3.8.2 DC Motor Control.................................................................................................................... 41
3.8.3 Capacitor .................................................................................................................................. 42
3.9.1 Car Chassis ............................................................................................................................... 47
3.9.2 Lithium Ion Batteries .............................................................................................................. 48
3.9.4 Jumper Wires ........................................................................................................................... 49
3.9.5 Software Components .............................................................................................................. 50
3.9.6 Cirkit designer .......................................................................................................................... 50
3.9.7 Arduino IDE ............................................................................................................................. 50
CHAPTER 4 .............................................................................................................................................. 52
SYSTEM IMPLEMENTATION AND RESULTS .............................................................. 52
4.1 Simulation Circuit ....................................................................................................................... 52
4.1.1 Code Implementation .............................................................................................................. 52
4.2.1 System Integration and Testing .............................................................................................. 56
4.3 Hardware Results : ..................................................................................................................... 58
CHAPTER 5 .............................................................................................................................................. 61
CONCLUSION AND FUTURE SCOPE .............................................................................. 61

vi
 5.1 Conclusion : ................................................................................................................................. 61
5.2 Future Applications .................................................................................................................... 67
CHAPTER 6 .............................................................................................................................................. 74
REFERENCES ........................................................................................................................ 74

vii
 LIST OF FIGURES
Fig 1: BLOCK DIAGRAM ...................................................................................................................... 19
Fig 2 :TRANSMITTER ............................................................................................................................ 26
Fig 3 : RECIEVER.................................................................................................................................... 28
Fig 4: NODEMCU MODULE .................................................................................................................. 29
Fig 5:ESP8266 Microcontroller ............................................................................................................... 30
Fig 6:GPIO PINS ...................................................................................................................................... 31
Fig 7 : BLUETOOH MODULE ............................................................................................................... 32
Fig 8 :NRF24L01 WIRELESS TRANSCEIVER ................................................................................... 35
Fig 9 :NFC MODULE .............................................................................................................................. 37
Fig10 :ACCELEROMETER ................................................................................................................... 40
Fig11:L298N Motor Drive ........................................................................................................................ 41
Fig 12: DC MOTOR ................................................................................................................................. 41
Fig13: CAPACITOR ................................................................................................................................. 42
Fig14: On/Off Button Circuitry ............................................................................................................... 43
Fig15 : ARDUINO UNO R3 ...................................................................................................................... 45
Fig 16: CAR CHASSIS ............................................................................................................................. 47
Fig 17: LITHIUM ION BATTERIES ..................................................................................................... 48
Fig 18: ESP32 CAM MODULE ............................................................................................................... 49
Fig 19: JUMPER WIRES ......................................................................................................................... 49
Fig 20 : CIRKIT DESIGNER .................................................................................................................. 50
Fig 21: ARDUINO IDE SOFTWARE ..................................................................................................... 51
Fig 22: SIMULATION CIRCUIT ........................................................................................................... 52
Fig 23: MOVING UPWARD .................................................................................................................... 55
Fig 24: DOWNWARDS ............................................................................................................................ 56
Fig 25 : TRANSMITTER HAND GLOVE ............................................................................................. 58
Fig 26:RECIEVER ROBOT .................................................................................................................... 59
Fig 27: ESP32-CAM MONITOR INTERFACE .................................................................................... 59

LIST OF TABLES

viii
 ABSTRACT
The Hand Gesture Controlled Car project utilizes an Arduino-based system to allow the user to
control a car through hand gestures. This project integrates an MPU6050 accelerometer sensor
with an Arduino and communicates wirelessly using Bluetooth technology (HC-05 modules). The
hand-mounted Arduino detects hand movements using the accelerometer, such as tilting in
different directions, and sends the corresponding data to a car-mounted Arduino via Bluetooth.
The car's Arduino receives the gesture data and operates the motors accordingly, enabling the car
to move forward, backward, left, or right based on the user's hand movements. This system
eliminates the need for traditional physical controllers, providing a novel and intuitive way to
control a robotic car.

The hand-mounted device detects gestures like forward, backward, left, right, and stop based on
the orientation of the hand. The Bluetooth modules (HC-05) on both devices communicate
wirelessly, transmitting the gesture information. On the car side, the data is received and processed,
and a motor driver (L298N) controls the motors to move the car.

In addition, the ESP32-CAM module is integrated into the system to add real-time video streaming
capabilities. This camera module allows the user to monitor the car's environment remotely via
Wi-Fi, enhancing the overall functionality and providing a visual feedback system for the user.
The ESP32-CAM can be programmed to stream live video to a smartphone or web browser,
providing an additional layer of control and interaction with the car.

This project demonstrates the practical application of Arduino platforms, sensors, Bluetooth
communication, and the ESP32-CAM module in robotics, offering an easy-to-implement solution
for wireless gesture control with added camera functio

ix
 CHAPTER 1

OVERVIEW OF THE PROJECT

1.1 Introduction
The Hand Gesture Control Robot Car project is a cutting-edge system designed to provide intuitive
control of a robot car using hand gestures. This project integrates the power of Internet of Things
(IoT) with gesture recognition to build an interactive and user-friendly robot control system. The
robot’s movement is determined by the gestures made by the user, which are captured by an
accelerometer and processed by a microcontroller. The data captured is communicated wirelessly,
allowing the user to control the robot from a distance.

This project integrates multiple technologies, including Arduino Uno, NodeMCU, and
Accelerometers, providing a versatile and flexible solution for robot control. By incorporating the
IoT aspect, the system allows for wireless interaction between the user and the robot, which adds
a layer of functionality and accessibility to the control mechanism.

Motivation

The motivation behind this project is to explore the possibilities of controlling robotic systems
using natural and intuitive input methods. Hand gestures provide a more natural interaction,
making the experience of controlling the robot more engaging. Furthermore, the integration of IoT
technology enables the robot to be operated remotely via wireless communication, making it more
adaptable to various environments and use cases.

The combination of gesture recognition and wireless communication opens doors to future
advancements in automation, assistive technology, and remote control systems. By integrating
these technologies, the project not only serves as a proof of concept but also lays the groundwork
for more complex systems.

The Hand Gesture Control Robot Car project is an innovative solution that utilizes gesture
recognition technology to control a robot car in real-time. This system allows users to control the
movement of the car by simply using hand gestures, eliminating the need for traditional input
devices like remote controls or joysticks. Instead of physically interacting with a device, the

1
user’hand movements are detected and processed by sensors, providing a natural and intuitive
means of control.

At the heart of this system is an accelerometer, a device capable of detecting acceleration and tilt
in three-dimensional space. This sensor is responsible for capturing the user’s hand gestures, which
are then interpreted by a microcontroller, specifically an Arduino Uno, to control the motors of the
robot. Additionally, the system incorporates NodeMCU, a Wi-Fi-enabled microcontroller that
facilitates wireless communication, making it possible to remotely control the robot through an
IoT platform.

The project is driven by the principles of Internet of Things (IoT), where multiple components,
including sensors, microcontrollers, and communication modules, work together seamlessly to
achieve the goal of gesture-based control. Through this project, the integration of IoT with robotic
systems is explored, allowing for enhanced functionality, mobility, and remote accessibility.

This project provides a significant leap forward in human-robot interaction, offering practical
applications in various fields such as robotics, assistive technology, remote automation, and
educational tools. By using hand gestures as input, the system simplifies the interaction between
the user and the robot, making it more accessible and user-friendly. Moreover, the wireless
communication aspect enables remote operation, making the system more flexible and versatile.

The objective of this project is not only to build a functional prototype of a gesture-controlled
robot but also to explore how IoT and embedded systems can come together to create smart,
interactive environments. This introduction outlines the fundamental concept of the project, setting
the stage for further discussion on its components, functionality, and potential applications.

1.2 Project Objectives

The Hand Gesture Control Robot Car project aims to develop an intuitive and innovative robotic
system that enables users to control a robot car using simple hand gestures. By leveraging the
capabilities of gesture recognition and wireless communication via IoT technologies, the project
seeks to address the limitations of traditional remote control systems and provide a more accessible
and engaging way to interact with robotic systems. The key objectives of the project are as follows:

1. Gesture-Based Control

2
The primary objective is to design and implement a gesture-based control mechanism for the robot
car. The system will utilize an accelerometer (such as MPU6050 or ADXL335) to detect hand
movements and translate them into actionable commands that control the robot's motion. Hand
gestures, such as tilting forward, backward, left, or right, will be recognized by the accelerometer
and used to direct the robot accordingly. This goal emphasizes ease of interaction, allowing users
to control the robot in a more natural, intuitive way without the need for physical controllers.

2. Wireless Communication via IoT

An essential feature of the project is the integration of IoT technologies to enable wireless
communication between the robot and a remote user. The NodeMCU, a Wi-Fi-enabled
microcontroller, will be used to establish communication between the robot and a mobile device
or web interface. This allows for remote control of the robot over a network, facilitating enhanced
mobility and accessibility. The objective is to demonstrate how IoT can extend the functionality of
a robotic system by enabling wireless operation.

3. Real-Time Gesture Recognition and Control

The project aims to ensure that the gesture recognition and control system operates in real-time.
The system must be capable of quickly processing the accelerometer data and responding to hand
gestures with minimal delay. This objective ensures a smooth and seamless user experience, where
the robot’s movements align precisely with the user’s gestures. Real-time control will be achieved
by implementing an efficient data processing algorithm and minimizing latency in the
communication between the components.

4. Efficient Motor Control and Feedback

Another key objective is to design an efficient control system for the robot’s motors. The Arduino
Uno will serve as the central controller, processing data from the accelerometer and sending signals
to the motor driver (e.g., L298N) to control the robot's movement. The robot will be capable of
moving in all directions, including forward, backward, left, and right, based on the recognized
hand gestures. The motor control system will include speed regulation and direction control to
provide full range of motion. Feedback mechanisms may also be implemented to inform the user
of the robot’s status (e.g., movement confirmation).

3
5. Exploring IoT for Remote Monitoring and Control

The project will explore the integration of the robot with an IoT platform (e.g., Blynk, ThingSpeak,
or a custom server) to allow remote monitoring and control of the robot car. This will not only
provide a remote control interface but also allow for advanced features such as monitoring the
robot's battery levels, status updates, and other performance metrics in real-time. The IoT aspect
of the project serves as an exploration of how wireless communication and remote accessibility
can enhance the capabilities of robotics.

6. Programming and Software Development

A significant objective of the project is to develop the necessary software to interface with the
hardware components and implement the control algorithms. The software will be written in C
programming, utilizing libraries for accelerometer data acquisition, motor control, and wireless
communication. This will involve writing code for data processing, gesture recognition, motor
driver control, and interaction with the NodeMCU for IoT functionality. The development will also
include debugging and optimization to ensure smooth operation.

7. Testing and Validation

Testing is a crucial aspect of the project to ensure the system's reliability and effectiveness. The
system will undergo various tests to validate the accuracy of the gesture recognition, the
responsiveness of the robot’s movements, and the reliability of the wireless communication. The
objective is to ensure that the robot can consistently interpret and respond to gestures in real-time,
with minimal errors or delays.

8. Practical Applications and Future Expansion

Finally, a broader objective of the project is to explore the practical applications of gesture-
controlled robots in various fields, such as:

• Assistive technology: Enabling individuals with limited mobility to control robots or

assistive devices using hand gestures.

• Education: Providing an interactive learning tool for students to understand robotics and
IoT.

4
 • Entertainment and gaming: Creating a new method for controlling robots in gaming or
entertainment environments.

• Automation and smart systems: Integrating the gesture control system into IoT-based
automation setups for smart homes or industrial robots.

Moreover, the project aims to lay the groundwork for future developments, such as integrating
more advanced gesture recognition techniques, improving wireless communication capabilities,
and expanding the system's functionality.

1.3 Project Methodology

The Hand Gesture Control Robot Car project follows a systematic approach to achieve its
objectives, integrating both hardware and software components. The methodology adopted for this
project involves multiple phases, including design, development, testing, and validation. Each
phase is crucial for ensuring the successful implementation of gesture control, wireless
communication, and efficient motor control. Below is a detailed breakdown of the methodology
used in this project:

1.3.1 Requirements Gathering and Analysis

The first step in the methodology involves gathering all the necessary requirements for the project.
This phase includes:

• Identifying the Components: Selecting the key hardware components, such as the
Arduino Uno, NodeMCU, accelerometer, motor driver, and the robot car chassis.
• Defining System Functions: Identifying the core functionalities, such as the robot’s
movement based on hand gestures, wireless communication through IoT, and real-time
control.
• Analyzing Constraints: Considering constraints such as the available power supply,
wireless range, maximum gesture detection range, and system response time.

1.3.2 System Design and Architecture

Once the requirements are clear, the system design phase begins. This involves both the hardware
and software design, followed by the development of the system architecture. The main activities
in this phase are:

5
Hardware Design:

• Selecting the Accelerometer: The project uses an accelerometer (e.g., MPU6050 or

ADXL335) to detect hand movements. The sensor must be able to detect accelerations
along three axes (X, Y, Z).

• Choosing the Microcontrollers: Arduino Uno will be used to process the accelerometer
data and control the motor driver. NodeMCU, with Wi-Fi capabilities, will be used to
enable wireless communication for IoT functionalities.

• Motor Control Setup: The motor driver (such as L298N) will interface with the Arduino
and control the motors of the robot car.

Software Design:

• Gesture Recognition Algorithm: The accelerometer data will be processed to recognize

specific gestures (e.g., tilt forward for moving forward, tilt backward for moving
backward).

• Control Logic: The logic for controlling the robot's movement (forward, backward, left,
right) based on the processed gesture data will be written in C programming for Arduino.

• Wireless Communication: The NodeMCU will be programmed to facilitate remote

control and monitoring, ensuring communication between the robot and external systems
(smartphone or cloud platforms).

System Architecture:

The system architecture will be mapped out to show the relationship between the components. The
microcontroller (Arduino) will receive accelerometer data, process it, and control the motors, while
the NodeMCU facilitates wireless communication. This will be represented in a diagram showing
the flow of data and control signals.

1.3.3 Component Integration and Development

After completing the design phase, the next step is integrating the hardware components and
writing the necessary software code. This phase includes:

6
Hardware Integration:

• Assembling the Robot Car: The components (motors, chassis, motor driver, Arduino,
NodeMCU, and accelerometer) will be physically assembled to form the complete robot
car.

• Connecting the Accelerometer to the Arduino: The accelerometer will be connected to

the Arduino via the I2C interface, allowing the Arduino to receive real-time data from the
sensor.

• Motor Control Setup: The motor driver will be wired to the Arduino, and the motors
will be connected to the driver to control the movement of the robot.

• NodeMCU Connection: The NodeMCU will be connected to the Arduino for enabling
wireless communication via Wi-Fi.

Software Development:

• Accelerometer Data Processing: Writing code to read data from the accelerometer,
process the raw acceleration values, and convert them into meaningful gestures.

• Gesture Recognition Logic: Implementing the logic to identify specific gestures (e.g.,
forward tilt, backward tilt) based on threshold values of the accelerometer readings.

• Motor Control Logic: Developing the motor control logic to translate the recognized
gestures into motor commands that will move the robot in the desired direction (forward,
backward, left, or right).

• Wireless Communication Code: Programming the NodeMCU to handle the wireless

communication, allowing the robot to be controlled remotely through IoT platforms (e.g.,
Blynk, ThingSpeak).

1.3.4 Testing and Debugging

Once the system is integrated and the code is implemented, thorough testing is conducted to ensure
the system functions as intended. This phase includes:

7
 • Unit Testing: Each individual component (accelerometer, Arduino, motor driver,
NodeMCU) will be tested separately to ensure proper functionality. For instance, testing
the accelerometer to verify that it correctly detects hand gestures.

• System Integration Testing: After unit testing, the entire system will be tested as a whole.
This involves testing the robot’s response to hand gestures in real-time, ensuring that the
system recognizes gestures accurately and controls the robot accordingly.

• Wireless Communication Testing: The wireless communication functionality will be

tested to ensure that the NodeMCU successfully establishes a Wi-Fi connection and allows
remote control of the robot.

• Debugging: Any issues or bugs discovered during testing will be identified and resolved.
This may involve adjusting thresholds for gesture recognition, optimizing communication
protocols, or refining motor control logic.

1.3.5 System Optimization

After the initial testing and debugging, the system will be optimized for better performance,
including:

• Gesture Sensitivity: Fine-tuning the thresholds for detecting hand gestures, ensuring that
small or large gestures are correctly recognized.

• Real-Time Performance: Minimizing delays between gesture input and robot response.
This will involve optimizing the code for speed and responsiveness.

• Battery and Power Management: Ensuring that the robot car is powered efficiently,
optimizing power consumption, and managing battery usage to prolong operating time.

• User Interface Optimization: If using an IoT platform for remote control, optimizing the
interface for better usability and responsiveness.

1.3.6 Deployment and Documentation

The final phase involves deploying the completed system and documenting the entire process. This
includes:

8
Deployment: The system is fully assembled, tested, and deployed for practical use. The robot car
is ready for demonstration, showing how the hand gestures are used to control the robot in real-
time.

Documentation: Comprehensive documentation will be created to detail the entire project

process, including:

• System Design: Diagrams and explanations of the hardware and software components.

• Code Documentation: Clear, well-commented code explaining the logic for gesture
recognition, motor control, and communication.

• Testing and Results: Detailed testing results, including any challenges faced and how they
were overcome.

• Future Enhancements: Suggestions for future improvements or features that could be

added to the system.

1.3.7 Evaluation and Conclusion

Finally, the project will be evaluated based on the following criteria:

• Functionality: The system must accurately recognize hand gestures and control the robot's
movement accordingly.

• Performance: The system must operate in real-time with minimal latency.

• Usability: The user interface, whether for remote control or monitoring, must be intuitive
and easy to use.

• Reliability: The system should function consistently over extended periods without failure.

The project will conclude with an evaluation of its success in meeting the defined objectives, along
with recommendations for future work.

Summary of the Methodology:

1. Requirements Gathering and Analysis: Identifying hardware and software requirements,

analyzing system constraints.

9
 2. System Design and Architecture: Designing hardware setup and software logic, including
system architecture.

3. Component Integration and Development: Assembling the robot, coding the system for
gesture recognition, motor control, and wireless communication.

4. Testing and Debugging: Testing each component and the entire system for functionality
and performance.

5. System Optimization: Fine-tuning the system for better performance and usability.

6. Deployment and Documentation: Final deployment and creation of comprehensive

project documentation.

7. Evaluation and Conclusion: Assessing the project’s success and potential for future
improvements.

This methodology ensures a structured and systematic approach to developing the Hand Gesture
Control Robot Car, facilitating successful completion and thorough evaluation of the project.

1.4 Organization Of The Project

The Hand Gesture Control Robot Car project is structured into several chapters, each focusing on
a specific aspect of the project, from the initial concept to the final implementation and evaluation.
Below is an outline of how the project is organized, along with a brief description of the content
and objectives of each chapter.

Chapter 1: Overview of the Project

This chapter provides a comprehensive introduction to the Hand Gesture Control Robot Car
project. It includes:

• The project background and context, explaining the relevance of the project in the field of
robotics and IoT.

• The motivation behind the project, highlighting the need for intuitive, hands-free control
systems.

10
 • The problem statement, identifying the limitations of existing robotic control methods and
how gesture-based control can address them.

• The objectives of the project, specifying the goals to be achieved, including gesture
recognition, wireless communication, and motor control.

• The scope of the project, outlining the boundaries and key components involved.

• An overview of the key components required for the system, such as the Arduino Uno,
NodeMCU, accelerometer, and motor driver.

• The deliverables and outcomes expected from the project.

Chapter 2: Literature Review

In this chapter, existing research and developments related to gesture-based control systems and
IoT robotics are reviewed. This includes:

• Related works on gesture recognition technologies, accelerometers, and motor control in

robotics.

• A review of IoT integration in robotics, exploring how wireless communication has been
applied in similar projects.

• A comparison of different types of gesture recognition systems, including their pros and
cons.

• An analysis of technological advancements that have influenced the design of the system,
such as advancements in microcontrollers, sensors, and wireless communication modules.

This chapter aims to provide a theoretical foundation for the project by identifying relevant
technologies, systems, and methods that can be applied.

Chapter 3: System Design and Architecture

This chapter outlines the design and architecture of the Hand Gesture Control Robot Car system.
It covers:

• The overall system architecture, explaining how each component (accelerometer, Arduino,
motor driver, NodeMCU) interacts with one another.

11
 • Detailed hardware design, including the selection of components and how they are
integrated to form the robot.

• Software design and the algorithms used for gesture recognition, motor control, and
communication protocols.

• The design of the wireless communication system using NodeMCU, detailing how the
robot will be controlled remotely via IoT.

• Diagrams, such as block diagrams and flowcharts, illustrating the system’s architecture and
data flow.

The aim of this chapter is to present a clear understanding of how the system is structured and how
the various components are connected.

Chapter 4: Implementation

This chapter discusses the implementation of the Hand Gesture Control Robot Car, including:

• The hardware assembly process, including the connection of sensors, motors, and the
microcontroller.

• The development of the software code for the accelerometer, motor control, and wireless
communication.

• The integration of gesture recognition algorithms with the hardware, detailing how hand
movements are translated into robot actions.

• The setup of IoT communication using NodeMCU, allowing for remote control and
monitoring of the robot.

• Code snippets and explanations of key sections of the software that handle data processing,
gesture recognition, and motor control.

The goal of this chapter is to provide a detailed walkthrough of the practical steps taken to assemble
and program the system.

Chapter 5: Testing and Results

12
This chapter focuses on the testing phase of the project, which ensures that the system operates as
expected. It includes:

Unit testing of individual components (accelerometer, motor driver, NodeMCU) to verify

functionality.

System integration testing, which involves testing the complete system (gesture recognition, motor
control, wireless communication) to ensure they work together seamlessly.

Performance evaluation of the system, including:

1. responds to hand gestures. Accuracy of gesture recognition: Assessing how well the
system detects and

2. Response time: Measuring the latency between gesture input and robot movement.

3. Reliability of wireless communication: Testing the stability of the remote control

via IoT.

Results from various test scenarios, including any challenges faced during dressed.

• Feedback and improvements: Identifying areas for system optimization and refinement
based on testing results.

The objective of this chapter is to ensure that the system functions reliably and meets the project’s
specifications.

Chapter 6: System Optimization and Enhancements

This chapter discusses the steps taken to optimize the system for better performance. It includes:

• Optimization of gesture recognition: Fine-tuning the threshold values for detecting gestures
to improve accuracy and reduce false positives.

• Enhancement of wireless communication: Improving the speed and reliability of the

NodeMCU communication for remote control.

• Power management: Strategies for reducing power consumption and optimizing battery life,
including optimizing motor control and sensor data sampling.

13
 • User interface improvements: If applicable, enhancing the IoT platform interface for
smoother interaction with the robot.

• Potential future enhancements, such as adding more complex gestures, increasing robot
capabilities (e.g., obstacle avoidance), or integrating additional sensors.

The aim of this chapter is to make the system more efficient and robust, improving the overall user
experience and performance.

Chapter 7: Conclusion and Future Work

The final chapter concludes the project by summarizing its main findings and achievements. It
includes:

• A summary of the project objectives and whether they were successfully achieved.

• A discussion on the contributions of the project to the field of robtics, IoT, and gesture-
based control systems.

• An analysis of the limitations encountered during the project and how they were overcome.

• Suggestions for future work, such as possible improvements to the robot, the addition of
more advanced features (e.g., machine learning for gesture recognition), or applications in
different fields.

This chapter serves as the wrap-up of the project, providing a reflection on the work completed
and outlining potential directions for future research or development.

14
 CHAPTER 2

LITERATURE REVIEW
The Hand Gesture Control Robot Car project draws upon several key concepts and technologies
that have been explored in existing research and development in the fields of gesture recognition,
robotics, and IoT (Internet of Things). This chapter provides a comprehensive review of relevant
literature, identifying the key technologies, methods, and trends that have shaped the design and
development of this project. It highlights existing work in gesture-controlled systems, wireless
communication, and IoT integration in robotics.

2.1 Gesture Recognition Systems

Gesture recognition refers to the process of interpreting human gestures using electronic devices,
often employing sensors such as accelerometers, gyroscopes, or cameras. In the context of the
Hand Gesture Control Robot Car, the gesture recognition system is critical for translating user
movements into commands that control the robot [1].

2.1.1 Accelerometer-Based Gesture Recognition

Accelerometers are widely used in gesture recognition systems due to their ability to measure
acceleration and movement along multiple axes (X, Y, and Z). Inertial sensors like MPU6050,
ADXL335, and ADXL345 are particularly popular for their precision in detecting orientation
changes and movement patterns[2].

• MPU6050: The MPU6050 is a six-axis motion tracking device that combines a 3-axis
accelerometer and a 3-axis gyroscope. Studies show that it is highly effective for detecting
simple hand gestures such as tilt, shake, and rotation, which can be mapped to directional
commands for robot control.

• ADXL335: The ADXL335 is another popular choice in gesture-based control applications,

known for its low power consumption and compact size. It is used in applications where
high accuracy in gesture recognition is required[3].

These accelerometer-based systems typically involve setting thresholds for acceleration changes
that correspond to specific gestures (e.g., a forward tilt for moving the robot forward). The system

15
then processes the raw data from the accelerometer, translates it into a gesture, and converts that
gesture into a command for the robot.

2.1.2 Vision-Based Gesture Recognition

Although not the primary focus of this project, vision-based gesture recognition remains an
important area of research. These systems use cameras or depth sensors (e.g., Microsoft Kinect or
Leap Motion) to track the user’s movements. Computer vision algorithms then analyze the image
data to recognize hand movements[4].

While vision-based systems offer rich and more complex gesture recognition, they require higher
computational resources and are more sensitive to environmental conditions (lighting, background,
etc.). They are also typically more complex to implement compared to accelerometer-based
solutions, which makes them less suited for low-cost, embedded systems such as the one developed
in this project.

2.1.3 Challenges In Gesture Recognition

Despite advances, gesture recognition still faces several challenges:

• Noise and interference: Accelerometer data can be noisy, especially if the sensor is subject
to vibrations or erratic movements. Various filtering techniques such as Kalman filters and
low-pass filters are often employed to smooth out this noise[5].

• Gesture ambiguity: Overlapping gestures can lead to misinterpretation. Fine-tuning the

threshold values and using machine learning algorithms to improve accuracy are
approaches being explored to mitigate this issue [6].

• Real-time processing: Real-time response is critical for gesture-based control systems.

Ensuring low-latency processing and rapid feedback requires optimization of both
hardware and software[7].

2.2 Wireless Communication And Iot Integration

The integration of IoT technologies allows the robot to be controlled remotely, enabling wireless
communication between the robot and the user. NodeMCU, which incorporates the ESP8266 Wi-
Fi module, is commonly used in IoT-based robotics for low-cost, wireless communication[8].

16
2.2.1 Iot In Robotics
The integration of IoT with robotics opens up a variety of possibilities, from simple remote control
to advanced features such as cloud-based monitoring and data analytics. IoT technologies are
particularly useful in scenarios where long-range control, monitoring, or automation is required.
In many systems, Wi-Fi, Bluetooth, and Zigbee are used to communicate with robots, with Wi-Fi
being the most common for long-range communication due to its availability and ease of setup [9].

• NodeMCU and ESP8266: The NodeMCU platform, based on the ESP8266

microcontroller, is a low-cost solution for embedding Wi-Fi capabilities into a wide range
of devices, including robots. The NodeMCU provides seamless integration with platforms
such as Blynk, ThingSpeak, or custom-built cloud systems, making it ideal for remote
control and monitoring in robotic applications (Dinesh et al., 2019).

2.2.2 Remote Control Of Robots Via Iot

Wireless remote control via IoT typically involves controlling a robot via a mobile application or
web interface that sends commands through the cloud to the robot. The NodeMCU facilitates this
communication by connecting the robot to the internet, allowing it to receive control commands
from anywhere in the world[10].

Research in this domain has focused on:

• Security: Ensuring secure communication between the robot and user is vital. Common
methods involve using encryption (e.g., SSL/TLS) and authentication mechanisms to
protect communication (Madhusree et al., 2020).

• User Interface: Developing intuitive and easy-to-use mobile apps or web dashboards that
interact with IoT-enabled robots. Platforms like Blynk and ThingSpeak are often used to
create these interfaces due to their ease of integration and real-time data streaming
capabilities.

2.3 Robot Control And Actuators

The robot car in this project relies on motor drivers and DC motors to move according to the
commands generated by the gesture recognition system. The design and control of robotic
actuators are essential to ensure precise movement and response to user commands[11].

17
2.3.1 Motor Control Using Arduino
Arduino-based motor control has become a standard for small robot projects. The L298N motor
driver is commonly used in such systems because it can control the direction and speed of motors
based on input signals from the Arduino. The motor driver interfaces between the low-power
microcontroller and the high-power motors, protecting the controller from high currents[12].

• H-Bridge Motor Control: The L298N uses an H-Bridge configuration to control the
motors. The motor’s direction and speed can be controlled by adjusting the PWM signals
sent from the Arduino, making it an efficient way to control robotic movement
(Bastarrachea et al., 2017).

2.3.2 Challenges in Motor Control

Motor control involves challenges related to:

• Speed control: Maintaining smooth movement of the robot requires precise PWM control
to adjust the speed of the motors.

• Direction control: Ensuring that the motors react instantly and accurately to gesture-based
inputs, which requires real-time processing.

2.4 Applications of Gesture-Controlled Robots

Gesture-controlled robots have been applied in several domains, including:

• Assistive Technology: Gesture-controlled robots have been explored for use by people
with disabilities, enabling them to control robots or assistive devices without needing a
traditional input device [13].

• Entertainment: Gesture control has been integrated into gaming systems where users can
control robots or avatars through their hand movements.

• Industrial Automation: Gesture-controlled robots are being considered for use in

environments where hands-free control is needed, such as manufacturing lines or
hazardous environments [14].

18
 CHAPTER 3

PROJECT DESCRIPTION

3.1 Block Diagram

Fig 1: BLOCK DIAGRAM

This system enables a robotic vehicle to be controlled using hand gestures. The transmitter section
detects and processes gestures, converting them into commands, while the receiver section
interprets these commands and controls the vehicle accordingly.

19
TRANSMITTER SECTION:

The transmitter is responsible for detecting gestures, processing them, and sending commands to
the robotic vehicle. It consists of the following modules:

1. Start Transmitter

When powered on, the transmitter system initializes its components.Ensures all modules, including
the microcontroller (ATmega 32), sensors, and communication modules, are ready.

2. Initialize Arduino

The Arduino microcontroller initializes hardware components and loads necessary libraries for
gesture processing.The system checks sensor connections, verifies power levels, and ensures stable
communication with peripherals.

3. Setup LCD Display

An LCD display (16x2 or OLED) is used to provide real-time feedback on detected gestures and
system status.

Displays messages such as:

“System Ready” – when initialization is complete.

“Gesture Detected: Move Forward” – when a valid gesture is recognized.

“Error: Unrecognized Gesture” – when an invalid gesture is detected.

4. Initialize Button Matrix

A button matrix is included as an alternative control mechanism.Provides manual control if gesture

recognition fails.

Common button functions:

Button 1: Move forward

Button 2: Move backward

20
 Button 3: Turn left

Button 4: Turn right

Button 5: Stop

5. Read Gesture Input (MPU6050 Accelerometer)

The MPU6050 accelerometer detects hand movement and orientation.It measures acceleration
along X, Y, and Z axes and angular velocity using a gyroscope.The data is captured in real-time
to track hand motions.

6. Process Gesture Data

The raw sensor values from the MPU6050 are processed using algorithms such as:

Kalman filtering – removes noise and improves accuracy.Threshold-based classification – maps

sensor values to predefined gestures.The processed gesture is compared with predefined
movement patterns stored in the Arduino's EEPROM or flash memory.

8. Transmit Command (Bluetooth HC-05 Module)

The processed command is transmitted wirelessly via the HC-05 Bluetooth module.Uses 2.4
GHz frequency with a 9600 baud rate for reliable data transfer.

Example Commands:

FWD – Move Forward, BWD – Move Backward, LFT – Turn Left, RGT – Turn Right, STP –
Stop.

RECEIVER SECTION:

The receiver section is responsible for receiving the transmitted commands, decoding them, and
controlling the robot’s movement.

1. Start Receiver

The receiver initializes its microcontroller and communication modules.Checks for incoming
Bluetooth signals and ensures all components are functioning properly.

2. Initialize ESP32 Camera (Optional)

21
If included, the ESP32 camera module provides a live video feed.Useful for remote surveillance
or autonomous navigation.

3. Setup Motor Driver (L298N / L293D)

The motor driver (L298N or L293D) is initialized to control the DC motors.Handles motor
direction and speed regulation using Pulse Width Modulation (PWM) signals.

Motor Connections:

Input1 & Input2: Control motor A (left motor).

Input3 & Input4: Control motor B (right motor).

Enable Pins: Adjust motor speed using PWM signals.

4. Receive Command (Bluetooth HC-05)

The receiver listens for Bluetooth signals sent by the transmitter.Parses received data and extracts
movement instructions.

Example Received Data Packet:

[START] FWD [CHECKSUM] [END]

The system verifies the checksum to ensure data integrity.

5. Decode Command

The received command is compared with predefined control instructions. If a valid command is
found, it is sent to the motor control module.

6. Process Motor Control

The microcontroller interprets the decoded command and activates the corresponding motor
control signals.The PWM duty cycle is adjusted to regulate motor speed.

7. Control DC Motors

The L298N motor driver controls the DC motors to move the robot.The robot responds in real-
time to user hand gestures.

22
5.Wireless Communication (Bluetooth HC-05)

The HC-05 Bluetooth module enables two-way wireless communication.Operates on a 2.4 GHz
RF frequency with a range of ~10 meters.Uses UART (TX/RX) serial communication to interface
with the microcontroller.

Data Transmission Format:

<Start> <Command> <Checksum> <End>

Example:

<S> FWD <X> <E>

Where:

S = Start byte

FWD = Move forward command

X = Checksum for error detection

E = End byte

3.2 Proposed Methodology

3.2.1 Methodology For Communication Signal

3.2.2Transmitter Module
An RF transmitter module is a small PCB i.e., printed circuit board sub-assembly capable of
transmitting a radio wave and modulating that wave to carry data. Transmitter modules are usually
implemented alongside a micro controller which will provide data to the module which is
transmitted. RF transmitters are usually subject to regulatory requirements which dictate the
maximum allowable transmitter power output, harmonics and band edge requirement. The
transmitter module of the gesture control robot consists of an accelerometer, a microcontroller, and
a wireless communication module. The accelerometer detects hand movements and provides raw
X, Y, and Z-axis values, which are processed by the microcontroller. To ensure accuracy, filtering
techniques such as a Kalman filter or moving average can be applied to remove noise. The

23
processed data is then mapped to specific gestures, such as tilting forward to move the robot
forward or tilting left to turn left. Once a gesture is recognized, the microcontroller encodes the
corresponding command into a data packet and transmits it wirelessly using modules like
nRF24L01, HC-12, Bluetooth, or Wi-Fi. To maintain reliable communication, error-checking
mechanisms like CRC or checksum can be implemented.

3.2.3 Receiver Module

An RF Receiver module nRF24L01 is 433 MHz radio receiver receives the modulated RF signal,
and then it demodulates . There are two types of RF receiver module. Super-regenerative modules
are usually of low cost and low power designs using a series of amplifiers use to extract modulated
data from a carrier wave. Super-regenerative modules are generally imprecise as their frequency
of operation varies in a fair amount with temperature and power supply voltage. Super heterodyne
receivers having a performance advantage over super regenerative; they offer increased an
accuracy and stability over a large voltage and temperature range. This stability comes from a fixed
crystal design which in turn leads to a comparatively more expensive product. Radio receiver
which receives the transmitted coded from the remote place these codes are converted to digital
format and output is available to the pin no 2 of the ic2 master microcontroller; this is the pin of
inbuilt art of the microcontroller. We Based on the input codes master will give command to slave
microcontroller and robot will behave as follows. Moves in forward direction Moves in reverse
direction, Speed controls in both the direction can even turn left or right while moving forward or
in reverse direction. In case of bump, moves reverse turn left or right and wail for the next
instruction. On the spot left or right turn to pass through the narrow space We have also added
head light, back light and turning lights to left a right.

3.2.4 Methodology For Motion Control

L298N is a dual H-bridge motor driver integrated circuit (IC). Motor drivers act as current
amplifiers as they take a low-current control signal and provide a higher-current signal. This higher
current signal is used to drive the motors. L298N contains two inbuilt H-bridge driver circuits. In
common mode of operation, two DC motors can be driven simultaneously, both in forward and
reverse direction. The motor operations of two motors can be controlled by input logic. When an
enable input is high, the associated driver gets enabled. As a result, the outputs become active and
work in phase with their inputs. Similarly, when the enable input is low, that driver is disabled, and

24
their outputs are off and in the high-impedance state. This project controls a remote robot through
RF. The ordinary 433 MHz RF modules are used in this project. Arduino microcontroller is used
in this project. These robots are used basically for industrial applications. This is an improved
version of the joy stick control robot which has been designed years ago. Intelligent spy robot
project has been designed for the spying purpose .it is radio controlled and can be operated at a
radial distance of 100m radius. Most probably our army youth need to venture into the enemy area
just to track their activities. Which is often a very risky job and may cost precious life? Such
dangerous job could be done using small spy robot all the developed and advance nations are in
the process of making it, a robot that can fight against enemy. Our robot us just a step towards
similar activity. Heart of our robot is microcontroller, we are using ARDUINO uno, ARDUINO
nano in these two microcontrollers the first microcontroller which acts as a transmitter micro
controller, encodes all the commands to RF transmitter. Then, the RECEIVER Microcontroller is
responsible for executing all the commands from the transmitter through the RF transmitter and it
gives the command to moto driver circuit which drives 4 Nos. of. Motors. Transmission through
RF (Radio frequency) is better than IR (infrared) because of many reasons. Firstly, signals through
RF can travel through larger distances making it suitable for long range applications. Also, while
IR mostly operates in line Of sight mode, RF signals can travel even when there is an obstruction
between transmitter & receiver. Next, RF transmission is more strong and reliable than IR
transmission. RF communication uses a specific frequency unlike IR signals which are affected by
other IR emitting sources. This RF module comprises of an RF Transmitter and an RF Receiver.
The transmitter/receiver (TX/RX) pair operates at a frequency of 433MHz an RF transmitter
receives serial data and transmits it wirelessly through RF through its antenna connected at pin4.
The transmission occurs at the rate of 1Kbps-10Kbps. The transmitted data is received by an RF
receiver operating at the same frequency as that of the transmitter.

25
3.3 Circuit Diagram

3.3.1 Transmitter

Fig 2 :TRANSMITTER

The transmitter circuit is designed to send data wirelessly using a combination of an ATmega
microcontroller, an MPU6050 accelerometer, a Bluetooth module, and supporting components.
Below is a detailed explanation of each component and its function:

1. ATmega-32 Chip

The ATmega-32 microcontroller is the central processing unit of the transmitter circuit. It is
responsible for processing the sensor data from the MPU6050 and transmitting it via the Bluetooth
module. The microcontroller is programmed to read inputs from the accelerometer and send the
processed data to the Bluetooth module.

2. MPU6050 Accelerometer

26
The MPU6050 is a 6-axis motion tracking sensor that includes a 3-axis accelerometer and a 3-axis
gyroscope. It detects changes in orientation and movement. The sensor data is read by the ATmega-
32 chip using the I2C communication protocol.

3.Bluetooth Module

The Bluetooth module, likely an HC-05 or HC-06, is used to establish a wireless communication
link. It receives data from the microcontroller and transmits it wirelessly to a receiver module,
such as a smartphone or another microcontroller.

4. Capacitor

A capacitor is included in the circuit to stabilize voltage fluctuations and filter out noise. It ensures
smooth operation of the microcontroller and other connected components.

5. Battery

A 9V battery is used as the power source for the circuit. It provides the necessary voltage to the
microcontroller and other components through proper voltage regulation.

3.3.2 Receiver
1. Arduino Uno :The core microcontroller that processes commands received from the Bluetooth
module and sends control signals to the motor driver for movement execution.

2. HC-05 Bluetooth Module : A wireless communication module that acts as a receiver, receiving
commands from a remote controller or mobile application and sending them to the Arduino for
processing.

3. ESP32-CAM Module : A Wi-Fi-enabled camera module that captures real-time video and
transmits it wirelessly for remote monitoring and navigation.

4. L298N Motor Driver : Controls the speed and direction of the motors based on the signals
received from the Arduino, allowing smooth and precise movement.

5. Motors (Front Left, Front Right, Back Left, Back Right) : These four DC motors drive the
robot, executing movements such as forward, backward, turning left, and turning right.

27
6. 18650 Battery Pack (7.4V - 12V) : A rechargeable battery pack that provides the necessary
power to run all receiver components, ensuring stable operation.

Fig 3 : RECIEVER

28
Switch : manual power switch that allows turning the receiver circuit on or off, helping conserve
battery life when the system is not in use.

3.4: Hardware Components

3.4.1 nodemcu :
Introduction to NodeMCU :

NodeMCU is an open-source development board based on the ESP8266 Wi-Fi module. It is widely
used in IoT (Internet of Things) applications due to its compact size, affordability, and ability to
connect to wireless networks. The NodeMCU board integrates the ESP8266 microcontroller with
additional features such as GPIO pins, PWM outputs, and serial communication interfaces. It also
supports programming via the Arduino IDE, which makes it accessible for developers who are
familiar with the Arduino environment.

In the context of the hand gesture-controlled robot car, the NodeMCU will be used to handle
communication between the car and the user's mobile device or controller. This chapter will
explore the features of the NodeMCU, its advantages in the system design, and the communication
modules that will be used to facilitate remote control and interaction.

Fig 4: NODEMCU MODULE

Features of NodeMCU

The NodeMCU board provides several important features that make it suitable for embedded
system applications such as robotics and IoT:

29
3.4.2 ESP8266 Microcontroller:
• The ESP8266 is a low-cost Wi-Fi System on Chip (SoC) that supports 802.11 b/g/n Wi-Fi
standards.

• The chip includes a Tensilica Xtensa LX106 core processor, which operates at a clock
speed of up to 80 MHz and has 64 KB of instruction RAM and 80 KB of data RAM.

Fig 5:ESP8266 Microcontroller

Wi-Fi Connectivity:

• NodeMCU provides seamless Wi-Fi connectivity, enabling wireless

communication with a mobile app, computer, or cloud service, which is crucial for
controlling the robot car remotely.

3.4.3 GPIO Pins:

• The board includes multiple General Purpose Input/Output (GPIO) pins that can be used
to interface with sensors, actuators, and other peripherals.

• These pins support digital input/output, PWM, ADC (analog to digital conversion), and
other functions essential for controlling various components in the robot car.

30
 Fig 6:GPIO PINS
Fi 6 : GPIO PINS
I/O Pin Mapping

The NodeMCU board offers 11 GPIO pins for general-purpose tasks, such as connecting sensors,
motors, or other peripherals. Each of these pins can be configured for different functions
(input/output, PWM, ADC, etc.) depending on the requirements of the system. Here’s a summary
of the I/O pins and their functionalities:

Pin
Pin Name Functionality
Number

General I/O (not PWM or

D0 GPIO16
ADC)

D1 GPIO5 I2C SDA, PWM, General I/O

D2 GPIO4 I2C SCL, PWM, General I/O

D3 GPIO0 PWM, Interrupts, General I/O

D4 GPIO2 PWM, Interrupts, General I/O

D5 GPIO14 PWM, SPI, General I/O

D6 GPIO12 PWM, SPI, General I/O

D7 GPIO13 PWM, SPI, General I/O

31
 Pin
Pin Name Functionality
Number

D8 GPIO15 PWM, SPI, General I/O

RX GPIO3 UART RX (Serial)

TX GPIO1 UART TX (Serial)

TABLE 1: PIN MAPPING

3.4.2 Bluetooth Module

The Bluetooth Module is an essential communication module in the hand gesture-controlled robot
car project, enabling wireless communication between the NodeMCU and a controlling device
such as a smartphone, tablet, or computer. The Bluetooth module provides a convenient way to
control the robot from a short distance, offering an easy interface for user commands. In this
project, the HC-05 Bluetooth module, one of the most commonly used Bluetooth modules in
embedded systems, is typically employed.

This section explains the Bluetooth module, its components, working principles, and its application
in the hand gesture-controlled robot car project.

Fig 7 : BLUETOOH MODULE

Overview of Bluetooth Module (HC-05)

32
The HC-05 is a Bluetooth 2.0 module that operates in master and slave modes. It allows
communication between a Bluetooth-enabled device (such as a smartphone or PC) and
microcontrollers like the NodeMCU. The HC-05 module is highly popular for simple and cost-
effective wireless communication due to its ease of use and integration with various platforms.

Working Principles of Bluetooth Communication:

The Bluetooth module allows the NodeMCU to communicate wirelessly with Bluetooth-enabled
devices by utilizing serial communication (UART). The communication between the NodeMCU
and the HC-05 Bluetooth module is bidirectional, meaning both devices can send and receive data.

1. Connecting the HC-05 to NodeMCU:

• TX (HC-05) → RX (NodeMCU).

• RX (HC-05) → TX (NodeMCU).

• VCC (HC-05) → 3.3V (or 5V depending on the voltage regulator used).

• GND (HC-05) → GND (NodeMCU).

2. Pairing:

• The HC-05 module must first be paired with a Bluetooth-enabled device (e.g., a
smartphone). Once paired, a communication link is established, allowing the
NodeMCU to receive data (commands) from the smartphone and respond
accordingly.

3. Communication Protocol:

• UART Protocol: The NodeMCU sends and receives data to/from the HC-05 via the
TX/RX pins. Data is transmitted over a serial link at a defined baud rate (9600 bps
by default).

• The NodeMCU interprets the data received from the Bluetooth device (e.g.,
forward, backward, left, right gestures for controlling the robot) and executes the
appropriate commands to move the robot.

4. Controlling the Robot:

33
 • User Input: The user can control the robot through an app (such as a custom Android or
iOS app) that sends Bluetooth commands via touch gestures or button presses.

• Command Processing: When the NodeMCU receives the command via Bluetooth, it
processes the input and controls the robot's motors or actuators accordingly, such as moving
forward or turning.

3.4.4 Applications in the Hand Gesture-Controlled Robot Car

In this project, the Bluetooth module (HC-05) plays a critical role in enabling wireless
communication between the NodeMCU and the control device. The following are the key use
cases for the Bluetooth module in the gesture-controlled robot car project:

1. Control Interface:

• A smartphone app or a custom Bluetooth control interface on a computer can be

used to send commands to the NodeMCU. The app sends the control signals to the
HC-05 via Bluetooth, and the NodeMCU executes the corresponding movement
actions on the robot.

• The user interface may display directional buttons or a joystick to control the
movement of the robot based on hand gestures.

2. Wireless Hand Gesture Recognition:

• The robot car uses sensors such as an accelerometer and gyroscope (e.g.,
MPU6050) to recognize the user’s hand gestures (e.g., tilt or rotation) and translates
these into commands for movement.

• The NodeMCU processes the gestures from the sensors and, using the Bluetooth
module, communicates with the control device for additional input or to send data
(e.g., battery status or obstacle warnings).

3. Real-Time Movement Control:

The Bluetooth module enables the real-time transmission of control signals. When the user
moves their hand in a specific direction, the NodeMCU receives the command and adjusts
the robot's motion instantly. For example:

34
 ▪ Forward gesture → Move robot forward.

▪ Left/right gesture → Turn the robot.

▪ Stop gesture → Stop the robot.

4. Remote Diagnostics and Monitoring:

• The Bluetooth module can be used to send diagnostic information from the NodeMCU to
the smartphone app. This could include battery status, motor health, sensor data, or other
telemetry that helps monitor the robot’s performance remotely.

3.5 Nrf24l01 Wireless Transceiver:

The NRF24L01 is a 2.4 GHz wireless transceiver module widely used in embedded systems and
IoT applications for short-range wireless communication. In the context of the hand gesture-
controlled robot car project, the NRF24L01 module can be employed to enable communication
between the robot and a remote control unit (such as another microcontroller or a computer),
providing an alternative to Bluetooth or Wi-Fi communication.

The NRF24L01 is known for its efficiency, small size, and ease of integration with various
microcontrollers, including the NodeMCU and Arduino platforms. It provides low-power, reliable
communication over short to medium distances, making it suitable for controlling the robot car
remotely.

This section outlines the features, working principles, and applications of the NRF24L01 in the
hand gesture-controlled robot car project.

Fig 8 :NRF24L01 WIRELESS TRANSCEIVER

35
Working Principles of NRF24L01
The NRF24L01 operates by sending and receiving data wirelessly via its 2.4 GHz frequency. The
module communicates with the microcontroller through the SPI interface (with MISO, MOSI,
SCK, and CSN pins), allowing the NodeMCU to send and receive data packets. Here’s how it
works:

1. Initialization:

• First, the NRF24L01 module is initialized through the SPI interface. The
microcontroller (e.g., NodeMCU) configures the module for communication by
setting parameters such as data rate, channel, and address.

• The module is configured as either the transmitter or receiver, depending on the

role in the communication process.

2. Transmission:

• When the NodeMCU (acting as the transmitter) receives input (e.g., hand gestures
from the accelerometer and gyroscope), it encodes the control data and sends it to
the NRF24L01 module via SPI.

• The NRF24L01 modulates the data into radio waves and transmits it to the receiver
module using its 2.4 GHz frequency.

3. Reception:

• On the receiving end, the NRF24L01 module (on the robot car) decodes the radio
waves back into digital data, which the microcontroller then processes.

• The NodeMCU receives the command (e.g., forward, backward, left, right) and acts
on it by controlling the motors of the robot..

o The NRF24L01 ensures low-latency, real-time communication, which is crucial for

controlling the robot based on gestures. The system can immediately respond to the
gestures and adjust the robot’s movements in real-time, providing smooth control.

36
3.6 Nfc Module
The NFC (Near Field Communication) module is a short-range wireless communication
technology that allows devices to exchange data when they are in close proximity (typically a few
centimeters). While NFC is primarily used for contactless payments and identification systems, it
can also be employed in IoT projects, including robotics, to enable secure data exchange, user
authentication, and device control.

In the context of the hand gesture-controlled robot car project, the NFC module can be utilized to
enhance the system's interaction by adding a layer of security and authentication. For example, an
NFC-enabled smartphone or card can be used to authorize robot access or initiate control
commands. This functionality allows for secure, localized, and efficient communication,
particularly when additional safety measures or user identification are needed.

This section outlines the key features, working principles, and applications of the NFC module in
the hand gesture-controlled robot car project.

Fig 9 :NFC MODULE

Overview of NFC Module

The NFC (Near Field Communication) module is a wireless communication technology that
works over a very short range, typically between 0 cm to 10 cm. The NFC module allows devices
equipped with an NFC reader and an NFC tag to communicate with each other.

37
In embedded systems, the PN532 NFC module is widely used for implementing NFC
communication. This module is capable of reading and writing data to NFC tags, making it suitable
for applications that require secure communication or identification systems.

Key Features of NFC Module:

1. Short Range Communication:

• NFC operates over short distances (typically up to 10 cm), which provides a level
of security for the communication and prevents unauthorized or accidental data
exchanges.

2. Data Transfer Rate:

• The data transfer rate for NFC is typically around 106 kbps to 424 kbps, which is
suitable for transferring small amounts of data, such as identification information
or control commands.

3. Low Power Consumption:

• The NFC module is designed for low-power operation, making it well-suited for
battery-powered applications like robotics, where energy efficiency is crucial.

4. Ease of Integration:

• The PN532 NFC module uses standard communication protocols such as I2C, SPI,
or UART to interface with microcontrollers. It is easy to integrate into various
platforms, such as NodeMCU or Arduino.

5. Multiple Tag Support:

• The PN532 supports the reading and writing of different types of NFC tags, such
as MIFARE, NTAG, and FeliCa, giving flexibility in terms of the type of tags or
cards used for interaction.

3.7 Introduction To Sensors

Sensors are integral components in the hand gesture-controlled robot car project, as they allow the
robot to detect both the user’s inputs (through hand gestures) and its surrounding environment.

38
These sensors help the robot to translate physical movements and environmental changes into
control signals, enabling the robot to respond accordingly.

In this project, sensors serve two main purposes:

1. Hand Gesture Recognition: Sensors like the accelerometer and gyroscope are used to
detect the orientation and movement of the user's hand. These sensors convert the hand
gestures into actionable commands for controlling the robot's movement, such as forward,
backward, left, or right.

2. Environmental Interaction: Sensors like the ultrasonic and infrared sensors are employed
to detect obstacles and help with navigation. These sensors measure distances and
proximity, enabling the robot to avoid obstacles and navigate safely through its
environment.

The integration of these sensors into the robot car allows for seamless interaction between the user
and the robot, creating a responsive and intuitive control system. The data gathered by these

sensors is processed by the microcontroller (such as NodeMCU or Arduino), which then issues
commands to the robot's motors, adjusting its movement in real time.

Key Sensors Used in the Project:

• Accelerometer

• Gyroscope

• Ultrasonic Sensor

• Infrared Sensor

Each sensor provides a specific function, contributing to the overall efficiency and accuracy of the
system. The following sections will provide more details on each of these sensors, how they work,
and their role in the hand gesture-controlled robot caR.

3.8 Accelerometer For Gesture Control

The accelerometer plays a crucial role in the hand gesture-controlled robot car project, as it is
responsible for detecting the orientation and movement of the user’s hand. By measuring the

39
acceleration forces exerted along the X, Y, and Z axes, the accelerometer enables the robot to
interpret the user's hand gestures and translate them into control signals that guide the robot’s
actions. This allows for intuitive control, where the robot responds in real-time to the position and
movement of the user's hand.

Fig10 :ACCELEROMETER

3.8.1 Introduction to L298N Motor Driver

The L298N motor driver is an integrated circuit (IC) that enables control over the direction and
speed of DC motors and stepper motors. It is one of the most commonly used motor drivers in
robotics and other embedded systems because of its ability to handle relatively high voltages and
currents. The L298N is particularly useful for controlling motors in systems where a
microcontroller, such as an Arduino or NodeMCU, is used to drive the motors.

In the context of the hand gesture-controlled robot car, the L298N motor driver is employed to
control the motors based on the signals received from the NodeMCU, which processes the
accelerometer data and translates hand gestures into movement instructions for the robot.

The L298N motor driver is a dual H-bridge driver, which means it can control two motors
independently, allowing the robot to move in different directions. It can control the motors'
direction and speed by using both digital signals for direction and PWM (Pulse Width Modulation)
for speed.

40
 Fig11:L298N Motor Drive

3.8.2 DC Motor Control

In the context of the gesture-controlled robot car project, DC motors (Direct Current motors) are
used to provide the driving force that propels the robot. The control of these motors is crucial for
achieving the desired movement and behavior of the robot. The L298N motor driver is used to
interface with the NodeMCU and control the DC motors in terms of direction and speed. This
section focuses on understanding how DC motor control works within the robot, particularly the
motor driver logic, motor control techniques, and how the motors respond to the signals provided
by the NodeMCU.

Fig 12: DC MOTOR

Working Principle of a DC Motor

A DC motor consists of two primary components:

41
 1. Stator: The stationary part of the motor that generates a magnetic field. This is usually a
permanent magnet or an electromagnet.

2. Rotor (Armature): The rotating part of the motor that is powered by an electric current
and interacts with the magnetic field of the stator.

When current flows through the armature (rotor), a magnetic field is generated, and the interaction
between the magnetic field of the stator and the rotor causes the rotor to rotate. The direction of
rotation of the DC motor depends on the direction of current flow through the motor windings, and
the speed depends on the amount of current supplied.

3.8.3 Capacitor
Power management is a critical aspect of any embedded system, especially when dealing with
motors and wireless communication modules. In a gesture-controlled robot car project, power
management ensures that the system operates efficiently and reliably by providing stable voltage
levels to the various components. This section will focus on the power supply system, including
the use of 47µF capacitors to improve performance and ensure stability.

Fig13: CAPACITOR

3.8.4 Small On/Off Button Circuitry

The On/Off button circuitry plays a critical role in turning the gesture-controlled robot car on and
off, providing an efficient and reliable way to control the power supply to the robot's electronics,
motors, and communication modules. This section outlines the components, working principle,
and design of the small On/Off button circuit, which is essential for controlling the power state of
the robot car.

42
 Fig14: On/Off Button Circuitry

3.9 Introduction Of Arduino

Arduino Uno is a microcontroller board, developed by Arduino based on the Atmega328
microcontroller and is marked as the first Arduino board developed. The software used for writing,
compiling & uploading code to Arduino boards is called Arduino IDE (Integrated Development
Environment), which is free to download from Arduino Official Site. It has an operating voltage
of 5V while the input voltage may vary from 7V to 12V.Arduino UNO has a maximum current
rating of 40mA, so the load shouldn't exceed this current rating or you may harm the boar. It comes
with a crystal oscillator of 16MHz, which is its operating frequency. Arduino Uno Pinout consists
of 14 digital pins starting from D0 toD13.It also has 6 analog pins starting from A0 to A5. It also
has 1 Reset Pin, which is used to reset the board programmatically. In order to reset the board, we
need to make this pin LOW. It also has 6 Power Pins, which provide different voltage levels.

The Arduino UNO is a standard board of Arduino. Here UNO means 'one' in Italian. It was named
as UNO to label the first release of Arduino Software. It was also the first USB board released by
Arduino. It is considered as the powerful board used in various projects. Arduino developed the
Arduino UNO board. Arduino UNO is based on an ATmega328P microcontroller. It is easy to use
compared to other boards, such as the Arduino Mega board, etc. The board consists of digital and
analog Input/Output pins (I/O), shields, and other circuits. Arduino is an open source platform
based around programmable development boards that can be integrated into a range of simple and
complex projects. The Arduino family consists of different types of development boards, with the
most common being. the Arduino UNO. An Arduino board contains a microcontroller which can
be programmed to sense and control devices in the physical world. The microcontroller is able to
interact with a large variety of components such as LEDs, motors and displays. Because of its

43
flexibility and sustainability, Arduino has become a popular prototyping development board which
is widely used across the world.

Types of Arduino:

All boards are entirely open-source, allowing users to build them separately and finally adapt them
to their exact needs. Over the years the different types of Arduino boards have been used to build
thousands of projects, from daily objects to compound scientific instruments. Arduino board is an
open-source platform used to make electronics projects. It consists of both a microcontroller and
a part of the software or Integrated Development Environment (IDE) that runs on your PC, used
to write & upload computer code to the physical board. The platform of an Arduino has become
very famous with designers or students just starting out with electronics, and for an excellent cause.
Unlike earlier programmable circuit boards, the Arduino doesn’t require a separate part of
hardware in order to program a new code onto the board you can just use a USB 10 Cable. As well,
the Arduino IDE uses a basic version of C++, making it simpler to learn the program. At last, the
Arduino board offers a typical form factor that breaks out the functions of the microcontroller into
a more available package.

• Aurdino Uno (R3)

• Arduino Nano
• Arduino Bluetooth
• Arduino Robot 4.3.1 ARDUINO UNO(R3):

ARDUINO UNO R3 :

Arduino UNO is a microcontroller board based on the ATmega328. It has 14 digital input/output
pins 6 analog input pins, a USB Connection, an I2C bus and a reset button .It is an open source
electronic prototyping board which can be programmed easily.

How to use Arduino Board:-

The 14-digital input/output pins can be used as input or output pins by using pin mode(), digital
read() and digital write() functions in arduino programming . Each pin operates at 5V and can
provide or receive a maximum of 40mA current, and has an internal pull-up resistor of 20-50 K

44
Ohms which are disconnected by default . Out of these 14 pins, some pins have specific
functions as listed below:

Fig15 : ARDUINO UNO R3

How to use Arduino Board:-

The 14-digital input/output pins can be used as input or output pins by using pin mode(), digital
read() and digital write() functions in arduino programming . Each pin operates at 5V and can
provide or receive a maximum of 40mA current, and has an internal pull-up resistor of 20-50 K
Ohms which are disconnected by default . Out of these 14 pins, some pins have specific
functions as listed below:

Communication using Arduino Board: Arduino can be used to communicate with a computer,
another Arduino board or other micro controllers. The ATmega328P microcontroller provides
UART TTL (5V) serial communication which can be done using digital pin 0 (Rx) and digital pin
1 (TX). An ATmega328 on the board channels this serial communication over USB and appears
as a virtual com port to software on the computer. The Arduino software includes a serial monitor
which allows simple textual data to be sent to and from the Arduino board. The Arduino software
includes a Wire library to simplify use of the I2C bus.

Arduino Features:

• The operating voltage is 5V

45
 • The recommended input voltage will range from 7v to 12V3.The input
voltage ranges from 6v to 20V
• Digital input/output pins are 14
• Analog i/p pins are 6
• DC Current for each input/output pin is 40 mA7.DC Current for 3.3V Pin
is 50 mA
• Flash Memory is 32 KBSRAM is 2 KB EEPROM is 1 KB
• CLK Speed is 16 MHz 4.9 ARDUINO DIGITAL I/O PIN

Arduino Digital I/O Pins:

The digital inputs and outputs (digital I/O) on the Arduino’s are what allow you to connect sensors,
actuators, and other ICs to the Arduino. Learning how to use the inputs and outputs will allow you
to use the Arduino to do some really useful things, such as reading switch inputs, lighting
indicators, and controlling relay outputs.

Digital Signals:

Unlike analog signals, which may take on any value within a range of values, digital signals have
two distinct values: HIGH (1) or LOW (0). You use digital signals where the input or output will
have one of those two values. 20 For example, one way that you might use a digital signal is to
turn an LED on or off

• LED: There is a built-in LED driven by digital pin 13. When the pin is high value, the LED is
on, when the pin is low, it is off.

• VIN: The input voltage to the Arduino/Genuine board when it is using an external power source
(as opposed to 5 volts from the USB connection or other regulated power source). You can supply
voltage through this pin, or, if supplying voltage via the power jack, access it through this pin.

• 5V: This pin outputs a regulated 5V from the regulator on the board. The board can be supplied
with power either from the DC power jack (7 - 20V), the USB connector (5V), or the VIN pin of
the board (7-20V). Supplying voltage via the 5V or 3.3V pins bypasses the regulator, and can
damage the board.

ARDUINO OPERATING VOLTAGE:

46
• Serial: 0 (RX) and 1 (TX). Used to receive (RX) and transmit (TX) TTL serial data. These pins
are connected to the corresponding pins of the ATmega8U2 USB-to-TTL Serial chip.

• External Interrupts: 2 and 3. These pins can be configured to trigger an interrupt on a low value,
a rising or falling edge, or a change in value. See the attach Interrupt () function for details.

• PWM: 3, 5, 6, 9, 10, and 11. Provide 8-bit PWM output with the analog Write() function.

• LED: 13. There is a built-in LED driven by digital pin 13. When the pin is HIGH value, the LED
is on, when the pin is LOW, it's off.

3.9.1 Car Chassis

This is a longer version of 4 WD double-layer smart car chassis. It comes with the four pairs of
Geared BO DC Motors and Wheels. Bo motor (Battery Operated) lightweight DC geared motor
which gives good torque and rpm at lower voltages. Here you can get BO DC Motor with varying
rated speed. This motor can run at approximately 200 rpm when driven by a single Li-Ion cell.
Great for battery operated lightweight robot Features

▪ Very handy and simple in assembling/disassembling.

▪ Strong components to withstand extreme terrain conditions.

▪ Double-layer structure, much of mounting holes, enough space

▪ Easy to install a variety of control panels, sensors ▪ Educational toys, Ideal for the DIY platform.

Fig 16: CAR CHASSIS

47
3.9.2 Lithium Ion Batteries
Li-ion batteries are a popular choice of rechargeable battery for use in many applications like
portable electronics, automobiles as well as stationary applications for providing uninterruptable
power supply. State of Charge (SoC) and State of Health (SoH) are important metrics of a Li-ion
battery that can help in both battery prognostics and diagnostics for ensuring high reliability and
prolonged lifetime .They are recharged using TP4056 Li-Ion Battery charging Module.

Fig 17: LITHIUM ION BATTERIES

3.9.3 ESP32 Cam Module

The ESP32 CAM Wi-Fi Module Bluetooth with OV2640 Camera Module 2MP For Face
Recognition has a very competitive small-size camera module that can operate independently as
a minimum system with a footprint of only 40 x 27 mm; a deep sleep current of up to 6mA and is
widely used in various IoT and Embedded applications. It is suitable for home smart devices,
industrial wireless control, wireless monitoring, and other applications .This module adopts a
DIP package and can be directly inserted into the backplane to realize rapid production of
products, providing customers with high-reliability connection mode, which is convenient for
application in various hardware terminals. The ESP32-CAM is a development module based on
the ESP32 microcontroller, designed for computer vision and wireless connectivity applications.
It is widely used in Internet of Things (IoT) projects, surveillance systems, facial recognition,
and remote monitoring. With built-in Wi-Fi and Bluetooth capabilities, it allows real-time image
and video transmission without requiring additional hardware.

One of its key features is the OV2640 camera, capable of capturing images at a resolution of up
to 1600x1200 pixels. Additionally, it includes a microSD card slot, making it easy to store photos
and videos without relying on an external Server.

48
 Fig 18: ESP32 CAM MODULE

3.9.4 Jumper Wires

Fig 19: JUMPER WIRES

Jumper wire are extremely handy component to have on hand, especially when prototyping.
Jumper wire is simply wires that have connector pins at each end, allowing them to be used to
connect two points to each other without soldering . Jumper wires are typically used with
breadboards and other prototyping tools in order to make it easy to change a circuit as needed.
Jumper wire typically come in three versions; male-to male, male-to-female, female-to-female.
The difference between each is in the end point of the wire. Male ends have a pin protruding and
can plug into things, while female ends do not and are used to plug things into .When connecting
two ports on a breadboard, a male-to-male wire is we’ll need.

49
3.9.5 Software Components

3.9.6 Cirkit designer

Fig 20 : CIRKIT DESIGNER

3.9.7 Arduino IDE

The Arduino Integrated Development Environment (IDE) is a popular open-source software used
for programming Arduino microcontroller boards. It provides a simple yet powerful platform for
writing, compiling, and uploading code, making it accessible to beginners and experienced
developers alike. The Arduino IDE supports C and C++, incorporating Arduino-specific libraries
that simplify hardware interaction. It is widely used in projects ranging from basic LED blinking
to complex robotics, automation, and IoT applications.

One of the key features of the Arduino IDE is its user-friendly interface, which includes a code
editor with syntax highlighting, auto-indentation, and error detection. The IDE also has a built-in
compiler that converts the written code into machine language and an uploader that transfers it to
the connected Arduino board via USB. Additionally, the Serial Monitor and Serial Plotter allow
users to debug and visualize real-time data from sensors and other connected devices.

50
The software supports a variety of Arduino boards, including the Arduino Uno, Mega, Nano, and
Due, along with third-party microcontrollers like the ESP8266, ESP32, and STM32. This
flexibility is further enhanced by the Board Manager, which lets users install additional board
definitions, and the Library Manager, which provides access to a vast collection of pre-written
libraries. These libraries enable easy integration of hardware components such as temperature
sensors, displays, and wireless communication modules.

Fig 21: ARDUINO IDE SOFTWARE

51
 CHAPTER 4

SYSTEM IMPLEMENTATION AND RESULTS

4.1 Simulation Circuit

Fig 22: SIMULATION CIRCUIT

4.1.1 Code Implementation

#include < Wire.h>

#include < LiquidCrystal.h>

#include < servo.h>

52
// Define the servo motor pins

#define SERVO_X_PIN 9 // Servo for X-axis (connected to PB1)

#define SERVO_Y_PIN 10 // Servo for Y-axis (connected to PB2)

// Define the joystick analog input pins

#define JOY_X_PIN A0 // X-axis of the joystick connected to pin A0

#define JOY_Y_PIN A1 // Y-axis of the joystick connected to pin A1

// Initialize the LCD with I2C address (0x27 is common, check your LCD's datasheet for the
correct address)

LiquidCrystal_I2C lcd(0x27, 16, 2); // 16 columns, 2 rows

Servo servoX; // Servo motor for X-axis

Servo servoY; // Servo motor for Y-axis

void setup() {

// Initialize servos

servoX.attach(SERVO_X_PIN);

servoY.attach(SERVO_Y_PIN);

// Initialize LCD

lcd.begin(16, 2);// Set LCD size

lcd.backlight();// Turn on the backlight

// Print a starting message

lcd.print("Joystick Direction");

// Set up analog input pins pins

Mode(JOY_X_PIN, INPUT);

pinMode(JOY_Y_PIN, INPUT);

53
}

void loop() {

// Read the joystick X and Y axis values (0 to 1023)

int joyX = analogRead(JOY_X_PIN)

; int joyY = analogRead(JOY_Y_PIN);

// Map the joystick X and Y axis to a servo angle (0 to 180 degrees)

int servoXAngle = map(joyX, 0, 1023, 0, 180); // X-axis controls servoX

int servoYAngle = map(joyY, 0, 1023, 0, 180); // Y-axis controls servoY

// Move the servos based on joystick position

servoX.write(servoXAngle);

servoY.write(servoYAngle);

// Display the joystick direction on the LCD lcd.clear();

// Display X-axis movement

lcd.setCursor(0, 0); // First row for X-axis

if (joyX < 400) { lcd.print("Right");

} else if (joyX > 624) {

lcd.print("Left");

} else {

lcd.print(" } ");

// Display Y-axis movement

lcd.setCursor(0, 1); // Second row for Y-axis

if (joyY < 400) {

lcd.print("Down");

54
} else if (joyY > 624) {

lcd.print("Up");

// Display Y-axis movement

lcd.setCursor(0, 1); // Second row for Y-axis

if (joyY < 400) {

} else if (joyY > 624) {

lcd.print("Up");

} else { lcd.print(" } ");

// Add a small delay to make the LCD readable

Delay(200);

4.2 Simulation Results :

Fig 23: MOVING UPWARD

55
 Fig 24: DOWNWARDS

4.2.1 System Integration and Testing

System Integration and Testing are crucial phases in ensuring that all the components of the
gesture-controlled robot car work together smoothly and efficiently. Integration ensures that
individual parts of the system, such as the NodeMCU, accelerometer (MPU6050), motor driver
(L298N), and motors, work harmoniously to achieve the desired functionality. Testing helps
identify and resolve issues before the system is finalized for deployment.

In this section, we will cover the steps involved in integrating the different components and then
testing the overall functionality of the gesture-controlled robot car.

1. System Integration:

System integration involves connecting and configuring the various hardware components and
ensuring that their functionality is synchronized for correct operation. The key elements to be
integrated in this project are:

56
 • NodeMCU (ESP8266): Acts as the central controller, handling the wireless
communication, receiving gesture commands, and controlling the motors.

• MPU6050 Accelerometer: Detects the gesture movements of the user and sends the data to
the NodeMCU for processing.

• L298N Motor Driver: Controls the direction and speed of the DC motors based on the
control signals from the NodeMCU.

• DC Motors: Drive the robot’s wheels, enabling movement.

The integration involves:

• Wiring the Components: Properly wiring the NodeMCU, MPU6050, L298N motor driver,
and DC motors together.

• Programming the NodeMCU: Ensuring that the NodeMCU is properly programmed to

handle the accelerometer’s data, process gestures, and send appropriate motor control
commands.

• Wireless Communication: Configuring Wi-Fi communication to send commands from a

mobile app or web interface to the NodeMCU.

• Power Supply: Ensuring the correct power supply to the NodeMCU, motor driver, and
motors.

Step-by-Step Integration Process

1. Connect the NodeMCU to Wi-Fi: Establish the connection between the NodeMCU and
the local Wi-Fi network, enabling remote control of the robot via a mobile app or web
interface.

2. Wire the Accelerometer (MPU6050): Connect the MPU6050 to the NodeMCU via the
I2C protocol to transmit acceleration data that will be used to recognize gestures.

3. Connect the Motor Driver (L298N): Wire the L298N motor driver to the NodeMCU,
ensuring that the IN1, IN2, IN3, and IN4 pins are connected to the appropriate GPIO pins
on the NodeMCU for controlling the motors.

57
 4. Attach the DC Motors: Connect the DC motors to the L298N motor driver for movement
control.

5. Ensure Power Supply: Make sure that the NodeMCU and the L298N motor driver are
properly powered. The NodeMCU uses 5V (via the USB or a separate power supply), while
the motors may require a higher voltage, typically 6V to 12V, depending on the motor
specifications.

6. Load the Code: Upload the combined Arduino code to the NodeMCU. This code will:

• Process accelerometer data.

• Perform gesture recognition.

• Send motor control signals based on gestures.

• Handle wireless communication (e.g., if using a mobile app for control).

7. Test Communication and Control: Ensure the NodeMCU can send and receive data over
the Wi-Fi network, and the mobile app or web interface correctly sends commands to the
NodeMCU.

4.3 Hardware Results :

Fig 25 : TRANSMITTER HAND GLOVE

58
 Fig 26:RECIEVER ROBOT

Fig 27: ESP32-CAM MONITOR INTERFACE

59
Output Steps:

1. Power On: Switch on the power supply for both the gesture controller and the robot.

2. Gesture Detection: Move your hand to create a gesture. The accelerometer detects the
tilt or motion.

3. Data Transmission: The gesture data is sent wirelessly (via RF/Bluetooth) from the
controller to the robot.

4. Signal Processing: The microcontroller on the robot receives the data and processes it.

5. Motor Actuation: Based on the received gesture signals, the motor driver activates the
appropriate motors for movement.

6. Robot Movement: The robot moves forward, backward, left, or right according to the
gesture.

7. Camera Functionality: If a camera is integrated, it captures live video or images and

transmits them wirelessly to the monitoring device.

8. Real-Time Control: Continuously move your hand to control the robot’s movement in
real time.

60
 CHAPTER 5

CONCLUSION AND FUTURE SCOPE

5.1 Conclusion :
The gesture-controlled robot car project successfully achieved its primary objective of creating
a mobile robot that can be controlled by hand gestures. The integration of multiple components,
including the MPU6050 accelerometer for gesture recognition, NodeMCU (ESP8266) for
wireless communication, and the L298N motor driver for motor control, provided a strong
foundation for implementing a real-time control system. The system exhibited reliable
performance in terms of gesture accuracy, motor control, wireless communication, and power
management.

Key findings and achievements of the project include:

1. Gesture Recognition: The system effectively recognized hand gestures using the
MPU6050 accelerometer, with good accuracy and minimal latency. The gesture-to-
movement mapping was responsive, enabling smooth robot navigation based on hand
movements.

2. Motor Control: The L298N motor driver enabled precise control of the robot's
movement, with the integration of PWM (Pulse Width Modulation) providing adjustable
speed control. The robot was able to move in different directions (forward, backward, left,
right) as dictated by gestures.

3. Wireless Communication: The NodeMCU (ESP8266) Wi-Fi module facilitated wireless

communication with the robot, providing remote control capabilities. The communication
latency was minimal, and the system maintained a reliable connection within the tested
range.

4. Power Management: The robot's power system was designed to ensure stable operation
with adequate battery life. Capacitors and voltage regulation components helped maintain
consistent power delivery to the motors and microcontroller.

61
 5. System Integration: The integration of the hardware and software components allowed
the system to function cohesively. Gesture recognition, motor control, and communication
modules worked seamlessly together, ensuring smooth operation and response.

Although the final prototype demonstrated the desired functionalities, there are areas that require
improvement for better performance and reliability, especially in more complex environments.

Summary of Findings

The gesture-controlled robot car project successfully demonstrated the integration of multiple
technologies, including gesture recognition, motor control, wireless communication, and
power management. The final prototype was capable of performing the desired functionalities in
a controlled environment, with the following key findings:

1. Gesture Recognition Accuracy

• The system effectively recognized basic hand gestures using the MPU6050
accelerometer, mapping gestures such as forward, backward, left, right, and stop to
corresponding robot movements.

• The accuracy of gesture recognition was approximately 95%, with reliable detection of
gestures under normal conditions.

• The system responded to gestures with minimal latency (less than 1 second), making it
suitable for real-time control.

2. Motor Control and Movement

• The L298N motor driver allowed for precise control of the robot’s movements, including
forward, backward, and turning actions.

• PWM (Pulse Width Modulation) was used to adjust motor speed, providing smooth
transitions between different speeds.

• The robot's movement was generally accurate, but performance was slightly affected by
inclined surfaces or obstacles, indicating a need for higher torque motors and more
advanced obstacle avoidance.

3. Wireless Communication
62
 • The NodeMCU (ESP8266) provided wireless communication between the robot and the
mobile app/remote controller, with low latency and reliable connectivity within a range
of 20-30 meters.

• The wireless communication was effective for short-distance control, but its performance
degraded in environments with weak Wi-Fi signals or physical obstructions.

4. Power Management

• The robot's power system, utilizing a battery and capacitors, ensured stable performance
for up to 2 hours under moderate use.

• The power management system successfully prevented voltage dips, maintaining stability
during motor operation.

• Battery life was sufficient for short-term operation but could be improved for longer usage
periods.

5. System Integration and Stability

• The integration of hardware components (accelerometer, motor driver, microcontroller)

and software resulted in a stable and functional system.

• The hardware-software integration worked cohesively, ensuring the robot's consistent

operation based on real-time gesture inputs and remote control commands.

• The system operated well in indoor environments but faced challenges in handling
complex terrains and long-range wireless communication.

6. Limitations and Areas for Improvement

• Gesture Recognition: The accuracy could be improved by introducing machine learning

algorithms to handle subtle variations in gesture performance and to recognize a wider set
of gestures.

• Obstacle Avoidance: The robot lacked advanced obstacle detection, and integrating
ultrasonic sensors or IR sensors could improve its ability to navigate complex
environments autonomously.

63
 • Wireless Communication: Although Wi-Fi provided stable communication, alternatives
like Bluetooth or NRF24L01 could offer more reliable connections in certain scenarios.

• Battery Life: The current battery could be replaced with higher-capacity alternatives (e.g.,
Li-ion or LiPo) for longer operational times.

7. Overall Performance

• The final prototype successfully met the basic goals of gesture-based control and wireless
communication.

• It demonstrated potential for practical applications in areas such as smart homes,

automated tasks, and robotics.

• However, further improvements in power efficiency, obstacle navigation, and wireless

communication reliability will be required for more robust real-world performance.

In conclusion, the project was successful in achieving its objectives, but further development is
necessary to enhance its capabilities and address existing limitations.

Potential Enhancements

While the gesture-controlled robot car successfully met its objectives, there are several areas for
potential enhancement to improve its performance, reliability, and functionality. These
enhancements could address existing limitations and expand the robot's capabilities, making it
more versatile and suitable for real-world applications. Below are some key potential
enhancements for future development:

1. Enhanced Gesture Recognition System

Current Limitations:

• The system currently recognizes a limited set of gestures, with a fixed set of angles for
each direction (forward, backward, left, right, and stop).

• Some gestures may be misinterpreted, especially if they are not performed with the
expected tilt or speed.

Potential Enhancements:

64
 • Machine Learning-Based Recognition: Implementing machine learning algorithms
(such as neural networks or decision trees) to improve the recognition of gestures. The
system could adapt to different users, environments, and even dynamic hand movements.

• Multimodal Gesture Recognition: Incorporating the ability to recognize multiple gestures

simultaneously (e.g., forward and left) or sequential gestures (e.g., start, stop, change
direction), which could increase the versatility of control.

• Gesture Sensitivity Adjustments: Implementing dynamic calibration of gesture

sensitivity based on the user's motion speed or environment, allowing for smoother and
more accurate recognition across different users and conditions.

2. Advanced Obstacle Avoidance

Current Limitations:

• The robot can move in any direction, but it lacks the ability to avoid obstacles
automatically. It may collide with obstacles in its path, which could be problematic in more
complex environments.

Potential Enhancements:

• Ultrasonic or LIDAR Sensors: Adding ultrasonic sensors or LIDAR sensors for

obstacle detection would enable the robot to identify obstacles in its environment and take
evasive actions. This would allow the robot to autonomously navigate around objects,
improving its mobility and usability in cluttered or dynamic environments.

• Real-Time Path Planning: Implementing real-time path planning algorithms, such as A

(A-star)* or Dijkstra’s algorithm, could allow the robot to calculate the best path around
obstacles and avoid collisions. This would also improve the robot's ability to navigate
through environments with varying layouts.

• Infrared Sensors: Integrating IR sensors for close-range obstacle detection can help
improve navigation in tight spaces, ensuring that the robot can safely navigate areas with
limited clearance.

3. Improved Wireless Communication

65
Current Limitations:

• The current Wi-Fi-based communication system works well for short-range control, but
its performance can degrade in environments with poor network conditions or physical
barriers, such as walls.

Potential Enhancements:

• Bluetooth Low Energy (BLE): Replacing Wi-Fi with Bluetooth Low Energy (BLE)
could reduce power consumption and improve communication reliability over short to
medium distances. BLE would also allow for faster, more stable connections in crowded
wireless environments.

• NRF24L01 Modules: Integrating NRF24L01 transceivers could provide a more reliable

and robust communication system with low latency and extended range. These modules
are ideal for real-time data transmission in environments where Wi-Fi is not available or
reliable.

• Long-Range Communication: For outdoor or larger-scale applications, implementing

LoRa (Long Range) communication could enable the robot to communicate over much
greater distances, even in remote areas where typical wireless networks are unavailable.

4. Power Management and Battery Life

Current Limitations:

• The robot operates for about 1.5 to 2 hours on a single charge, which may not be sufficient
for extended tasks. The existing battery system is adequate for short-duration tasks but may
limit the robot’s practical usability.

Potential Enhancements:

• Higher Capacity Batteries: Switching to Li-ion or LiPo batteries with higher energy
density would significantly improve battery life, allowing the robot to run for longer
periods (up to 4-5 hours or more) before requiring a recharge.

66
 • Energy Recovery Systems: Incorporating regenerative braking or solar charging
panels could help extend battery life by recharging the battery during operation,
particularly for outdoor or long-duration use.

• Power-Efficient Components: Optimizing the power consumption of the motors,

sensors, and microcontroller could further extend battery life. Low-power operation modes
for components during idle periods (e.g., deep sleep for the NodeMCU) would conserve
energy when the robot is not actively moving.

5. Enhanced Mobility and Terrain Handling

Current Limitations:

• The robot is designed for flat surfaces and struggles with uneven terrain or obstacles larger
than its wheels' clearance. This limits its versatility for outdoor use or in environments that
are not perfectly flat.

Potential Enhancements:

• High-Torque Motors: Upgrading to high-torque motors would provide better traction

and power, enabling the robot to move more easily over rough or inclined terrain. This
could also improve its ability to carry additional payloads or navigate steep surfaces.

• All-Terrain Mobility: Introducing tracked wheels or suspension systems could enhance

the robot’s ability to move over obstacles, uneven surfaces, or soft terrains like grass or
sand. Tracks are particularly useful for stability and continuous movement in challenging
environments.

• Adjustable Suspension: Adding adjustable suspension to the wheels would help absorb
shocks and improve the robot’s stability when moving over obstacles, enhancing both
performance and durability.

5.2 Future Applications

The gesture-controlled robot car project presents significant potential for future applications
across various domains. As the system evolves with enhanced features such as improved obstacle
avoidance, autonomous navigation, and advanced communication systems, its use cases will

67
extend beyond simple remote control. Below are some key future applications where this
technology could be deployed:

1. Home Automation and Assistance

a. Smart Home Integration

• The robot could become an integral part of smart home ecosystems, interacting with other
devices and assisting in daily household tasks. For instance, it could deliver objects (like
remote controls, snacks, or cleaning supplies) from one room to another, controlled via
hand gestures or voice commands.

• The robot could serve as a mobile assistant, moving from room to room and interacting
with other IoT devices (smart lights, thermostats, cameras) based on user commands or
automation schedules.

b. Elderly and Disabled Assistance

• For elderly or disabled individuals, the robot could provide physical assistance by carrying
groceries, providing mobility support, or fetching items. Gesture-based control would
allow individuals with limited mobility to easily direct the robot to assist them.

• The robot could be integrated with emergency alert systems, capable of recognizing
certain gestures or sounds and alerting caregivers or emergency services when needed.

2. Surveillance and Security

a. Mobile Surveillance Robot

• Equipped with cameras and sensors, the robot could patrol a designated area and monitor
for suspicious activities. It could be used in residential homes, businesses, or public spaces
to provide autonomous surveillance.

• The robot could be controlled remotely or set to autonomous patrol mode, allowing it to
traverse predetermined routes while sending real-time video feeds and status reports to a
remote user.

68
 • Gesture-based controls could be used to maneuver the robot in tight spaces, such as
narrow hallways or parking lots, without the need for extensive training or remote control
devices.

b. Security Drone for Event Monitoring

• In larger environments such as malls, offices, or factories, this robot could act as a mobile
security drone, patrolling the area and sending updates or alerts in case of suspicious
movements or breaches.

• The system could be integrated with AI-driven object detection to identify security threats
or unauthorized persons, enhancing surveillance capabilities.

3. Healthcare and Medical Applications

a. Hospital Assistance

• The robot could be employed in hospitals to transport medical supplies, medications, or

equipment between departments. It would reduce the workload of hospital staff and ensure
timely delivery of essential items, all while being controlled via simple gestures or mobile
apps.

• In rehabilitation settings, gesture control could also be used for physical therapy exercises.
The robot could assist patients in performing specific movements or exercises as part of
their therapy routines.

b. Telemedicine and Remote Healthcare

• The robot could be used in telemedicine, where it acts as a remote-controlled device to

bring patients and healthcare professionals closer together. For instance, a doctor could
guide the robot to a patient in another room, where the robot would assist with diagnostics
or therapy sessions.

• In remote locations, the robot could act as a telemedicine platform, carrying sensors for
diagnostic tools (e.g., heart rate monitors, temperature sensors) and relaying patient
information back to medical professionals.

4. Search and Rescue Operations

69
a. Disaster Response

• The robot could be deployed in disaster zones to assist in search and rescue missions. With
its ability to navigate difficult terrains, including collapsed buildings or debris, it could
deliver supplies, assist with locating survivors, or help identify hazards.

• The robot could be equipped with additional sensors such as thermal cameras, gas
sensors, or sensors for detecting vibrations, making it an effective tool for rescuing
individuals trapped under rubble or assessing hazardous environments.

• Gesture control would allow rescuers to operate the robot remotely in situations where
traditional controls might be difficult to use, such as when wearing heavy gloves or while
wearing protective gear.

b. Environmental Monitoring

• The robot could assist in monitoring environments that are difficult or dangerous for
humans to reach, such as wildfire zones, flood-prone areas, or toxic waste sites. It could
use a combination of thermal imaging, gas detectors, and motion sensors to detect
hazards and deliver important data back to emergency response teams.

• Gesture or voice commands could be used to guide the robot remotely through these
hazardous areas, offering first responders real-time insights into the environment.

5. Educational and Research Applications

a. STEM Education

• The robot could be used as a teaching tool in STEM (Science, Technology, Engineering,
and Mathematics) education. Students could learn about robotics, sensors, and
programming by interacting with and customizing the robot for various tasks, using
platforms like Arduino or NodeMCU.

• The robot could be programmed to execute specific tasks, such as gesture-controlled

movement, encouraging students to explore different technologies and learn about control
systems, sensor integration, and wireless communication.

b. Research and Development in Robotics

70
 • Universities and research institutions could use the robot as a prototype for developing new
robotics algorithms related to gesture recognition, machine learning, and autonomous
navigation.

• Researchers could explore ways to improve the robot's capabilities in areas such as human-
robot interaction, AI-driven path planning, and sensor fusion for real-time decision-
making in dynamic environments.

6. Commercial Applications

a. Retail and Customer Service

• Retail stores could use the robot as a mobile assistant to help customers find products or
guide them to specific areas of the store. It could be integrated into the store's inventory
system, allowing customers to ask the robot where specific items are located.

• The robot could also be employed in malls or large commercial spaces to provide
customer service, such as answering frequently asked questions or directing visitors to
various sections, events, or departments.

b. Warehouse Automation

• The robot could be used in warehouses for material handling and inventory
management. With advanced sensors and motors, it could autonomously retrieve and
deliver items, as well as assist in sorting or organizing products.

• Gesture controls could be used by warehouse staff to remotely guide the robot to specific
aisles or shelves, reducing manual effort and increasing operational efficiency.

7. Entertainment and Gaming

a. Interactive Games

• The robot could be used in interactive gaming systems where players use gestures to
control the robot's movement in a virtual or augmented reality environment. It could
become an extension of the gaming experience, where players perform gestures to control
characters or robots in the game.

71
 • Gesture control could also be used for interactive exhibitions, escape rooms, or immersive
theater experiences where participants can control robots to solve puzzles or assist in
storytelling.

b. Personal Entertainment

• The robot could act as a personal companion, playing music, moving objects around, or
providing entertainment in the form of light shows or interactive performances.

• Gesture control could be used to interact with the robot, allowing users to change music,
adjust lighting, or request specific entertainment features with simple hand motions.

8. Agriculture and Environmental Monitoring

a. Precision Farming

• The robot could be adapted for precision farming, where it helps farmers monitor crop
health, distribute fertilizers, or inspect fields. It could be equipped with environmental
sensors to gather data on soil moisture, temperature, and plant health, providing real-time
insights to farmers.

• Using wireless communication and sensor feedback, the robot could guide its path
autonomously across fields, collecting data that could help optimize agricultural practices
and improve crop yields.

b. Environmental Conservation

• The robot could be used in conservation efforts to monitor wildlife, track environmental
changes, or even plant trees in deforested areas. With the ability to travel through various
terrains and interact with its environment, it could assist researchers in gathering data from
sensitive ecological areas without disturbing the natural habitat.

Conclusion

The gesture-controlled robot car has tremendous potential for expanding into various domains
beyond its initial use case. With enhancements in mobility, power, and functionality, the robot
could play significant roles in healthcare, security, education, agriculture, and other sectors. As

72
the technology matures, it could become an indispensable tool in both personal and commercial
applications, providing automation, assistance, and intelligence in a wide range of tasks.

73
 CHAPTER 6

REFERENCES
[1] N. Mohamed, M. B. Mustafa, and N. Jomhari, ‘‘A review of the hand gesture recognition
system: Current progress and future directions,’’ IEEE Access, vol. 9, pp. 157422–157436, 2021,
doi: 10.1109/ACCESS.2021.3129650.

[2] Z. R. Saeed, Z. B. Zainol, B. B. Zaidan, and A. H. Alamoodi, ‘‘A system atic review on systems-
based sensory gloves for sign language pattern recognition: An update from 2017 to 2022,’’ IEEE
Access, vol. 10, pp. 123358–123377, 2022, doi: 10.1109/ACCESS.2022.3219430.

[3] R. T. Johari, R. Ramli, Z. Zulkoffli, and N. Saibani, ‘‘A systematic literature review on vision
based hand gesture for sign language trans lation,’’ Jurnal Kejuruteraan, vol. 35, no. 2, pp. 287
302, Mar. 2023, doi: 10.17576/jkukm-2023-35(2)-03.

[4] R. T. Johari, R. Ramli, Z. Zulkoffli, and N. Saibani, ‘‘A systematic literature review on vision
based hand gesture for sign language trans lation,’’ Jurnal Kejuruteraan, vol. 35, no. 2, pp. 287
302, Mar. 2023, doi: 10.17576/jkukm-2023-35(2)-03.

[5] M. S. Al-Samarraay, M. M. Salih, M. A. Ahmed, A. A. Zaidan, O. S. Albahri, D. Pamucar, H.

A. AlSattar, A. H. Alamoodi, B. B. Zaidan, K. Dawood, and A. S. Albahri, ‘‘A new extension of
FDOSM based on Pythagorean fuzzy environment for evaluating and benchmarking sign language
recognition systems,’’ Neural Comput. Appl., vol. 34, no. 6, pp. 4937–4955, Mar. 2022, doi:
10.1007/s00521-021-06683-3.

[6] R. E. Nogales and M. E. Benalcázar, ‘‘Hand gesture recognition using machine learning and
infrared information: A systematic literature review,’’ Int. J. Mach. Learn. Cybern., vol. 12, no. 10,
pp. 2859–2886, Oct. 2021, doi: 10.1007/s13042-021-01372-y.

[7] H. Zahid, M. Rashid, S. Hussain, F. Azim, S. A. Syed, and A. Saad, ‘Recognition of Urdu sign
language: A systematic review of the machine learning classification,’’ PeerJ Comput. Sci., vol. 8,
p. e883, Feb. 2022, doi: 10.7717/peerj-cs.883.

74
[8] N. Mohamed, M. B. Mustafa, and N. Jomhari, ‘‘A review of the hand gesture recognition
system: Current progress and future directions,’’ IEEE Access, vol. 9, pp. 157422–157436, 2021,
doi: 10.1109/ACCESS.2021.3129650.

[9] S. Wang, A. Wang, M. Ran, L. Liu, Y. Peng, M. Liu, G. Su, A. Alhudhaif, F. Alenezi, and N.
Alnaim, ‘‘Hand gesture recognition framework using a lie group based spatio-temporal recurrent
network with multiple handworn motion sensors,’’ Inf. Sci., vol. 606, pp. 722–741, Aug. 2022,
doi: 10.1016/j.ins.2022.05.085.

[10] A. Harichandran and J. Teizer, ‘‘Automated recognition of hand gestures for crane rigging
using data gloves in virtual reality,’’ in Proc. Int. Symp. Autom. Robot. Construction, Int. Assoc.
Autom. Robot. Construct. (IAARC), 2022, pp. 304–311, doi: 10.22260/isarc2022/0043.

[11] A. H. Hoppe, D. Klooz, F. van de Camp, and R. Stiefelhagen, ‘‘Mouse based hand gesture
interaction in virtual reality,’’ in Proc. Int. Conf. Hum.-Comput. Interact., 2023, pp. 192–198, doi:
10.1007/978-3-031- 36004-6_26.

[12] M. J. Cheok, Z. Omar, and M. H. Jaward, ‘‘A review of hand gesture and sign language
recognition techniques,’’ Int. J. Mach. Learn. Cybern., vol. 10, no. 1, pp. 131–153, Jan. 2019, doi:
10.1007/s13042-017-0705-5.

[13] C. Chansri and J. Srinonchat, ‘‘Hand gesture recognition for Thai sign language in complex
background using fusion of depth and color video,’’ Proc. Comput. Sci., vol. 86, pp. 257–260, Jan.
2016, doi: 10.1016/j.procs.2016.05.113.

[14] A. Sharma, A. Mittal, S. Singh, and V. Awatramani, ‘‘Hand gesture recognition using image
processing and feature extraction techniques,’’ Proc. Comput. Sci., vol. 173, pp. 181 190, Jan.
2020, doi: 10.1016/j.procs.2020.06.022.

[15] E.-S.-M. El-Alfy and H. Luqman, ‘‘A comprehensive survey and taxonomy of sign language
research,’’ Eng. Appl. Artif. Intell., vol. 114, Sep. 2022, Art. no. 105198, doi:
10.1016/j.engappai.2022.105198.

75