1. MICROCONTROLLED HOME Keith Jones EKU Deparment of Technology CEN

2. 2 OUTLINE Motivation Introduction Problem Statement Proposed Solution Results Conclusion

3. 3 MOTIVATION  My parents and I like to go out of town to visit family in West Virginia.  We often find ourselves wondering who we are going to get to look after thing while we are gone.  We usually would ask somebody from church that we trust, but we still don’t like to give out a copy of our house key.  This motivated me to research farther into the matter of how a person could control items in their home without the usual key or switch.

4. 4 INTRODUCTION When I first started thinking about a Project I decided that I wanted to do something with networking, but I also wanted to incorporate electronics in some form. I began to think about ways that I could combine networking with another electronics class that I had taken in the past. I decided that it would be a really interesting idea if I could find a microcontroller that had networkability and could be connected up to a network just like any other networkable device. After a lot of looking and emailing microcontroller manufacturers I finally found the Dallas Semiconductors TINI evaluation KIT with embedded ethernet.

5. 5 PROBLEM STATEMENT The problem that I dealt with was how to get the code into the microcontroller. How to execute the code in a web page. And how to get the outputs to a real world device for control.

6. 6 PROPOSED SOLUTION  The first step in figuring out all of the problems was to first research and see if what I was wanting to do had been done before. I knew that I would not be able to come up with code from scratch to accomplish what I wanted to do.

7. 7 PROPOSED SOLUTION I was able to find code examples and instructions on how to set up the microcontroller as a web server that would host a website that also had the ability to show the status of outputs live as they happen.

8. 8 PROPOSED SOLUTION However, the process was not as easy as the instructions made it out to be. There are many tools that have to be used to completely get the webserver up and running.

9. 9 TOOLS REQUIRED TINI SDK: TINI Software Development Kit. Java SDK: Java Software Development Kit. Device Controller Package: Includes servlet code and icon images. Apache ANT: Tools for Developing the TINI webserver TINI ANT: An Apache add-in that allows the build to be TINI specific. Tynamo Webserver: A webserver compiler specifically for building a TINI webserver. NetComponents Library: A library of java tools allowing Tynamo Webserver to automatically FTP into the microcontroller and send files. All of these tools are required to assemble, compile, and send the final webserver to the TINI.

10. 10 THE TINI

11. 11 PROBLEMS The main problem I had was in poor documentation. The documentation I received was hard to follow and interpret. There are many cases where a properties file would need to be edited, but the information did not say which file the properties document was in.

12. 12 RESULTS The result is a webpage that can be accessed from anywhere and outputs can be made such as locking a door or turning on lights.

13. 13 WEB PAGE

14. 14 CONCLUSIONS Remote controlling of home features can be done with a little patience and with good documentation. The type of home controlling I did may fit the needs of what some people want more than others.

15. 15 CONCLUSIONS With more work this design could be embedded into devices such as a TV, Stove, ect to allow remote control and access with a simple click of a mouse. Overall I was not able to build as much for demonstration as I wanted to, but I was able to get the control part working. The rest is just circuitry.

16. 16 FUTURE WORK Where I have currently left off with the project would be a great place for someone else to pick up the project and do some more advanced things like add more outputs, change the site interface around, or even develop the microcontroller into something different than remote home control.

17. 17 Future Work Questions? Suggestions?