My MikroElektronika Buggy was gathering dust for some time in my office, as I lacked the inspiration for new projects. That is until I have started to play with Redkea. And then it came to me: why not using Redkea to control the Buggy?
A few days of hard work, and now it’s ready to be showcased on the blog.
So, as usual, first a few words about the hardware. Obviously, I have started with the Buggy, with a Clicker 2 for PIC32MX as “brain”. I have chosen the PIC32 microcontroller as it can be programmed in Arduino IDE, same as the ESP8266, making things simpler.
As a side note, there’s a Buggy for PIC32MX4 bundle which includes the Buggy, the Clicker 2 and one BLE click. If you can, get the bundle as it will come a bit cheaper than buying all the components separately.
WiFi connection is achieved using one WiFi3 click, which is based on the ubiquitous ESP8266 chip from Espressif. A fair warning here: this project implies programming the WiFi3 click in Arduino IDE. By doing this, you have a small chance to brick the WiFi3 click. Also, you won’t be able to return to the original firmware that comes with the WiFi3 click. That firmware is no longer available. You can, however, flash the ESP8266 with another working AT firmware, but you will have a newer version of the AT command set.
So, the WiFi3 click was prepared with 8-pin stackable headers for the mikroBUS connectors, and with a 7-pin header row for the GPIO pins. Programming in Arduino IDE is done using my programming rig, choosing either “Generic ESP8266 module – 4M (3M SPIFFS)” or “Node MCU 1.0”.
Once programmed, the WiFi3 click is placed into mikroBUS socket #1 of the Clicker 2 for PIC32MX board. The Clicker 2 for PIC32MX board is also programmed in Arduino IDE, using the latest (1.4.1) ChipKit board definitions.
So, here’s the Buggy, ready to go: