S13: Door Alarm System
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Door Alarm System
Abstract
This section should be a couple lines to describe what your project does.
Our project is a alarm system that will allow the user to lock/unlock a door simply by sending a text message. An RFID module will also be implemented as an alternative to opening the door. The user can receive a text message or phone call from the system about the current status of the door. The purpose for this project is to improve security as well as allowing easier access for people who are tired of using the traditional key.
Objectives & Introduction
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.
- System will lock or unlock base on the message sent by the user
- If door scans an RFID tag
- Tags with correct code will have access
- System will send text message that a correct tag has been scanned.
- System will have function to call user's phone
Team Members & Responsibilities
Thanh Huynh
- Design and creating FreeRTOS task for:
- Communication with GSM
- Sending and reciveing SMS message
- Making phone call
- Reading RFID tags
- Processing information and passing it to GSM
- Interfacing with servo
- Interfacing with LCD
- Communication with GSM
Phi Le
- Drivers Development for:
- Both UART2 and UART3 driver
- Pulse width modulation (PWM)
- Interfacing servo to board
- Hardware construction of system
- Assisted and gave input in trouble shooting
Schedule
| Week Number | Planned Tasks | Actual Tasks |
|---|---|---|
| Week 1
|
|
|
| Week 2
|
|
|
| Week 3
|
|
|
| Week 4
|
|
|
| Week 5
|
|
|
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 |
|---|---|
| 2012 SJ One Board | $40 |
| RFID Complete Kit | $50 |
| Jumper Wires | $6 |
| SD Card 16gb | $10 |
| NewHaven LCD | $25 |
| GSM/GPS Module V3 | $89 |
| Piezo Buzzer | $1 |
| Servo | $15 |
| Total: | $236 |
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:
- Could not establish serial communication with GSM module v3
- GSM jumpers need to be in correct location. The following switch configuration needs to be established on the board in order to send or receive AT commands. Switch 1: USB, Switch 2: Comm, Switch 3: GSM.
- Uart is is not working properly, sometimes it work and sometimes is does not.
- All ground wires need to be connected together in order to establish a common GROUND.
- GSM module is not sending back any acknowledgement signal or is not processing any AT command that I am sending to it.
- A newline character 'r' is required after most AT command sent to GSM.
- Sometime a delay is required before the next AT command can be sent.
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
List any references used in project.
- DFROBOT's Wiki:http://www.dfrobot.com/wiki/index.php/GPS/GPRS/GSM_Module_V3.0_(SKU:TEL0051)
- SIM908 AT Command Manual_V1.01
- RFID ID-12 Data sheet
Appendix
You can list the references you used.
