Difference between revisions of "S15: Automated Meeting Room Reservation"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Schedule)
Line 51: Line 51:
 
| Identify hardware requirement, Order parts, Researching about datasheets
 
| Identify hardware requirement, Order parts, Researching about datasheets
 
| Complete
 
| Complete
|
 
 
|-
 
|-
 
! scope="row"| 2
 
! scope="row"| 2
Line 59: Line 58:
 
| Interfacing the hardware, Developing an Algorithm
 
| Interfacing the hardware, Developing an Algorithm
 
| In Progress
 
| In Progress
|
 
 
|-
 
|-
 
! scope="row"| 3
 
! scope="row"| 3
Line 67: Line 65:
 
| Test the motion sensors, Configuring and testing  Nordic communication
 
| Test the motion sensors, Configuring and testing  Nordic communication
 
|  
 
|  
|
 
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
Line 75: Line 72:
 
| Integrating Nordic and motion sensors and testing the entire setup.
 
| Integrating Nordic and motion sensors and testing the entire setup.
 
|  
 
|  
|
 
 
|-
 
|-
 
! scope="row"| 5
 
! scope="row"| 5
Line 83: Line 79:
 
| Writing the project report and updating the wiki page accordingly.
 
| Writing the project report and updating the wiki page accordingly.
 
|  
 
|  
|
 
 
|-
 
|-
 
! scope="row"| 6
 
! scope="row"| 6

Revision as of 01:37, 15 April 2015

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

Automated Meeting Room Reservation

Abstract

To implement a wireless automated meeting room reservation system using Nordic Wireless modules and SJONE boards. Each SJOne board will communicate with a central Board to convey the status of meeting room in use through.

Objectives & Introduction

The automated meeting room reservation is achieved through the built-in Nordic Wireless interface. Each board acts as a node in the mesh network which sends and receives information and communicates with a central node. The following objectives are to be implemented:

  • Auto detection of room use
  • Shortest Path routes
  • Address nodes with auto-replies
  • Track the rooms in use at the central server.

Team Members & Responsibilities

1. Sumeet Bhagwat

2. Ajinkya Khasnis

3. Atresh Gummadavelly

4. Sujay Kulkarni

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# Date Start End Task Actual
1 4/13 Apr 7, 2015 Apr 14, 2015 Identify hardware requirement, Order parts, Researching about datasheets Complete
2 4/13 Apr 14, 2015 Apr 21, 2015 Interfacing the hardware, Developing an Algorithm In Progress
3 4/13 Apr 21, 2015 Apr 28, 2015 Test the motion sensors, Configuring and testing Nordic communication
4 4/13 May 5, 2015 Apr 28, 2015 Integrating Nordic and motion sensors and testing the entire setup.
5 4/13 May 5, 2015 May 12,2015 Writing the project report and updating the wiki page accordingly.
6 4/13 May 22, 2015 May 22, 2015 Project Demo.

Parts List & Cost

Item Price Quantity Price
SJ One Board $80 4 $320


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:

My Issue #1

Discuss the issue and resolution.

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

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.