Difference between revisions of "S18: M.E.O.W"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 38: Line 38:
 
|-
 
|-
 
! scope="col"| Week#
 
! scope="col"| Week#
−
! scope="col"| Start Week
+
! scope="col"| Date
 
! scope="col"| Task
 
! scope="col"| Task
 
! scope="col"| Status
 
! scope="col"| Status
−
! scope="col"| Actual Completion Date
 
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
|4/14/2018
+
| 03/04
−
|PCB Design and Feature definition
+
|
−
|Completed
+
* Research hardware and software, plan steps.
−
|4/20/2018
+
* Team Building and Ideas.
 +
|  
 +
* Decided what the project will entail and the approach.
 +
* Team member tasks are given.
 
|-
 
|-
 
! scope="row"| 2
 
! scope="row"| 2
−
|4/23/2018
+
| 03/11
−
|HW bench protoyping
+
|  
−
|Ongoing
+
* Team Research.
−
|N/A
+
|  
 +
* Individual Research on the subject. Meow Week.
 
|-
 
|-
 
! scope="row"| 3
 
! scope="row"| 3
−
|4/30/2018
+
| 03/18
−
|Lower Power protoyping
+
|  
−
|Not started
+
* Give specific tasks to team members.
−
|N/A
+
* PCB Design.
 +
* Finalize the project idea.
 +
|  
 +
* Divided the project into different sections.
 +
* Assigned roles and responsibilities to each member.
 +
* Initial PCB design is done in Eagle.
 
|-
 
|-
 
! scope="row"| 4
 
! scope="row"| 4
−
|5/7/2018
+
| 03/25
−
|SW Ready for integration and system testing
+
|  
−
|Not Started
+
* To finalize PCB, and order components.
−
|N/A
+
|  
 +
* Ordered Components, PCB was sent for printing.
 
|-
 
|-
 
! scope="row"| 5
 
! scope="row"| 5
−
|5/7/2018
+
| 04/01
−
|Alpha prototype ready
+
|  
−
|Not Started
+
* Power mode research(different team members different areas).
−
|N/A
+
* Solder PCB components and test.
 +
* Modify the architecture and flow of project if necessary.
 +
|  
 +
* Individual research on power modes initialized.
 +
* Finished Soldering components on the PCB.
 +
* Architecture and flow of project modified and implemented.
 
|-
 
|-
 
! scope="row"| 6
 
! scope="row"| 6
−
|5/14/2018
+
| 04/08
−
|FInal product ready for demo
+
|
−
|Not Started
+
* Test and Implement the PIR motion sensors and connections.
−
|N/A
+
* Establish connections between the LPC and Beaglebone.
 +
|
 +
* PIR sensor test and implementation done.
 +
* Interrupt and connections between the two microcontroller boards are done.
 +
|-
 +
! scope="row"| 7
 +
| 04/15
 +
|
 +
* Test all the lower level components.
 +
* implement the sleep mode and power down modes.
 +
|  
 +
* Tested the lower level sensors and the power source (PCB and Lipo Battery).
 +
* Tested and implemented one of the power down modes.
 +
|-
 +
! scope="row"| 8
 +
| 04/22
 +
|
 +
* Prototype of the shell of the project.
 +
* write and further test implementation of low power modes.
 +
|
 +
* 3d rendering of the prototype done. yet to be printed.
 +
* further research and implementation of power modes done. More research needed.
 +
|-
 +
! scope="row"| 9
 +
| 04/29
 +
|
 +
* Rob Went to Napa Valley.
 +
 
 +
|
 +
* Rob drank wine.
 +
|-
 +
! scope="row"| 10
 +
| 05/06
 +
|
 +
* Get the Camera and the overall system done.
 +
* Bitcoin will hit 10000.
 +
* Test the power consumption of each
 +
|
 +
 
 +
|-
 +
! scope="row"| 11
 +
| 05/13
 +
|
 +
* MEOW @ PREET
 +
|
  
 +
|-
 
|}
 
|}
  

Revision as of 09:02, 1 May 2018

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.


Microcontroller Energy Observation Widget (M.E.O.W)

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

  • R "Meow Meow" Nikfar
    • Team Lead, PCB Design, Sensor Design and Implementation, Hardware Testing, Power Analysis, Sleep-Mode Firmware
  • Ahsan "Whiskers" Uddin
    • BeagleBone Testing, Video Capture Implementation, Storage, Sleep-Mode Research
  • Nelson "fluffy" Wong
    • Deep Power Modes, Power Analysis, Communications
  • Britto "Kitty Kat" Thomas
    • CAN BUS Low Power Research, Power Analysis
  • Sai Kiran "Mittens" Rachamadugu
    • Testing, Board Communications, User Interface

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 Task Status
1 03/04
  • Research hardware and software, plan steps.
  • Team Building and Ideas.
  • Decided what the project will entail and the approach.
  • Team member tasks are given.
2 03/11
  • Team Research.
  • Individual Research on the subject. Meow Week.
3 03/18
  • Give specific tasks to team members.
  • PCB Design.
  • Finalize the project idea.
  • Divided the project into different sections.
  • Assigned roles and responsibilities to each member.
  • Initial PCB design is done in Eagle.
4 03/25
  • To finalize PCB, and order components.
  • Ordered Components, PCB was sent for printing.
5 04/01
  • Power mode research(different team members different areas).
  • Solder PCB components and test.
  • Modify the architecture and flow of project if necessary.
  • Individual research on power modes initialized.
  • Finished Soldering components on the PCB.
  • Architecture and flow of project modified and implemented.
6 04/08
  • Test and Implement the PIR motion sensors and connections.
  • Establish connections between the LPC and Beaglebone.
  • PIR sensor test and implementation done.
  • Interrupt and connections between the two microcontroller boards are done.
7 04/15
  • Test all the lower level components.
  • implement the sleep mode and power down modes.
  • Tested the lower level sensors and the power source (PCB and Lipo Battery).
  • Tested and implemented one of the power down modes.
8 04/22
  • Prototype of the shell of the project.
  • write and further test implementation of low power modes.
  • 3d rendering of the prototype done. yet to be printed.
  • further research and implementation of power modes done. More research needed.
9 04/29
  • Rob Went to Napa Valley.
  • Rob drank wine.
10 05/06
  • Get the Camera and the overall system done.
  • Bitcoin will hit 10000.
  • Test the power consumption of each
11 05/13
  • MEOW @ PREET

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.

Low-Level Hardware

The low-level design starts from the PIR Motion Sensors and ends with the storage of the video data. The LPC1758 plays a big role in the communication of the overall system. The PIR sensors are each connected to the LPC1758 using a GPIO protocol and send signals if an object or and person is within their range. Once the signal is sent from the Sensors, the LPC wakes up and consumes power from the PCB which either uses the power from a plugged source or the backup LIPO battery. LPC then sends the right information to the BeagleBone board using UART protocol.

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:

<Bug/issue name>

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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=S18:_M.E.O.W&oldid=44567"