- NodeMCU (ESP-12E module with ESP8266 controller) and motor shield / breakout board. Available here.
- Two ubiquitous, cheap Chinese motor modules (UCCMMs). Available here. An improved quality, domestically sourced alternative with motors and wheels purchased separately.
- 6 AA battery holder, such as this one. Rechargeable NiMH batteries are highly recommended, as battery life is 1-2 hours on Alkaline cells.
- Arduino core libraries for the ESP8266.
- Control over WiFi from a mobile device or computer via a browser-based user interface.
- Cardboard robot body, ranging from a simple box, to a laser cut design from CAD.
The goal is to keep the cost of a base "kit" to under 20USD.
To aid in ideation and your designs, reference CAD files are provided for standard Kit of Parts hardware and a handful of reference designs:
- Kit of Parts CAD - High-fidelity models of the motors, MCU + motor shield and various battery options.
- Cardboard NewBot 2.0 A revised, simpler NewBot designed for a workshop at the Bay Area Maker Faire.
- Cardboard NewBot 1.0 - A rectangular "box" robot made with tab and slot construction. Upon testing with actual kids (of many ages), this bot was discovered to be too hard to assemble.
- "(BOX) Factory of Sadness" - A wedge-bot design with kill saw and 3D printed parts.
This section describes the minimum steps needed to load this firmware onto your NodeMCU. The firmware should work out of the box for a basic robot setup. Subsequent sections describe the development environment for customizing the firmware.
- Download and install the Arduino IDE.
- Install the ESP8266 devtools add-on. Directions here. OS X users must install serial port drivers. The NodeMCU typically has an CP210x usb to serial chip, but to save money the manufacturer might have used a CH340 or CH341 chip. Identify the chip on your board by looking at the markings on the chip. The chip should can be just in front of the usb port. CH340 and CH341 driver [here] (https://blog.sengotta.net/signed-mac-os-driver-for-winchiphead-ch340-serial-bridge/) CP210x driver here.
- Install the ESP8266FS file system upload add-on. Directions here.
- Install Arduino networking libraries. Currently, these are not available in the Library Manager and must be installed manually. Directions for installing Arduino libraries are available here.
Loading the firmware:
- Download this entire repository to your Arduino projects directory. Make sure the containing folder is called 'BattleBot-Control' (by default, GitHub will name the zip 'Battlebot-Control-<branch name>').
BattleBot-Control.inoin the Arduino IDE.
- Ensure the following settings are set in the "Tools" menu:
- Board: "NodeMCU 1.0 (ESP-12E Module)"
- CPU Frequency: "80 MHz"
- Flash Size: "4M (3M SPIFFS)"
- Upload Speed: "115200"
- Choose correct serial port for module
- Load the Sketch to the module, "Sketch" > "Upload".
After the default firmware is loaded, the robot should be drivable. In the default configuration, the robot creates a WiFi access point (AP). If you connect to this network and enter the URL of the robot, a user interface will be served up in the browser, allowing you to drive.
- Connect to the WiFi network "BattleBot-xxxxxxxxxxxx". "xxxxxxxxxxxx" is a unique string for each robot.
- Use a phone or tablet to use the built-in touch interface.
- Use a computer to use the mouse or a gamepad (coming soon).
- Navigate to the robot in a web browser.
- On iOS, OS X and Linux, the robot can be found with mDNS at
- On Android and Windows (without mDNS installed) use
http://192.168.4.1/(in the default AP mode only). When connected to an external WiFi network, use an mDNS app like ZeroConf Browser to find the IP address of the robot. TODO: add notes for connecting from Windows (involves installing mDNS / Bonjour for Windows).
- You may need to explicitly type
http://before the URL or IP to connect, as some browsers will assume
https://, which is not supported.
Connecting to the robot access point is inconvenient for development, since it generally precludes using the internet at the same time. For development, an alternative configuration is provided. In this setup, the robot will connect to an existing WiFi network. The development machine also connects to this network, making the robot and internet available at the same time.
To prevent hard-coding the network credentials in the source code, WiFi configuration is accomplished via a configuration file uploaded to the robot file system in the
data/ directory of this project.
That is, the SSID of the network to connect to and the password, on one line, separated by a colon. This file should be created in the
data/ directory of this project. A
.gitignore is present to prevent the file from being checked in to source control inadvertently.
The robot will attempt to connect to the configured network for 10 seconds. If the connection can't be established it will fall back to AP mode. See the Status LED section below.
You can also force the robot to use AP mode by grounding pin D5 during startup (i.e. connect pins 'D' and 'G' of column 5 on the GPIO header strip and press RESET). This feature is useful if you inadvertently connect to a network, only to discover it has firewall rules preventing machine to machine communication.
To load the file on the robot, you can either reload the entire file system with the "ESP8266 Sketch Data Upload", or follow an alternative faster procedure:
- Connect to the robot in the default access point (AP) mode.
- Open a shell and navigate to base project directory, the one with this file in it.
- Run this command in the shell:
$ ./upload.sh wifi.config
This command will upload any file (relative to the root of the
data/ directory) to the robot file system.
When complete, reset the robot. The robot should now connect to the WiFi network specified in the file. To return to access point mode, simply delete the configuration file and reload the file system, or use the abreviated command (as above):
$ ./delete.sh wifi.config
This command will delete a file from the robot file system.
Note that the
delete.sh can also be used to update the HTML resources on the robot during development. If
upload.sh is run with no argument, it will upload all files in the
data/ directory. This is slow, but is still significantly faster than reloading the entire file system.
The default firmware assumes a certain robot hardware / wiring configuration.
- Motor channel A -> Right motor (as judged from behind the robot)
- Motor channel B -> Left motor (as judged from behind the robot)
- Motors should be wired so that a positive voltage on the A+/B+ terminal produces forward motion.
Get this wrong and the robot will not drive as expected with the default control interface.
The NodeMCU has two blue LEDs. One (the "front") LED is directly on ESP8266 board, near the antenna. The second (the "middle rear") LED is on the NodeMCU carrier board, closer to micro-USB connection. Due to the pin usage on the motor driver board, the connection to front LED is shared with the direction signal for the B motor channel. Therefore, this LED will be illuminated whenever the left motor is travelling in the reverse direction.
Luckily, the middle rear LED is connected to a dedicated line and can be used for general status. The default firmware utilizes different blink patterns on this LED to indicate various robot states. These states are:
- Solid on -> Robot is running various setup code, such as WiFi, mDNS and other hardware setup. In testing, these operations generally complete quickly, so this state isn't likely to be observed unless something goes wrong.
- 10Hz fast blink -> This state indicates the robot is trying to connect to a WiFi network (non-AP development mode with
- Chirp blink (short on, long off) -> Robot is in an "idle" state, waiting for a client to connect.
- 1Hz medium blink -> Robot is in the "driving" state. Client is connected and the robot is actively receiving drive commands.
Note, if the robot is in the driving state and the client becomes disconnected, the robot will stop and revert to the idle state after 2.5 seconds. This is a safety measure to prevent the robot from getting stuck on the last command it received and running away in the event of connection trouble.
The robot emits various debugging messages over the USB serial connection. These can be observed from the Arduino IDE or in a dedicated serial terminal. The baud rate is 115200.