Difference between revisions of "S13: Door Alarm System"

From Embedded Systems Learning Academy
Jump to: navigation, search
Line 27: Line 27:
 
== Schedule ==
 
== Schedule ==
 
<table class="wikitable">
 
<table class="wikitable">
<th>Week Number</th> <th>Planned Items</th> <th>Actual Items</th>
+
<th>Week Number</th> <th>Planned Tasks</th> <th>Actual Tasks</th>
  
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
Week 1: Design
+
Week 1:  
 
<BR/>(April 5)
 
<BR/>(April 5)
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
* Order Parts
+
* Order RFID reader & tags
 +
* Order GSM Module
 
* Go over the project
 
* Go over the project
 
</td>
 
</td>
 
<td>
 
<td>
* Ordered parts
+
* Received RFID parts
* Designed proximity sensor placement
+
* Waiting for GSM module
* Designed obstacle avoidance algorithm
 
* Designed move to destination GPS algorithm
 
 
</td>
 
</td>
  
Line 49: Line 48:
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
Week 2: Construction
+
Week 2:
<BR/>(November 5)
+
<BR/>(April 12)
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
* Upgrade leading car with microcontroller, XBee, GPS, <BR/> and a battery pack
+
* Get RIFD to interface with UART
* Upgrade following car with microcontroller, XBee, GPS, <BR/> compass, proximity sensors, motor controllers, and a <BR/> battery pack
 
* Read GPS coordinate from GPS module
 
 
</td>
 
</td>
 
<td>
 
<td>
* Tested proximity sensors
+
* Pending
* Finished ADC and PWM drivers
 
* Paired XBee modules
 
* Read GPS coordinates and computed required bearing and <BR/>distance to travel to destination
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 67: Line 61:
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
Week 3: Drivers
+
Week 3:  
<BR/>(November 12)
+
<BR/>(April 19)
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
* Read direction from compass
+
* Learn AT commands
* Enable car driving capabilities / motor controllers
+
* Get GSM Module to work
* Send / receive data using XBee modules
 
 
</td>
 
</td>
 
<td>
 
<td>
* Motors controllers fully interfaced
+
* Pending
* Mounted proximity sensors, motor controllers, microcontroller, and GPS
 
* Created upgrade module for leading car
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 84: Line 75:
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
Week 4: Coding
+
Week 4:  
<BR/>(November 19)
+
<BR/>(April 26)
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
* Code obstacle avoidance
+
* Construct alarm system
 +
* Interface devices
 
</td>
 
</td>
 
<td>
 
<td>
* Tested obstacle avoidance
+
* Pending
* Sent GPS data from leading car to following car
 
* Swapped to non-tilt compensated compass
 
* Mounted compass
 
* Restructure and reorganize code
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 101: Line 89:
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
Week 5: Coding
+
Week 5:
<BR/>(November 26)
+
<BR/>(May 3)
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
* Code moving toward GPS coordinate
+
* Write PWM driver for door Lock
 +
* Create task with FreeRTOS
 
</td>
 
</td>
 
<td>
 
<td>
* Tested obstacle avoidance
+
* Pending
* Swapped a proximity sensor to unify sensors
 
* Swapped to less power hungry motor controllers
 
* New motor controllers fully interfaced
 
* Upgraded to use 5xAA battery pack
 
* Rewired parts with finalized placement
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 119: Line 103:
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
Week 6: Testing
+
Week 6:  
<BR/>(December 3)
+
<BR/>(May 10)
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
* Testing
+
* Testing and Fix bugs
 +
* Write Report
 
</td>
 
</td>
 
<td>
 
<td>
* Tested obstacle avoidance
+
* Pending
* Tested move to GPS coordinate
 
 
</td>
 
</td>
 
</tr>
 
</tr>
Line 133: Line 117:
 
<tr>
 
<tr>
 
<td> <center>
 
<td> <center>
Week 7: Finalization
+
Week 7:  
<BR/>(December 10)
+
<BR/>(May 24)
 
</center> </td>
 
</center> </td>
 
<td>
 
<td>
Line 141: Line 125:
 
</td>
 
</td>
 
<td>
 
<td>
* Tested move to GPS coordinate
+
* Pending
 
</td>
 
</td>
 
</tr>
 
</tr>

Revision as of 05:15, 12 April 2013

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.

Project Title

Abstract

This section should be a couple lines to describe what your project does.

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.

Team Members & Responsibilities

  • Team Member 1
    • Driver Development
  • Team Member 2
    • FreeRTOS Software Design

Schedule

Week Number Planned Tasks Actual Tasks

Week 1:
(April 5)

  • Order RFID reader & tags
  • Order GSM Module
  • Go over the project
  • Received RFID parts
  • Waiting for GSM module

Week 2:
(April 12)

  • Get RIFD to interface with UART
  • Pending

Week 3:
(April 19)

  • Learn AT commands
  • Get GSM Module to work
  • Pending

Week 4:
(April 26)

  • Construct alarm system
  • Interface devices
  • Pending

Week 5:
(May 3)

  • Write PWM driver for door Lock
  • Create task with FreeRTOS
  • Pending

Week 6:
(May 10)

  • Testing and Fix bugs
  • Write Report
  • Pending

Week 7:
(May 24)

  • Make final changes for demo
  • Finalize content in Wiki article
  • Pending

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

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

List any references used in project.

Appendix

You can list the references you used.