Difference between revisions of "F12: Android Door Lock"
Rosemary f12 (talk | contribs) (→Introduction & Features) |
Rosemary f12 (talk | contribs) (→Schedule) |
||
| Line 57: | Line 57: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| + | * UART 1 Driver | ||
* Wifly driver | * Wifly driver | ||
* Android app UI | * Android app UI | ||
| Line 72: | Line 73: | ||
<td> | <td> | ||
* Android to LPC2148 communication | * Android to LPC2148 communication | ||
| + | * Automate default WiFly network connection | ||
| + | * Start Web server | ||
* Update Wiki | * Update Wiki | ||
</td> | </td> | ||
| Line 84: | Line 87: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * Construct door lock mechanism | + | * Construct door lock mechanism circuit |
| + | * Write driver for GPIO to enable and disable lock | ||
| + | * Continue with Web Server | ||
* Update Wiki | * Update Wiki | ||
</td> | </td> | ||
| Line 97: | Line 102: | ||
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | * Web Server | + | * Enable MP3 to play when door is opened. |
| − | * | + | * Continue with Web Server |
| + | * Update Wiki | ||
| + | </td> | ||
| + | <td> | ||
| + | Done | ||
| + | </td> | ||
| + | </tr> | ||
| + | |||
| + | <tr> | ||
| + | <td> <center> | ||
| + | December 7, 2012 | ||
| + | </center> </td> | ||
| + | <td> | ||
| + | * Write Real Time Clock Driver | ||
| + | * Create a task for time stamp logging | ||
| + | * Construct box to contain messy wires and modules | ||
| + | * Write task for count down door unlock | ||
* Update Wiki | * Update Wiki | ||
</td> | </td> | ||
| Line 105: | Line 126: | ||
</td> | </td> | ||
</tr> | </tr> | ||
| + | |||
<tr> | <tr> | ||
<td> <center> | <td> <center> | ||
| − | December | + | December 14, 2012 |
</center> </td> | </center> </td> | ||
<td> | <td> | ||
| − | |||
* Testing | * Testing | ||
* Fix bugs | * Fix bugs | ||
| Line 120: | Line 141: | ||
</td> | </td> | ||
</tr> | </tr> | ||
| + | |||
<p>Cost of shipping and handling excluded</p> | <p>Cost of shipping and handling excluded</p> | ||
Revision as of 02:12, 10 December 2012
Contents
Android Door Lock
Abstract
Using a Wifi connection, our door lock can be locked and unlocked remotely with an Android device.
Introduction & Features
- UART communication between RN-XV WiFly Module and LPC2148 Microcontroller.
- Andriod application that enables wireless door access.
- WiFly module for wireless communication between Android and LPC2148 Microcontroller.
- TCP communication running on LPC2148 handling requests from the Android application.
- Web server to handle user permission, to set door codes, and to view time stamps of when the door was accessed.
- MP3 player that allows customizable tunes to play when the door is unlocked.
- Filing system that stores all the log times that the door has been accessed.
- Electronic door strike that unlocks when door code is recognized.
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
Team Members & Responsibilities
- Rosemary Chen
- Created the UART1 driver that enables communication between the wireless module and the micro controller.
- Created the Real Time Clock driver used for logging the time that users access the door.
- Created the user interface for setting and configuring the wifly module as well as automating the default settings for network connection.
- Created a task for
- Correct password detection
- Enabling the lock when password is detected
- Logging the time when the door is accessed
- Playing a tune when the door is unlocked.
- Cindy Li
- Created the web server that allows the host to track door users, enable or disable users, and sets the door code.
- Hai Wang
- Create a TCP client Android application that allows connectivity between the wireless module (server) and the Android application (client). The application is responsible for sending the correct door code to the server in order for the door to unlock.
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week Number | Scheduled Items | Actual |
|---|---|---|
| November 2, 2012 |
|
Done |
| November 9, 2012 |
|
Done |
| November 16, 2012 |
|
Done |
| November 23, 2012 |
|
Done |
| November 30, 2012 |
|
Done |
| December 7, 2012 |
|
In progress |
| December 14, 2012 |
|
In progress |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Parts | Cost |
|---|---|
|
Nexus 7 Android Tablet |
$249.00 |
|
RN-XV WiFly Module |
$34.95 |
|
Electric Door Strike |
$12.00 |
|
LPC2148 Microcontroller |
$60.00 |
**Cost excludes shipping and handling
Design & Implementation
The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.
Hardware Design
Discuss your hardware design here. Show detailed schematics, and the interface here.
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
Implementation
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
Wifi Connection Issues
Many wifi connection issues were encountered. To solve this problem, a dedicated task was created to re-connect to wifi if the connection was ever lost.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
Send me your zipped source code and I will upload this to SourceForge and link it for you.
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
- Android Developers Website: http://developer.android.com/index.html
- RN-XV Wireless Module User Manual: http://dlnmh9ip6v2uc.cloudfront.net/datasheets/Wireless/WiFi/WiFly-RN-XV-DS.pdf
- TO-98 : http://www.classiccmp.org/rtellason/transdata/2n3858.pdf
Appendix
You can list the references you used.
