Universal Programmable Remote Control
Cornell University, ECE 476
Our design turned out to be approximately what we expected. As mentioned before, we had planned to build our own solder-board circuit so that the remote control was truly not attached to any strings or wires, but lack of expertise seemed to take us back from that idea. Also, we could not implement permanent memory backup for the buttons recorded because eeprom memory was not sufficient. That aside, our code was implemented as designed, with some small modifications along the way. If we have had more time we would’ve considered implementing this on another chip with other memory options, and include the option of identifying the format when recording in order to compact the representation of the wave in memory.
As mentioned before, our remote control worked for the standard that we tested it on. We are confident that any other standard that uses an approximately 40KHz modulation frequency will be compatible with our product because of the design decisions we have taken.
Our idea we discovered in casual conversation with some friends also in the class and research was immediately done about standards and approaches to similar projects, from public sources, so as to better grasp the complexity of our task. However, the implementation and actual design were ours. We did, however, get our idea of using time to record the signals from a similar project done in Stanford’s microcontrollers class. Our product would be considered in early development, so patents are not really considered as a possibility. Our purpose was to better understand how data transmission at infrared frequencies was done, and this project was chosen because of its everyday appearance. The website design, however, is a generous gift from a good friend, who also helped usto understand the basics of web design.
3. (…to be honest and realistic in stating claims or estimates based on available data.)
We believe that from the beginning we were realistic about the specifications of our projects given time, knowledge, and economic constrains. Our final product was very close to these expectations, and we have tested our design in a real device and verifies that it worked properly.
5. (…to improve the understanding of technology, its appropriate application, and potential consequences.)
As mentioned before, one of the reasons we chose this project was because of our desire to learn about Infrared data transmission. We believe that this area of electrical engineering is one that we must be in contact with, and learn about.
6. (…to maintain and improve our technical competence and to undertake technological tasks for others only if qualified by training or experience, or after full disclosure of pertinent limitations.)
We believe that we took a project that we felt we were completely qualified to undertake, that interested us, and that would make us better engineers by teaching us about the field, and about product engineering in general.
7. (…to seek, accept, and offer honest criticism of technical work, to acknowledge and correct errors, and to credit properly the contributions of others.)
We want to thank the TAs for the honest criticism, encouragement, and ideas that they have put into our work, and believe that it was an integral part of this experience.
8. (…to assist colleagues and co-workers in their professional development and to support them in following this code of ethics.)
We also believe that a very important part of this project was to be able to interact with our peers by taking in recommendations and feedback, and be able to provide the same for them. We felt that the laboratory was a co-operative work environment.