Now that we have successfully deployed our prototypes, it is time to consider how we are going to replicate this progress on an arduino. The Arduino is a  less powerful micro-controller than the raspberry pi and it does not have built-in WiFi capabilities. This means that we will have to use an external shield or module that can talk to the internet. We think that our best bet is using a low-cost wifi chip called the ESP8266. This has a very simple external connection to the Arduino using a breadboard. You can also program the ESP8266 directly, but it is said to be more complex, and we are unaware of the power consumption due to the fact that we could never officially turn it off, and only send it to sleep.

The ESP8266 works off of AT commands, some of which can be found on this pdf. You can send these to the chip via the serial monitor in the arduino programming environment, or you can use the software serial library to allow you to send them from your code. We will most likely not be using dweet for this application, but sending our data to a central raspberry pi that then can use dweet, or a different service to upload the data to our dashboard.

There are several libraries that you can use for the chip, however we will most likely be using Software Serial. As far as the connections go, we will need a breadboard, esp8266, an adapter because the esp8266 cannot plug directly into the breadboard (due to the layout of its legs), an arduino, jumper wires, an external power source, and two 10k resistors. Javier and I are going to get together and see if we can get our computers communicating with the chip before we start uploading code.