As we enter the third month of working on our project, I believe that the Trailer Automation team (we really need a better name) is well on our way to having a working prototype in time for the Make-o-Rama at the end of April. Most of the components we need to build our system have come in, and we’ve been able to begin testing while we wait for other parts like a gas sensor, Ethernet shield, and another Arduino board to arrive.
So far this project has taught me two things: (1) most people creating home automation systems have degrees in computer science and/or electrical engineering and (2) the Internet is a beautiful thing. I’ve learned more on my own in these past three weeks than I think most computer science students learn in a semester. Chloe, Annalise and I recently discovered that our project involves more than just programming some sensors and sticking them in our trailer, and that the Instructuable we’ve been using to guide us isn’t as helpful and detailed as we previously thought. While this is stressful in that it means we’re navigating the sea of computer programming and automation systems largely on our own, it’s also (forcing) allowing us to become a lot more knowledgeable about the details of our project.
We are nowhere close to being as experienced and educated as the other people building wireless and Ethernet gateways with Arduino Uno boards, but this is why the World Wide Web is our saving grace: the people that are experts with Arduino, OpenHAB and home automation systems are all online. Resources like GitHub, SparkFun, Stack Overflow and independent Arduino wikis (like this one) have become our new best friends. They’ve helped us understand how components like proto shields and RFM wireless transceivers work, as well as the purposes of programs like OpenHAB and I2C. While all of this new information can be overwhelming, we’re trying to take a few steps at a time and not get too worried about all of the technical aspects.
And little by little, we’re making progress. Currently we’re able to operate a motion and a light sensor at the same time (our end goal is to have all five sensors running at once), and just last class we finally got the sound sensor to detect changes in noise. Some days are frustrating, and ninety minutes of trial and error gets us nowhere. But other days, our troubleshooting pays off and with one slight change we have another working sensor (this point was made painfully obvious last class when two class periods of a nonresponsive sound sensor was remedied by correctly connecting power and ground).
We still have the temperature/humidity and the gas sensors to test and program, but it’s my hope that all of the trial and error we’re experiencing now will make it easier for us as we move forward with our project. It’s kind of daunting to think that over half of our time to work on this project is already gone, I’m but optimistic that we’re progressing faster now than at the beginning of the semester, when we were feeling slightly suffocated by the scale and level of this project. Equipped with a toolbox of online forums, YouTube videos and breadboard wires, I’ve realized that even stressful projects like programming sensors that wirelessly sync with smart phones can be done if you don’t let the intricacy of the project scare you senseless.