Difference between revisions of "F16: I2Coffee"
(→Hardware Design) |
(→Hardware Interface) |
||
| Line 108: | Line 108: | ||
=== Hardware Interface === | === 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. | + | 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. |
| + | |||
| + | The coffee making machine uses I2C protocol to establish communication between a master and slave board. The slave SJSUOne board is also used to control the different I/O connections used in this project. | ||
| + | |||
| + | <b>Hardware Used</b> | ||
| + | <ul> | ||
| + | <li>Transistor</li> | ||
| + | <li>Resistors</li> | ||
| + | <li>5v DC Motor</li> | ||
| + | <li>5v Step Motor</li> | ||
| + | </ul> | ||
=== Software Design === | === Software Design === | ||
Revision as of 03:32, 20 December 2016
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.
==I2Coffee ==
Abstract
i2Coffee is a coffee maker machine that allows its user to pick from different types of coffee powders. i2Coffee will also allow the user to choose their ideal coffee temperature.
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
- Man Hin Wong
- Emil: wongmanhin@msn.com
- Mauricio Rivera
- Email: mauricio.rivera1993@yahoo.com
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 | Actual |
|---|---|---|---|
| 1 | 11/4 | Finalize schedule and materials. | Done |
| 2 | 11/11 | Design schematic with slave and master board. | Done |
| 3 | 11/18 | Test I2C code and enhance it. | Pending. |
| 4 | 11/25 | Debug and enhance code. | Done |
| 5 | 12/2 | Start building project. | Done |
| 6 | 12/9 | Test prototype. | Pending. |
| 7 | 12/16 | Finalize project and demo. | Pending. |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Item | Quantity | Cost (1) |
|---|---|---|
| SJSU One Board | 2 | $60 |
| 5V DC Motors | 4 | $2 |
| 5V Servos | 3 | $3 |
| Shoe Box | 1 |
Design & Implementation
Hardware Design
Block diagram
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.
The coffee making machine uses I2C protocol to establish communication between a master and slave board. The slave SJSUOne board is also used to control the different I/O connections used in this project.
Hardware Used
- Transistor
- Resistors
- 5v DC Motor
- 5v Step Motor
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.
