Remote control car running on Arduino

[HB] Buzzer

[HB] Mini Breadboard

[HB] Dupont wires

[HB] L298N Module

[HB] Arduino Nano

[HB] Voltage regulator (5V output)

Arduino IDE

[HB] NRF24L01+PA+LNA

[HB] NRF24L01 adapter

<html><body>Main article: <a href="https://www.hibit.dev/posts/98/diy-remote-control-car-running-on-arduino?utm_source=arduino&amp;utm_medium=social&amp;utm_campaign=projects">DIY - Remote control car running on Arduino </a>Radio control cars are small vehicles powered by electric or gas motors that can be remotely controlled by a transmitter. The transmitter sends signals to a receiver on the car, allowing the operator to control the car's speed, direction, and steering. Radio control cars are available in a variety of sizes, from miniature models that can fit in the palm of your hand to large off-road vehicles that can climb over rough terrain. They are often sold with predefined chips and built-in software. Due to limited circuitry and insufficient documentation, enhancing or modifying existing RC cars can become a challenging task. The primary objective of our project is to overcome these obstacles and create a completely customizable RC car that can be fully controlled. In addition, it will be a perfect pair for our AirControl joystick. The name given to the project is Merin. <h3>Merin project</h3><a href="https://www.hibit.dev/posts/94/diy-remote-control-car-running-on-arduino-concept">DIY - Remote control car running on Arduino: concept </a><a href="https://www.hibit.dev/posts/95/diy-remote-control-car-running-on-arduino-mounting">DIY - Remote control car running on Arduino: mounting </a><a href="https://www.hibit.dev/posts/96/diy-remote-control-car-running-on-arduino-code">DIY - Remote control car running on Arduino: code </a><h3>Prerequisites</h3>Reading the <a href="https://www.hibit.dev/posts/84/diy-universal-rc-joystick">AirControl documentation </a>is highly recommended as it will serve as the car controller. Additionally, we suggest reviewing the <a href="https://www.hibit.dev/posts/89/how-to-use-the-l298n-motor-driver-module">L298N motor driver </a>, which will be employed in the project, and familiarizing oneself with <a href="https://www.hibit.dev/posts/62/playing-popular-songs-with-arduino-and-a-buzzer">buzzers and how they work </a>. <h3>Frame and components</h3>In the context of the project, the decision was made not to create a new RC car from raw materials, but rather to purchase an already existing model. Modifying an existing model would allow us to skip many of the time-consuming steps and focus primarily on the modifications. This will allow us to save time and resources while still achieving the desired outcome. Additionally, acquiring a pre-assembled RC car provides more sophisticated design than the team would have been able to create independently. Once we had reviewed all the available options, we selected a 1:18 scale car with black windows and a spacious interior (hopefully). We are optimistic that this choice will meet our needs. <figure><img src="https://www.hibit.dev/images/posts/2023/rc_car_overview.png"/><figcaption>Original RC car overview</figcaption></figure>The car already includes valuable features that can be reused such as front headlights, brake lights and functional suspension. The project involves using AirControl joystick as primary control mechanism. The original joystick will not work once the modifications are complete. The custom joystick will offer unique features that the original one lacks. <h3>Original state and cleanup</h3>We began our investigation by disassembling the frame to uncover its internal components and understand how they work. By gaining a clear understanding of the car's original configuration, we were able to approach the modifications with greater confidence, knowing what changes were necessary and how they would integrate with the existing system. After the initial inspection and disassembly, the team was able to identify which components could be repurposed, which ones could be improved, and which ones were not necessary. We also identified areas where we could introduce new features to enhance the car's functionality. To start mounting new components, we first unmounted the existing ones and ensured that we keep the necessary elements. The original state of the car and its internal components can be seen in the image below. <figure><img src="https://www.hibit.dev/images/posts/2023/merin_original_state.png"/><figcaption>Merin initial state</figcaption></figure> <figure><img src="https://www.hibit.dev/images/posts/2023/merin_top_frame.png"/><figcaption>Merin top frame</figcaption></figure> <figure><img src="https://www.hibit.dev/images/posts/2023/merin_battery_box.png"/><figcaption>Merin battery box</figcaption></figure>After removing all the unnecessary components from the car, we begin the process of designing and mounting our custom circuitry. <h3>System assembly and integration</h3>The only remaining elements are the suspension, direction, motors, and lights. We aim to not only utilize those existing elements but also enhance their functionality. To control the direction and speed of the motors, we will be using the L298N module. This particular module has the capability to control up to two DC motors at once, allowing for precise and efficient control over the movement of the vehicle. Exactly what we need. <figure><img src="https://www.hibit.dev/images/posts/2023/merin_cleanup.png"/><figcaption>Merin cleanup</figcaption></figure><h3>Direction motor</h3>In our initial plans, we aimed to make possible various turning angles for the car. However, evaluating the original direction motor, we realized it wouldn't be adequate for that. Therefore, the car's direction will only have three states: left, right, and none. However, we have expanded the turning range of the vehicle by removing a small plastic section located on the wheels direction. <h3>Speed motor</h3>Initially, the motors could only apply full throttle. Our objective is to enhance this functionality by enabling a variable speed control, which would allow the motors to steadily increase or decrease their velocity, or sustain a constant speed. While these cars don't come with built-in braking, we can use the motors to slow down and stop the vehicle. We'll do this by reducing the motor speed, either to a lower speed or to zero. Finally we'll simulate inertia by gradually reducing the speed over time. <h3>Additional features</h3>Our intention was to incorporate the head and brake lights of the car into our design. The original lights were designed to be continuously on and couldn't be turned off. We are going to improve that functionality by enabling the lights to be turned on and off. Furthermore, we aimed to provide independent control of the headlights. On the other side, to ensure that the brake lights are easily distinguishable, we have set the default position lights intensity slightly lower than that of the brake lights. An added function we are incorporating is a horn that utilizes a buzzer to generate sound. It can be triggered by a dedicated button on the joystick. <h3>Microcontroller</h3>The car's functions, such as the motor controller, lights, and direction control, will be coordinated and controlled by an Arduino Nano, which will serve as the brain and central hub for all of the car's features. Additionally, as the goal is to pair Merin with the AirControl joystick, the Arduino Nano will communicate with the joystick via an NRF24L module. This wireless communication will allow greater flexibility controlling the car, as well as enabling potential future modifications. <h3>Wiring schema</h3>The power source for the remote-controlled car is a 9V battery, which will provide enough power to supply the circuit and both motors for speed and direction control. The buzzer, lights, and NRF24L01 communication module are directly connected to the Arduino Nano. The use of a 9V battery is a good choice as it provides enough voltage to run the system without being too heavy for the vehicle. <figure><img src="https://www.hibit.dev/images/posts/2023/schemas/merin.png"/><figcaption>Remote control car (Merin) wiring</figcaption></figure> <figure><img src="https://www.hibit.dev/images/posts/2023/merin_mounted.png"/><figcaption>Merin mounted</figcaption></figure>The final circuitry has been carefully mounted onto the frame of the car. This circuitry allows new features to be implemented, including the ability to control the speed of the vehicle, turn on and off the lights, and even honk the horn. The physical assembly of the car has been completed with all the components properly installed and ready for use. The next steps involve reprogramming the Arduino Nano with the appropriate software to enable all the features, including pairing the car with the AirControl joystick via the NRF24L01 module. <h3>Installing Arduino libraries</h3>Using existing libraries, we can communicate with the NRF24L01 module and save time. These libraries have been tested and improved by the community over the years, providing a robust code base. We strongly suggest using these libraries instead of building everything from scratch. The same applies to the AirControl library that simplifies the usage by providing pre-defined structures. These libraries can be downloaded from our official repository: <ol><li>RF24 official library: <a href="https://github.com/hibit-dev/merin/raw/master/lib/RF24.zip">Download here </a></li><li>AirControl official library: <a href="https://github.com/hibit-dev/merin/raw/master/lib/AirControl.zip">Download here </a></li></ol>To import a library, open the Arduino IDE, go to Sketch &gt; Include Library &gt; Add .ZIP Library and select the library file downloaded from our GitHub repository. <figure><img src="https://www.hibit.dev/images/posts/2023/arduino_import_library.png"/><figcaption>Arduino IDE library import</figcaption></figure>Then you can simply use include statement: <pre>#include "RF24.h" </pre><pre>#include "nRF24L01.h" </pre><pre>#include "AirControl.h" </pre><h3>AirControl library</h3>The AirControl library defines structures for the joystick and its control elements. These structures contain information about each control element and allow us to know the current state of each element at any given moment. <pre>struct button { </pre><pre>	 byte pressed = 0; </pre><pre>}; </pre><pre>struct toggle { </pre><pre>	 byte on = 0; </pre><pre>}; </pre><pre>struct potentiometer { </pre><pre>	 byte level = 0; </pre><pre>}; </pre><pre>struct analog { </pre><pre>	 short x, y; </pre><pre>	 button button; </pre><pre>}; </pre><pre>//Max size of this struct is 32 bytes - NRF24L01 buffer limit </pre><pre>struct air_control { </pre><pre>	 char key[10] = "hibit"; </pre><pre>	 struct { </pre><pre>	 analog left, right; </pre><pre>	 } analogs; </pre><pre>	 struct { </pre><pre>	 toggle upper, lower; </pre><pre>	 } toggles; </pre><pre>	 struct { </pre><pre>	 struct { </pre><pre>	 button upper, lower; </pre><pre>	 } left, right; </pre><pre>	 } buttons; </pre><pre>	 struct { </pre><pre>	 potentiometer left, right; </pre><pre>	 } potentiometers; </pre><pre>}; </pre>The library additionally includes a debug function that displays the current state of the controller. <h3>Remote control</h3>The advantage of using custom components and the AirControl joystick is the ability to fully customize the communication. This allows us to assign specific functions to buttons and control various features in the way we prefer. <figure><img src="https://www.hibit.dev/images/posts/2023/merin_aircontrol.png"/><figcaption>AirControl joystick functions for Merin</figcaption></figure>The image displayed above provides a clear overview of how we have mapped the different buttons and components of the AirControl joystick to control various functions of the car. By mapping the different joystick components to specific functions, we are able to have full control over the car's movements and other features. By reading the code in the following section, it will become apparent how each button is utilized. <h3>Merin Arduino code</h3>The source code for the Merin project is organized into separate logical files with descriptive names, each responsible for a specific component or a part of it. The main.ino file contains the program's entry point and definitions, while the remote car logic is contained in the merin.ino file. All functions in this file use a common language and are well-documented with comments to clarify certain sections of code. <pre>void control() </pre><pre>{ </pre><pre>	 bool hasLightsOn = airControl.toggles.upper.on; </pre><pre>	 // Driving dark places? </pre><pre>	 if (airControl.buttons.right.upper.pressed || hasLightsOn) { </pre><pre>	 headlightsOn(); </pre><pre>	 } else { </pre><pre>	 lightsOff(); </pre><pre>	 } </pre><pre>	 // Setting direction </pre><pre>	 if (airControl.toggles.lower.on) { </pre><pre>	 if (isMotorDirectionUnset(motorSpeed) || isMotorDirectionForward(motorSpeed)) { </pre><pre>	 brakelightsOn(); </pre><pre>	 switchDirectionBackward(); </pre><pre>	 } </pre><pre>	 } else { </pre><pre>	 if (isMotorDirectionUnset(motorSpeed) || isMotorDirectionBackward(motorSpeed)) { </pre><pre>	 brakelightsOn(); </pre><pre>	 switchDirectionForward(); </pre><pre>	 } </pre><pre>	 } </pre><pre>	 // Turning left or right? </pre><pre>	 if (airControl.analogs.left.x &gt; 50) { </pre><pre>	 turnRight(); </pre><pre>	 } else if (airControl.analogs.left.x &lt; -50) { </pre><pre>	 turnLeft(); </pre><pre>	 } else { </pre><pre>	 turnNone(); </pre><pre>	 } </pre><pre>	 // Setting speed </pre><pre>	 if (airControl.analogs.right.y &lt; -10 ) { </pre><pre>	 brakelightsOn(); </pre><pre>	 brake(airControl.analogs.right.y); </pre><pre>	 } else { </pre><pre>	 // Recheck lights </pre><pre>	 if (hasLightsOn) { </pre><pre>	 lightsOn(); </pre><pre>	 } else { </pre><pre>	 brakelightsOff(); </pre><pre>	 } </pre><pre>	 if (airControl.analogs.right.y &gt; 15) { </pre><pre>	 accelerate(airControl.analogs.right.y, airControl.potentiometers.left.level); </pre><pre>	 } else { </pre><pre>	 brakeGradually(random(2)); </pre><pre>	 } </pre><pre>	 } </pre><pre>	 // Make some noise! </pre><pre>	 if (airControl.buttons.right.lower.pressed) { </pre><pre>	 hornOn(); </pre><pre>	 } else { </pre><pre>	 hornOff(); </pre><pre>	 } </pre><pre>	 delay(30); </pre><pre>} </pre><pre>void switchDirectionBackward() </pre><pre>{ </pre><pre>	 brakeUntilStop(); </pre><pre>	 setMotorDirectionBackward(motorSpeed); </pre><pre>	 sendToSpeedMotor(); </pre><pre>} </pre><pre>void switchDirectionForward() </pre><pre>{ </pre><pre>	 brakeUntilStop(); </pre><pre>	 setMotorDirectionForward(motorSpeed); </pre><pre>	 sendToSpeedMotor(); </pre><pre>} </pre><pre>void accelerate(int speed, byte precision) </pre><pre>{ </pre><pre>	 int speedToApply = map(speed, 0, 127, 0, precision); </pre><pre>	 if (speedToApply &lt; motorSpeed.speed) { </pre><pre>	 return; </pre><pre>	 } </pre><pre>	 setMotorSpeed(motorSpeed, speedToApply); </pre><pre>	 sendToSpeedMotor(); </pre><pre>} </pre><pre>void brake(int speed) </pre><pre>{ </pre><pre>	 int value = map(speed, 0, -127, 0, motorSpeed.speed); </pre><pre>	 setMotorSpeed(motorSpeed, motorSpeed.speed - value); </pre><pre>	 sendToSpeedMotor(); </pre><pre>} </pre><pre>void brakeGradually(int delta) </pre><pre>{ </pre><pre>	 int value = max(0, motorSpeed.speed - delta); </pre><pre>	 setMotorSpeed(motorSpeed, value &gt; 30 ? value : 0); </pre><pre>	 sendToSpeedMotor(); </pre><pre>} </pre><pre>void brakeUntilStop() </pre><pre>{ </pre><pre>	 setMotorSpeed(motorSpeed, 0); </pre><pre>	 unsetMotorDirection(motorSpeed); </pre><pre>	 sendToSpeedMotor(); </pre><pre>	 delay(100); </pre><pre>} </pre><pre>void turnNone() </pre><pre>{ </pre><pre>	 unsetMotorDirection(motorDirection); </pre><pre>	 sendToDirectionMotor(); </pre><pre>} </pre><pre>void turnLeft() </pre><pre>{ </pre><pre>	 setMotorDirectionForward(motorDirection); </pre><pre>	 sendToDirectionMotor(); </pre><pre>} </pre><pre>void turnRight() </pre><pre>{ </pre><pre>	 setMotorDirectionBackward(motorDirection); </pre><pre>	 sendToDirectionMotor(); </pre><pre>} </pre>Note: the snippet is part of Arduino project located in our <a href="https://github.com/hibit-dev/merin/tree/master/src/main">GitHub repository </a>with the code separated in different logical files. <h3>Code explanation</h3>The speed control joystick is used for acceleration with positive values and braking with negative ones. To prevent errors with small values, a threshold has been set to ignore them. The same approach is taken with the direction analog module, but with a higher threshold since there are only two turn states. The car's speed will increase with higher provided values and gradually decrease to 0 without acceleration. It simulates the effect of inertia instead of abruptly stopping the car. To improve speed control, a sensitivity rate can be set using the right side potentiometer. When the shaft is turned to maximum, the speed control joystick will be in the highest sensitivity mode. As a quick note, when the car is braking, the corresponding rear red lights turn on. When the position lights are on, the braking lights can still be distinguished as they shine brighter than the regular position lights. <h3>Conclusion</h3>The Arduino Nano acts as the main control unit for the car, allowing us to coordinate and manage all of its functions. This provides us with the flexibility to personalize the car to meet our specific needs with a wide range of features that can be controlled by the AirControl joystick. The modifications we made to the car will not only make it more enjoyable to use but also increase its versatility beyond its original capabilities. We understand that there are various areas for improvement, from the battery to the motors. However, that is beyond the scope of the current post. </body></html>

HiBit - Merin

Remote Control Car

Remote control car running on Arduino

Design a fully customizable remote-controlled car, controllable via Arduino, utilizing the components of your choice.